Behdad Esfahbod wrote:
On Wed, 2008-04-23 at 14:59 -0500, Chris Adams wrote:
Once upon a time, Matthew Miller <mattdm@xxxxxxxxxx> said:
And I think we could solve 99.9% of the annoyance by addressing ifconfig,
fdisk, lsmod, route, and the other small handful of programs mentioned in
this thread. Like I said, it worked for traceroute back in 2003. :)
Again, here's my personal list-at-a-glance of things to look at:
bind:
/usr/sbin/rndc
chkconfig:
/sbin/chkconfig
freeipmi:
/usr/sbin/ipmiconsole
/usr/sbin/ipmipower
hardlink:
/usr/sbin/hardlink
iproute:
/sbin/ip
module-init-tools:
/sbin/lsmod
/sbin/modinfo
net-tools:
/sbin/arp
/sbin/ifconfig
/sbin/route
ntp:
/usr/sbin/ntpq
pciutils:
/sbin/lspci
usbutils:
/sbin/lsusb
wireless-tools:
/sbin/iwconfig
/sbin/iwlist
That's 16 commands from 11 packages. Yes, there are a few more, but not
all that many. How hard would is be to just fix these (either symlink
or just move to /bin or /usr/bin as appropriate)?
How could you leave /sbin/pidof out? Oh why, really, why is pidof
in /sbin in the first place? sigh...
Because pidof is considered a helper application for init and init
scripts (indeed, it is packaged as part of sysvinit). Its not really
considered a tool for interactive use. (not that I agree).
--CJD
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
