Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
have you tried "locate"? Type "updatedb" then "locate mke2fs" It should be under /sbin. So you can run it as root by typing "./sbin/mke2fs" or switching to /sbin and typing "./mke2fs"
Ubien (et al) thank you. I was able to run the command ./mke2fs /dev/fd0 from within sbin. (I'll have to remember that)
Unfortunately, the command has not helped me trouble shoot my floppy access problem as suggested by another linux friend. It just sits there--the command that is.
I'll return to the hardware forum to pursue this further.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
Quote:
Originally posted by KnightAbel /sbin is not in the Red Hat path by default... I learned that after many hours of hitting my head against the keyboard.
It is not in the user path, but is definitely in root's path. Make sure you login as root or 'su -' to root instead of a plain 'su'. Almost all binaries in /sbin and /usr/sbin are written for execution by the superuser. Although there are 'harmless' binaries like /sbin/lsmod that can be run properly by a normal user. If Redhat started including /sbin and /usr/sbin in the default user paths, I'd flame them to death .. because /sbin for superuser-binaries that root needs before the /usr filesystem is mounted. And /usr/sbin the ones not so essential ones that can wait.
Originally posted by nxny It is not in the user path, but is definitely in root's path. Make sure you login as root or 'su -' to root instead of a plain 'su'. Almost all binaries in /sbin and /usr/sbin are written for execution by the superuser. Although there are 'harmless' binaries like /sbin/lsmod that can be run properly by a normal user. If Redhat started including /sbin and /usr/sbin in the default user paths, I'd flame them to death .. because /sbin for superuser-binaries that root needs before the /usr filesystem is mounted. And /usr/sbin the ones not so essential ones that can wait.
hmm... well alright, I usually use su instead of logging in as root though. the only time I login as root is when I know I'm gonna be doing alot of work on my system, like when I recompile the kernel.
I got a good hardy laugh from that!
I had the same problem with my cd writer i was going nuts and finally i looked inside the case and whammo no power!
You are not the only one!
commuter
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.