On 5/4/05, Pete French <[EMAIL PROTECTED]> wrote:
> > Bingo! Restarting sysinstall always causes this problem. It's a well
> > known problem with several open PRs (see for example bin/38854,
> > bin/42162 and bin/45565 - all dating back to 2002). It's 100%
> > recreateable by restarting sysinsta
> Bingo! Restarting sysinstall always causes this problem. It's a well
> known problem with several open PRs (see for example bin/38854,
> bin/42162 and bin/45565 - all dating back to 2002). It's 100%
> recreateable by restarting sysinstall realatively early in the install
> procedure, and I've
On Wed, 2005-05-04 at 12:29 +0100, Pete French wrote:
> > I haven't been able to reproduce this yet. I've successfully done an
> > FTP install both from an initial floppy boot and from an initial disc1
> > CD boot. So it's not a "totally generic" problem, it might have
> > something to do with th
> I haven't been able to reproduce this yet. I've successfully done an
> FTP install both from an initial floppy boot and from an initial disc1
> CD boot. So it's not a "totally generic" problem, it might have
> something to do with the pathway you are following through sysinstall.
Possibly. I h
On Tue, 2005-05-03 at 16:54 +0100, Pete French wrote:
> Just been trying to install a new machine with 5.4-RC4. I normally
> do this using the bootonly image and FTP. But doing an FTP install
> always gives me the error "/: write failed, filesystem full" when
> it fetches the first chunk and tries
Just been trying to install a new machine with 5.4-RC4. I normally
do this using the bootonly image and FTP. But doing an FTP install
always gives me the error "/: write failed, filesystem full" when
it fetches the first chunk and tries to write it out.
I get exactly the same problem doing an FTP
