Re: problems installing Debian 2.0 "Scientific Workstation"
On Fri, Jul 24, 1998 at 09:16:59AM -0400, James G. MacKinnon wrote:
> Yesterday I helped a colleague and new Linux user install Debian 2.0
> (taken from a local mirror that should have been up-to-date). She chose
> the "Scientific Workstation" option, which meant that a great many
> packages were installed at once. Perhaps this is why we ran into problems.
> We encountered a few minor problems and two major ones during the dselect
> phase of the installation.
> 1. On at least two occasions during the installation of packages,
> something seemed to go into an infinite loop, spewing the message "expr:
> syntax error" on the screen. The only way I could figure out how to stop
> it was to switch to another console, find out what process was using CPU
> time, and kill it (it needed kill -9, as I recall). The installation
> process then proceeded. Two packages that were definitely affected were
> the vga16 and s3 X servers, neither of which were needed anyway (although
> vga16 would have been necessary if we had needed to use XF86Setup;
> luckily, we did not). I believe there was also one "expr: syntax error"
> message when we were installing the Mach64 server (which is the one that
> we used).
Which X versions did you use ? 220.127.116.11-3 ?
This bug was IMHO fixed in -4
> 2. I was unable to install emacs, and packages that depend on it,
> successfully. I tried numerous times, removing emacs20 and other things,
> then reinstalling. I always ended up with emacs20 installed but only
> half-configured. Also, auctex would not install because it said it wanted
Hmm, my auctex version:
Depends: emacs19 | emacs20
It should install with emacs20.
Christian Meder, email: email@example.com
What's the railroad to me ?
I never go to see
Where it ends.
It fills a few hollows,
And makes banks for the swallows,
It sets the sand a-blowing,
And the blackberries a-growing.
(Henry David Thoreau)
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com