What, exactly, goes wrong? Does the dd command complete? What happens when you attempt to boot the USB?
I'm not sure whether Unetbootin works for Salix at the moment. But the copy-to-USB method definitely should.
Sorry if this is a silly question, but you do realise you need to replace the path in that command with the path to the iso image as you downloaded it, and with the correct device (for the USB)?
So for example, if it is in Downloads, and the image is called salix.iso (which it isn't) and you are in your home directory, and the stick is seen as /dev/sdc (which it probably isn't) you would need to type
Code:
dd if=Downloads/salix.iso of=/dev/sdc
To check the device, do
Code:
lsblk
without having inserted the stick; insert the stick and do it again. If I do this i see, first time:
Code:
[code]mimosa[~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 29.8G 0 disk
├─sda1 8:1 0 10.6G 0 part /
└─sda3 8:3 0 18.8G 0 part /home[/code]
Second time:
Code:
mimosa[~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 29.8G 0 disk
├─sda1 8:1 0 10.6G 0 part /
└─sda3 8:3 0 18.8G 0 part /home
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 402.4G 0 part
└─sdb2 8:18 0 529G 0 part
That isn't a USB stick, it's an external hard drive, containing two partitions. But the point is, you can clearly see the device name your newly inserted device has been allocated, and that is the one you want to use for the dd command. Note that if there is an existing partition (e.g. sdb1) you don't want to write to that, you want the device, which in this case is /dev/sdb.
EDIT root privileges shouldn't be needed to write to a USB, corrected accordingly - thanks for pointing that out laprjns!
Statistics: Posted by mimosa — 11. Nov 2016, 09:12