-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 14 March 2007 08:30, Cassiano Leal <[EMAIL PROTECTED]> was heard to say: > Really? I didn't know that. What are the basic steps to do it? I > was really eager to try sid, but didn't want to break my etch and > have to reinstall everything!
I've never actually done a chroot system. Sorry. But I can tell you that running Unstable where ever I run Debian over the last 7 years has been a great way to learn. Yes, the Udev and Xorg transitions were difficult, but hardly impossible. Everyone running Unstable goes through the changes at about the same time, and someone, somewhere, always has figured out how to resolve it. Remember, with a Linux-based system, it is exceptionally difficult to actually "hose" the system. Oh, sure, the wireless network might not come up, or as with the Xorg change X might not automatically start with the correct screen settings, but 99.9% of the time problems are predictable and easily fixed. Kernel updates, even from 2.0 to 2.2, 2.2 to 2.4, 2.4 to 2.6, have all been interesting, as in Chinese Curse, with 2.4 to 2.6 being the most interesting. But those are very rare and very well documented. Ah, the swap-storms of 2.4.9.... Is this the kind of thing I'll be telling my grandkids about while rocking on the porch, the way other people talk about hurricanes and floods and revenuers? I have to compile the MadWifi module for my wireless card. I have to do that each time the kernel or the driver is, so it takes an extra couple of minutes and a reboot. No big deal. About the only bit of serious advice I'd give in running Unstable is what I'd give anyone: Don't purge a previous, working, kernel until you know the new kernel is working. :^) One way I avoid cruft is that I use dselect, and make sure to "purge" all obsolete and other packages that are being removed. Maybe aptitude has a setting for that, I don't know. Curt- - -- September 11th, 2001 The proudest day for gun control and central planning advocates in American history -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRfgCfy9Y35yItIgBAQIyxQf/ZP1apOZNVtTayCcp73TN0NloQMvCZrHk oiSrTm7+SuV16Y4R15BxxAXGc++OXRskV6jm+J4tNJ4XdPhqul+84kOZWCX9W0l5 DN5x1wL39PdNa1f4Qb8h6LmDietkhSrngau4zMu4MNb2jrPoIhao7yKiu5wgqwU1 xMdYZjDhJbZD2BqO2UWy9BTTtMYXa9Qlis1Y3lx57arDLv5ZIF7BnNSdQ0VnXMi8 TNdKv7uHuJK3NxlpyE6Z6h0dm05rzkv1KiDnKGUhbyYfzJOKhhDuDZKJDfyiJeyA 7LHRx1Xr6mY2NKz22pyFD//UdVprjNlNcv1ZsiiCAV/Kn7/G1zA5eg== =m5Lm -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
