SEO

Hi all,

This one has me a bit miffed (lilo always does) and I'll try to keep
it simple, because it is?. Consider this:

HDA (only HD on system)
|
--> HDA1 (windoze junk)
|
--> HDA2 (DOS Extended)
| |
| -->HDA5 (windoze junk)
| |
| -->HDA6 (more windows junk)
|
--> HDA3 (Slack 9 Linux)
|
--> HDA4 (Linux Swap)

Currently, using lilo 22.4 to multi-boot works just as it should.
This was accomplished with liloconfig and the simple install to MBR
option. Nothing fancy here with only two entries in /etc/lilo.conf.
One for DOS and one for Linux.

Yesterday, I removed lilo 22.4 and installed lilo 22.5 from the
extras directory. Afterwards, the same routine described above for
setting up the MBR was used. Only this time, instead of seeing the
boot menu on reboot, lilo spit out an error like this "L 01 01 01 01
01...". Not good. I tried a few things to remedy this, looked over
the docs and man pages and still no solution. Finally, as a last
ditch effort, I removed 22.5, re-installed 22.4, used liloconfig to
set up the MBR, rebooted, and was greeted with a proper boot menu.
It worked without a hitch.

Is there some sort of major change to lilo 22.5 as opposed to 22.4
that I missed? An option perhaps? Has anyone else run into this
before? The procedure described above is just way to simple even for
this newbie to muck up.

Any or all suggestions greatly appreciated.

Thanks,

>
> Any or all suggestions greatly appreciated.
>
> Thanks,

If it isn't broken, don't fix it.

Scott wrote:
>
> Yesterday, I removed lilo 22.4 and installed lilo 22.5 from the
> extras directory. Afterwards, the same routine described above for
> setting up the MBR was used. Only this time, instead of seeing the
> boot menu on reboot, lilo spit out an error like this "L 01 01 01 01
> 01...". Not good. I tried a few things to remedy this, looked over
> the docs and man pages and still no solution. Finally, as a last
> ditch effort, I removed 22.5, re-installed 22.4, used liloconfig to
> set up the MBR, rebooted, and was greeted with a proper boot menu.
> It worked without a hitch.
>
> Is there some sort of major change to lilo 22.5 as opposed to 22.4
> that I missed? An option perhaps? Has anyone else run into this
> before? The procedure described above is just way to simple even for
> this newbie to muck up.
>
> Any or all suggestions greatly appreciated.

I use lilo-2.5.7.2 and have no problems with it. If you are
interested in trying a lilo.SlackBuild script I have let me know
and I'll post a link.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.0 Kernel 2.4.22 i686 (GCC) 3.3
Uptime: 4 days, 14:34, 1 user, load average: 1.49, 1.43, 1.28

On 09-03-2003, in alt.os.linux.slackware,
David <thunderbolt01@netscape.net> wrote:

>> Is there some sort of major change to lilo 22.5 as opposed to
>> 22.4 that I missed? An option perhaps? Has anyone else run into
>> this before? The procedure described above is just way to simple
>> even for this newbie to muck up.
>>
>> Any or all suggestions greatly appreciated.
>
> I use lilo-2.5.7.2 and have no problems with it. If you are
> interested in trying a lilo.SlackBuild script I have let me know
> and I'll post a link.

Thanks for mentioning the magic number. Just pulled down 22.5.7.2
from slack-current and it worked like a charm. Guess something just
wasn't quite right with 22.5 after all. Since I do plan on
recompiling lilo, I suppose I could take a look at that SlackBuild
script. Go ahead and post the link if you would.

Thanks again,

Scott wrote:
>
> Thanks for mentioning the magic number. Just pulled down 22.5.7.2
> from slack-current and it worked like a charm. Guess something just
> wasn't quite right with 22.5 after all. Since I do plan on
> recompiling lilo, I suppose I could take a look at that SlackBuild
> script. Go ahead and post the link if you would.

The lilo.SlackBuild is in the "a" directory at either of the
links below.

http://12.219.169.125/pub/linux/SlackBuild
ftp://12.219.169.125/linux/SlackBuild

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.0 Kernel 2.4.22 i686 (GCC) 3.3
Uptime: 5 days, 21:34, 1 user, load average: 1.12, 1.30, 1.35

