installpkg messing up perms
in [Slackware]
|
From: Dario Niedermann on 12 Jul 2010 15:53 Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote: > Dario Niedermann wrote: > >> Anyway - as you and Henrik stated - installpkg is actually tampering >> with system directories, ... > > That isn't at all what Mike and Henrik stated. Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote [emphasis added to facilitate reading comprehension]: | PACKAGES containing a directory WILL SET THE PERMISSION of that | directory to the permissions it has in the package. Also, all packages | must of course contain THE / DIRECTORY. Mike Jones <luck(a)dasteem.invalid> wrote [emphasis added to facilitate reading comprehension]: | This also means that running SlackBuild scripts and other things that | (RE)GENERATE SYSTEM DIRS WILL SET THEM within the user's umask and not | root's. > If you're installing self-made packages Dario Niedermann <M8R-cthw2f(a)spamherelots.com> wrote [emphasis added to facilitate reading comprehension]: | '/' set to 700 after installing a SLACKBUILD. -- > head -n1 /etc/*-{version,release} && uname -moprs Slackware 12.2.0 Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
From: Sylvain Robitaille on 12 Jul 2010 16:32 Dario Niedermann wrote: >> That isn't at all what Mike and Henrik stated. > > Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote [emphasis added > to facilitate reading comprehension]: .... and yet you still don't seem to get it ... >| PACKAGES containing a directory WILL SET THE PERMISSION of that >| directory to the permissions it has in the package. ... That's not saying that "installpkg is tampering with permissions" is it? > Mike Jones <luck(a)dasteem.invalid> wrote [emphasis added to facilitate > reading comprehension]: .... and yet you still don't seem to get it ... >| This also means that running SlackBuild scripts and other things that >| (RE)GENERATE SYSTEM DIRS WILL SET THEM within the user's umask and not >| root's. That's not saying that "installpkg is tampering with permissions" is it? >> If you're installing self-made packages > > Dario Niedermann <M8R-cthw2f(a)spamherelots.com> wrote [emphasis added > to facilitate reading comprehension]: .... oh, I think I see now where the comprehension "issues" are occurring .... >| '/' set to 700 after installing a SLACKBUILD. One does not "install" a SlackBuild. A SlackBuild is a script that one runs to build a package, then one installs the resulting package. As I said, you're barking up the wrong tree. Fix your SlackBuild script to leave the resulting package with the correct permissions, and all will be well. In fact, it seems to me that this is what Henrik and Mike also stated, though in different words ... Care to have another go? -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: William Hunt on 12 Jul 2010 21:20 On Mon, 12 Jul 2010, Sylvain Robitaille wrote: > Dario Niedermann wrote: > >> That isn't at all what Mike and Henrik stated. [...] > > One does not "install" a SlackBuild. A SlackBuild is a script that one > runs to build a package, then one installs the resulting package. > > As I said, you're barking up the wrong tree. Fix your SlackBuild script > to leave the resulting package with the correct permissions, and all > will be well. In fact, it seems to me that this is what Henrik and Mike > also stated, though in different words ... > > Care to have another go? I'd also suggest the OP use tar, with the '-tv' switches, to look at the index of a standard Slackware package (or two) and compare it against the index of his home-built package. Look for differences between the two in the way permissions are set within each package (tar file). HTH -- William Hunt, Portland Oregon USA
From: Dario Niedermann on 13 Jul 2010 07:09 William Hunt <wjh(a)prv8.net> wrote: > I'd also suggest the OP use tar, with the '-tv' switches, > to look at the index of a standard Slackware package (or two) > and compare it against the index of his home-built package. > Look for differences between the two in the way permissions > are set within each package (tar file). I'm not installing self-made packages: the problems I described came from packages made by Slackbuilds downloaded from slackbuilds.org. -- > head -n1 /etc/*-{version,release} && uname -moprs Slackware 12.2.0 Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
From: Grant on 13 Jul 2010 08:37
On Tue, 13 Jul 2010 13:09:48 +0200, Dario Niedermann <M8R-cthw2f(a)spamherelots.com> wrote: >William Hunt <wjh(a)prv8.net> wrote: > >> I'd also suggest the OP use tar, with the '-tv' switches, >> to look at the index of a standard Slackware package (or two) >> and compare it against the index of his home-built package. >> Look for differences between the two in the way permissions >> are set within each package (tar file). > >I'm not installing self-made packages: the problems I described came >from packages made by Slackbuilds downloaded from slackbuilds.org. SlackBuilds do not carry packages last I looked. A SlackBuild script allows you to make a package, following the instructions, as root. On a root account, no su madness, a proper root login. Me? I prefer to build from source, and install extras to the /usr/local tree, but each to 'is own ;) Grant. |