On Mon 03 Jul 2023 at 12:14:11 (+0100), debian-u...@howorth.org.uk wrote:
> Nicolas George wrote:
> > Roger Price (12023-07-03):
> > > Exactly my point that inanimate objects of which there are many
> > > examples are best known by numbers. Numbers so well known that
> > > songs are written about
On Mon 03 Jul 2023 at 10:42:15 (+0200), Roger Price wrote:
> On Sun, 2 Jul 2023, David Wright wrote:
>
> > Perhaps more people remember the A5 is the Holyhead Road, rather than
>
> Exactly my point that inanimate objects of which there are many examples
> are best known by numbers. Numbers so we
On Tue, 04 Jul 2023 11:33:20 +0100
"mick.crane" wrote:
> On 2023-07-03 23:34, Emanuel Berg wrote:
> > tomas wrote:
> >
> >> Or is "metric" one of these things spared by the
> >> Brexit Bonfire?
> >
> > It depends which gear your camp is since the metric system is
> > partly implemented and
jeremy ardley wrote:
> Or is "metric" one of these things spared by the
> Brexit Bonfire?
It depends which gear your camp is since the metric
system is partly implemented and partly co-exists
>>>
>>> British Standard Pipe still in use for plumbing and 1/4",
>>> 3/8" of speci
On 4/7/23 19:22, Emanuel Berg wrote:
mick.crane wrote:
Or is "metric" one of these things spared by the
Brexit Bonfire?
It depends which gear your camp is since the metric system
is partly implemented and partly co-exists
British Standard Pipe still in use for plumbing and 1/4",
3/8" of spe
mick.crane wrote:
>>> Or is "metric" one of these things spared by the
>>> Brexit Bonfire?
>>
>> It depends which gear your camp is since the metric system
>> is partly implemented and partly co-exists
>
> British Standard Pipe still in use for plumbing and 1/4",
> 3/8" of specification I forget f
On 2023-07-03 23:34, Emanuel Berg wrote:
tomas wrote:
Or is "metric" one of these things spared by the
Brexit Bonfire?
It depends which gear your camp is since the metric system is
partly implemented and partly co-exists
British Standard Pipe still in use for plumbing and 1/4", 3/8" of
spe
On Mon, 03 Jul 2023 23:34:50 +0200
Emanuel Berg wrote:
Hello Emanuel,
>Maybe the UK roads also follow a system.
They certainly did. The remnants can be seen still. Maybe wikipedia
has an article about it - I've not checked. A DDG (or other search
engine) lookup would find something.
--
Re
On Mon, 03 Jul 2023 23:33:23 +0200
Emanuel Berg wrote:
Hello Emanuel,
>days, they want their product or project to come up first if
>anyone Googles them.
What comes up first is the company with biggest wallet. Name, or
number, matters not one iota.
--
Regards _ "Valid sig separator
tomas wrote:
> Or is "metric" one of these things spared by the
> Brexit Bonfire?
It depends which gear your camp is since the metric system is
partly implemented and partly co-exists (e.g. on product
labels) in the UK ... and the supposed all-Metric world.
Everything, of course, Made in China an
Brad Rogers wrote:
>> But M5 can be a bolt size and a lot of other things as well,
>
> Context! When the conversation is about roads in the UK, why
> would *anyone* think bolt size?
I agree, but that's why people have a hangup with names these
days, they want their product or project to come up f
tomas wrote:
>>> But M5 can be a bolt size and a lot of other things as well,
>>
>> Context! When the conversation is about roads in the UK,
>> why would *anyone* think bolt size?
>
> Especially metric ones =:-o
Maybe the UK roads also follow a system. They were the first
guys having one, after
debian-user wrote:
No but I live in the UK and I know the A1, A2, A4, A5, A6
and many others, plus the M1, M4, M5, M6.
>>
>> But M5 can be a bolt size and a lot of other things as
>> well, while creative names may stay "more" unique.
>
> Nonsense. Curt's reply (which you cut when wrongl
On Mon, Jul 03, 2023 at 05:53:10PM +0100, Brad Rogers wrote:
> On Mon, 03 Jul 2023 18:28:49 +0200
> Emanuel Berg wrote:
>
> Hello Emanuel,
>
> >But M5 can be a bolt size and a lot of other things as well,
>
> Context! When the conversation is about roads in the UK, why would
> *anyone* think b
On Mon, 03 Jul 2023 18:28:49 +0200
Emanuel Berg wrote:
Hello Emanuel,
>But M5 can be a bolt size and a lot of other things as well,
Context! When the conversation is about roads in the UK, why would
*anyone* think bolt size?
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
On 2023-07-01 15:15, David Wright wrote:
You don't have to memorize all of Debian's codenames in order, do you?
There are about three or four in current use at any one time. (And the
release numbers might be monotonic, but they're not sequential, so
memorizing them would be just as tricky.)
Th
Emanuel Berg wrote:
> Curt wrote:
>
> >> No but I live in the UK and I know the A1, A2, A4, A5, A6
> >> and many others, plus the M1, M4, M5, M6.
>
> But M5 can be a bolt size and a lot of other things as well,
> while creative names may stay "more" unique.
Nonsense. Curt's reply (which you c
Curt wrote:
>> No but I live in the UK and I know the A1, A2, A4, A5, A6
>> and many others, plus the M1, M4, M5, M6.
But M5 can be a bolt size and a lot of other things as well,
while creative names may stay "more" unique.
But on the other hand there are many Emmas and Camillas, and
people tend
On 2023-07-03, debian-u...@howorth.org.uk wrote:
> Nicolas George wrote:
>> Roger Price (12023-07-03):
>> > Exactly my point that inanimate objects of which there are many
>> > examples are best known by numbers. Numbers so well known that
>> > songs are written about the number: historic US 66
Nicolas George wrote:
> Roger Price (12023-07-03):
> > Exactly my point that inanimate objects of which there are many
> > examples are best known by numbers. Numbers so well known that
> > songs are written about the number: historic US 66 [1], and in
> > France the historic N7 [2], a vacation h
On Mon, Jul 3, 2023 at 4:42 AM Roger Price wrote:
>
> On Sun, 2 Jul 2023, David Wright wrote:
>
> > Perhaps more people remember the A5 is the Holyhead Road, rather than
>
> Exactly my point that inanimate objects of which there are many examples are
> best known by numbers. Numbers so well known
Roger Price (12023-07-03):
> Exactly my point that inanimate objects of which there are many examples are
> best known by numbers. Numbers so well known that songs are written about
> the number: historic US 66 [1], and in France the historic N7 [2], a
> vacation highway.
And you know which one i
On Sun, 2 Jul 2023, David Wright wrote:
Perhaps more people remember the A5 is the Holyhead Road, rather than
Exactly my point that inanimate objects of which there are many examples are
best known by numbers. Numbers so well known that songs are written about the
number: historic US 66 [1]
On Sun 02 Jul 2023 at 11:30:39 (-0400), Dan Ritter wrote:
> David Wright wrote:
> > On Sat 01 Jul 2023 at 11:34:53 (-0400), Dan Ritter wrote:
> > > David Wright wrote:
> > > > On Mon 26 Jun 2023 at 17:22:04 (-0400), Jeffrey Walton wrote:
> > > > > On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter
> >
On Sun 02 Jul 2023 at 12:08:27 (-0400), Stefan Monnier wrote:
> >> > Unlike numbers, names are memorable and unambiguous (when well-chosen).
> >> This claim is far from evident and needs justification. The only
> [...]
> > Leaving aside that Titanic is the real name of the ship and not a
> > coden
Stefan Monnier wrote:
>> Leaving aside that Titanic is the real name of the ship and
>> not a codename, the evidence is all around you. Look no
>> further than your login name, or the name of your computer.
>> A huge slice of the Internet's infrastructure, DNS, is
>> concerned with allowing people
>> > Unlike numbers, names are memorable and unambiguous (when well-chosen).
>> This claim is far from evident and needs justification. The only
[...]
> Leaving aside that Titanic is the real name of the ship and not a
> codename, the evidence is all around you. Look no further than
> your login
David Wright wrote:
> On Sat 01 Jul 2023 at 11:34:53 (-0400), Dan Ritter wrote:
> > David Wright wrote:
> > > On Mon 26 Jun 2023 at 17:22:04 (-0400), Jeffrey Walton wrote:
> > > > On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter
> > > > wrote:
> > > > > riveravaldez wrote:
> > > > > > It would be pos
On Sat 01 Jul 2023 at 11:34:53 (-0400), Dan Ritter wrote:
> David Wright wrote:
> > On Mon 26 Jun 2023 at 17:22:04 (-0400), Jeffrey Walton wrote:
> > > On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter wrote:
> > > > riveravaldez wrote:
> > > > > It would be possible, as an alternative, to populate sour
On Sat 01 Jul 2023 at 18:00:01 (+0200), Roger Price wrote:
> On Sat, 1 Jul 2023, David Wright wrote:
>
> > Unlike numbers, names are memorable and unambiguous (when well-chosen).
>
> This claim is far from evident and needs justification. The only
> example I can think of is project number 401 w
On Sat, 01 Jul 2023 10:45:54 -0400
Stefan Monnier wrote:
> > But I can't see what's wrong with codenames. It's not just a
> > "tradition", it's standard practice in most fields of endeavour.
> > You slap a name on a project, and everyone knows what they're
> > talking about. Unlike numbers, names
On Sat, 1 Jul 2023, David Wright wrote:
Unlike numbers, names are memorable and unambiguous (when well-chosen).
This claim is far from evident and needs justification. The only example I can
think of is project number 401 which later became the product "Titanic". However
the name is not mem
David Wright wrote:
> On Mon 26 Jun 2023 at 17:22:04 (-0400), Jeffrey Walton wrote:
> > On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter wrote:
> > > riveravaldez wrote:
> > > > It would be possible, as an alternative, to populate sources.list with
> > > > '2021',
> > > > for instance, instead of 'bul
> But I can't see what's wrong with codenames. It's not just a "tradition",
> it's standard practice in most fields of endeavour. You slap a name on
> a project, and everyone knows what they're talking about. Unlike numbers,
> names are memorable and unambiguous (when well-chosen).
AFAICT codename
On Mon 26 Jun 2023 at 17:22:04 (-0400), Jeffrey Walton wrote:
> On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter wrote:
> > riveravaldez wrote:
> > > It would be possible, as an alternative, to populate sources.list with
> > > '2021',
> > > for instance, instead of 'bullseye', 'bookworm', etc.?
> > >
>
>> > DO NOT USE "stable" IN YOUR sources.list FILE!
>> And this is because... ?
> Because a full release upgrade is a process that requires planning and
> execution with intent. There are many steps to follow, in order to
> maximize the chances of it actually working, and not breaking your
> syste
On Mon, 26 Jun 2023 23:06:41 -0400
Greg Wooledge wrote:
> On Mon, Jun 26, 2023 at 10:51:36PM -0400, pa...@quillandmouse.com
> wrote:
> > On Mon, 26 Jun 2023 22:10:38 -0400
> > Greg Wooledge wrote:
> >
> > > DO NOT USE "stable" IN YOUR sources.list FILE!
> > >
> > And this is because... ?
>
[
On Tue, Jun 27, 2023 at 08:51:07AM +0200, Erwan David wrote:
> Le 27/06/2023 à 05:06, Greg Wooledge a écrit :
> >
> > A lot of people who run stable releases use automatic upgrades. This
> > is a thing that will attempt to run "apt update" and "apt upgrade"
> > automatically for you in the backgr
Le 27/06/2023 à 05:06, Greg Wooledge a écrit :
A lot of people who run stable releases use automatic upgrades. This
is a thing that will attempt to run "apt update" and "apt upgrade"
automatically for you in the background.
If you use the "stable" label in your source.list file, and if you als
table to refer to the current and
> > > > previous releases
> > >
> > > This sounds good in theory, but in the sources.list file, Debian
> > > defaults to the code names, not "stable"/"testing"/"unstable".
> > > Fixing this req
On Mon, Jun 26, 2023 at 10:51:36PM -0400, pa...@quillandmouse.com wrote:
> On Mon, 26 Jun 2023 22:10:38 -0400
> Greg Wooledge wrote:
>
> > DO NOT USE "stable" IN YOUR sources.list FILE!
> >
> And this is because... ?
Because a full release upgrade is a process that requires planning and
executi
but in the sources.list file, Debian
> > defaults to the code names, not "stable"/"testing"/"unstable".
> > Fixing this requires a manual edit.
>
> DO NOT USE "stable" IN YOUR sources.list FILE!
>
> EVER!!
>
> G!!!
>
On Mon, Jun 26, 2023 at 09:53:33PM -0400, pa...@quillandmouse.com wrote:
> > * Stable/OldStable/OldOldStable to refer to the current and previous
> > releases
>
> This sounds good in theory, but in the sources.list file, Debian
> defaults to the code names, not "s
On Mon, 26 Jun 2023 21:01:17 +0200
Nicolas George wrote:
[snip]
> Twenty five years ago I started naming my computers after the
> characters in an obscure French sci-fi duology. The names are still
> pretty much unique, but I have had trouble finding names for new
> boxes, especially since it ha
On Mon, 26 Jun 2023 17:04:57 +0100
Darac Marjal wrote:
>
> On 26/06/2023 09:18, Roger Price wrote:
> > I have difficulty remembering the Debian code names for releases
> > Buzz Rex Bo Hamm Slink Potato Woody Sarge Etch Lenny Squeeze Wheezy
> > Jessie Stretch Buster Bull
On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter wrote:
>
> riveravaldez wrote:
> > It would be possible, as an alternative, to populate sources.list with
> > '2021',
> > for instance, instead of 'bullseye', 'bookworm', etc.?
> >
> > We could have something like, 'Debian 2023 - Bookworm', so, preservin
riveravaldez wrote:
> It would be possible, as an alternative, to populate sources.list with '2021',
> for instance, instead of 'bullseye', 'bookworm', etc.?
>
> We could have something like, 'Debian 2023 - Bookworm', so, preserving
> tradition, but allowing '2023' to be used as an alternative re
On 6/26/23, Nicolas George wrote:
> ghe2001 (12023-06-26):
> (...)
> What works for Ubuntu is that their version numbers are really the year.
> We know what year we are in, usually.
It would be possible, as an alternative, to populate sources.list with '2021',
for instance, instead of 'bullseye',
On 27/06/2023 03:40, Kent West wrote:
Code-names are awesome. I prefer them to be something like "First" or
"Secundo" or "Twelve"
The wallpaper for Ubuntu Hardy Heron was exquisite.
--
Ash Joubert (they/them)
Director / Game Developer
Transient Software
On Mon, Jun 26, 2023 at 06:33:37PM +0200, Roger Price wrote:
> On Mon, 26 Jun 2023, Darac Marjal wrote:
>
The reason for Debian using code names - and it was one of the first Linux
distributions to use code names routinely - was very simple.
Debian 1.0 never happened. InfoMagic took a c
ghe2001 (12023-06-26):
> I've been using Debian for some 20 years, and I've had the impression
> that Ian started with the major characters in Toy Story and the names
> have moved toward the minor ones (no proof, just an impression).
That is the problem with major characters, there are a limited n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've been using Debian for some 20 years, and I've had the impression that Ian
started with the major characters in Toy Story and the names have moved toward
the minor ones (no proof, just an impression). I'm sure it seemed to be a good
idea at t
On Mon, 26 Jun 2023, Darac Marjal wrote:
As you can see, the intention of code names is so that developers
(of Debian) have a way to refer to an as-yet-unreleased collection of
packages. Once those set of packages are released (literally, put out there
in the wild), then they become a
On Mon, Jun 26, 2023 at 12:21 PM Charles Curley
wrote:
>
> On Mon, 26 Jun 2023 17:04:57 +0100
> Darac Marjal wrote:
>
> > OK, a question back at you, then: Why do you feel the need to
> > remember Debian codenames?
>
> Imprimis: Because you use the code names as
On Mon, 26 Jun 2023 17:04:57 +0100
Darac Marjal wrote:
> OK, a question back at you, then: Why do you feel the need to
> remember Debian codenames?
Imprimis: Because you use the code names as part of configuring
systems, e.g. in /etc/apt/sources.list
Secundus: Because some utiliti
On 26/06/2023 09:18, Roger Price wrote:
I have difficulty remembering the Debian code names for releases Buzz
Rex Bo Hamm Slink Potato Woody Sarge Etch Lenny Squeeze Wheezy Jessie
Stretch Buster Bullseye Bookworm Trixie and Forky.
It's much easier to remember that release numbers are
On 2023-06-26 at 11:40, Kent West wrote:
> On Mon, Jun 26, 2023 at 10:29 AM Arno Lehmann wrote:
>
>>
>> Also, I struggle with the names, always need to go to the project web
>> page or wikipedia if I need to look up which version has which name, and
>> it
ns, and thus my wish is to keep those code names, as
> inconsistent and hard to memorize they are. It's Debian, and I like
> it. I still have etchnhalf running on two old boxes, even :-)
Seeing how we're currently at a name that starts with `b`, maybe it's
a good time to switc
On Mon, Jun 26, 2023 at 10:29 AM Arno Lehmann wrote:
>
> Also, I struggle with the names, always need to go to the project web
> page or wikipedia if I need to look up which version has which name, and
> it's always a nuisance.
>
>
>
Code-names are awesome. I prefer
to the project web
page or wikipedia if I need to look up which version has which name, and
it's always a nuisance.
A small one, though. Also, I really like the Debian project, its
resulting software collections, and thus my wish is to keep those code
names, as inconsistent and hard to mem
On Monday, June 26, 2023, Charles Curley
wrote:
> On Mon, 26 Jun 2023 10:18:30 +0200 (CEST)
> Roger Price wrote:
>
>> Is there some reason why Debian still continues to invent and use
>> code names?
>
> At least use some sequence of code names with an order to them.
&
On Mon, 26 Jun 2023 10:18:30 +0200 (CEST)
Roger Price wrote:
> Is there some reason why Debian still continues to invent and use
> code names?
At least use some sequence of code names with an order to them.
Ubuntu's code names are in alphabetical order. Maybe the names of
t
On Mon, Jun 26, 2023 at 10:18:30AM +0200, Roger Price wrote:
> I have difficulty remembering the Debian code names for releases Buzz Rex Bo
> Hamm Slink Potato Woody Sarge Etch Lenny Squeeze Wheezy Jessie Stretch
> Buster Bullseye Bookworm Trixie and Forky.
>
> It's much eas
On Mon, Jun 26, 2023 at 4:18 AM Roger Price wrote:
>
> I have difficulty remembering the Debian code names for releases Buzz Rex Bo
> Hamm Slink Potato Woody Sarge Etch Lenny Squeeze Wheezy Jessie Stretch Buster
> Bullseye Bookworm Trixie and Forky.
>
> It's much easier t
I have difficulty remembering the Debian code names for releases Buzz Rex Bo
Hamm Slink Potato Woody Sarge Etch Lenny Squeeze Wheezy Jessie Stretch Buster
Bullseye Bookworm Trixie and Forky.
It's much easier to remember that release numbers are in a sequence 1.1 ... 14.
Quoting from Goo
On Sat, 2007-01-13 at 12:19 +0200, Andrei Popescu wrote:
> Greg Folkert: sorry for the CC, but you kept ignoring my other messages
> about this.
I am writing an "article" on this and doing research. I currently have a
massive document being worked upon. So far it is ~35 pages and growing.
The the
On Sat, 13 Jan 2007 16:28:47 -0700
Paul E Condon <[EMAIL PROTECTED]> wrote:
> OTOH, people who are involved in maintaining user documentation should
> avoid statements that would lead a new user to believe that the two
> types of names (release and code) are absolutely equivalent. They are
> not e
On Sat, Jan 13, 2007 at 12:19:08PM +0200, Andrei Popescu wrote:
> Greg Folkert: sorry for the CC, but you kept ignoring my other messages
> about this.
>
> Dear all,
>
> In the thread 'smooth upgrades' that was still running a few days ago
> there was the question
On Sat, 13 Jan 2007 13:54:50 -0800
Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
> > Now 'etch' has priority 990 vs 500 of sid. This will keep the system
> > running *unstable* (when etch is released apt will want to upgrade
> > to next testing).
>
> ummm... this, as I understand it, is not co
On Sat, Jan 13, 2007 at 12:19:08PM +0200, Andrei Popescu wrote:
> Greg Folkert: sorry for the CC, but you kept ignoring my other messages
> about this.
>
> Dear all,
>
> In the thread 'smooth upgrades' that was still running a few days ago
> there was the question
Hi,
On Sat, Jan 13, 2007 at 12:19:08PM +0200, Andrei Popescu wrote:
...
> Dear all,
>
> In the thread 'smooth upgrades' that was still running a few days ago
> there was the question of release names vs. code-names in the
> Default-Release option. The docs
...
>
>
Greg Folkert: sorry for the CC, but you kept ignoring my other messages
about this.
Dear all,
In the thread 'smooth upgrades' that was still running a few days ago
there was the question of release names vs. code-names in the
Default-Release option. The docs
http://www.debian.org/doc/m
Martin Fluch wrote:
>
> On Mon, 18 Oct 1999, Oki DZ wrote:
>
> > Where did hamm (?), slink, and potato come from? Toy Story?
>
> Jep.
>
> > When are we going to have buzz version?
>
> Dono (no expert in that :)
Debian 1.1 was 'buzz', 1.2 was 'rex' and 1.3 was 'bo'
On Mon, 18 Oct 1999, Oki DZ wrote:
> Where did hamm (?), slink, and potato come from? Toy Story?
Jep.
> When are we going to have buzz version?
Dono (no expert in that :)
Martin
--
If the box says 'Windows 95 or better', it should run on Linux, right?
Hi,
Where did hamm (?), slink, and potato come from? Toy Story?
When are we going to have buzz version?
Oki
> Two questions:
> 1. What's good about GNU libc?
> 2. Whose libc is libc5?
LIBC5 is GNU libc with substantial patches for Linux. LIBC6 is GNU libc with
the Linux support merged back in to the main source thread. GNU calls these
LIBC 1 and 2. We call it LIBC6 on Linux because our version numbers d
From: Vadim Vygonets <[EMAIL PROTECTED]>
> 1. What's good about GNU libc?
All Linux distributions without exception have decided to use it, as far as
I am aware. I think this is because H.J. Lu, the current Linux libc maintainer,
led the movement. The library will be used on, Hurd, and MkLinux.
>
On Apr 3, Douglas L Stewart wrote
> On Thu, 3 Apr 1997, Jason Gunthorpe wrote:
> > Can we use glibc NOW along with the normal c lib? I have a program that
> > will require the use of pthreads and it might be a good idea to use a
> > thread safe C library, I can likely get by without, but..
>
> li
On Thu, 3 Apr 1997, Douglas L Stewart wrote:
> On Thu, 3 Apr 1997, Jason Gunthorpe wrote:
>
> libc 6 hasn't been officially released yet and it'll be a little while
> before any distribution includes it as a stable package. I'd suggest just
> getting a normal pthreads package and being careful t
On Thu, 3 Apr 1997, Jason Gunthorpe wrote:
> Can we use glibc NOW along with the normal c lib? I have a program that
> will require the use of pthreads and it might be a good idea to use a
> thread safe C library, I can likely get by without, but..
libc 6 hasn't been officially released yet and
On Thu, 3 Apr 1997, Douglas L Stewart wrote:
[Clip about glibc]
> 3) Fully MT safe.
Can we use glibc NOW along with the normal c lib? I have a program that
will require the use of pthreads and it might be a good idea to use a
thread safe C library, I can likely get by without, but..
Thanks,
Jas
On Thu, 3 Apr 1997, Vadim Vygonets wrote:
> > The release after that will be Debian-2.0 . The major difference in 2.0
> > will be that it is based on GNU LIBC, known in Linux circles as "libc 6".
>
> Two questions:
> 1. What's good about GNU libc?
A million things.
1) Full internationalization.
On Wed, 2 Apr 1997, Bruce Perens wrote:
> The release after that will be Debian-2.0 . The major difference in 2.0
> will be that it is based on GNU LIBC, known in Linux circles as "libc 6".
Two questions:
1. What's good about GNU libc?
2. Whose libc is libc5?
Vadik.
--
Vadim Vygonets * [EMAIL P
27;d better stop it.
The next release is called Debian-1.3 . All Debian releases have code
names before they are released, the code names are chosen for "Toy Story"
characters, because I called 1.1 "buzz" and it became a tradition.
The release after that will be Debian-2.0 . The m
84 matches
Mail list logo
