Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux > #41691 > unrolled thread

Re: Systemd fun fun fun

Back to article view | Back to alt.os.linux

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Systemd fun fun fun Innocuous <myemail6622@yahoo.com> - 2017-01-28 10:30 -0500
    Re: Systemd fun fun fun William Unruh <unruh@invalid.ca> - 2017-01-28 18:55 +0000
      Re: Systemd fun fun fun "J.O. Aho" <user@example.net> - 2017-01-28 22:23 +0100
      Re: Systemd fun fun fun Joe <joe@jretrading.com> - 2017-01-28 22:13 +0000
        Re: Systemd fun fun fun Richard Kettlewell <invalid@invalid.invalid> - 2017-01-28 22:29 +0000
        Re: Systemd fun fun fun "Carlos E.R." <robin_listas@invalid.es> - 2017-01-29 02:43 +0100
          Re: Systemd fun fun fun Joe <joe@jretrading.com> - 2017-01-29 09:01 +0000
            Re: Systemd fun fun fun "J.O. Aho" <user@example.net> - 2017-01-29 12:40 +0100
              Re: Systemd fun fun fun Joe <joe@jretrading.com> - 2017-01-29 19:07 +0000
                Re: Systemd fun fun fun "J.O. Aho" <user@example.net> - 2017-01-29 20:50 +0100
                  [A BIT SOLVED]Re: Systemd fun fun fun Joe <joe@jretrading.com> - 2017-01-29 20:13 +0000
            Re: Systemd fun fun fun "Carlos E.R." <robin_listas@invalid.es> - 2017-01-30 04:23 +0100
              Re: Systemd fun fun fun Joe <joe@jretrading.com> - 2017-01-30 08:38 +0000
                Re: Systemd fun fun fun "Carlos E.R." <robin_listas@invalid.es> - 2017-01-30 14:12 +0100
                  Re: Systemd fun fun fun Joe <joe@jretrading.com> - 2017-01-30 15:05 +0000
                  Re: Systemd fun fun fun "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2017-01-30 11:53 -0600
          Re: Systemd fun fun fun Shadow <Sh@dow.br> - 2017-01-29 11:38 -0200
            Re: Systemd fun fun fun Chris Ahlstrom <OFeem1987@teleworm.us> - 2017-01-29 19:54 -0500
        Re: Systemd fun fun fun William Unruh <unruh@invalid.ca> - 2017-01-29 07:00 +0000
          Re: Systemd fun fun fun Joe <joe@jretrading.com> - 2017-01-29 09:01 +0000
      Re: Systemd fun fun fun Whiskers <catwheezel@operamail.com> - 2017-01-29 15:49 +0000

Page 1 of 2  [1] 2  Next page →

#41691 — Re: Systemd fun fun fun

On 10/04/2016 12:40 PM, Ivan Shmakov wrote:
>>>>>> Yrrah <Yrrah-acf@acf.invalid> writes:

>   Broken by design: systemd
>   http://ewontfix.com/14
>
> 	I think these provide nice summaries on what to expect of this
> 	specific part of the "modern" GNU/Linux system design.
>


I do not like systemd. I've changed over to using Devuan.
The concept of systemd is wrong in my view.

[toc] | [next] | [standalone]

#41692

On 2017-01-28, Innocuous <myemail6622@yahoo.com> wrote:
> On 10/04/2016 12:40 PM, Ivan Shmakov wrote:
>>>>>>> Yrrah <Yrrah-acf@acf.invalid> writes:
>
>>   Broken by design: systemd
>>   http://ewontfix.com/14
>>
>> 	I think these provide nice summaries on what to expect of this
>> 	specific part of the "modern" GNU/Linux system design.
>>
>
>
> I do not like systemd. I've changed over to using Devuan.
> The concept of systemd is wrong in my view.
Not sure the concept is wrong. Fast booting is a good idea. The implimentation has problems.

[toc] | [prev] | [next] | [standalone]

#41693

