[systemd-devel] rename a block device

[Pascal]

thanks for this quick feedback Lennart.
don't worry, this is not an evolution request for systemd :-)
yes for blockdev --setro and, unfortunately, yes for overflows from file
systems.
*I had once considered using qemu-nbd/snapshot to "tolerate" some writes
without altering the real device (because absorbed by the snapshot)...*

regards, lacsaP.

Le lun. 25 avr. 2022 à 16:33, Lennart Poettering <lennart at poettering.net> a
écrit :

> On Mo, 25.04.22 16:25, Pascal (patatetom at gmail.com) wrote:
>
> > hi,
> >
> > the udev rules prohibit renaming anything other than a network device :
> > what is (would be) the way to really rename a block device (not just to
> > create a symbolic link) ?
>
> This functionality does not exist in the kernel to my knowledge. And
> the uevents for renaming network interface devices are messy enough to
> handle, let's please not add this for another subsystem!
>
> Are you aware of the udev.blockdev_read_only kernel cmdline option
> btw?
>
> (note that Linux is broken, marking a block device read-only actually
> is cosmetics mostly. File systems you mount from them may and do still
> write to the devices happily regardless whether read-only or
> not. Event through loopbck devices actually. You need to pass
> 'norecovery' as mount option to relevant file systems if you want
> true read-only access. It's crazy, if you ask me)
>
> Lennart
>
> --
> Lennart Poettering, Berlin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20220425/6b283afd/attachment-0001.htm>