home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!ub4b!news.cs.kuleuven.ac.be!blekul11!alijku11!k111114
- Organization: Johannes Kepler University Linz - Computing Center
- Date: Tuesday, 10 Nov 1992 02:50:49 CET
- From: <K111114@ALIJKU11.BITNET>
- Message-ID: <92315.025049K111114@ALIJKU11.BITNET>
- Newsgroups: comp.os.linux
- Subject: lilo / SLS installing
- Lines: 33
-
- hi,
- i guess someone might to know which problems to avoid when installing lilo/SLS
- a) I have a sun, and unpacked lilo there to look at the source. after doing so,
- I ftp'd the -unpacked- files to a MSDOS disk, after that I mounted it on
- on /dev/fd0 and copied it to /etc/lilo. Tried to compile it, but failed.
- The Problem was that dparam.S should have been called dparam.s (not the
- lowercase s) ... msdos isn't case sensitve, ya know, and I was tired at 3:00
- in the morning so I simply oversaw it ...
- Therefore: don't ever unpack your files on whatever machine you are.
- Unpack it on the machine you wanna install them
- b) The version I got was version lilo.6. After compiling, i tried to run it:
- lilo -b /dev/hda2 -i ./boot.b /Image. All I got was a:
- "First boot sector is version 6. Expected version was 4."
- I took me a long time to recognize that in /usr/bin, there's a lilo sitting,
- too ||| And since PATHNAME has no .: firstplace , it took the file from
- /usr/bin ... *cough* right syntax would be:
- ./lilo -b /dev/hda2 ... etc.
- BUT: Could someone who takes care for the SLS package, please update the
- version of lilo in /usr/bin ?
- It's really confusing if you are installing SLS the first time to have
- different versions of /usr/bin files WITHIN ||| the package...
-
- Mebbe this all looks very simple for the experts ... hum ... *shrug*
- But where are the experts then ? on #linux (irc ?)
-
- Herp.
- K111114 @ alijku11.bitnet
-
- Beginning is hard. Bloody beginning is bloody hard.
- -------------------------------------------------------------------------------
- .. and then the expert said: "Oh , of course | You have to have the version
- configuration number of the major release subcount be equal to the unit-id
- progress field at offset C30AB00 ... Hum, guess what? Do a rm -rf /"
-