Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

install problems

There is no need for /boot to be a separate partition.  Unless you have a
special situation, /boot is usually an ordinary directory below the
partition mounted as the root filesystem (/).

The most likely problem here is that the "lilo" command was not run.

-- Mike

On 2000-05-26 at 13:18 -0400, Brian J. Conway wrote:

> You need to run fdisk (dos or linux versions) and set the /boot partition
> (or maybe just /, depending on your setup) active.  This isn't done by
> default in most linux partitioning programs, and there's no glaring error
> that comes up if you try to exit linux's fdisk without setting one active
> (as opposed to dos fdisk).

Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at (Subject line is ignored).

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /