VectorLinux
October 20, 2014, 01:35:08 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: 1 [2]
  Print  
Author Topic: [SOLVED] removing LILO from BOOT SECTOR  (Read 4771 times)
uelsk8s
Administrator
Vectorian
*****
Posts: 2504



« Reply #15 on: February 24, 2011, 05:58:17 pm »

Why are we making this so hard?
Either 1) add the line
Code:
timeout = 0
or 2) comment the line
Code:
#prompt

then run
Code:
lilo

from inside 6.0
then reboot
Logged
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #16 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

   
Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #17 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

Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
icedtea
Vectorite
***
Posts: 142



« Reply #18 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?
Logged

using VL 5.1 SOHO , 5.8 GOLD
uelsk8s
Administrator
Vectorian
*****
Posts: 2504



« Reply #19 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
Logged
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #20 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
Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
icedtea
Vectorite
***
Posts: 142



« Reply #21 on: February 25, 2011, 03:31:55 am »

Why are we making this so hard?
Either 1) add the line
Code:
timeout = 0
or 2) comment the line
Code:
#prompt

then run
Code:
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?
Logged

using VL 5.1 SOHO , 5.8 GOLD
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #22 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)


Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
icedtea
Vectorite
***
Posts: 142



« Reply #23 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


Logged

using VL 5.1 SOHO , 5.8 GOLD
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #24 on: February 25, 2011, 06:17:20 am »

Use it lilo -u  /dev/hdc13

Post results
Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
icedtea
Vectorite
***
Posts: 142



« Reply #25 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.  Smiley  again. .THANK YOU
« Last Edit: February 25, 2011, 02:11:55 pm by icedtea » Logged

using VL 5.1 SOHO , 5.8 GOLD
rm-r
DoucheBag
Vectorite
***
Posts: 115


« Reply #26 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" )
Logged

"Problems are seldom resolved by thinking in the same manner they were created"

"What is viewed is not important - That which is seen is"
Pages: 1 [2]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!