On Sat, 02 Sep 2000, I. Tura wrote: > The fastest way I use is: > > > Download the file /dists/stable/main/binary-i386*/Packages.gz > > *Or your architecture > > Uncompress it and search there the packages you'll need. keywords: > sawmill > or wmaker for the window managers, for example. You'll need the packages > that the window manager depends on. You also need the file (bon't remember > location) base2.2.tgz for the base. > > You'll need the floppies in /dists/stable/main/disks-i386/ > > > Note: the name of the base file and the locations can be inaccurate, but > near from they. > > > Don't know if I'm missing something... >
Hmm, well the first thing I'd want to do is compile a custom kernel. I wouldn't go for the X stuff at first but rather install the (minimal) base system, then joe (favorite editor) and mc to finish setup and then (although through apt preferably) I install binutils, ncurses, gcc and stuff needed to compile a kernel from menuconfig to get all hardware working and set finish up. If it boots well again and stufgf works, I install whatever i need through apt including X (I happen to prefer kde so I'd apt kde2) Of course this is just my preference, maybe here's an interesting discussion.. how to initially set up a debian system. In my case I use a cable modem which basically means I can get away with two disks and a lot of apting... anyhow I think it makes sense to initially narrow down your packages installs as much as possible. Greetings to everyone, Dan -- Danny Pansters [EMAIL PROTECTED] www.ricin.com
