public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: jmills@siberia.gtri.gatech.edu (John M. Mills)
To: blinux-list@goldfish.cube.net
Cc: kjahds@khjads.com
Subject: Beeping LILO (Was: Re: Booting Linux)
Date: Thu, 1 Aug 1996 10:37:51 -0400	[thread overview]
Message-ID: <199608011437.KAA18915@siberia.gtri.gatech.edu> (raw)

With regard to LILO completing its prompt with a "beep":

I suggested:

old:
ospc:	.ascii	"O"
	.byte	32,0
                 ^ ^-- null byte terminates the string
                 +---- ASCII <space>
new:
ospc:	.ascii	"O"
	.byte	7,7,32,0
                ^ ^ -- two ascii <BEL> ('\a') characters
One of these is enough for me.

I dug out lilo.<ver>.tar.gz matching my installation, made the change,
and it worked.  Here is what I did (hope I didn't miss anything).

As 'su'-- _carefully_:

1) unpack lilo.<ver>.tar.gz into /usr/src/lilo  [in my Slackware box]
2) 'cd /usr/src/lilo'
3) edit second.S for the desired number of "beeps"
4) 'make' or 'make boot.b' -- this is the boot sector which will be installed
5) 'mv /boot/boot.b /boot/boot.b.orig' -- paranoia patch - my SOP
6) 'cp boot.b /boot/boot.b'
7) '/etc/lilo/install' if you just did 'make boot.b', or './lilo' if you
   did 'make'

If you did 'make', but didn't use a matching version of lilo, you get
a nastigram which will tell you what version you _should_ have used.  You
may then choose to find the right version, or do a full re-installation
of your shiny new lilo.  You're on your own for that route.  I was lazy.

John M. Mills, Senior Research Engineer   --   john.m.mills@gtri.gatech.edu
   Georgia Tech Research Institute, Georgia Tech, Atlanta, GA 30332-0853
        Phone contacts: 770.528.3258 (voice), 770.528.7083 (FAX)
                    "ACLOG welcomes you to Atlanta"


             reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John M. Mills [this message]
 ` T. V. Raman
 ` T. V. Raman
   ` Kris Van Hees

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=199608011437.KAA18915@siberia.gtri.gatech.edu \
    --to=jmills@siberia.gtri.gatech.edu \
    --cc=blinux-list@goldfish.cube.net \
    --cc=kjahds@khjads.com \
    /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).