On 01/28/17 19:55, William Unruh wrote:
> On 2017-01-28, Innocuous <myemail6622@yahoo.com> wrote:
>> On 10/04/2016 12:40 PM, Ivan Shmakov wrote:
>>>>>>>> Yrrah <Yrrah-acf@acf.invalid> writes:
>>
>>>   Broken by design: systemd
>>>   http://ewontfix.com/14
>>>
>>> 	I think these provide nice summaries on what to expect of this
>>> 	specific part of the "modern" GNU/Linux system design.
>>>
>>
>>
>> I do not like systemd. I've changed over to using Devuan.
>> The concept of systemd is wrong in my view.
> Not sure the concept is wrong. Fast booting is a good idea. The implimentation has problems.

There are other init systems which supports parallel starting of
services without the faults. systemd do not start everything, some
things it just leaves for later, so you may have a flawed system.

-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#41694

On Sat, 28 Jan 2017 18:55:04 -0000 (UTC)
William Unruh <unruh@invalid.ca> wrote:

> On 2017-01-28, Innocuous <myemail6622@yahoo.com> wrote:
> > On 10/04/2016 12:40 PM, Ivan Shmakov wrote:  
> >>>>>>> Yrrah <Yrrah-acf@acf.invalid> writes:  
> >  
> >>   Broken by design: systemd
> >>   http://ewontfix.com/14
> >>
> >> 	I think these provide nice summaries on what to expect of
> >> this specific part of the "modern" GNU/Linux system design.
> >>  
> >
> >
> > I do not like systemd. I've changed over to using Devuan.
> > The concept of systemd is wrong in my view.  
> Not sure the concept is wrong. Fast booting is a good idea. The
> implimentation has problems.

As was said, parallel booting appeared some time before systemd, in
sid, at least.

Fast booting would be nice, but I'll believe it when I see it. Some
months ago, to add insult to injury, grub started adding about a
ten-second timeout ('Press any key..') before loading the initrd, and I
still haven't found how to stop that, other than hovering over it
waiting to hit a key. It ought to be something simple.... 

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#41695

Joe <joe@jretrading.com> writes:
> William Unruh <unruh@invalid.ca> wrote:
>> Not sure the concept is wrong. Fast booting is a good idea. The
>> implimentation has problems.
>
> As was said, parallel booting appeared some time before systemd, in
> sid, at least.

Dependency-based booting (which is the mechanism supporting parallel
booting) was introduced in Debian 6.0 (squeeze), released in 2011.  It
wasn’t just about performance or parallelism, the old system based on
statically configured sequence numbering was hopelessly fragile.

> Fast booting would be nice, but I'll believe it when I see it. Some
> months ago, to add insult to injury, grub started adding about a
> ten-second timeout ('Press any key..') before loading the initrd, and I
> still haven't found how to stop that, other than hovering over it
> waiting to hit a key. It ought to be something simple.... 

https://www.gnu.org/software/grub/manual/html_node/Simple-configuration.html

-- 
http://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#41698

On 2017-01-28 23:13, Joe wrote:
> Fast booting would be nice, but I'll believe it when I see it. Some
> months ago, to add insult to injury, grub started adding about a
> ten-second timeout ('Press any key..') before loading the initrd, and I
> still haven't found how to stop that, other than hovering over it
> waiting to hit a key. It ought to be something simple.... 

In openSUSE - check if it is the same in your distro:

/etc/default/grub:

GRUB_TIMEOUT=8

Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#41701

On Sun, 29 Jan 2017 02:43:05 +0100
"Carlos E.R." <robin_listas@invalid.es> wrote:

> On 2017-01-28 23:13, Joe wrote:
> > Fast booting would be nice, but I'll believe it when I see it. Some
> > months ago, to add insult to injury, grub started adding about a
> > ten-second timeout ('Press any key..') before loading the initrd,
> > and I still haven't found how to stop that, other than hovering
> > over it waiting to hit a key. It ought to be something simple....   
> 
> In openSUSE - check if it is the same in your distro:
> 
> /etc/default/grub:
> 
> GRUB_TIMEOUT=8
> 
> Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.
> 

My grub timeout is on 5 and works as expected.

In recent months, the *next* screen says 'loading ramdisc' or similar,
followed by 'press any key' and sits there for ten seconds or so if I
don't press a key. I haven't found anything anywhere which seems to
refer to this.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#41703

