> > > 3. The netsetup script is missing a "/" in front
> > of
> > > the calls to netsetup.
> >
> > Are you referring to netconfig? As far as I know,
> > we don't have anything
> > in Slackware called netsetup.
> >
>
> Ah.. sorry.. I ment netconfig. I was thinking of the
> name of the script that is used on Tru64.
Okay, the lack of a leading / is not a bug. That's how we've got things
set up throughout Slackware. The reasoning for that is so all the scripts
can be run properly from the bootdisk. If you run /sbin/netconfig, that
should work out just fine for you. The things in /var/log/setup are meant
to be called from the setup script at install time.
> > I'll bet you did a "make menuconfig" and that
> > segfaulted. Try linking
> > /bin/sh to /bin/bash1 instead of /bin/bash. That
> > fixes things on my
> > machines. It sounds like a bad build of bash 2, but
> > it's so buggy anyways
> > that it's hard to tell :)
> >
> > What kind of hardware are you running again? And
> > what specific messages
> > are you getting from the kernel crash?
>
> Yes.. you are correct. I relinked /bin/sh to
> /bin/bash1 and was able to get a kernel to compile:)
I did some searching around today and discovered that this is a known
problem. Apparently, there are (were?) some memcpy() issues in glibc a
few months back. This bug appears when running certain scripts through
bash. The suggested solution was to simply recompile bash. That didn't
fix anything for me, so I'm still not sure what to do about bash.
For now, I'm just going to recommend that bash1 be symlinked as sh instead
of bash2. I'm just hoping that Patrick is able to merge in ksh at some
point. I sure will set that up as the defaul shell :)
> I'm running on a Digital PWS 500au (a.k.a. Miata). The
> error message I would get is a kernel panic that it's
> unable to access a virtual memory address. I wish I
> could print it out. It happens just after the
> initialization of the builton devices and right before
> it starts to mount the filesystem. If you want, I can
> send you the kernel and the config file that I used.
Yes, send me anything that you think might help. If you want to play
around with trying to get the Slackware kernel to boot, here's what you
can do: The config file that I used to build the kernel is kept in
/kernels/generic.s/config. You could try tweaking that config file and
playing with it until you get something figured out. If you are able to
determine one or two specific options that cause the kernel to crash, then
I could just remove those options from the build.
Alternatively, I could make a miata.s bootdisk and we could see what
happens. I want to stay away from making a bootdisk for each machine
type unless it is absolutely necissary.
> I found it.. the only thing is that is needs the VGA16
> xserver to start up. It's okay.. I used the good old
> xf86config script to get things up and running. So far
> KDE is working. I'll let you know about the other
> WM's.
Strangely, the VGA16 server did not build on my Alpha. That's why I
didn't include it. I don't know if that is a bug in my build or not. Is
that server present in other distributions?
I'm glad to know that KDE is working out for you. I thought that my KDE
build was a bit broken. I was going to take a look at it more closely
here in a few days and see what's up. I'm personally missing a few things
in the /opt/kde/share directory, which leads to some errors on startup and
causes the KDE Control Center to crash.
> Thanks for the post on the Changelog file. I compiled
> rsync on my Tru64 box and just rsynced the tree. I had
> to move the tree over to the Tru64 box.. running out
> of room on the 4.3 gig disk on the 500au.
Yep. The source and package tree is getting pretty large.
> I'm having lots of fun remembering slackware and
> seeing how things have moved along for linux in
> general. I started out with the old SLS distro long
> ago and still tell my friends to use Slackware if they
> want to use Linux. I've been using Solaris and Tru64
> soo much in recent times that I'd forgotten about
> where it all began for me. So I'm having lots of fun
> with slackware on my alpha!
Cool! Glad to know that someone is enjoying all this work :)
--
Chris Lumens - chris@slackware.com - KG6CIH
@n=(-42,-85,-83,-19,65,2,-10,-10,-15,-3,2,-10,73,-4,8,-4,2,79,8,17,15,7,14,2);
print map{chr(-$n[$i++]+ord)} sort(split(//,'place random string here')),"\n";
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT