VectorLinux

The nuts and bolts => Installation & Updates => Topic started by: icedtea on February 22, 2011, 04:58:51 am

Title: [SOLVED] removing LILO from BOOT SECTOR
Post by: icedtea on February 22, 2011, 04:58:51 am
ok, i am not sure how could i start this one.. but.. i have an existing LILO.. VL 5.8

now i installed VL6.0 AND installed its own LILO in the boot sector.. now everytime i choose this VL6.0 its own LILO still appears.. (instead of starting to boot).. i want to remove it. . .

or can i edit my VL6.0's LILO to disable it?

here is my VL6.0 LILO :

Quote
root:# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdc13
default = linux
#compact
#prompt
#timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ bootsplash-high
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769


# End LILO global section
# Partition 1: Linux GUI mode
image = /boot/vmlinuz
 #   root = /dev/hdc13
 #   label = linux
 #   append = "splash=silent "
 #   read-only
 #   initrd = /boot/initrd
# Partition 2: Linux GUI mode
image = /boot/vmlinuz
#    root = /dev/hdc13
#    label = linux-gui
#    append = "4 splash=silent "
#    read-only
#    initrd = /boot/initrd
vector6:/~
root:#



Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 22, 2011, 11:21:03 am
VL 5.8  loader image is being dis[played ?
Where is the VL 5.8 boot directory located:

Do you still have/want to use  VL 5.8

If so, steps to correct:

Chain link newer VL 6 lilo to point to the version/s desired
Note that  the name of compressed kernel "vmlinuz" is  optional
All you really care is,  whatever chosen  readily shows which is what)
And most importantly *where*

To boot VL 6. , lilo boot-loader needs the full path & name of VL6  boot image


Re-run command lilo 

IIRC,  VL  has a utility (vasm?) to do all above

HTH -best luck
Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 22, 2011, 02:10:16 pm
VL5.8 is my Main LILO.. i still want to use it.. (as of now)

it carries my other boxes, slackware,zenwalk. and just recently, VL6.0

in my VL5.8,

VL6.0 is added as :

# VectorLinux 6
    other = /dev/hdc13
    label =VL6.0

my problem is.. this VL6.0 own LILO was installed in the boot sector.. so everytime i choose VL6.0 in my MAIN LILO, it will still prompt another boot loader..
Title: Re: removing LILO from BOOT SECTOR
Post by: uelsk8s on February 22, 2011, 02:34:33 pm
you have a couple options from here
1) run vliloconf from the 5.8 install and have IT add your 6.0 install.

2) change the timout in the 6.0 lilo.conf to 0 so it does not display anything and boots quickly

Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 22, 2011, 02:42:05 pm
you have a couple options from here
1) run vliloconf from the 5.8 install and have IT add your 6.0 install.

2) change the timout in the 6.0 lilo.conf to 0 so it does not display anything and boots quickly




i will try option 1 .. 

will this do for option 2 ?


# Start LILO global section
boot = /dev/hdc13
default = linux
#compact
#prompt
#timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 22, 2011, 03:50:08 pm
WHICHEVER loader is used (*or* chain load)  set the default O/system

IF chain loading (some O/systems do not have multi-boot capabilities) Edit others to  only boot themselves

When multi-system booting, any loader only need find appropriate kernel image   

Allow sufficient timeout (tab/Esc will stop countdown) to use options
Changing only VL 6 loader timeout does not *eliminate* current events   

Nowdays most live or install CD's allow booting into any present O/system
 
IF your Mbr ever becomes corrupted, we can supply commands to wipe,
then Cfg *any* loader, (Grub/2 is better for multiples) & install any loader   
 
Caveats:

http://en.wikipedia.org/wiki/GNU_GRUB
("Unlike LILO, there is no need to reinstall GRUB to the MBR or a partition after changes to the configuration file.")

While lilo can do most everything desired, Grub/Grub2 has become the de-facto standard

It is easier to repair, is more user friendly/adaptable  for  multiple O/systems
Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 24, 2011, 04:08:50 am
here is my entire VL 6.0 LILO

Quote

root:# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdc13
default = linux
#compact
prompt
#timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ bootsplash-high
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769


# End LILO global section
# Partition 1: Linux GUI mode
#image = /boot/vmlinuz
 #   root = /dev/hdc13
 #   label = linux
 #   append = "splash=silent "
 #   read-only
 #   initrd = /boot/initrd
# Partition 2: Linux GUI mode
#image = /boot/vmlinuz
#    root = /dev/hdc13
#    label = linux-gui
#    append = "4 splash=silent "
#    read-only
#    initrd = /boot/initrd
vector6:/~
root:#





and STILL.. it drops down to its OWN LILO after i chose VL6.0 in my "EXISTING LILO"
Title: Re: removing LILO from BOOT SECTOR
Post by: uelsk8s on February 24, 2011, 07:35:06 am
A few posts ago I posted the solutions:
you have a couple options from here
1) run vliloconf from the 5.8 install and have IT add your 6.0 install.

2) change the timout in the 6.0 lilo.conf to 0 so it does not display anything and boots quickly


#1 is still IMO the better way.

#2 should look like this
timeout = 0

Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 24, 2011, 09:59:53 am
Icedtea:

Since the 5,8 version worked I  agree  w/Uelsk8s

You can cleanup that configuration file for ease of reading by deleting commented lines

Where did the last lines
(vector6:/~
root:# 

come from
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 24, 2011, 10:52:35 am
Icedtea

Re-examining-  it appears you did use 5.8  to chain vl6
When running lilo - see file created by using

#/sbin/lilo -t  -q  -v >  lilotest

http://linux.die.net/man/8/lilo

EDIT: sorry forgot to mention - your first request was only how to remove the installed lilo(boot loader)   from VL6
when you folowed VL install procedures to install it

(You chose to install that into VL6 sector -rather than  the Mbr (not wishing to  overwrite 5.8 version)
 
Please see lilo - u - v  /dev/sdc13
Above command  is presuming VL6 uses newer device naming convention -("S" d~ )    otherwise use  /dev/hdc13

HTH
Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 24, 2011, 01:39:15 pm
Quote

Where did the last lines
(vector6:/~
root:# 

come from

it is after giving the cat file. (it gets back to my root prompt)


Quote

EDIT: sorry forgot to mention - your first request was only how to remove the installed lilo(boot loader)   from VL6
when you folowed VL install procedures to install it

(You chose to install that into VL6 sector -rather than  the Mbr (not wishing to  overwrite 5.8 version)



correct.


Ok, if i will run vlilconf from 5.8, i will re-install LILO in the MBR .. right? (since this is my main loader)

just want to verify, it will detect 2 disks, /dev/hda --win  and /dev/hdc --linux disk

i must install the loader in my first primary drive which is /dev/hda .. right?
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 24, 2011, 04:19:11 pm
Yes , we are on same page now
(By your description - you now cannot boot VL6 ?)

If so, using 5.8 run #fdisk -l
See if it picks up all devices
--------------------------------------------------------------------
Background:
The original 5.8 @ install detected other O/systems
VL 6 should have ( E.G. Why are there no other O/systems listed in VL6 lilo file ?)

@ Install's (create loader step) Vector should have notified what the probe found,
offered to add other O/systems to lilo
 
Did you run the (lilo *test*)  w/any Linux version to confirm options
Was either VL version a live cd or just an ISO to install
 
If not detected properly, (since an install probes all devices~ ) 
If probes are faulty, *Any Linux* version can be edited to include as desired then installed wherever wanted
 
Option - can supply data to build  your own lilo boot-floppy, which does not touch the Mbr

IMO - grub is the best choice for multiple boot users
Suggetion ~ take time out, download such as:

  http://www.sysresccd.org/Main_Page

With that a user is never shut out of access, can repair most anything
(INCLUDING Windows)

HTH

Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 24, 2011, 04:40:09 pm
actually.. i can boot VL6.0 and was able to connect to the internet.. .no problem.

my concern is..  just. "everytime i choose VL6.0 FROM my 5.8 LILO.. it still goes to VL6.0's OWN LILO"

all i want is to "remove VL6.0's LILO.. so if i choose VL6.0 from 5.8, then it will boot at once..


example :

VL5.8 LILO
           -->Selected VL6.0
                     --> will still direct to VL6.0's LILO (instead of booting directly) --because when i ran vliloconf, i install VL6.0 lilo in the boot sector
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 24, 2011, 05:40:25 pm
What is happening:

VL5.8 does NOT boot VL 6 ~instead you are presented w/ VL6 boot- loader
From *there*  VL6 boots

You do not *need*  a boot -loader on  VL 6

Why  no *test run* to confirm ?

Reiterated - EITHER version can be configured to create a /etc/lilo.conf file
The installer offered options  after which, if lilo.conf is not current to later installs, device modifications;
The sys-admin (root user) must manually edit events

Then running /sbin/lilo install it ---via parsing that  configuration file content
-----------------------------------------------------------------------------------------------------
Do NOT be afraid to play around w/system ~ unlike Windows, *anything* is repairable

Relying on a distribution variant's peculiarities  as a "quickest " solution_ Is a personal decision
As such,  we all make choices THAT is OUR RIGHT
Under FOSS, when that works, great - but - what has  then been learned ?

It is often stated Linux "should-be" a  glitch-free out_of_the_box experience
Is Mac/Windows -  none are perfect
Developers are hard pressed to meet *demands* and only human
We all make mistakes - experienced or new-user
Only non-configurable embedded versions (if/when they meet needs) come closest

Wasted time - when is learning anything new not worthy of it
 



Title: Re: removing LILO from BOOT SECTOR
Post by: roarde on February 24, 2011, 05:42:38 pm
Please post lilo.conf from 5.8 (if much too long, "relevant sections"), and the output from "lilo -V -v" from 6 and 5.8.
Title: Re: removing LILO from BOOT SECTOR
Post by: uelsk8s on February 24, 2011, 05:58:17 pm
Why are we making this so hard?
Either 1) add the line
Code: [Select]
timeout = 0or 2) comment the line
Code: [Select]
#prompt
then run
Code: [Select]
lilo
from inside 6.0
then reboot
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 24, 2011, 06:01:53 pm
Roarde

This is not a VL glitch

All any  boot-loader needs is to find the compressed  kernel image (no matter HOW it is named !)

The  system map etc. is a LILO requirement

To find that kernel image any loader needs the correct path 
BOTH lilo configs work one is now redundant
You already *have* the VL 6 content

Initrd itself is not a boot requirement for installed O/systems

Please see loader and kernel boot sequence events

http://www.debianhelp.co.uk/boot.htm

   
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 24, 2011, 06:14:25 pm
Uelsk8s

Yes your advice was already agreed upon >  as the fastest/"work_around_simplist "  method

It was also stated, that does NOT meet the original request
NOR does it change what is happening
His choice - He wanted to eliminate the current results

We can only suggest  -it is then up to him to use,.emperically test, or adopt suggestions
 
What is so hard to understand a  "loader* is not absolutely required on any O/system partition
It must exist somewhere
They access data to find any  kernel -from there the kernel takes over

Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 24, 2011, 08:02:20 pm
Quote

What is happening:

VL5.8 does NOT boot VL 6 ~instead you are presented w/ VL6 boot- loader
From *there*  VL6 boots

correct.


Quote

You do not *need*  a boot -loader on  VL 6

correct.


Quote

Why  no *test run* to confirm ?



i am at the office now. . i will try it when i get home.


Quote

then run
lilo
from inside 6.0
then reboot



if i do this. . . VL6.0 might over write my 5.8 LILO. . .or will it not happen?
Title: Re: removing LILO from BOOT SECTOR
Post by: uelsk8s on February 24, 2011, 08:28:19 pm
if i do this. . . VL6.0 might over write my 5.8 LILO. . .or will it not happen?
it will NOT happen.
your VL6 LILO is set to write to hdc13
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 24, 2011, 09:29:28 pm
icedtea :

Fastest - do as Uelsk8s suggests (VL6 loader was NOT installed to the Mbr)
As configured, it will not overwrite present Mbr

Your choice

(*Remove* e now-Installed VL6  loader  (from boot sector)   ONLY  ~  IF desired ~ using supplied data)
--------------------------------------------------------------------------------------------------------------------------------
Developers:

A boot-loader install from within VL 6  used OWN post-built  lilo.conf file

It was  instructed  to install in VL6  partition NOT the Mbr
 VL 5.8   boot-loader was installed to the Mbr
The VL 5.8 (lilo) loader   does  NOT need a VL 6  lilo loader post -installed to it's boot sector

When lilo  is used, the VL6  location of it's system map & "linuz" image is all 5.8 lilo -boot_loader  needs
 (in VL6  /boot  directory)

LILO needs a system.map  because it cannot understand file systems
Therefore it must be able to locate the root (/)  file system of an O/sytem
*and* location of  a kernel image

It is NOW :"chain-loading" from one boot-loader to activate the next
Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 25, 2011, 03:31:55 am
Why are we making this so hard?
Either 1) add the line
Code: [Select]
timeout = 0or 2) comment the line
Code: [Select]
#prompt
then run
Code: [Select]
lilo
from inside 6.0
then reboot

