2.2.7 install report
OK, if I get a chance I will duplicate, elaborate, check old bug reports
and file new ones. Until then...
I think the most significant new (at least to me) problem was the failure
of ppp to load. Also, I got hung up trying to get packages off the CD, but
that may reflect oddities of my setup.
I ran off the compact i386 distribution, 1.44 formats. I copied the larger
files to the first partition of my main drive, which is formatted vfat (Win
98. I do not use the latest format--FAT32?--because I need to see it from
NT).
I booted off diskettes for the initial install. I pointed it at the hard
drive for base2_2. Unlike my previous attempts, this worked. This may be
from my slavish adherence to the file hierarchy, as advised in earlier
posts. Or perhaps something is fixed.
I did notice that when the installation routine asked for paths and I told
it to auto-search, it came up with /mountpoint/path
where mountpoint was some local mount point, and path was the "regular"
path. Could this be the source of some problems? Nobody is going to enter
a path with /mountpoint at the start, and this might cause any hand entered
path to fail.
Things went smoothly until driver selection. Here are the drivers, in the
order I loaded them.
nfs -- failed with warnings about unresolved symbols in (from?) sunrpc.o
ntfs, vfat, awe_wave--all fine
joy_creative -- failed. Could be my hardware, or a conflict with awe_wave
Can anyone tell me if I need the lp driver? I have a parallel port with a
printer on it.
ppp--fails. Many unresolved symbols /lib/module/2.2.14/net/ppp.o. This is
critical for me.
Done with driver configuration.
I then got dumped automatically into network configuration as if I were on
a decent network! I've already reported this as a bug for 2.2.6; it's
still there for 2.2.7. The message refers to eth0 and asks about DHCP or
B?TP. Though I have an ethernet card in the machine it isn't connected,
and this was the wrong path for me. I hit enter mostly to get through this
section.
On to setting up the base system.
After responding to the shadow password question it asked where to get the
deb's (not the way the question was phrased). I said to use the CD. It
asked for a name for the CD. I typed it in, hit enter, and nothing happened.
Installation was completely hung at this point. Well, the other consoles
worked, and I could have killed it--but it didn't go forward. ^c and ^d
had no effect.
This is obviously bad behavior. On the other hand, my CD was extremely
nonstandard: I burned it with assorted debs and a packages file which was
right for the whole archive, but not too good for the CD.
Also, I really need apt behavior, which I think was an option (I want it to
look for packages in a variety of places).
That's all for now!
Reply to: