> I've done some more testing on the 2.2.18 kernel
> config file that I have been working on. It works on a
> Digital PWS 500au system and it also works on a
> PC164LX alpha clone. It has builtin support for the
> Qlogic and the NCR/Symbios scsi controllers that are
> common in both of those systems. I've also added
> support for a few other scsi controllers and modulized
> as much as possible all across. It is setup to be as
> generic as possible, so it's compiled with the generic
> option. Please have others on the list test this out
> if they can today so I can make any last minute
> changes.
Well, thanks. I'll throw this config into the /kernels directory soon
and get a kernel built using it. What do you recommend that I call the
directory that it gets placed in? I'd like to name it after machine type,
if that is at all reasonable.
> Also, if you want I can include the module
> config line to get the builton sound card working in
> the PWS 500au. I think that would be a good idea for
> the digital/compaq systems to have a file with a list
> of config lines for any builton stuff.
Sure... send me whatever information you want. I could also add a README
file to each kernel directory, or maybe something in the top-level of
the distribution tree for machine-specific information.
> I'm about to do an install of slackware on the suse
> partition, since at this point I don't need it and it
> will make for a good test install from scratch. I
> don't have enough working floppies to test out the
> boot disks.. it's been a long time since I've had to
> use a floppy. But I'm going to keep searching through
> my closet to see if I can find enough that are in
> working order. If that turns out, then I'll try an
> install with the bootdisk and if I need to make
> changes I'll get with you on that. i
Having a bunch of floppies required was not something that I wanted to do.
However, it does remove the dependance upon another operating system being
on the machine. Given those two choices, I think floppies are a much
better way to go about it. Hopefully, the bootable CD thing will not be
long in coming. Once this stupid master cd gets made, I'll start looking
at setup and making real discs in earnest.
> I'm also going to
> sit down and go through each subset and test as much
> as possible. If I come across anything, I'll type it
> up in a text file and send it to you ASAP. I have to
> get a longer cable for my cd-burner, so I won't be
> able to work on making a bootable cd image just yet.
> I'll go out tomorrow during lunch and get the cable at
> fry's. If there is anything you would like for me to
> test in particular, let me know. I'm planning on doing
> an all dayer on this to help out.
I hate to say things like this, but if you use emacs, tcl, python, GNOME,
etc. on a regular basis, those would be prime things to test out. I don't
use any of that stuff at all so I cannot verify if it works or not. Those
are some of the big ones. Besides that, I don't have anything
specifically that you could test out. Just play with things and see what
catches fire and what doesn't. I'll get as much as possible taken care of
today.
Thanks for your help on this so far, espeically with the kernel config.
--
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