var x, y;
img = getImage("placeholder");
x = getImagePageLeft(img);
y = getImagePageTop(img);
All your woody are (not quite, but very very very soon) belong to us.
There are currently, 43 guest(s) and 3 member(s) that are online.
You are Anonymous user. You can register for free by clicking here.
Is /usr/sbin really the proper place for traceroute? Posted on Thursday, June 14 @ 15:20:24 BST
Once again the debate on moving some useful software from
/usr/sbin to /usr/bin, and once again the same arguments come
up. Whether to allow some breakage and move the software that
users mostly use from /usr/sbin to /usr/bin.
Interesting enough, there are a few programs in /usr/sbin
that get invoked almost daily by a normal user, and still they
are kept in /usr/sbin. One of these programs is traceroute
which brought up the discussion this time, this time it was the
maintainer of traceroute-nanog that wanted to know the general
opinion, and as before failed to get a clear view of users
4.10 /usr/sbin: Non-essential standard system binaries
This directory contains any non-essential binaries used exclusively by
the system administrator. System administration programs that are
required for system repair, system recovery, mounting /usr, or other
essential functions must be placed in /sbin instead.
The biggest point for against are:
traceroute must stay in /usr/sbin because moving it will
break local scripts that depend on it being exactly where it
has been for the last 5+ years.
To adhere to FHS, almost everything in /sbin,/usr/sbin
will have to be moved out: ifconfig, sendmail, route,
Any single good reasons were not mentioned, although it
makes perfect sense (at least to me) to move the file from sbin
to bin. I think this comment covers pretty much of
The useful purpose is fixing a FHS non-compliance bug. Or the
purpose is making the system more usable for users.
The fact that other packages have had to exhibit breakage to
"work around" this packages breakage, is hardly a glowing
recommendation to keep things broken.
-- Vince Mulhollon
Personally i feel that suggesting things like adding
/usr/sbin to your $PATH is kind of weird answer coming from
people who try to make everything work like they are supposed
to. Adding sbin to path is not a solution it's a workaround for
an OLD bug. Personally i don't like workarounds if the original
bug can be fixed, why not fix it and get the long term gain