On 01/29/17 10:01, Joe wrote:
> On Sun, 29 Jan 2017 02:43:05 +0100
> "Carlos E.R." <robin_listas@invalid.es> wrote:
> 
>> On 2017-01-28 23:13, Joe wrote:
>>> Fast booting would be nice, but I'll believe it when I see it. Some
>>> months ago, to add insult to injury, grub started adding about a
>>> ten-second timeout ('Press any key..') before loading the initrd,
>>> and I still haven't found how to stop that, other than hovering
>>> over it waiting to hit a key. It ought to be something simple....   
>>
>> In openSUSE - check if it is the same in your distro:
>>
>> /etc/default/grub:
>>
>> GRUB_TIMEOUT=8
>>
>> Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.
>>
> 
> My grub timeout is on 5 and works as expected.
> 
> In recent months, the *next* screen says 'loading ramdisc' or similar,
> followed by 'press any key' and sits there for ten seconds or so if I
> don't press a key. I haven't found anything anywhere which seems to
> refer to this.

This would be in dracut settings, which is the one used in many
distribution to build the initramfs image. Most likely a change in a
script your distro uses or you have by mistake changed.

-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#41707

On Sun, 29 Jan 2017 12:40:49 +0100
"J.O. Aho" <user@example.net> wrote:

> On 01/29/17 10:01, Joe wrote:
> > On Sun, 29 Jan 2017 02:43:05 +0100
> > "Carlos E.R." <robin_listas@invalid.es> wrote:
> >   
> >> On 2017-01-28 23:13, Joe wrote:  
> >>> Fast booting would be nice, but I'll believe it when I see it.
> >>> Some months ago, to add insult to injury, grub started adding
> >>> about a ten-second timeout ('Press any key..') before loading the
> >>> initrd, and I still haven't found how to stop that, other than
> >>> hovering over it waiting to hit a key. It ought to be something
> >>> simple....     
> >>
> >> In openSUSE - check if it is the same in your distro:
> >>
> >> /etc/default/grub:
> >>
> >> GRUB_TIMEOUT=8
> >>
> >> Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.
> >>  
> > 
> > My grub timeout is on 5 and works as expected.
> > 
> > In recent months, the *next* screen says 'loading ramdisc' or
> > similar, followed by 'press any key' and sits there for ten seconds
> > or so if I don't press a key. I haven't found anything anywhere
> > which seems to refer to this.  
> 
> This would be in dracut settings, which is the one used in many
> distribution to build the initramfs image. Most likely a change in a
> script your distro uses or you have by mistake changed.
> 

Thatnks for the try, but dracut isn't installed here and
initramfs-tools is used to create the initrd. I can find nothing
in /etc/initramfs-tools referring to a time.

There's no /etc/default entry for initramfs-tools, and the grub entry
contains only its own timeout.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#41708

On 01/29/17 20:07, Joe wrote:
> On Sun, 29 Jan 2017 12:40:49 +0100
> "J.O. Aho" <user@example.net> wrote:
> 
>> On 01/29/17 10:01, Joe wrote:
>>> On Sun, 29 Jan 2017 02:43:05 +0100
>>> "Carlos E.R." <robin_listas@invalid.es> wrote:
>>>   
>>>> On 2017-01-28 23:13, Joe wrote:  
>>>>> Fast booting would be nice, but I'll believe it when I see it.
>>>>> Some months ago, to add insult to injury, grub started adding
>>>>> about a ten-second timeout ('Press any key..') before loading the
>>>>> initrd, and I still haven't found how to stop that, other than
>>>>> hovering over it waiting to hit a key. It ought to be something
>>>>> simple....     
>>>>
>>>> In openSUSE - check if it is the same in your distro:
>>>>
>>>> /etc/default/grub:
>>>>
>>>> GRUB_TIMEOUT=8
>>>>
>>>> Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.
>>>>  
>>>
>>> My grub timeout is on 5 and works as expected.
>>>
>>> In recent months, the *next* screen says 'loading ramdisc' or
>>> similar, followed by 'press any key' and sits there for ten seconds
>>> or so if I don't press a key. I haven't found anything anywhere
>>> which seems to refer to this.  
>>
>> This would be in dracut settings, which is the one used in many
>> distribution to build the initramfs image. Most likely a change in a
>> script your distro uses or you have by mistake changed.
>>
> 
> Thatnks for the try, but dracut isn't installed here and
> initramfs-tools is used to create the initrd.

Should be possible with that too.

> I can find nothing
> in /etc/initramfs-tools referring to a time.

