[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What's the device name of my microSD card?



Quoting Reco (2019-04-21 20:29:09)
>         Hi.
> 
> On Sun, Apr 21, 2019 at 06:02:33PM +0000, Erik Josefsson wrote:
> > I have just assembled a [Teres machine] to learn how to set it up from the instructions on http://box.redpill.dk/ mentioned before on this list.
> > 
> > I run into my ignorance already at instruction 2: "Locate device name of your microSD card".
> > 
> > It turns out when I use completion with ls /dev/disk/by-id/ that my new USB microSD card reader says that my micro SD card has two names:
> > 
> >    usb-Generic_STORAGE_DEVICE_000000001532-0:0
> 
> It has one name. This one, to be exact.
> 
> >    usb-Generic_STORAGE_DEVICE_000000001532-0:0-part1
> 
> And this is the first partition of said device.
> 
> 
> > This ambiguity becomes problematic when I try instruction 4) "Decompress and copy image onto card" with "Fast method" b):
> > 
> >    sudo sh -c 'zcat core-lime2-1.0b17.img.gz > /dev/disk/by-id/my-sd-card'
> 
> Ugh. Why run zcat as root if you can avoid it:
> 
> zcat core-lime2-1.0b17.img.gz | sudo tee \
> /dev/disk/by-id/usb-Generic_STORAGE_DEVICE_000000001532-0\:0 > /dev/null

Interesting - why is zcat more dangerous than tee to run as root?

Using tee and throwing away its very feature (duplicating a pipe) feels 
excessive to me.  For separating root and non-root parts I seem to 
recall that one can use cat.

...but the ideal for me would be a command considered safe to call as 
root which did _not_ involve piping tricks, to limit the risk of 
confusion (I still remember myself in my early days of linux typing ">" 
instead of "<" and accidentally wiping a file I wanted to read).

(but before anyone suggests it: No, "dd" is the wrong tool here!)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


Reply to: