> Well.. I was very excited to see slackware boot up on
> my alpha! I've been dreaming about the moment for some
> time. I did come across some errors.. so here is the
> list:
Excellent! Glad to see it's working at least a little bit for you :)
> 1. For the packages to install properly, the /var/log/
> tree needs to be made so that the scripts and logs can
> be installed as the packages are installed. I just
> mkdir'd all of the subdirs for /var/log.
That's right. You need to have /var/log/packages and /var/log/scripts
for installpkg to work right. I meant to add that to the INSTALL file,
but it must have slipped past me. Adding it now...
> 2. The manpages were not working.. I found that groff
> is linked against the previous version of libstdc++..
> so I created a link in /usr/lib that points to the
> current version.
Ah! This is a result of having gcc installed, but not the egcs packages
from /contrib/egcs-1.1.2. I haven't noticed this problem because I've
currently got both compilers intalled. I'm sure this will break other
things as well. I'll make a "to fix" list and put this on it.
> 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.
> 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?
> 5. I did see the odd links in / to libs that are in
> /usr/lib or /usr/X11R6/lib.
Yep. That's a problem with my xbin package. Since it's part of this
huge congolmeration of other packages that all get built at the same
time. That's a few days of work right there, so I'm not too anxious to
work on it. I believe you can safely remove those symlinks. I think
the proper ones are created.
> 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.
> The install directions were very good and easy to
> follow. The hardest part was just installing Suse on
> another partition... it has lots of brokeness in it.
The install will get easier. I promise. I heard back from Rich Payne
about my process for making bootable discs, and he says that it's worked
for him. So maybe there's a deeper problem at work here. Once I can get
bootable discs going, that should make things much easier.
If anyone wants to try to make a bootable cd, go for it.
> 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.
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
> Well.. I'm going to call it a day.. and get some food.
> I've been at this most of the day.
Glad it's working out for you! I probably won't get the groff thing fixed
tonight (it being 11:47pm) but hopefully I should have a nice batch of
things for tomorrow. Whee!
--
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