i did this. . .but it did not worked.

my current VL6.0

Quote

root:# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdc13
default = linux
#compact
prompt
timeout = 0
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ 1024x768x256
vga = 773

# End LILO global section
# Partition 1: Linux GUI mode
#image = /boot/vmlinuz
#    root = /dev/hdc13
 #   label = linux
  #  append = " "
   # read-only
   
# Partition 2: Linux GUI mode
#image = /boot/vmlinuz
 #   root = /dev/hdc13
  # label = linux-gui
   # append = "4  "
    #read-only

in the VL6.0 lilo this 2 items appear:

linux
linux-gui

and they are both booting.. (GUI) since its my default in inittab




Quote
Re-examining-  it appears you did use 5.8  to chain vl6
When running lilo - see file created by using

#/sbin/lilo -t  -q  -v >  lilotest

will i run this in 5.8 lilo or 6.0 lilo?
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 25, 2011, 05:44:37 am
You did NOT  comment out (#)  the "prompt" line in VL6 lilo.conf
Quote
will i run this in 5.8 lilo or 6.0 lilo?

Never mind, if you are not satisfied after using # before line  "prompt"-

Shouldn't be necessary - but from VL 6 - First   post  this (created lilo-files.txt):

(Command)   ls -ll  /boot |cat >  lilo_files.txt

The | symbol is upper-case of keyboard's ( /)

THEN still in VL 6,  try

lilo - t  -u -v  /dev/hdc13 > rmlilo.txt
Read it to see results of (test only) remove lilo  command
If it worked USE it  (lilo -u -v  /dev/hdc13)


Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 25, 2011, 06:12:19 am
Quote

 cat rmlilotest.txt
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 02:39:03 on Apr  1 2008.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/hdc13
Warning: /dev/hdc13 is not on the first disk
Reading old boot sector.
Restoring old boot sector.




Quote

icey:$ cat lilo_files.txt
total 6514
lrwxrwxrwx 1 root root      20 2011-02-20 14:21 System.map -> System.map-2.6.27.12
-rw-r--r-- 1 root root 1356775 2009-01-22 15:14 System.map-2.6.27.12
drwxr-xr-x 2 root root     184 2011-02-20 14:21 bitmap/
-rw-r--r-- 1 root root     512 2011-02-21 19:35 boot.160D
-rw-r--r-- 1 root root     193 2005-01-23 07:37 boot.label
lrwxrwxrwx 1 root root      16 2011-02-20 14:21 config -> config-2.6.27.12
-rw-r--r-- 1 root root   76888 2009-01-22 15:14 config-2.6.27.12
-rw-r--r-- 1 root root    5040 2008-04-01 15:39 diag1.img
drwxr-xr-x 2 root root     512 2008-06-16 21:32 grub/
-rw-r--r-- 1 root root  346032 2009-01-05 17:18 initrd
-rw------- 1 root root  415232 2011-02-25 19:23 map
-rw-r--r-- 1 root root   15754 2008-02-22 08:08 slack.bmp
drwxr-xr-x 2 root root      48 2011-02-21 19:35 tamu/
lrwxrwxrwx 1 root root      17 2011-02-20 14:21 vmlinuz -> vmlinuz-2.6.27.12
-rw-r--r-- 1 root root 4427632 2011-02-20 14:31 vmlinuz-2.6.27.12


Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 25, 2011, 06:17:20 am
Use it lilo -u  /dev/hdc13

Post results
Title: Re: removing LILO from BOOT SECTOR
Post by: icedtea on February 25, 2011, 02:06:33 pm
i got it.

this was the one :

Quote

# Start LILO global section
boot = /dev/hdc13
default = linux
#compact
#prompt
#timeout = 0



# End LILO global section
# Partition 1: Linux GUI mode
image = /boot/vmlinuz
    root = /dev/hdc13
    label = linux
    append = " "
    read-only
   
# Partition 2: Linux GUI mode
#image = /boot/vmlinuz
  #  root = /dev/hdc13
   #label = linux-gui
    #append = "4  "
    #read-only



i just noticed it minutes ago before posting this. . .

everytime i run lilo.. . it posts, added linux*  even though the  label = linux-gui is NOT commented. . .

then upon loading the VL6.0  as i posted earlier.. the labels "linux" and "linux-gui" appears.. BUT ANY OF THE TWO just loads my default GUI. .. 

i tried COMMENTING OUT, the label "linux" and VL6.0 DID NOT BOOT.. it just hangs at "loading VL6.0 and a cursor blinking"

not sure how it reads BUT.. . does this one :

boot = /dev/hdc13
default = linux

READS this ?  (i know that "label" is just a name)

image = /boot/vmlinuz
    root = /dev/hdc13
    label = linux
    append = " "
    read-only


i thought that.. this "PARTITION n"  (n is the number)  are the same.

# Partition 1: Linux GUI mode
# Partition 2: Linux GUI mode



again a BIG THANKS to the GUYS who replied on this thread.. and has the patience to support me. . .

NOW that this has been solved.. i will jump now into configuring the WIFI tool (xfce) sorry to bother much of your time.. really appreciated it.  :)  again. .THANK YOU
Title: Re: removing LILO from BOOT SECTOR
Post by: rm-r on February 25, 2011, 03:43:30 pm
Good -

Uelsk8s - LOL  do you have any hair left ?

Many may:
~ Be curious why latest VL7 was not tried
~ Like to see  an explanation of why_

~  /boot directory contains   four symlinks (of identical name)  as those pointed to in_the_ same_location
(&  what the heck is "tamu" )