I would take a look at the script it may build into the initramfs, you
could take the one you have and unpack it and see what's inside, if you
don't seem to find it there then I'm not sure.



> There's no /etc/default entry for initramfs-tools, and the grub entry
> contains only its own timeout.

When reread your original post, you said it was before initrd, which
then should rule out the initramfs file.

Have you looked at the scripts in /etc/grub.d ? those are used to make
the entries in the grub menu.


-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#41709 — [A BIT SOLVED]Re: Systemd fun fun fun

On Sun, 29 Jan 2017 20:50:02 +0100
"J.O. Aho" <user@example.net> wrote:

> On 01/29/17 20:07, Joe wrote:
> > On Sun, 29 Jan 2017 12:40:49 +0100
> > "J.O. Aho" <user@example.net> wrote:
> >   
> >> On 01/29/17 10:01, Joe wrote:  

> >>>
> >>> In recent months, the *next* screen says 'loading ramdisc' or
> >>> similar, followed by 'press any key' and sits there for ten
> >>> seconds or so if I don't press a key. I haven't found anything
> >>> anywhere which seems to refer to this.    
> >>
> >> This would be in dracut settings, which is the one used in many
> >> distribution to build the initramfs image. Most likely a change in
> >> a script your distro uses or you have by mistake changed.
> >>  
> > 
> > Thatnks for the try, but dracut isn't installed here and
> > initramfs-tools is used to create the initrd.  
> 
> Should be possible with that too.
> 
> > I can find nothing
> > in /etc/initramfs-tools referring to a time.  
> 
> I would take a look at the script it may build into the initramfs, you
> could take the one you have and unpack it and see what's inside, if
> you don't seem to find it there then I'm not sure.
> 
> 
> 
> > There's no /etc/default entry for initramfs-tools, and the grub
> > entry contains only its own timeout.  
> 
> When reread your original post, you said it was before initrd, which
> then should rule out the initramfs file.
> 
> Have you looked at the scripts in /etc/grub.d ? those are used to make
> the entries in the grub menu.
> 
> 
OK, a bit of light is shed. I'm seeing these lines after the grub menu
selection or timeout:

oading Linux <kernel number>...
oading initial ramdisk...

ress any key to continue...


I'm making the assumption that the monitor has not yet synchronised and
there are the letters L, L and P at the beginning of these three lines.

If I make the assumption that there is also a vertical error, leave the
system sitting on the grub menu until I manually pull the sync across
and down, then go onto the next page, I see the line:

no symbol table

above the others. Light dawns. I still don't know what the problem is,
but I now know it isn't some new configuration that I'm missing, it's
something broken. It looks like this:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841297

 except I don't have grub-efi. Poking around further, some people say
it can be fixed by repairing or reinstalling grub, but it's not causing
me enough trouble to be worth the risk. Presumably when a new grub2
arrives, it will sort itself out.

Hope this helps someone else, at least about the monitor gotcha...

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#41714

On 2017-01-29 10:01, Joe wrote:
> On Sun, 29 Jan 2017 02:43:05 +0100
> "Carlos E.R." <robin_listas@invalid.es> wrote:
> 
>> On 2017-01-28 23:13, Joe wrote:
>>> Fast booting would be nice, but I'll believe it when I see it. Some
>>> months ago, to add insult to injury, grub started adding about a
>>> ten-second timeout ('Press any key..') before loading the initrd,
>>> and I still haven't found how to stop that, other than hovering
>>> over it waiting to hit a key. It ought to be something simple....   
>>
>> In openSUSE - check if it is the same in your distro:
>>
>> /etc/default/grub:
>>
>> GRUB_TIMEOUT=8
>>
>> Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.
>>
> 
> My grub timeout is on 5 and works as expected.
> 
> In recent months, the *next* screen says 'loading ramdisc' or similar,
> followed by 'press any key' and sits there for ten seconds or so if I
> don't press a key. I haven't found anything anywhere which seems to
> refer to this.

Then it seems like some problem it finds and waits for your intervention.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#41718

On Mon, 30 Jan 2017 04:23:31 +0100
"Carlos E.R." <robin_listas@invalid.es> wrote:


> 
> Then it seems like some problem it finds and waits for your
> intervention.
> 

