Re: Testing the new boot floppies
Dale Scheetz wrote:
> The PPP option is never set in /root/dbootstrap_settings (I've looked a
> couple of times at your previous directions)
>
> I don't know what the "something" is that dbootstrap wants either. If you
> don't install the Ethernet driver for your card, the network configuration
> complains. In the previous release, after declaring a host name, you were
> asked if you were on a network, and told to answer no if you were going to
> use the PPP connection method. This question is never asked. PPP is never
> mentioned in any of the install screens that I have seen, so I don't know
> where, or what you would click to make this flag be set.
Ok. If there's someone who knows how this is supposed to work, could you
please speak up?
If nobody knowns, I'm going to go read the relevant parts of dbootstrap,
and if I can't figure them out, I may just make base-config _always_
prompt about whether ppp should be used.
> It sounds like you can set it up to ask about ppp dispite the lack of a
> flag in /root/dbootstrap_settings? If you could do this, I would be
> satisfied ;-)
Well I wasn't installing, just running base-config in a chrooted
base-system that I prepped by making the file myself.
> Well, my experience was a bit different. The first time, when I dropped
> the ppp connection the download process simply hung, all counters stopped.
> I suppose if I had been patient I might have experienced some kind of
> timeout, but I wasn't and I didn't.
>
> When I went back the next day and ran it again, it only estimated 4 hours,
> and only took about 6. When it was done, gpm and man-db had failed to
> download and I was asked if I wanted to retry. This failed with the same
> "file not found" errors as before, however, when I finally ran the process
> from scratch (restarting base-config) it was able to retrieve and install
> these two packages.
Sounds to me like it probably needed to re-run apt-get update, since you
were installing from frozen and those packages presumably changed in the
meantime.
Hmm. I can run apt-get update everytime, though the chances of getting
bitten by that once it's stable are slim.
> On the first failure however, when I answered "No" nothing else happened.
> The messages I recieved suggested that gpm and man-db were the only
> packages not installed, but dpkg quickly informed me that none of the
> intended packages hd been installed. I tried apt-get install * but was
> told that the first file in the archives was not found (even though it was
> truely there). Cd'd to the archives directory and ran dpkg -i ./*.deb and
> got everything to install that was in the archives with three minor
> esceptions. Two tetex packages had not even been unpacked, and another
> package (don't remember) had to be configured.
>
> When I returned to this process again, the packages selected were
> downloaded (gpm and man-db) and installed. It seems if there are any
> download problems the install stops without trying to install the packages
> that _were_ downloaded. This is less than helpful.
Apt thing, talk to Jason Gunthorpe.
> On the task selection screen I selected all the gnome tasks and all the
> xfree86 tasks and the only package I get installed is xfree_common, seems
> that these tasks don't work!
That's quite strange.
--
see shy jo
Reply to: