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.
Hello,
I am wanting to install Slackware on a usb stick so that I can boot from it and use Slackware on different computers. I was wondering if I can do the standard install procedure, using the usb stick as the install drive. If I can than are there any pitfalls I should watch out for?
This is about installing FROM an usb device, not TO usb. (And the complexity of the how-to is totally absurd by the way. To install slackware FROM usb device you just have to copy kernels/hugesmp.s/bzImage and isolinux/initrd.img to the already existing fat filesystem on your stick. Then make it bootable with syslinux. Done.)
You can install slackware TO an usb device just like you install it on any other hard drive. The only pitfall is, that the slackware standard for naming devices in /etc/fstab is the tradiotional unix way (/dev/sdN). So if it's sdb on one computer it could be sdf on another one. To solve this issue use labels or uuids to identify the partitions.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Check man for the following :
Code:
fstab , lilo.conf, vol_id, e2_label
Personally I find it easier using UUID rather than LABEL for these operations (even though the strings are longer) as it doesn't seem the swap partitions can be labelled - hence the fstab entries for swap partitions which may change are messed up. Using UUID fixes this.
Personally I find it easier using UUID rather than LABEL for these operations (even though the strings are longer) as it doesn't seem the swap partitions can be labelled - hence the fstab entries for swap partitions which may change are messed up. Using UUID fixes this.
Code:
bash-3.1# mkswap -L 2nd_SWAP /dev/sda8
Setting up swapspace version 1, size = 10490408 KiB
LABEL=2nd_SWAP, UUID=223ddafe-da6a-4045-abc2-77fa45059ec3
bash-3.1# swapon -v -L 2nd_SWAP
swapon on /dev/sda8
bash-3.1# cat /proc/swaps
Filename Type Size Used Priority
/dev/sda5 partition 5253212 0 -1
/dev/sda8 partition 10490404 0 -2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.