On Thursday 2013-10-17 22:16, Colin Guthrie wrote:
> Perhaps a dumb question but are you 100% certain that
> systemd-remount-fs.service has been run? I've not seen any debug about
> it so far on this thread:
[lots of prose]
>
>That said, as the tool worked properly, it would seem that
'Twas brillig, and Warpme at 17/10/13 20:25 did gyre and gimble:
> On 10/17/13 7:59 PM, Colin Guthrie wrote:
>> 'Twas brillig, and Warpme at 17/10/13 18:15 did gyre and gimble:
>>> On 10/17/13 4:27 PM, Colin Guthrie wrote:
Perhaps a dumb question but are you 100% certain that
systemd-remo
Am 17.10.2013 21:25, schrieb Warpme:
> So summarizing:
> 1.systemd-remount-fs.service status from boot sequence is OK - but / is ro
> 2.starting /usr/lib/systemd/systemd-remount-fs switches / to rw
> 3.systemctl restart systemd-remount-fs.service switches / to rw
>
> Console output from 1 & 3 is
On 10/17/13 7:59 PM, Colin Guthrie wrote:
'Twas brillig, and Warpme at 17/10/13 18:15 did gyre and gimble:
On 10/17/13 4:27 PM, Colin Guthrie wrote:
Perhaps a dumb question but are you 100% certain that
systemd-remount-fs.service has been run? I've not seen any debug about
it so far on this thr
'Twas brillig, and Warpme at 17/10/13 18:15 did gyre and gimble:
> On 10/17/13 4:27 PM, Colin Guthrie wrote:
>> Perhaps a dumb question but are you 100% certain that
>> systemd-remount-fs.service has been run? I've not seen any debug about
>> it so far on this thread:
>>
>> systemctl status systemd
On 10/17/13 4:27 PM, Colin Guthrie wrote:
Perhaps a dumb question but are you 100% certain that
systemd-remount-fs.service has been run? I've not seen any debug about
it so far on this thread:
systemctl status systemd-remount-fs.service
Col
Col,
Console reports "Starting Remount Root and Ke
'Twas brillig, and Warpme at 17/10/13 13:59 did gyre and gimble:
> On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
>>> Maybe we should disable [re]mounting / by systemd at all?
>> All systemd does, is call 'mount -o remount /'. I ha
On Thu, Oct 17, 2013 at 02:59:37PM +0200, Warpme wrote:
> On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
> >>Maybe we should disable [re]mounting / by systemd at all?
> >All systemd does, is call 'mount -o remount /'. I have no ide
Am 17.10.2013 14:59, schrieb Warpme:
> On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
>>> Maybe we should disable [re]mounting / by systemd at all?
>> All systemd does, is call 'mount -o remount /'. I have no idea how you end
>>
On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
Maybe we should disable [re]mounting / by systemd at all?
All systemd does, is call 'mount -o remount /'. I have no idea how you end
up with a read-only filesystem.
As a work-around,
On Thu, Oct 17, 2013 at 4:54 AM, Andrey Borzenkov wrote:
> В Thu, 17 Oct 2013 00:07:55 +0200
> Kay Sievers пишет:
>
>> > typically the line looks like this
>> > UUID=b834776d-69d1-49c6-97c1-d6d758a438f0 / ext4 defaults
>> >
>> > i doubt that anything smells what "none" means
>>
>> It typically m
В Thu, 17 Oct 2013 00:07:55 +0200
Kay Sievers пишет:
>
> > typically the line looks like this
> > UUID=b834776d-69d1-49c6-97c1-d6d758a438f0 / ext4 defaults
> >
> > i doubt that anything smells what "none" means
>
> It typically makes not much sense to specify the id of the rootfs in a
> file s
On Wed, Oct 16, 2013 at 7:35 PM, Reindl Harald wrote:
>> none / auto remount,rw 0 0
>
> why "none" and "remount"?
"none" because at the time fstab is read, / is already mounted;
therefore the device already known. Specifying the root device in
fstab is in most cases really pointless and makes st
On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
> Maybe we should disable [re]mounting / by systemd at all?
All systemd does, is call 'mount -o remount /'. I have no idea how you end
up with a read-only filesystem.
As a work-around, you can add
/etc/systemd/system/systemd-remount-fs.servic
On 10/16/13 9:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 08:31:02PM +0200, Warpme wrote:
Zbyszku,
I add remount just after pivot_root. No change.
I don't get one thing: why exactly such script works OK for SysV ?
If it works for SysV - it means script leaves / in rw mode.
On Wed, Oct 16, 2013 at 08:31:02PM +0200, Warpme wrote:
> Zbyszku,
> I add remount just after pivot_root. No change.
> I don't get one thing: why exactly such script works OK for SysV ?
> If it works for SysV - it means script leaves / in rw mode.
> So it leaves / in rw mode also for systemd (only
On 10/16/13 7:40 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 07:22:28PM +0200, Warpme wrote:
On 10/16/13 7:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 06:18:12PM +0200, Warpme wrote:
Hi,
I want to switch init system from SysV to systemd-196.
Sys is PXE
On Wed, Oct 16, 2013 at 07:22:28PM +0200, Warpme wrote:
> On 10/16/13 7:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Wed, Oct 16, 2013 at 06:18:12PM +0200, Warpme wrote:
> >>Hi,
> >>I want to switch init system from SysV to systemd-196.
> >>Sys is PXE booted disk-less appliance with rootfs based
Am 16.10.2013 19:22, schrieb Warpme:
> On 10/16/13 7:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> On Wed, Oct 16, 2013 at 06:18:12PM +0200, Warpme wrote:
>>> Hi,
>>> I want to switch init system from SysV to systemd-196.
>>> Sys is PXE booted disk-less appliance with rootfs based on overlayfs.
>>
On 10/16/13 7:02 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 06:18:12PM +0200, Warpme wrote:
Hi,
I want to switch init system from SysV to systemd-196.
Sys is PXE booted disk-less appliance with rootfs based on overlayfs.
Currently I can PXEboot, successfully switch root from
On Wed, Oct 16, 2013 at 06:18:12PM +0200, Warpme wrote:
> Hi,
> I want to switch init system from SysV to systemd-196.
> Sys is PXE booted disk-less appliance with rootfs based on overlayfs.
>
> Currently I can PXEboot, successfully switch root from initrd to
> overlayfs based root, systemd starts
Hi,
I want to switch init system from SysV to systemd-196.
Sys is PXE booted disk-less appliance with rootfs based on overlayfs.
Currently I can PXEboot, successfully switch root from initrd to
overlayfs based root, systemd starts and executes many of it's units.
Unfortunately user units are fa
22 matches
Mail list logo