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.
I'm on an Acer chromebook (the specs are below). I got crouton and did sudo bash. I ran the following command to make a bootable USB flash drive and install Slackware 14.2 on that same 32GB USB flash drive:
Note that this creates a live cd, and no changes will be saved when you shutdown. You will have a "fresh" slackware each time you boot. If you want changes to persist, install to the usb using the installer provided by the iso
Last edited by TheEzekielProject; 08-04-2017 at 10:54 PM.
Note that this creates a live cd, and no changes will be saved when you shutdown. You will have a "fresh" slackware each time you boot. If you want changes to persist, install to the usb using the installer provided by the iso
The dd command is so I can boot off the stick drive and get going with the installation. That's my intention - to install Slackware with the installer that comes with d1.
/dev/sda is a block device on your system, /dev/sda1, /dev/sda2 etc, are partitions on the block device.
I'd definitely recommend double and even triple checking that you do select the device you are intending to install to as picking the wrong one will delete EVERYTHING on that device!
You should be able to find the proper device by running
Code:
lsblk
You should get output similar to
Code:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 223.1G 0 part /
sdb 8:16 0 1.8T 0 disk
└─home 254:0 0 1.8T 0 crypt
├─home-home 254:1 0 1.8T 0 lvm /home
└─home-swap 254:2 0 19G 0 lvm [SWAP]
sdd 8:48 0 2.7T 0 disk
└─sdd2 8:50 0 2.7T 0 part
└─3tb 254:3 0 2.7T 0 crypt /media/3tb
sr0 11:0 1 1024M 0 rom
Since you have a 32GB usb, look for a 32GB (or thereabout) in SIZE and note its device name.
In that case I would run lsblk without the usb attached and then with it attached and compare output. You should be able to get the proper device name.
Both sda and sda1 pop up. So, I'll use sda with the dd command as you recommended. But not right now 'cause I'm busy with some math problems. I'll get to that tomorrow morning and I'll let you know how it went.
Both sda and sda1 pop up. So, I'll use sda with the dd command as you recommended. But not right now 'cause I'm busy with some math problems. I'll get to that tomorrow morning and I'll let you know how it went.
Ok, so sda1 is a partition on sda. These are the same device.
Devices are differentiated by the last letter. e.g. /dev/sda, /dev/sdb, /dev/sdc, etc, these are separate physical devices.
Edit: I just want to make it abundantly clear. I'd hate for you to completely wipeout your Chromebook OS because of a miscommunication
Last edited by TheEzekielProject; 08-05-2017 at 12:19 AM.
Good luck! Come back if you have any more questions!
OK, so I got this thing to boot from the USB drive, but after I pressed enter at "boot:", you know, where it tells you to enter any parameters if you have any to enter, the screen went stark black right away, and it's non-responsive. No characters, no beeping sounds, nothing.
I wish I could provide more info or text snippets from the screen. But, that's pretty much all that happens.
It happens right after I press enter and before the text starts rolling by - so I don't get to see any booting up text at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.