Hi Visali,
Am 25.02.2016 20:47 schrieb "Vasiliy Tolstov" :
>
> Hi,i want to build image that mounts readonly /usr and / readwrite.
That is really simple to do:
Just edit the kernel command line to include the appropriate flags to mount
usr read-only. Documentation for the flags can be found here
26.02.2016 00:55, Francis Moreau пишет:
> On Wed, Feb 24, 2016 at 6:12 PM, Lennart Poettering
> wrote:
>> On Wed, 24.02.16 17:40, Francis Moreau ([email protected]) wrote:
>>
>>> Hello,
>>>
>>> It seems that the unit generator for sysv init scripts translate
>>> "Required-Start: X" into "Afte
Hello, I’m trying to run user systemd services with DefaultEnvironment set
in a user.conf under $HOME/.config/systemd/ but it isn't being read.
The only .conf files I have seen being read are /etc/systemd/user.conf and
/etc/systemd/user.conf.d/*.conf
It should work, according to this page (under E
Today I have found a nice backtrace in my journal:
Feb 19 03:59:59 AmiloXi3650 systemd-coredump[1336]: Process 540
(kactivitymanage) of user 1000 dumped core.
Stack trace of
thread 540:
#0
On Wed, Feb 24, 2016 at 6:12 PM, Lennart Poettering
wrote:
> On Wed, 24.02.16 17:40, Francis Moreau ([email protected]) wrote:
>
>> Hello,
>>
>> It seems that the unit generator for sysv init scripts translate
>> "Required-Start: X" into "After=X" native ordering deps only.
>>
>> I would also
Hi,i want to build image that mounts readonly /usr and / readwrite.
I have dracut , systemd and efi system.
Does somebody have examples of systemd units ?
Also how /etc filled with systemd?
Thanks
___
systemd-devel mailing list
[email protected]
A bit of an update. disabling the second core didn't make much difference,
a couple of seconds max.
I played around with my own init task based on bootchart and tracked it
down to the fact that nanosleep was being called. I basically have the
following code below which gives me the same boot time
On Thu, Feb 25, 2016 at 10:30:47AM +, warpme wrote:
> Hi *
>
> I updated my system and one aspect of update was systemd update from 208 to
> 229.
>
> After this update my custom udev rules dealing with USB as stopped working.
>
> It looks like triggered by udev mount lives only during udev
Hi *
I updated my system and one aspect of update was systemd update from 208 to 229.
After this update my custom udev rules dealing with USB as stopped working.
After investigation the problem look following to me:
1.insert USB HDD
2.udev rule starts, creates mount dir, mounts USB dev. All seem
On Wed, 24 Feb 2016, Jon Stanley wrote:
I'd like a systemd unit (and only that unit) to be controlled by a
specific user. The unit runs as this user, so I thought about user
instances of systemd. This service should be started when the system
starts, so you'd have to enable linger in systemd-logi
10 matches
Mail list logo
