Hola, aca va lilo.conf, que es lo que habria que poner para
bootear desde /dev/hda2??
Muchas gracias,
Andres
On Tue, 19 Feb 2002, Diego Alvarez wrote:
>
> hola...
>
> tendrias que adjuntar tu lilo.conf para ver que esta mal.
>
>
> saludos, Diego.
>
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
#
install=/boot/boot.b
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=50
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
single-key
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask,
<mode>)
#
# vga=ask
# vga=9
#
vga=normal
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
default=Linux
image=/vmlinuz
label=Linux
read-only
# restricted
alias=1
#image=/vmlinuz.old
# label=LinuxOLD
# read-only
# optional
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment
the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
other=/dev/hda2
label=potato
# restricted
read-only
optional
alias=2
> El Tue, 19 Feb 2002 18:43:22 -0500 (EST)
> Andres <andres@ccpo.odu.edu> escribió:
>
> >
> > Hola,
> >
> > Tengo dos particiones en mi computador (hda1 y hda2), e
instale
> > potato en ambas pues quiero transformar una en woody y mantener la
otra
> > estable, funcionando, en caso de que no me funcione el upgrade (ya
he
> > fallado un par de veces, cosas de novato). /dev/hda2 tiene potato
con
> > ximian-gnome todo funcionando bien. Ahora estoy desde /dev/hda1
que tiene
> > potato basico, con un minimo de archivos para hacer el apt-get
> > dist-upgrade a woody.
> >
> > El problema ahora es que no se como configurar lilo para
que
> > pueda seleccionar cual de las dos particiones funcionar. Hice unas
> > modificaciones en /etc/lilo.conf pero reclama que la otra
particion
> > /dev/hda2 no es boteable. He usado fdisk para cambiar la
caracteristica
> > booteable o no de ambas particiones pero no logro bootear desde
/dev/hda2.
> >
> >
> > Otra pregunta: que apt-sources se necesitan para cambiar a
woody?
> >
> > Cualquier ayuda, bienvenida...
> >
> > Andres
> >
> >
> > --
> > To UNSUBSCRIBE, email to
debian-user-spanish-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
> >
>
>
> --
> it has always been in the back of my mind
> dreaming about going to the corners of time
> i always wanted to fly in strange machines
>
> i wanna do centuries in a lifetime
> and feel it with my hands
> ...
> The Gathering.
>
>
> --
> To UNSUBSCRIBE, email to
debian-user-spanish-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>
--
To UNSUBSCRIBE, email to debian-user-spanish-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org