my predicament is this. I'm trying to put linux onto my sager 3880. my only real option at home is wireless, and the signal is pretty iffy (im usually constantly switching between my network and my neighbor's, shhh, don't tell!). i can't use ethernet at home because the cable modem is in my roomates room and i don't want to be in there forever if it takes a long time. but i can use the ethernet on campus, which is pretty fast. my question is this. if i get everything partitioned right and do as much offline as i can, how long do i have to be plugged in to get everything it needs? do i have to be there typing commands and whatnot or is it a scripted download (can i just leave it in my roomate's room for a day and come back to get it when it's done)? can i download everything it needs for the install and burn it onto the CD along with the mini OS that I boot from? or do i really need to steal my roomates room for a day?
I really want to do a stage 1 install. i've messed around with Kubunto for a while, and know my way pretty decently around the unix filestructure, although i still don't know how to do anything with bash. I want to do a stage 1 install so i can just get it over with, and learn my way around the system really well. so basically stage 2 or 3 tarballs are out.
I really want to do a stage 1 install. i've messed around with Kubunto for a while, and know my way pretty decently around the unix filestructure, although i still don't know how to do anything with bash. I want to do a stage 1 install so i can just get it over with, and learn my way around the system really well. so basically stage 2 or 3 tarballs are out.






Ie boot the livecd, set up the drives and misc configs, chroot in, bootstrap the system. Shut down if need be. Boot back up, do a few preliminary things to resume the session (like copying over the resolver cache, IIRC, and chrooting in again) and off you go with a system base compile. You can shut down again if you want. Now configure the kernel and compile it (compiling a kernel from scratch is 6 minutes on a 3.2GHz P4 with a -j2 flag; you'll spend more time actually configuring it