am my homecomputer; beam myself into
the future." --Kraftwerk, 1981
> --
> From: Schackel, Fa. Integrata, ZRZ
> DA[SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, August 24, 1999 3:54 PM
> To: Stanley, Jeremy
> Subject: Abwesenheitsnotiz: Booti
On Wed, Aug 25, 1999 at 10:12:18AM -0400, Stanley, Jeremy wrote:
> Shouldn't be too hard to throw together a bash script that reruns LILO
> for each MBR, with different parameters, I wouldn't think... Anyone
> disagree?
If anyone has the time to do that (eh, takes the time to do that), then
why
> Shouldn't be too hard to throw together a bash script that reruns LILO
> for each MBR, with different parameters, I wouldn't think... Anyone
> disagree?
Hmmm here's a question...
If you run the raid on the whole drives instead of creating partitions,
do you even need to re-run lilo for all dev
OTECTED]
> Subject: Re: Booting Root RAID 1 Directly _Is_ Possible
>
> > This does open RAID-5 systems up for a full-redundancy solution with
> > little loss in capacity... Allocate the first 5 or 10MB on each
> drive
> > in your array for /boot as an n-way RAID-1 mir
anley, Jeremy
> Subject: RE: Booting Root RAID 1 Directly _Is_ Possible
>
> On Tue, 24 Aug 1999, Stanley, Jeremy wrote:
> > This does open RAID-5 systems up for a full-redundancy solution with
> > little loss in capacity... Allocate the first 5 or 10MB on each
> dri
Ferrell
> Cc: Harald Nordgård-Hansen; James Manning; Linux RAID Mailing List
> Subject: Re: Booting Root RAID 1 Directly _Is_ Possible
>
> On Tue, 24 Aug 1999, Mark Ferrell wrote:
>
[clip]
> Don't forget, though, that we're only talking about booting RAID 1
> here...
>
[snip]
On Tue, 24 Aug 1999, Mark Ferrell wrote:
> Maybe you two could work together and make a RaidRoot-HOWTO that covers both lilo
> and grub??
I think that's an excellent idea - one stop shopping.
Don't forget, though, that we're only talking about booting RAID 1 here...
not RAID booting in general.
Maybe you two could work together and make a RaidRoot-HOWTO that covers both lilo
and grub??
--
Mark Ferrell : [EMAIL PROTECTED]
Andy Poling wrote:
> On 23 Aug 1999, Harald Nordgård-Hansen wrote:
> > James Manning <[EMAIL PROTECTED]> writes:
> > > > How come I've been running this for about a
On Sun, Aug 22, 1999 at 01:28:32PM +0200, Harald Nordgård-Hansen wrote:
> disk=/dev/md1
> bios=0x80
> sectors=32
> heads=64
> cylinders=4341
> partition = /dev/md0
> start = 32
Gosh, you are a genius,
or pheraps i am just a dumbass
i spent a lot of time trying
On 23 Aug 1999, Harald Nordgård-Hansen wrote:
> James Manning <[EMAIL PROTECTED]> writes:
> > > How come I've been running this for about a year and a half, then?
> >
> > I believe he's talking about not having to do *any* non-raid partitions
> > (ie your /boot I believe, reading your lilo.conf)
One method I've seen on another platform (Solaris/Veritas)
is as follows:
1) boot loader knows about a list of the various components
of the boot RAID device (accomplished via eeprom on SPARC)
and will attempt to boot from the first of these it can
talk to
2) first component is accessed
James Manning <[EMAIL PROTECTED]> writes:
> > How come I've been running this for about a year and a half, then?
>
> I believe he's talking about not having to do *any* non-raid partitions
> (ie your /boot I believe, reading your lilo.conf)
> (...)
>
> Please enlighten if I missed the point in hi
> How come I've been running this for about a year and a half, then?
I believe he's talking about not having to do *any* non-raid partitions
(ie your /boot I believe, reading your lilo.conf) I have to admit, his
success with GRUB has been good to hear about. Adding in the code
to handle raid wi
Andy Poling <[EMAIL PROTECTED]> writes:
> LILO is just not going to let me boot my RAID 1 root.
>
> This is not a slam on LILO. Heck, I've happily used it for years to boot my
> Linux systems, and probably will continue to on my non-root-raid systems
> just because it works out of the box.
How
Andy Poling wrote:
>
>
> I'm willing to put together a cookbook description, of sorts, to patch and set
> up GRUB to boot RAID 1, and post it to the list. I guess my question is
> whether there's any interest in such a thing. It's entirely possible that
> most people are smarter than me, and
OK maybe this isn't rocket science, but I've seen it asked plenty of times,
and the only solutions I've seen presented required seperate /boot
partitions and/or ramdisks. Yech (IMHO). I don't want a 12-step boot
process involving a bunch of different partitions... I just want it to work.
The pr
16 matches
Mail list logo
