installpkg messing up perms
in [Slackware]
|
From: Mike Jones on 13 Jul 2010 17:13 Responding to Sylvain Robitaille: > Grant wrote: > >> ... A SlackBuild script allows you to make a package, ... as root. >> >> On a root account, no su madness, a proper root login. > > This all suggests, however, that perhaps the scripts at Slackbuilds.org > don't explicitly set a umask, and I would argue that this is an > oversight that should be corrected. There's no reason anyone should > have to *login* as root, rather than simply use su or sudo, to get the > expected result. More importantly, there's no reason that a root > environment should be predictable. The scripts should explicitly set > whatever environment they expect to have. Hmmm. Good point. If dir trees are to be "updated", then umask settings would seem to be in order as a sanity check. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 13 Jul 2010 17:17 Responding to Robby Workman: > On 2010-07-13, 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. >> >> > > Leave root's umask at 0022, and/or switch to root properly from your > user account, and/or manually set umask to 0022 before using one of the > build scripts. This is NOT a problem with the scripts, or is it a > problem with pkgtools. > > -RW Pretty much the default wisdoms on this one. I barfed a few things myself until I discovered my "su" (with no dash) SNAFU and updated my .bashrc accordingly. root="su -" -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Dario Niedermann on 13 Jul 2010 17:17 Robby Workman <newsgroups(a)rlworkman.net> wrote: > switch to root properly from your user account What do you mean "properly"? Su and sudo are not "proper"? Who said that? The pkgtools development team? The slackbuilds.org crew? > This is NOT a problem with the scripts, > or is it a problem with pkgtools. Of course! God forbid! Gee, I swear this is the most arrogant and self-righteous community I've ever seen, bar none. -- > head -n1 /etc/*-{version,release} && uname -moprs Slackware 12.2.0 Linux 2.6.27.31-smp i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
From: Dario Niedermann on 13 Jul 2010 18:40 Dan C <youmustbejoking(a)lan.invalid> wrote: > <village idiot's bullshit snipped> *PLONK*
From: Grant on 13 Jul 2010 19:59
On Tue, 13 Jul 2010 19:57:40 +0200, Dario Niedermann <M8R-cthw2f(a)spamherelots.com> wrote: >Joost Kremers <joostkremers(a)yahoo.com> wrote: > >> as others have pointed out already, the issue is *not* related to >> installpkg. the issue is with the permissions set in the package >> itself. > >The issue is that installpkg isn't smart enough to prevent a defective >package from screwing up the filesystem. Did you miss the bit about installpkg being a simple shell script? You're arguing with a bunch of people using slackware for years, saying that their distro's basic installer script is broken. If it is so broken don't you think we'd have noticed by now? Slackware has some quaint notions, covering for user mistakes is not one of them ;) Didn't you know, unix-like OS give the user enough rope to shoot themself in the foot? Grant. |