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.
There are less than 24 hours left to vote in the 2011 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Ubuntu: An Absolute Beginners Guide
Ubuntu is a free, open-source computer operating system with 20 million users worldwide.
This 30 page guide was written for beginners and will tell you everything you need to know about the Ubuntu experience. You will learn how to install and setup Ubuntu on your computer, find technical support in your community, understand the Ubuntu philosophy, navigate the Unity desktop interface and use Ubuntu compatible software programs.
Click Here to receive this Complete Guide absolutely free.
I have Slackware64, v13.1, on my desktop PC, but the video card took a dump so I can't do much with it.
Can I pull out the HD(IDE) and connect it to my laptop and boot via USB to run it? I haven't done much as far as customization goes, just running the huge.s kernal, adjusted the fstab, but that's about it.
It's going to be a week before another video card arrives and I'd like to be able to get to my files and setup.
I tried this once, all you have to do is edit xorg.conf to set a different video card and maybe some other file you changed specifically for your hardware.
Yes and no. As long as your laptop is capable of booting from USB (my older laptop is not) then you can theoretically boot from the HD from the desktop. The problem most likely to occur is differences in hardware will mean that some things won't work.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
I've just done this taking my USB attached disk to my Brother's house and booting his system from it when I stayed (I didn't want to use his Windows). Here's the things to watch.
You may well find that to use the root="LABEL=" in lilo.conf you will need to use the generic kernel with an initial ram disk as this handles this option. I changed my lilo.conf to use this form of the root= line
Code:
root="LABEL=root"
after applying the required labels to my partitions. I also changed to this in /etc/fstab
to handle mounting the partitions should the device change across systems. I have this in lilo to handle USB booting
Code:
append="rootdelay=10 vt.default_utf8=0"
I also moved /etc/X11/xorg.conf to a save file as my xorg uses nvidia and his doesn't. I also saved and edited /etc/rc.d/rc.inet1.conf as his network was detected differently and setup a little different from mine.
As fas as I remember that was it - it just worked and I was pleasantly surprised how easy it was as his hardware is totally different from my usual.
Well, it booted, but when it comes time to mount the root drive, it fails and halts. It gives me three choices to enter when I boot and I can enter root=/dev/sda1, root=/dev/sda2 and root=/sda/sr0. These are the drives in the laptop, but it doesn't tell me what drive the USB drive is. Is there a way to tell? Once I have that, I believe I can boot easily.
Right now I'm running of a liveCD of eLive to access my data, but I'd rather just boot into Slackware and have all my tools and software.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
To use the LABEL functions you'll need to run the generic kernel and also need the appropriate devices, (something like ehci-hcd,usb-storage,ext4 and associated), in the initial ram disk. You first need to have applied those labels to the partitions with mkswap for the swap and e2label for the ext4. You also need the wait setting for allow the kernel load to wait for the usb to spin up. This can be found by looking at man mkinitrd.
I appreciate all this may sound a bit much. It may well be easier at this stage to boot up with the slackware install disks and see what devices are being detected by running "fdisk -l" as root. You can then chroot -bind the /proc and /dev devices and then chroot to the slackware root partition on the usb drive. You then need to create the initial ram disk with the appropriate mkintrd command and apply the labels to the partitions with mkswap -L and e2label. Then you need a lilo stanza for the generic kernel and initial ram disk.
The alternative is to do all the above to see what the usb disk is being detected as and try booting to the huge kernel using a set device as the root device in lilo and fstab i.e use this as the root device and bot to the huge kernel. You'll still need a rootdelay in lilo.conf to allow the usb drive to spin up. The huge kernel won't work with LABEL settings though.
Yes you'll need to do a bit of research but you should be able to get this all working reasonably easily.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.