On Thu, 1 Mar 2018 18:48:30 +0100 "H. Nikolaus Schaller" <h...@goldelico.com> wrote:
> > > > Accessing "/dev/sdc<x>" is completely wrong and luckily I had no "/dev/sdc" > > that could be erased! The same is true for "/media/P<x>"! > > Well, it is impossible to perfectly prevent erasing the wrong device, because > only the user can know what the SD card reader with an SD really is. > So it is equally risky as calling fdisk directly. > No, if you call fdisk you see what disk you use. Here Sven thought, makesd would access /dev/sdg but did access /dev/sdc! That is a different thing. fdisk does not do any writes when it is called without a device name to work on! makesd does. Sven's sudo construction is just equal to calling makesd *without* DEV set!!! In that case makesd should not take a predefined device. Maybe makesd also should display a list what it wants to do asking for final confirmation The best thing would be to call makesd from NAND with a graphical interface. > There is at least one protection: you can't overwrite /dev/sda. > > What you could do is to just sudo chmod o+rw /dev/your-sd-reader > but I am not sure what happens with newly created partitions. > No, that would not work, because you want to mount the device and create device nodes on it, which would require root privileges again. Regards, Andreas
pgpp_pifJLwea.pgp
Description: OpenPGP digital signature
_______________________________________________ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
