public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "erik burggraaf" <erik@erik-burggraaf.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Load time is rediculous
Date: Wed, 6 Nov 2002 15:06:21 -0500	[thread overview]
Message-ID: <00a501c285d0$044ad4e0$3ccb8d18@erikdesktop> (raw)
In-Reply-To: <Pine.LNX.4.44.0211061428450.424-100000@igueths>

Well, There's no delay setting in my lilo file.  What if I put one in below
the timeout.  It would look something like:
"delay = 10
I'd just go ahead and do it, but I don't want to have to rescue my system if
it coughs on the command.
Thanks,
Erik
----- Original Message -----
From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, November 06, 2002 2:32 PM
Subject: Re: Load time is rediculous


> Does the kernel try to probe for any devices during this time period?
> Which setting specifically did you change? The timeout or the delay (both
> settings under boot message). If you are going to change any timeouts I'd
> suggest changing the delay to boot the first image, which defaults to 20
> seconds.
>
> May you code in the power of the source,
> may the kernel, libraries, and utilities be with you,
> throughout all distributions until the end of the epoch.
>
> On Wed, 6 Nov 2002, erik burggraaf wrote:
>
> > Hi guys, I'm back at work on my little linux box.  Well, we have this
> > problem of load time.  It runs to about 3 minutes, which is rediculous,
> > since for about 2 minutes 30 seconds, it's just sitting there picking
it's
> > nose.  I've used vi to edit the /etc/lilo.conf file so that the timeout
has
> > been set from 1200 down to 10.  This hasn't had any effect on my load
time,
> > though.  Is there another setting in there I should look at?  Could
there be
> > another reason for the problem?  Am I stuck with this?  Please say I'm
not
> > stuck.  Smile.
> > Help much appreciated as always.
> > Cheers,
> > Erik
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.408 / Virus Database: 230 - Release Date: 24/10/2002
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.408 / Virus Database: 230 - Release Date: 24/10/2002




  reply	other threads:[~ UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 erik burggraaf
 ` Charles Hallenbeck
   ` Ann Parsons
     ` erik burggraaf
       ` Ann Parsons
         ` Geoff Shang
       ` Toby Fisher
       ` Steve Holmes
       ` dashielljt
   ` erik burggraaf
     ` Igor Gueths
       ` erik burggraaf
       ` shaun_oliver
     ` Geoff Shang
 ` Igor Gueths
   ` erik burggraaf [this message]
     ` Adam Myrow
       ` erik burggraaf
       ` Maurice A. Mines
     ` Geoff Shang
 ` Kerry Hoath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00a501c285d0$044ad4e0$3ccb8d18@erikdesktop' \
    --to=erik@erik-burggraaf.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).