Hi Chris,
--- Chris Lumens <chris@slackware.com> wrote:
> > 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.
> > 4. The kernel crashes upon bootup. I'm currently
> using
> > an old 2.13 kernel from Suse. I tried to rebuild
> the
> > kernel.. but making even the kernel configuration
> > programs fails. But.. make mrproper works:)
>
> 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'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.
>
> > I have not tried to setup X yet.. I did not see
> > XF86Setup command anywhere..? Maybe it's just me..
> > I've been away from Linux for some time now.
>
> /usr/X11R6/bin/XF86Setup. It's in the
> xset-3.3.6-alpha-1.tgz package.
>
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.
> > Should I rsync every night? Also.. if a new
> package
> > gets synced.. do I need to reinstall or can I
> upgrade
> > the package somehow?
>
> How about if I post the ChangeLog.txt file somewhere
> that you can see it?
> Then, you can check that and sync out only if
> anything has changed. If
> you've still got the tree that you sunc down last
> night, rsync will only
> download the changes.
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.
> You can use upgradepkg on packages. If they change
> name (like with the
> build number), you can still use upgradepkg. For
> example, let's say
> you've got vim installed and I put out a new vim
> package with a higher
> build number. You could upgrade it like so:
>
> # upgradepkg vim-5.6-alpha-1%vim-5.6-alpha-2
>
I'll try out the upgradepkg.
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!
-Octave
=====
******************************************************
* Octave J. Orgeron * Specializing in : *
* Unix Systems Administrator * Solaris/Tru64/Linux *
* Sun Microsystems, Inc. * Certified Solaris *
* octave@sun.com * Systems Administrator *
******************************************************
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT