Re: Woody Boot Floppies Report
> On Sat, Jun 16, 2001 at 09:06:42AM -0400, Russell Hires wrote:
>> Okay,
>>
>> No success just yet. I was able to boot using the kernel and booted into
>> the ramdisk (named root.bin), but the kernel panicked. (I'm a holdout
>> for BootX, BTW. I still like it, and I'm still dual booting, as I share
>> my computer with the computer illiterate :-) The error message is:
>> Exception PC C00D7980 Signal 4. So, I rebooted using the same kernel,
>> and every thing was peachy.
>
> what machines do you have?
Well, so far I have just my Beige G3/266 standard everything except for
my Voodoo3 card. Hopefully in the next week or two I will have access to
a couple iMacs at the school where I volunteer. I'll use
yaboot/ybin/whatever-it's-called on those. Summer school begins next
week I think. The demand for the machines won't be like it was during
the school year, so I might be able to get something done.
> if its a newworld you will get no
> support. use yaboot not BootX. Any bug report from a NewWorld
> hardware user booting with BootX will not be considered. its caused
> by BootX period.
>
This is good to know. The thing I'm most afraid of is really doing some
damage with the whole booting procedure on the NewWorld machines. I'll
cross that bridge when I come to it.
>> The install was going well according to the steps laid out, until I got
>> to the install kernel modules part: I got unresolved symbols errors for
>> several of the modules (sorry I don't remember which ones, I'll take
>
> we know about these, its not a failure. every single debian kernel i
> have ever seen has had this issue, not just on powerpc either. i
> don't know why...
>
It's the debian kernels? Is there something that debian does that munges
up the symbols? Or something else? Is it only for Woody, or is it the
boot floppies?
<snip>
>> The next thing was setting up the network. To my surprise, when I chose
>> to set things up via DHCP, it worked. Or so I thought...when I try to
>
> your dsl device must have a dhcp daemon running on it, giving out
> bogus info...
Yeah, I don't know what to do about this, because I attempted to install
potato a while back and set the networking information to the default
manual stuff (i.e., local address is 192.168.1.1, etc.) and then I
couldn't get PPPoE to work. Maybe I should just skip that step. <shrug>
>
>> connect to the net, I can't, because I have DSL connection that uses
>> PPPoE. This is where the base tarball would have helped me out a lot.
>
> i don't know what can be done about that hideous thing known as
> pppoe. but the base tarball is dead and will likely never return.
Well, that presents me with the chicken and egg problem of: I've got the
.debs that PPPoE depends on, but I can't install them without dpkg, and
I don't know how to install that without dpkg...
>
>> So, I got stopped at the network. I'm going to have to figure out a way
>
>> It seems that the Woody boot floppies are attempting to be boot once, do
>> a complete install from there, and keep on truckin' after that; Rather
>> than boot once, get some basic stuff working, reboot, get the rest of
>> the system going...
>
> no its not, it works exactly as potato did in that respect, the only
> difference is the base install uses real .debs rather then a precooked
> root filesystem tarball. the base you get installed from woody's
> installer is pretty much the same as the one in potato. very small
> and limited, just enough to boot and get you on your way to using
> dselect/tasksel to make things useful.
So the base doesn't depend on the file "Release", located at
http://http.us.debian.org:80/debian/dists/woody/ ? Or, it does, but I
can d/l that doc to my local drive, and use it from there? It sounds
like the install from this point requires that you be networked to get
the base files, or have them locally. So, is there a list of the real
.debs that I can d/l individually, or am I missing something again?
(sorry if I am) I just need enough to get my PPPoE working, so I can get
the rest of everything.
> the reason we killed the base tarball was because it was a nightmare
> to maintain/build and required a rebuild of the boot-floppies just to
> update a package in base, debootstrap eliminates all that hassle.
>
I don't mean to sound like I'm complaining. Easier maintenance is a Good
Thing. I'm thinking of a proposition like this: since PPPoE is GPLed,
perhaps it could part of the install (ick!), or an optional part at the
very least, for those of us stuck using it...or even just an extra piece
to be downloaded, with a tag like "If you're stuck using PPPoE..."
Thanks for your help!
Russell
Reply to: