Subject: Re: Configuration errors after successful install
From: John Price (jprice@floop.com)
Date: Sun May 14 2000 - 09:08:51 MDT
Thanks Ed! That did it! We repartitioned and gave /usr 700 MB from the 1.5
G we had allocated for root. We were able to configure and run. We are now
up and running on Xwindows. Next challenge is to configure the network card
and get our Pentium and Macs connected to our Linux box. The hardware is
already connected, so it's just a matter of getting Samba running and
configuring the network card and installing its drivers. Any advice om
that?
John D. Price
jprice@floop.com
http://www.floop.com
----- Original Message -----
From: Ed Jaeger <ed.jaeger@bgcorp.com>
To: <yellowdog-general@lists.yellowdoglinux.com>
Sent: Friday, May 12, 2000 11:34 PM
Subject: Re: Configuration errors after successful install
> Your /usr is too small & probably full, therefore configuration files
> can't be written.
>
> Try running
>
> df
>
> as root & see how much space you have on each filesystem.
>
> John Price wrote:
> >
> > We are installing YDL 1.2 server on a Starmax clone machine. We have it
> > partitioned with the following partitions and we've mounted them exactly
as
> > the instructions indicate:
> >
> > / 1.5 G
> > /usr 80M
> > /home 450M
> > /mush 200M
> > swap 128M
> >
> > This pretty much fills the HD since there is a also minimum version of
Mac
> > OS9 in an HFS paritition on our 2.5 G IDE HD, and we have 80 M of RAM.
> >
> > We got through the partitioning and figured out the wierd reboot quirk
after
> > getting the mount error. After rebooting, skipping repartitioning, and
> > mounting successfully we then selected the default install and got a
> > successful install, but we are getting nowhere with the long list of
> > configuration errors we get in the next step after the successful
install.
> > Among the unconfigured items are MOUSE and AUTHENTICATION. The RETRY
button
> > produces the same errors over and over again, it won't let us go BACK,
and
> > the MENU button just gives us the same old list of unconfigured (and
> > apparently unconfigurable) items. Booting from the hard drive and
> > attempting to log in as 'root' gives us an invalid login message. What
are
> > we doing wrong and where do we go from here?
> >
> > John D. Price
> > jprice@floop.com
> > http://www.floop.com
>
> --
> ---
> Ed Jaeger
>
> "Discovery consists of seeing what everybody has seen and thinking what
> nobody has thought."
>
> -- Albert von Szent-Gyorgyi
>
This archive was generated by hypermail 2a24 : Sun May 14 2000 - 09:01:31 MDT