Subject: Re: afterstep fails, and others too
To: Frederick Bruckman <firstname.lastname@example.org>
From: jeff <email@example.com>
Date: 11/24/2000 23:57:38
Thanks for your reply!
I just installed netbsd today and I'm a complete newbie.
But I know thing or two about Linux (PPc, YellowDog, SuSE, MkLinux,
etc...) Anyway, here's what I did:
Installed 1.5b2 (via ftp--ftp.netbsd.org, default on the install boot.fs).
Partitions: rwd0a root 1000mb; rwd0b 180mb swap; rwd0g 2997mb /usr.
Complete install, went off without a hitch.
Reboot into netbsd, prompt for root device. Entered 'wd0a', the internal
hd on my Powerbook G3/266 '98.
(I'm booting through OF 2.0.1)
(I have a scanner and cdr hooked up to scsi, properly cabled and
Adjusted some basic settings in rc.conf. Reboot.
Prompted for root device and entered 'wd0a'.
Enetered x (fvwm).
Did: sup -v -s (after setting things up acc to instructions)
"sysctl -w kern.maxproc=2000
...and it froze solid.
So: to answer the original question: yep, it's the latest pkgsrc.
"Principium sapientiae silentium est."
On Fri, 24 Nov 2000, Frederick Bruckman wrote:
> On Fri, 24 Nov 2000, jeff wrote:
> > > This exact problem occurs (it seems) with all big installs (e.g., kde,
> > > gnome, afterstep, abiword, etc.).
> > >
> > > The final error message (after a bunch of error 1 messages, is "unable to
> > > make dependencies".
> Is this the one where xpm depends on itself? Try updating to the very
> latest pkgsrc, or if you can use anoncvs, at least update pkgsrc/mk
> and graphics/xpm, and try it again.