On Thu, Sep 04 2003, in alt.os.linux.slackware,
David <thunderbolt01@netscape.net> wrote:

> Scott wrote:
>>
>> Thanks for mentioning the magic number. Just pulled down 22.5.7.2
>> from slack-current and it worked like a charm. Guess something
>> just wasn't quite right with 22.5 after all. Since I do plan on
>> recompiling lilo, I suppose I could take a look at that
>> SlackBuild script. Go ahead and post the link if you would.
>
> The lilo.SlackBuild is in the "a" directory at either of the links
> below.
>
> http://12.219.169.125/pub/linux/SlackBuild

Got a 404 error here for some reason.

> ftp://12.219.169.125/linux/SlackBuild

Worked fine. Snagged the entire lilo directory. I can see in the
build script you've provided for makepkg. Excellent. After checking
a mirror of slack-current, it seems the build script there doesn't
have that luxury. You've made things a bit easier. BTW - I'm kinda
interested in something you have at that address. I'll email ya
about it.

Thanks,

Scott wrote:
>
> Got a 404 error here for some reason.

Hmmmm?? Don't know why it seems to work for me. I don't see any
404 error in my logs for that link. But at least you were able to
get it.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.0 Kernel 2.4.22 i686 (GCC) 3.3
Uptime: 6 days, 13:34, 1 user, load average: 0.22, 0.22, 0.19

David wrote:
> Scott wrote:
>>
>> Got a 404 error here for some reason.
>
> Hmmmm?? Don't know why it seems to work for me. I don't see any 404
> error in my logs for that link. But at least you were able to get it.

Maybe because I didn't add a "/" on the end of it?

http://12.219.169.125/pub/linux/SlackBuild/

Just a guess since both ways work for me.
--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.0 Kernel 2.4.22 i686 (GCC) 3.3
Uptime: 6 days, 13:49, 1 user, load average: 0.10, 0.22, 0.20

On Fri, Sep 05 2003, in alt.os.linux.slackware,
David <thunderbolt01@netscape.net> wrote:

> David wrote:
>> Scott wrote:
>>>
>>> Got a 404 error here for some reason.
>>
>> Hmmmm?? Don't know why it seems to work for me. I don't see any 404
>> error in my logs for that link. But at least you were able to get it.
>
> Maybe because I didn't add a "/" on the end of it?
>
> *http://12.219.169.125/pub/linux/SlackBuild/*
>
> Just a guess since both ways work for me.

Wait now... Before you I am think a total dumbass, I need to explain
something. I've been playing around with Slrn and Xbrowser variable.
I've set Slrn to call this simple script when using SHIFT-U:
(Copied, modified, and re-created straight from the KDE Klipper config)

#!/bin/sh
#
# slrnmoz.sh
# General Purpose: Call Mozilla/Netscape Browser
# Date: 09/04/2003
#
# If browser already open, send arguement via -remote command,
# otherwise
# start the browser with argument.
#
# TODO: Funny?
#
# ps x |grep -q '[m]ozilla' && mozilla -remote "openURL($1,new-tab)"
# || mozilla $1 &

When I hit SHIFT-U in slrn and picked the URL you first gave it didn't
work. Not at all. However, I just tried it again and with the added
slash and it worked perfectly. Is the weakness here my fault or
yours?... Yep, guess this newbie has work to do. Can we blame Slrn
for any of this?...

Fine. I'm still a dumb-ass. Shoot me.

Scott wrote:
>
> Wait now... Before you I am think a total dumbass, I need to explain
> something. I've been playing around with Slrn and Xbrowser variable.
> I've set Slrn to call this simple script when using SHIFT-U:
> (Copied, modified, and re-created straight from the KDE Klipper config)
>
--snip script--
>
> When I hit SHIFT-U in slrn and picked the URL you first gave it didn't
> work. Not at all. However, I just tried it again and with the added
> slash and it worked perfectly. Is the weakness here my fault or
> yours?... Yep, guess this newbie has work to do. Can we blame Slrn
> for any of this?...
>
> Fine. I'm still a dumb-ass. Shoot me.

I can't say what the cause was. In my first post I didn't include
the last "/" so that was my fault. But I don't know if that was
the cause of the problem or not.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.0 Kernel 2.4.22 i686 (GCC) 3.3
Uptime: 6 days, 16:34, 1 user, load average: 0.37, 0.32, 0.27