I've reached a point in my Slackware journey where I feel confident enough to remove my Mint 10 linux. It used to be my 'go to distro' when I trashed my Slackware installation. Now, I have Slax on a USB and I think that is enough.Mint 10 occupies /dev/sda5 (root) and /dev/sda6 (home) while Slackware occupies /dev/sda7 (root) and /dev/sda8 (home).If I delete the /dev/sda5 & /dev/sda6 partitions, can I very safely resize /dev/sda7 and /dev/sda8 to use the space freed up?
I wish that some partitions were hidden and others were read only, moreover I wish that these settings can't be edited by other users (except of course root user). For do this, have I only in "fstab" file in "etc" folder to comment (or delete) lines relatives to partitions that I wish are hides and I set options to "ro" to lines relatives to partitions that I wish are read only?
I'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd 0801 47428608 sda1 <-- this is my Windows partition 0802 30719552 sda2 <-- this is my Linux partition 0b00 1048575 sr0 driver:sr 0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp #mount /dev/device /slacktemp #chroot /slacktemp #cd /slacktemp/etc <-- for me it told me that doesn't exist #vi lilo.conf <-- couldn't do nothing and was frozen #lilo -v -t -b /dev/device #lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I just did a fresh install of slack 13.1 on a separate drive to the one I was previously using. I've been having trouble getting lilo to work, so that I can choose between either drive. Lilo is currently installed to /dev/sda, with the old system on /dev/sda1 and the new installation on /dev/sdb1. I keep getting errors like these:
Code: Fatal: Trying to map files from unnamed device 0x0011 (NFS/RAID mirror down ?) I managed to install lilo from the old system by copying the kernel image from the new system into the /boot/ directory and running lilo. I am now on the new system and trying the same thing in reverse but it isn't working. I have searched around a bit and there's a lot of talk of chroot-ing into the other partition to run lilo. I don't understand why the process isn't working both ways though. I can't run lilo on my new installation even with the two kernel images in the local /boot/ folder. Is this something to do with btrfs or am I missing something to do with lilo? This is my lilo.conf file. I am trying to run lilo using this file from my new installation on /dev/sdb1 and getting the error given above.
* Prevent the sdb1 + sdb2 ext4 partitions from being shown in Nautilus/Thunar Places sidebar.
* Prevent the Western Digital SmartWare VirtualCD, sdr1, from being shown in Nautilus/Thunar Places sidebar. It is just a VCD that is part of the firmware of the external (sdb) hard drive. *GAG!*
I don't care if they are mounted or not, though I prefer if they aren't. As long as they don't show up on the Places sidebar AT ALL, I'll be happy. I never use them, but keep mounting them by accident.
Here's my fstab, can you tell me why it's not doing the above?
I have quite a lot of testing operating systems installed. Some with their own home or boot partition. Now my places section in nautilus is an utter MESS. I was not able to find any working solution how to hide these partitions.
I have 2 drives formatted NTFS, which I'm mounting with /etc/fstab to ~/Movies/ and ~/Music/ and an EXT4 partition on my primary drive for games, mounted to ~/Roms/ and I would like for these drives to NOT show up in the side panel of nautilus.
I've been doing some looking around, and what I've found so far is that supposedly if you mount a partition/drive somewhere besides /media/ nautilus will ignore it. I'm finding this not to be the case, and it's driving me bonkers. here's my fstab:
Code: # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5).
i installed slackware 13.1, previously i had slackware 13, i made the following partitions:
everything went fine until i rebooted slackware after installation. lilo didnt boot at all, just a black screen. i booted with the DVD, and checked the lilo config file. the contents on lilo looks fine, just like any other lilo on google. for example i have this: boot = /dev/sda
i installed lilo on the MBR., i then changed this to boot = /dev/sda1 , on root and nothing same thing lilo always complains at the end: Partition entry not found , but how come , /etc/fstab shows all partitions are mounted ,( i am doing this in KDE environment). i reinstalled again , same thing. I also get a warning: video doesnt not support VESA mode, i changed to vga = normal again it complains that video doesnt support vesa even when i set it to normal, (note that i am running lilo after i made those changes, even rebooting , and same thing happens.
when i installed lilo, it let me choose video modes for the boot screen because lilo showed that my video card supports vesa mode, but then it doesnt boot at all. did slackware 13.1 changed so much that my laptop is no longer supported?? everything was fine with slackware 13 or is it because slackware needs a separate /boot partition, if so how come i just installed slackware 13 with just / and swap?
I finally got everything installed and then slackware setup prompted me to reboot. then i did and it just took me back to windowsxpx64. so then i tried booting off my usb, and it worked, however when i login as root, i just get the bash commandline and not interface or programs or anything. i cannot login as any other user and the setup did not prompt me to make another user account. so how would i activate lilo or make it so i can boot with it to slackware? i rather use grub but for now i would just like to get slackware working right.
I look after some small office where computers run ubuntu. Sometimes they phone me for help. For that reason, I decided to install ubuntu alongside with my slack.I seem to have problems with lilo configuration. Ubuntu is installed on software raid :
/boot = md0 (raid 1 of sda1+sdb1) / = md1 (raid 0 of sda2+sdb2)
I finally installed Slackware and now I have Windows, Slackware and Ubuntu in my laptop. I installed Ubuntu at the last order and at that time GRUB the default loader. But I feel that I'd like to use lilo more, so I booted into Slackware and run "lilo" and then lilo became the default loader.But then I cannot access Ubuntu anymore. Because in lilo there're no information about Ubuntu. So I added some information about Ubuntu according to that of Windows in lilo. But that failed. I still cannot access Ubuntu. I searched for the posts about this problem, and this is what they say:
I have been given a new old computer, Asus K8N-E with a 2GHz AMD Athlon 64.OpenBSD and Debian works like a charm. But with Slackware 13.1, LILO won't be installed properly. There are two disks: a 10GB ATA-drive with the system and a 250GB SATA-drive as a data repository.
Apparently the computer insists that the SATA is the first disk. Subsequently the bootable partition is not on the first disk and disables LILO to be installed. This is when I try to install LILO to a partition. When it is installed to MBR, it says something about overlapping and can't boot.
I've read that you can fix lilo after a bad edit by booting from install cd1 and entering: Code:boot: bare.i root=/dev/hda X noinitrd ro at the boot prompt. Can someone confirm this or suggest a better way? I'm using slackware 13.
I'm currently dual-booting slack 13.0 and ubuntu 10.04 When slack was originally installed, I had an earlier version of ubuntu on it, and lilo did not pick up the ubuntu. At that time, I didn't care, because I had no use for the 'old' ubuntu. When I installed ubuntu 10.04, the boot config file (/boot/grub/grub.cfg) did include an entry for slackware. Great! I am looking forward to upgrading slack to 13.1, but I want to make sure this time that I can also boot ubuntu, should I need to use it.
1)Slack installation instructions that would enable me to include the other distro in the initial install
2)Instructions on how to edit andprocess lilo.conf after the slack What follows is a dump of df from the ubunutu 'side'..
tim@bart:~$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda6 52866604 6227476 43953640 13% / none 1478976 300 1478676 1% /dev
With the continued growth of SATA devices, I have really been having problems with my boot loader. In the old days, it was pretty easy to make sure that the IDE devices stayed put. However, now everything is an sd device. Specifying a root directory of /dev/sda1 in lilo is no longer a sure thing. If you have a USB device plugged in or an ESATA device, your sd devices are no longer guaranteed to stay put.In reading through the lilo documentation, it appears that you can specify root devices by UUID or even by LABEL.
I installed Ubuntu 10.04 on a spare partition, but didn't want to install Grub since I'm sure Ubuntu isn't going to be around for more than a little test drive. The problem I have is that lilo doesn't like the initrd.img file, complaining that it's too large. I'm assuming this file should be in the initrd line for the lilo entry. If someone is booting Ubuntu 10.04 with lilo it would be nice to see the lilo entry or any tips.
My thread "Can't add Ubuntu into lilo.conf" was merged with this one.That problem has been solved, As I solved that problem, I got several more questions: When applying the changes by run "lilo", there's a warning about "large-memory". How come and how to solve? When loading into lilo, there's a capital character "U" in front of "Ubuntu". At the same time, there's nothing in front of Slackware or Windows. I wonder why. And, now that lilo read the booting info from slackware, if sometimes slackware get collapsed, could I still be able to access lilo? If I can access lilo, can I still boot into the other OSes?
During the upgrade of my slackware from 13.0 to 13.1 an electric problem happen on my sony laptop. So the upgrade is fine, disk is fine but no time to run the lilo for configure the new boot. Now impossible to boot. I boot on a backtrack live CD, and can't repair my lilo.Is someone could help me. I use slackware since the 3.2 (kheops in french).
I understand that making any changes wrt to kernel on Slackware one has to rerun Lilo. If an install was made onto a disk already using other distros and Grub and wanting to keep Grub, do I still need to install Lilo?I believe that one could use the 'chainloader' entry in Grub to boot the Slackware. And Lilo can be installed to its own / root partition.I suppose really what I'm asking is Slackware totally dependent on Lilo?
I want to use a different bmp image in Lilo when the system boots up. What I want to know is how do I get this new image to confirm to the specs as detailed in liloconfig. Or are these specifications only a guideline?
I have a laptop that I have installed Slack-current on, I am currently using the usb image to boot from. Windows7 is installed on sda2 and sda2 has been marked with the bootable flag, I would like to use lilo to boot the laptop do i install lilo to sda or to sda2?Will win7 still be able to boot using lilo as the boot loader ?
Another issue i noted during install is that the kernel panicked using the dvd to install with an error stating it could not read from the booting device, I eventually used the usb-pxe install to load the system however since 13.1 i have not been able to load a system using the dvd.
When I installed Slackware, I did not install LILO. Instead, in my LMDE, I ran: grub-install --recheck /dev/sda, then I ran: update-grub, then: reboot. This worked ok, although I have 4 grub enteries for Slackware - who knows why, but there are 4.I decided to install grub from the Slackware DVD. I copied the extras/source/grub folder to home and as su, ran pkgtool and selected grub from /tmp.From the root directory, as su, I did: rub-install --recheck /dev/sda but when I tried: update-grub (or grub-update), I got: command not found. I rebooted... (probably should not have done that)Grub menu sort of appeared with not boot options.I rebooted into Slackware from the Slackware DVD and now I am writing this from my Slackware installation.
I made this same mistake installing 13.0 several months ago and fixed it back then by trying different things,but I still don't understand why.So here's what I did this time to screw up with 13.1:-Partitioned the hard drive to have /boot partition at sda1 of type ext2 (root partition is at sda3)-manually configured LILO and chose to install bootloader to the MBR-went into that 'add linux' option in the LILO menu and pointed it to sda1When I try to boot slackware 13.1 I get a kernel panic. I'm sure the answer must be obvious but I don't find LILO very easy to understand. What did I do wrong and what should I do to fix this?