On Saturday 12 December 2009 04:32:19 Bruce Dubbs wrote:
> It's trivial for any user to adjust PATH to search /sbin and /usr/sbin.
I always link /usr to . and /sbin to bin when building LFS
signature.asc
Description: This is a digitally signed message part.
--
http://linuxfromscratch.org/mailma
>> I do. And I do install psmisc. I'm just thinking how important
>> it is? Debian considers it optional (it is misc after all) and
>> installs to /usr/bin and Slackware builds both killall and fuser
>> in procps.
>
> Oh, so both of those are available there? Are they more or less
> compatible w
On Fri, 2009-12-11 at 11:14 +0100, Alexander Kozlov wrote:
> I do. And I do install psmisc. I'm just thinking how important it
> is? Debian considers it optional (it is misc after all) and
> installs to /usr/bin and Slackware builds both killall and fuser in
> procps.
Oh, so both of those are a
Bruce Dubbs wrote:
> Mike McCarty wrote:
>> If you think that, then it would be reasonable to put it into
>> /bin.
>
> Actually, /bin is for files needed by root when /usr is not mounted and
> also needed by regular users when /usr is mounted.
Yes. That's why I responded the way I did. I don't t
Mike McCarty wrote:
> Bruce Dubbs wrote:
>> Mike McCarty wrote:
>>
>>> I'd use /sbin for things like automount, fsck, fdisk, killall, etc.
>> Regular users can use killall for their own processes, fdisk and fsck
>> for floppies or usb devices, etc. The protection is in the devices and
>> proces
Bruce Dubbs wrote:
> Mike McCarty wrote:
>
>> I'd use /sbin for things like automount, fsck, fdisk, killall, etc.
>
> Regular users can use killall for their own processes, fdisk and fsck
> for floppies or usb devices, etc. The protection is in the devices and
> processes, not the executables
Mike McCarty wrote:
> I'd use /sbin for things like automount, fsck, fdisk, killall, etc.
Regular users can use killall for their own processes, fdisk and fsck
for floppies or usb devices, etc. The protection is in the devices and
processes, not the executables.
-- Bruce
--
http://linux
> Slackware builds both killall and fuser in procps.
hmm.. apparently from the same psmisc-*.tar.gz source as LFS does.
Sorry for the noise, I seem to stay with psmisc.
Question about `dirname $(which killall)` is still valid though.
Alex.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-sup
>> Another question, who needs psmisc? Slackware does not use them,
>> neither lfs-bootscripts.
>
> You don't use killall or fuser?
>
> Simon.
I do. And I do install psmisc. I'm just thinking how important it
is? Debian considers it optional (it is misc after all) and
installs to /usr/bin and Sl
Alexander Kozlov wrote:
>>> psmisc 22.8 configured with --prefix=/usr installs killall to
>>> /usr/bin.
>>>
>>> No problem to leave it there, as debian does, but I move it to
>>> /bin to keep my old init scripts unchanged. Anyway, the command
>>> "ln -sv killall /bin/pidof" in Sec. 6.52 should be
On Fri, 2009-12-11 at 08:59 +0100, Alexander Kozlov wrote:
> Another question, who needs psmisc? Slackware does not use them,
> neither lfs-bootscripts.
You don't use killall or fuser?
Simon.
signature.asc
Description: This is a digitally signed message part
--
http://linuxfromscratch.org/mai
>> psmisc 22.8 configured with --prefix=/usr installs killall to
>> /usr/bin.
>>
>> No problem to leave it there, as debian does, but I move it to
>> /bin to keep my old init scripts unchanged. Anyway, the command
>> "ln -sv killall /bin/pidof" in Sec. 6.52 should be corrected.
>
> if this is wro
12 matches
Mail list logo
