[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: reporting problems with boot-floppies



The 2.2.17-2000-09-14 requires new base tar archive because of
the new wrapper script for more I18N support.

Please get the new base2_2.tgz from the specifid URL and use it 
when you test this new b-f.
Thanks.

In <20000917120035.A467@desktop.ourmanpann.com>,
  on Sun, 17 Sep 2000 12:00:35 -0700,
    on Re: reporting problems with boot-floppies,
 Pann McCuaig <pann@ourmanpann.com> wrote:

> Uh, apparently broken.
> 
> I tried the new ones, the 5-floppy set from
                        ~~~~~~~~~~~~~~~~

> <URL:http://auric.debian.org/~aph/bf/2.2.17-2000-09-14/>
> 
> with the following result:
> 
> Everything went smoothly until the first reboot (from a boot floppy),
> and this is where I was dead in the water:
> 
> ---------------------------------  schnipp!  -------------------------
> Starting internet supervisor: inetd.
> /bin/sh: /sbin/termwrap: No such file or directory
> /bin/sh: exec: /sbin/termwrap: cannot execute: No such file or directory
> ... (repeats several times) ...
> Init: Id "1" respawning too fast: disabled for 5 minutes
> ---------------------------------  schnapp!  -------------------------
> (waits 5 minutes, fails again)

In <20000917163603.A4548@quark.eou.edu>,
  on Sun, 17 Sep 2000 16:36:03 -0700,
    on Re: reporting problems with boot-floppies,
 esoR ocsirF <rosef@eou.edu> wrote:

> hmmm,
> I too tried the images found at
> http://auric.debian.org/~aph/bf/2.2.17-2000-09-14/images-1.44/idepci/
                                                    ~~~~~~~~~~~~~~~~~~
> Same problem, install went fine all the way through reboot, then bang!
> 
> lines read 
> 
> Starting internet superserver: inetd.
> /bin/sh: /sbin/termwrap: No such file or directory
> /bin/sh: exec: /sbin/termwrap: cannot execute: No such file or directory
> ... over and over...
> INIT: id "1" respawning to fast: disabled for 5 minutes

-- 
  Taketoshi Sano: <sano@debian.org>,<sano@debian.or.jp>,<kgh12351@nifty.ne.jp>



Reply to: