Re: slink_cd - progress

[John Lapeyre <lapeyre@physics.arizona.edu>]

	I just made some i386 images with slink-cd 0.09 and burned them
and tested a little.  The mirror was uptodate wrt ftp1.us.debian.org
early morining March 3rd (MST). 

	Everything worked OK.  The multicd method is very slow and
awkward.  It seems that multiple CDs cannot be easily used with apt ?
I used the multi-cd method.  Everytime I needed a new package, I
didn't know which disk it was on and was forced to start dselect and
watch it read package lists, etc.  The good news is everthing worked
in installing, no big jams and crashing dpkg , which I have
experienced before.  

        I installed a couple of non-free packages just to
force it to use all three binary disks.  It, of course, installs
packages out of order and causes dependency problems, but they were
fixed quickly in the configuring stages.  I got fvwm2 up and running
and quit.  Getting this far would be an extraordinarily difficult and
frustrating task for someone who had never used unix.

	I didn't edit the config files in slink-cd to 
remove non-existent local packages .  This causes dselect
to complain that it can't find Packages.cd for local.  This
is not a big deal, it can be fixed on my next try.
	I found that non-us is not included even if I set the
diretory in the slink_cd script and give non-us on the command line.
I have to add lines to the slink2.list file to get them in.  
This may be what you intended , anyway.

Summary:
	I did not find anything that obviously does not work as intended.
The installation is slow and painful, but fairly smooth.

	Thanks again for all the hard work.

-- 
John Lapeyre <lapeyre@physics.arizona.edu>
Tucson,AZ     http://www.physics.arizona.edu/~lapeyre