On Thu, 12.05.11 08:55, Scott James Remnant ([email protected]) wrote:
> On Tue, May 10, 2011 at 9:39 AM, Lennart Poettering
> wrote:
>
> > Note that you need to delay execution of user code after the base system
> > is set up anyway, in order to ensure that the right perms are set on the
> > vo
On 05/15/2011 06:42 PM, Kay Sievers wrote:
> Hmm, you sure, you shouldn't put the:
> server:/path
> notation in here, instead of a non-existing fake device from the kernel?
heh, you was right :)
i've fixed this entry and it works out of the box with systemd original
remount-rootfs.service :)
> D
On Sun, May 15, 2011 at 18:03, Mariusz Bialonczyk wrote:
> On 05/15/2011 04:16 PM, Kay Sievers wrote:
>> What's in fstab for /? Maybe just that needs a fix for mount(8) to
>> understand what we do here.
> I have the following line for rootfs in fstab:
> /dev/nfs / nfs defa
Hi and thank you for respond
On 05/15/2011 04:16 PM, Kay Sievers wrote:
> What's in fstab for /? Maybe just that needs a fix for mount(8) to
> understand what we do here.
I have the following line for rootfs in fstab:
/dev/nfs/ nfs defaults0 0
> Just a firs
On Sun, May 15, 2011 at 12:49, Mariusz Bialonczyk wrote:
> Last time I gave a try to systemd as my init replacement. I am using it on
> debian sid system (systemd is from experimental), My rootfs is on NFS share
> (I have "ip=dhcp root=/dev/nfs and nfsroot=..." appended as kernel
> parameters).
>
Hello
Last time I gave a try to systemd as my init replacement. I am using it on
debian sid system (systemd is from experimental), My rootfs is on NFS share
(I have "ip=dhcp root=/dev/nfs and nfsroot=..." appended as kernel parameters).
First problem in my configuration is remounting my root filesy
