SlackwareThis Forum is for the discussion of Slackware Linux.
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.
What is the path to pico if it can't be found by just typing pico?
Lilo didn't install right to the superblock... so when I boot with a floppy all the paths aren't loaded.
I am using Slackware 8.1
Also where I may have goofed... I created a 15MB /boot and when Lilo asked for a partition I thought it was asking for where I put root so I told it /dev/hda2. Should that have been /dev/hda1? my /boot partition?
No cause if you created a 15 meg /boot and told it to set it as root ( / ) then most likely it wouldnt have installed as / needs way more space than 15 megs.
Maybe you set lilo to load on the bootblock of /dev/hda2 instead of the MBR?
If so then in /etc/lilo.conf there should be a line at the top that says boot=/dev/hda2, change that to boot=/dev/hda. Type /sbin/lilo at a prompt to activate your new lilo.conf
I must be losing it, I totally read his question wrong about the /, /boot and lilo but I did swear I gave the correct path to pico though, but there seems to be an echo..
That is exactly what I did... Darin... I was just going to reinstall Slackware 8.1 again... to fix it... but now that I know the actual path to run pico... I should be able to fix it in the /etc/lilo.config
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.