[Nbd] [w@...112...: Re: nbd-client started at boot (for root device) is not persistent]

[Wouter Verhelst <w@...112...>]

Only after I'd sent this did I notice the Cc was gone...

----- Forwarded message from Wouter Verhelst <w@...112...> -----

Date: Fri, 25 Nov 2016 09:04:32 +0100
From: Wouter Verhelst <w@...112...>
To: Victor <vixtor@...17...>
Subject: Re: [Nbd] nbd-client started at boot (for root device) is not persistent
Message-ID: <20161125080432.vgzj7dll3tinydph@...3...>
In-Reply-To: <CAMOh2p+2SFjck=z2C5ynyT0SseKPPJQ7z+RGb2SbocFP65vn-Q@...18...>
Organization: none
User-Agent: NeoMutt/20161104 (1.7.1)

On Fri, Nov 25, 2016 at 09:00:20AM +0200, Victor wrote:
> I am wondering - is there any way for a process to re-read the VFS after /dev
> and /sys were moved to /root/dev and /root/sys and then root was moved with
> MS_MOVE to /, and finally a chroot was performed and init started?
> 
> If not, what would you think about the following: create a new run flag for
> nbd-client (let's call it --replace). If this command line flag is used,
> nbd-client first kills an existing nbd-client providing the same resource then
> starts normally.

Can't do that, because then the shutdown protection that systemd provides is
gone (that's only valid for processes which have been started from initramfs).

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
       people in the world who think they really understand all of its rules,
       and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

----- End forwarded message -----

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
       people in the world who think they really understand all of its rules,
       and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12