well if you open /etc/apt/sources.list and change the instances of "testing" to "sarge", then when sarge gets released in a month you'll automatically be moved to the "stable" sarge without even knowing it
Nice trick....am just looking at upgrading the kernel at the mo, there seems to be a few 2.6.* ones out (currently on 2.6.3)Originally Posted by directhex
Also trying to find out where all my mem has gone, it was reporting 404mb used......which carn't be right can it ?
btw the system feels quicker, even if the boot up is slow. And thats on my old clunking 8.6Gb hdd i am using at the mo for testing
Originally Posted by directhexHelp !Code:#deb file:///cdrom/ sarge main #deb cdrom:[Debian GNU/Linux testing _Sarge_ - Official NetInst Snapshot i386 Binary-1 (20040430)]/ unstable contrib main #deb http://security.debian.org/ stable/updates main contrib deb cdrom:[Debian GNU/Linux testing _Sarge_ - Official NetInst Snapshot i386 Binary-1 (20040430)]/ unstable contrib main deb ftp://debian.blueyonder.co.uk/pub/debian/ testing main deb-src ftp://debian.blueyonder.co.uk/pub/debian/ testing main deb http://security.debian.org/ stable/updates main contrib
just change "testing" to "sarge" like he said :|
first three are comented out, meaning they actually do nothing so ignore those ;x
#<command>
^^ thats commented out, does nothing, used for temporarily removing lines, and adding tips or whatever ;x
er, if your northbridge fan is humming loudly, disconnect it. _dont_ kick the side of the case, it _will_ break it.
i know :/
im using "unstable", which means i get it as its released.. i think :| got random sources for things like opera/apps in there too :>
er, if your northbridge fan is humming loudly, disconnect it. _dont_ kick the side of the case, it _will_ break it.
i know :/
Done
Cheers
"woody" is a link to the current "stable" version. when sarge replaces woody as stable, users who have "woody" rigidly set will stay with the old version, users with "stable" will suddenly jump from the old "woody" stable to "sarge" stable. equally, "sarge" is currently the "testing" version (think a beta for the next release). if a user has "testing" in their sources.list, then when "sarge" becomes equivalent to "stable", they will stick on "testing" - which will become a link to debian 3.2(?) testing, codenamed "etch". if their sources.list defines "sarge" rigidly, then they'll follow sarge into stability (and, in theory, into obsoletion in a couple of years).
a little confusing, reading that back. best way to think of it is that "stable" and "testing" always stay with those names, and when releases are made they shift along - e.g. once upon a time woody was testing & potato was stable; in a month from now sarge will be stable and etch testing - right this second, woody is stable, sarge is testing, potato is obsolete, and etch doesn't exist.
Well i followed that anyway
There are currently 1 users browsing this thread. (0 members and 1 guests)