On Fri, Feb 14, 2014 at 5:52 AM, Darac Marjal wrote:
> On Thu, Feb 13, 2014 at 06:57:36PM +0100, Hans wrote:
>> Am Donnerstag, 13. Februar 2014, 16:05:47 schrieb Jonathan Dowland:
>>> On Thu, Feb 13, 2014 at 03:16:12PM +0100, Hans wrote:
Maybe I missed something? Or is systemd still not
On Fri, 14 Feb 2014 12:40:34 +
Brian wrote:
> On Fri 14 Feb 2014 at 15:48:43 +0400, Reco wrote:
>
> > But, given systemd insists on using its' own mount implementation, I'm
> > not sure whenever systemd honors this flag.
>
> There is no reason why it shouldn't and it does. Tested.
I disagr
On 20140214_124034, Brian wrote:
> On Fri 14 Feb 2014 at 15:48:43 +0400, Reco wrote:
>
> > But, given systemd insists on using its' own mount implementation, I'm
> > not sure whenever systemd honors this flag.
>
> There is no reason why it shouldn't and it does. Tested.
^^^
On Fri, Feb 14, 2014 at 12:40:34PM +, Brian wrote:
> On Fri 14 Feb 2014 at 15:48:43 +0400, Reco wrote:
>
> > But, given systemd insists on using its' own mount implementation, I'm
> > not sure whenever systemd honors this flag.
>
> There is no reason why it shouldn't and it does. Tested.
Ah,
On Fri 14 Feb 2014 at 15:48:43 +0400, Reco wrote:
> But, given systemd insists on using its' own mount implementation, I'm
> not sure whenever systemd honors this flag.
There is no reason why it shouldn't and it does. Tested.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
wi
Hi.
On Fri, Feb 14, 2014 at 10:52:45AM +, Darac Marjal wrote:
> I have noticed this with systemd, too. Under SysV, you can have a line
> like the above and it's treated as "If the above device is available,
> mount it, otherwise display an error (but the boot will continue to run,
> if possib
On Fri 14 Feb 2014 at 10:52:45 +, Darac Marjal wrote:
>
> I don't know (haven't looked actually, but I hope some kind soul knows
> the answer) if there's an option that says "This device is optional, but
> if it IS there, mount it at boot".
I've not followed through on the advice it gives, bu
On Thu, Feb 13, 2014 at 06:57:36PM +0100, Hans wrote:
> Am Donnerstag, 13. Februar 2014, 16:05:47 schrieb Jonathan Dowland:
> > On Thu, Feb 13, 2014 at 03:16:12PM +0100, Hans wrote:
> > > Maybe I missed something? Or is systemd still not working with
> > > encrypted partitions? There was nothing in
Hi,
Dňa Thu, 13 Feb 2014 19:27:00 +0100 Ralf Mardorf
napísal:
> use a stopwatch, but I suspect it's something like 7 seconds vs 9
> seconds for my installs. Even if it would be 1 second vs 1 minute,
> how often do we turn off and on our PCs? When I mention a "PC" I
> exclude "tablet PCs".
Good
Am Donnerstag, 13. Februar 2014, 19:27:00 schrieb Ralf Mardorf:
> On Thu, 2014-02-13 at 18:57 +0100, Hans wrote:
> > Again, I was impressed, how fast it boots
>
> For machines that fit to my needs, the startup time between upstart,
> systemd and SysVint doesn't variate that much. Yes, startup when
On Thu, 2014-02-13 at 18:57 +0100, Hans wrote:
> Again, I was impressed, how fast it boots
For machines that fit to my needs, the startup time between upstart,
systemd and SysVint doesn't variate that much. Yes, startup when using
upstart and systemd is faster, than when using SysVinit. I need to
Am Donnerstag, 13. Februar 2014, 16:05:47 schrieb Jonathan Dowland:
> On Thu, Feb 13, 2014 at 03:16:12PM +0100, Hans wrote:
> > Maybe I missed something? Or is systemd still not working with
> > encrypted partitions? There was nothing in the doc about it (as far as
> > I read)
>
> I use systemd wi
On Thu, Feb 13, 2014 at 03:16:12PM +0100, Hans wrote:
> Maybe I missed something? Or is systemd still not working with
> encrypted partitions? There was nothing in the doc about it (as far as
> I read)
I use systemd with encrypted partitions without problems.
Can you boot the machine, and at the
Le 13/02/2014 15:16, Hans a écrit :
Hi list,
sorry, it is me again. ASfter I installed systemd and addded init=/bin/systemd
into grub (like the README told), the boot hangs. The debian wiki says
init=/lib/systemd/systemd, but that is afaik nearly the same.
I suppose, it is because my partitzion
On Thu, 2014-02-13 at 15:16 +0100, Hans wrote:
> Is there something known about using encrypted partitions? I have the root-
> partition ( = "/ ") and the partition, where the kernel resides ( = /boot)
> unencryptetd. They work well. But when the boot will get access to the
> encrypted partitions
Hi list,
sorry, it is me again. ASfter I installed systemd and addded init=/bin/systemd
into grub (like the README told), the boot hangs. The debian wiki says
init=/lib/systemd/systemd, but that is afaik nearly the same.
I suppose, it is because my partitzions are encrypted and are mounted as
s removed.
>
> > 3. Is the entry in ther commandline of grub init=7lib/systemd/systemd
> > needed? (My system hangs, when this is used)
>
> (I assume that "7lib" is "/lib" in grub.cfg)
>
> At what point does it hang?
This was a typo. I meant /lib of course.
It hangs, when the "/" device is goi
On Wed, Feb 12, 2014 at 4:03 PM, Andrei POPESCU
wrote:
> On Mi, 12 feb 14, 21:28:19, Hans wrote:
>>
>> 3. Is the entry in ther commandline of grub init=7lib/systemd/systemd needed?
>> (My system hangs, when this is used)
>
> According to /usr/share/doc/systemd/README.Debian this should be
>
> init
On Wed, Feb 12, 2014 at 3:28 PM, Hans wrote:
> 1. Must I install systemd-sysv additionally to systemd?
No. Installing systemd-sysv will replace sysvinit's "/sbin/init" by a
symlink to "/lib/systemd/systemd".
> 2. Must I remove the essential package sysvinit?
No.
In jessie, sysvinit just pro
On Mi, 12 feb 14, 21:28:19, Hans wrote:
> Hi all,
>
> as I welcome and want to test the new systemd, but not break my system, I
> have
> some questions. Hope, they can be easily answered and are not too dumb.
>
> 1. Must I install systemd-sysv additionally to systemd?
No.
> 2. Must I remove
On Wed, 2014-02-12 at 21:28 +0100, Hans wrote:
> as I welcome and want to test the new systemd, but not break my system, I
> have
> some questions.
Perhaps you should clone your install, keep the original as is and
switch to systemd only for the clone.
"Where to get help?
As systemd is a very
Hi all,
as I welcome and want to test the new systemd, but not break my system, I have
some questions. Hope, they can be easily answered and are not too dumb.
1. Must I install systemd-sysv additionally to systemd?
2. Must I remove the essential package sysvinit?
3. Is the entry in ther comma
22 matches
Mail list logo