Yes, I now know it is a 'no symbol table' error, though there doesn't
seem to be any trouble.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#41719

On 2017-01-30 09:38, Joe wrote:
> On Mon, 30 Jan 2017 04:23:31 +0100
> "Carlos E.R." <robin_listas@invalid.es> wrote:
> 
> 
>>
>> Then it seems like some problem it finds and waits for your
>> intervention.
>>
> 
> Yes, I now know it is a 'no symbol table' error, though there doesn't
> seem to be any trouble.

Google finds hits. I looked at one:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839

seems to indicate a grub bug.


-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#41720

On Mon, 30 Jan 2017 14:12:25 +0100
"Carlos E.R." <robin_listas@invalid.es> wrote:

> On 2017-01-30 09:38, Joe wrote:
> > On Mon, 30 Jan 2017 04:23:31 +0100
> > "Carlos E.R." <robin_listas@invalid.es> wrote:
> > 
> >   
> >>
> >> Then it seems like some problem it finds and waits for your
> >> intervention.
> >>  
> > 
> > Yes, I now know it is a 'no symbol table' error, though there
> > doesn't seem to be any trouble.  
> 
> Google finds hits. I looked at one:
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839
> 
> seems to indicate a grub bug.
> 
> 

Thanks, yes, I found that page and got the impression that some people
had solved it by reinstalling grub, but that had not worked for others.
I'm on LVM for all except /boot, which may be relevant or may not.

It's not really serious enough to mess around with, as everything still
seems to work OK. I have problems, but they are the same ones I had
before this started happening, which could well have been in October.
If it was causing other people problems, it would probably have been
fixed by now.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#41724

On Mon, 30 Jan 2017 14:12:25 +0100
"Carlos E.R." <robin_listas@invalid.es> wrote:

> On 2017-01-30 09:38, Joe wrote:
> > On Mon, 30 Jan 2017 04:23:31 +0100
> > "Carlos E.R." <robin_listas@invalid.es> wrote:
> > 
> >   
> >>
> >> Then it seems like some problem it finds and waits for your
> >> intervention.
> >>  
> > 
> > Yes, I now know it is a 'no symbol table' error, though there
> > doesn't seem to be any trouble.  
> 
> Google finds hits. I looked at one:
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839
> 
> seems to indicate a grub bug.
> 
I thought I'd heard that expression before:
----------
<https://duckduckgo.com/?q=grub+bug&t=midori&ia=web>
...and images:
<https://duckduckgo.com/?q=grub+bug&t=midori&iax=1&ia=images>
----------

Big smile.

Cybe R. Wizard
-- 
Nice computers don't go down.
	Larry Niven, Steven Barnes
		"The Barsoom Project"

[toc] | [prev] | [next] | [standalone]

#41705

On Sun, 29 Jan 2017 02:43:05 +0100, "Carlos E.R."
<robin_listas@invalid.es> wrote:

>On 2017-01-28 23:13, Joe wrote:
>> Fast booting would be nice, but I'll believe it when I see it. Some
>> months ago, to add insult to injury, grub started adding about a
>> ten-second timeout ('Press any key..') before loading the initrd, and I
>> still haven't found how to stop that, other than hovering over it
>> waiting to hit a key. It ought to be something simple.... 
>
>In openSUSE - check if it is the same in your distro:
>
>/etc/default/grub:
>
>GRUB_TIMEOUT=8
>
>Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.

	Not just:
update-grub
	???
	How complicated.
	[]'s
-- 
Don't be evil - Google 2004
We have a new policy  - Google 2012

[toc] | [prev] | [next] | [standalone]

#41713

Shadow wrote this copyrighted missive and expects royalties:

> On Sun, 29 Jan 2017 02:43:05 +0100, "Carlos E.R."
> <robin_listas@invalid.es> wrote:
>
>>On 2017-01-28 23:13, Joe wrote:
>>> Fast booting would be nice, but I'll believe it when I see it. Some
>>> months ago, to add insult to injury, grub started adding about a
>>> ten-second timeout ('Press any key..') before loading the initrd, and I
>>> still haven't found how to stop that, other than hovering over it
>>> waiting to hit a key. It ought to be something simple.... 
>>
>>In openSUSE - check if it is the same in your distro:
>>
>>/etc/default/grub:
>>
>>GRUB_TIMEOUT=8
>>
>>Then run "grub2-mkconfig -o /boot/grub2/grub.cfg" to apply.
>
> 	Not just:
> update-grub
> 	???
> 	How complicated.
> 	[]'s

It's pretty simple, and not related to systemd. (I use roughly the same
on CentOS.)

-- 
For a light heart lives long.
		-- Shakespeare, "Love's Labour's Lost"

[toc] | [prev] | [next] | [standalone]

#41699

On 2017-01-28, Joe <joe@jretrading.com> wrote:
> On Sat, 28 Jan 2017 18:55:04 -0000 (UTC)
> William Unruh <unruh@invalid.ca> wrote:
>
>> On 2017-01-28, Innocuous <myemail6622@yahoo.com> wrote:
>> > On 10/04/2016 12:40 PM, Ivan Shmakov wrote:  
>> >>>>>>> Yrrah <Yrrah-acf@acf.invalid> writes:  
>> >  
>> >>   Broken by design: systemd
>> >>   http://ewontfix.com/14
>> >>
>> >> 	I think these provide nice summaries on what to expect of
>> >> this specific part of the "modern" GNU/Linux system design.
>> >>  
>> >
>> >
>> > I do not like systemd. I've changed over to using Devuan.
>> > The concept of systemd is wrong in my view.  
>> Not sure the concept is wrong. Fast booting is a good idea. The
>> implimentation has problems.
>
> As was said, parallel booting appeared some time before systemd, in
> sid, at least.
>
> Fast booting would be nice, but I'll believe it when I see it. Some
> months ago, to add insult to injury, grub started adding about a
> ten-second timeout ('Press any key..') before loading the initrd, and I
> still haven't found how to stop that, other than hovering over it
> waiting to hit a key. It ought to be something simple.... 

Nothing to do with systemd. 
Edit the line in /boot/grub2/
set timeout=
to whatever you want. I have mine at 5 so I can if I wish boot windows.
But make it whatever you want. 

>

[toc] | [prev] | [next] | [standalone]

#41702

On Sun, 29 Jan 2017 07:00:37 -0000 (UTC)
William Unruh <unruh@invalid.ca> wrote:

> On 2017-01-28, Joe <joe@jretrading.com> wrote:
> > On Sat, 28 Jan 2017 18:55:04 -0000 (UTC)
> > William Unruh <unruh@invalid.ca> wrote:
> >  
> >> On 2017-01-28, Innocuous <myemail6622@yahoo.com> wrote:  
> >> > On 10/04/2016 12:40 PM, Ivan Shmakov wrote:    
> >> >>>>>>> Yrrah <Yrrah-acf@acf.invalid> writes:    
> >> >    
> >> >>   Broken by design: systemd
> >> >>   http://ewontfix.com/14
> >> >>
> >> >> 	I think these provide nice summaries on what to expect
> >> >> of this specific part of the "modern" GNU/Linux system design.
> >> >>    
> >> >
> >> >
> >> > I do not like systemd. I've changed over to using Devuan.
> >> > The concept of systemd is wrong in my view.    
> >> Not sure the concept is wrong. Fast booting is a good idea. The
> >> implimentation has problems.  
> >
> > As was said, parallel booting appeared some time before systemd, in
> > sid, at least.
> >
> > Fast booting would be nice, but I'll believe it when I see it. Some
> > months ago, to add insult to injury, grub started adding about a
> > ten-second timeout ('Press any key..') before loading the initrd,
> > and I still haven't found how to stop that, other than hovering
> > over it waiting to hit a key. It ought to be something simple....   
> 
> Nothing to do with systemd. 

I wasn't suggesting that it was, just that systemd doesn't
automatically deliver a fast boot, and this phenomenon has slowed it
even more unless I give it a kick.

> Edit the line in /boot/grub2/
> set timeout=
> to whatever you want. I have mine at 5 so I can if I wish boot
> windows. But make it whatever you want. 
> 
> >  

Possibly it is only in sid so far.

My grub timeout is on 5 and works as expected.

In recent months, the *next* screen says 'loading ramdisc' or similar,
followed by 'press any key' and sits there for ten seconds or so if I
don't press a key. I haven't found anything anywhere which seems to
refer to this.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | alt.os.linux

csiph-web