Dale Scheetz <[EMAIL PROTECTED]> wrote:
> It seems to me that we have accepted non-modified source as DFSG compliant
> as long as modified binaries are not restricted.
We allow exceptions to point 3, as long as point 4 is satisfied
(explicit permission to distribute software built from
modified so
I'm having a problem sending mail to [EMAIL PROTECTED],
the host name doesn't have an MX record, and appears to have
a dynamic ip address. The mail relay being used
(mail.rdu.bellsouth.net) also doesn't appear to know anything
about this host name.
--
Raul
--
To UNSUBSCRIBE, email to [EMAIL PR
>>This is a draft.<<
I've written a document which touches on what I feel are important
meta-policy issues. It's a little bit of history, a little bit of
speculation, and a bit of an essay on how I think of debian.
I'm sure other people have different ideas. I hope none of what
I've written mak
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Actually, when Debian was formed it had only one developer,
> and no one could contribute packages, since that would have diluted
> the distributions tight integration. This bazaar thing has evolved.
My memory doesn't extend back that far, nor
Buddha Buck <[EMAIL PROTECTED]> wrote:
> Reading your draft, I see discussion of the importance of the goals,
> but not the importance of the standards -- or at least, not in as many
> words.
Fair enough.
Do you think the small change you recommended satisfy this need? Or are
you asking for some
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I remember Debian 0.04. Basically, it was what we'd nowadays term "base +
> bootfloppies" - an minimalistic base system on which to build the
> distribution. Even then, mailing lists were central to development, and
> development was a group effort.
T
Marcus Brinkmann <[EMAIL PROTECTED]> wrote:
> Am I the only one reading the following in the way that derived works are
> forbidden?
>
> " ...provided that in all above cases Seyon is intact
> and is not made part of any program either in whole or in part [...]."
We need explicit permission to
It seems to me that bug #21998 against xbase (xbase provides a manpage
for Xnest) should be promoted to severe: while this bug exists it's
impossible to install xnest.
Am I way off base here?
--
Raul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contac
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> I am interested in something way more fundamental to the project than
> the mere next release. Unless we thing beyond the next quarter, and
> if we fail to make more or less radical changes, we are doomed to
> repeat the pattern of past releases.
Y
Craig Sanders <[EMAIL PROTECTED]> wrote:
> BTW, the fact that you don't understand sendmail doesn't prevent others
> from doing so.
The problem with sendmail isn't that it's difficult to understand, it's
that it rewrites headers, by default. This introduces a whole class of
rather subtle bugs tha
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Awhile ago I read here of a package someone made called (I think) xteddy,
> which was replacement login screen for X.
Er.. that's not quite what xteddy is.
--
Raul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trou
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Since people want to discuss goals, let us get this over and
> done with. Email me goals, and I promise to have a 100 by the
> weekend. Then maybe we can get off and try and actually *DO*
> something, like design and implementation, rather than
Joost Witteveen <[EMAIL PROTECTED]> wrote:
> OK, that may well be true. But still the text of the GPL is clear:
> you are not allowed to change it, whether you change the name of your
> cahnged version or not.
You're saying that all those people who have licensed their software
under modified vers
Jules Bean <[EMAIL PROTECTED]> wrote:
> Talked myself into a corner. Someone dig me out?
Hmm, you raised some good points I hadn't thought about...
How about this quote:
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrend
On 5/5/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> Sorry to spam debian-devel -- and with a long message containing long
> paragraphs too, horrors! -- in replying to this.
Who is sorry? How sorry?
Let's assume, for the sake of argument, that this sorry-ness is not
something that matte
On 5/6/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> On 5/6/05, Raul Miller <[EMAIL PROTECTED]> wrote:
> > On 5/5/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> > > > On Wed, May 04, 2005 at 11:51:51PM -0500, Peter Samuelson wrote:
> >
On 5/6/05, Humberto Massa <[EMAIL PROTECTED]> wrote:
> ??? Let's try again: '' The GPL tries to define "work based on the
> Program" in terms of "derivative work under copyright law", and then,
> after this definition and a colon, it tries to explain what is a
> "derivative work under copyright law
On 5/6/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> On 5/6/05, Raul Miller <[EMAIL PROTECTED]> wrote:
> > On 5/6/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> [snip]
> > > Second sentence in Section 0: The "Program", below, refers to
On 5/9/05, Humberto Massa <[EMAIL PROTECTED]> wrote:
> You can't re-state something saying a different thing. GPL#0 says
> that "a work based on the Program" is "a derivative work under
> copyright law", and then says "that is to say, a work
> containing...", which is NOT a re-statement of a "deriv
On 5/10/05, Humberto Massa <[EMAIL PROTECTED]> wrote:
> Raul Miller wrote:
> >That's another re-statement of what "a work based on the Program"
> >means.
> >
> The GPL just equated the two, before the colon! It states, clearly, that
> the "a w
On 5/10/05, Glenn Maynard <[EMAIL PROTECTED]> wrote:
> In the past, UW has (in my opinion) played deliberate word games to
> retroactively revoke the Freeness of a prior Pine license, and this license
> is clearly non-free *without* any such stretching or contriving.
I don't think the issue at tha
On 5/11/05, Peter Samuelson <[EMAIL PROTECTED]> wrote:
> > The GPL did not use the word "equals".
> > Neither "that is to say" nor "namely" are equal to "equals".
>
> Are we to understand that your argument hinges on such fine semantic
> distinctions as claiming that "that is to say" does not conn
On 5/11/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> So I'm not going to say that your point of view isn't perfectly valid
> as your own point of view; but I don't have any reason to believe that
> it's a good predictor of how a court case involving the FSF suing
> FooSoft for linking agains
On 5/11/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> On 5/11/05, Raul Miller <[EMAIL PROTECTED]> wrote:
> > Of course, a court case does not have to be argued that way.
> No, but if it's to have a prayer of winning, it has to be argued in
> terms of the law
On 5/11/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> Fine. I have been goaded into rebutting this specimen.
Most of this is focused on contract law issues. I've written a
separate post suggesting the obvious alternative (Tort law)
> > Since Section 0 says that the GPL grants you license
On 5/18/05, Roberto C. Sanchez <[EMAIL PROTECTED]> wrote:
> That is completely not possible. Once you offer (and someone accepts)
> code under the terms of the GPL, they are for evermore entitled to use
> *that* code under the GPL.
There are some exceptions to this. For example, if you're not th
On 5/19/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> The GPL is anomalous in that the drafter has published a widely
> believed, but patently false, set of claims about its legal basis in
> the "FSF FAQ".
For the record, I disagree that this faq is "patently false".
It is, in places, a bi
> > For the record, I disagree that this faq is "patently false".
> >
> > It is, in places, a bit simplistic, but I wouldn't advise anyone
> > delve into those fine points of law unless they've retained
> > the services of a lawyer (at which point the FAQ is merely
> > an interesting commentary --
On 5/19/05, Michael K. Edwards <[EMAIL PROTECTED]> wrote:
> Perhaps that is indeed what you would do. I don't consider lawyers to
> be the only persons capable of reading the law for themselves. They
> are the only ones authorized to offer certain forms of legal advice
> and legal representation,
On 6/12/06, Theodore Tso <[EMAIL PROTECTED]> wrote:
The d-l list has a problem which is shared by many Debian mailing
lists (including debian-vote and debian-devel, and I'm sure it's not
limited to them) which is that far too many people subscribe to the
"last post wins" school of debate. People
Ian Murdock:
No, I'm not saying this at all. I'm saying that fairly soon our
primary emphasis (from a development point of view) will be the ELF
distribution. We'll still update the a.out distribution, of
course, but it'll become less and less of a priority from a
development point
Costa D Rasmussen:
I wish we had setterm. I noticed it was missing and thought I must
be ignorant about how to do without it.
What's the drill here? Do we need to lobby the author, write a clone?
setterm was written by Ted Ts'o. He thought it was such a trivial
program that it didn't
For what it's worth:
I've been pretty strung out lately (illness, deadlines, lack of
sleep). Please take anything I mailed out yesterday with at least a
grain of salt. [Not that you shouldn't in any event, but especially
for Sep 28 95].
Sorry about that.
--
Raul
Ian Jackson:
: Changing package names is usually a bad idea unless there's a good
: reason.
Or, more generally, inventing new interfaces where existing interfaces
will suffice is usually a bad idea unless there's a good reason.
: IMO the real solution is to have a real FTP method for dselect that
Ian Jackson:
This is where the problem starts :-). Obviously this can be done
fairly easily if you're willing to have the user download a list of
all the files included in every package, plus their sizes. I don't
think that's reasonable, though; even compressed, the Contents file
f
Dirk Eddelbuettel:
I don't want to take them away from anyone, not even from Emacs
specialists. I simply want to have the option of installing them
or not.
Well, you could delete them.
$ (cd /usr/lib/emacs/site-lisp/w3; for x in *.elc; do rm `basename $x c`; done)
If I want to read
Package: dpkg
Version: 1.0.5
If I start up dselect, choose "select", and hit return without making
any changes, I wind up with the following screen. I am not able to
fathom the purpose of this screen, nor am I particularly interested in
removing these packages from my system. [Of course, it's pl
This mechanism, while it might be convenient for some people, looks
very noisy for people without mime support.
I'd recommend that there be a new mailing list to support this kind of
traffic.
Also, there'd need to be some kind of convenient mechanism for
developers without intrinsic mime support
Ok... so what's RPM? Anyone know? Any lessons to learn here? Or
people to cooperate with?
--
Raul
Date: Thu, 19 Oct 1995 10:38:21 -0400 (EDT)
From: Erik Troan <[EMAIL PROTECTED]>
To: linux-alpha@vger.rutgers.edu
Subject: Red Hat Alpha Packages
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; char
I think that debian should include umsdos support.
Here's what's needed:
(1) a kernel with umsdos support compiled in
(2) the utility umssync
Also, umsdos pulls a stunt for the root partition -- for this case the
subdirectory that, under the msdos file system, would be named "linux"
is recast as
On a newly created (though slightly fudged) debian system, I'm getting
the message:
dpkg: cannot scan updates directory `/var/lib/dpkg/updates/': No such file or
directory
when I try and use dpkg (-i or -C, for instance).
/var/lib/dpkg/updates/ exists and is empty.
--
Raul
I'm trying to puzzle out /bin/perl
On a new system today, I tried to run perl and ran into problems
because /usr/lib/libdb.so.1 wasn't available. Can anyone tell me if
I'm doing something wrong or if it's the system that's wrong?
Thanks,
--
Raul
Here's an strace of dpkg failing. [Remember, this is on an empty
directory.]
Notice especially the line that reads:
readdir(4, 0x48000) = -1 ENOENT (No such file or directory)
I don't have a clue where that 0x48000 argument is coming from, but it
looks like it's corrupt
I had written:
> On a newly created (though slightly fudged) debian system, I'm getting
> the message:
> dpkg: cannot scan updates directory `/var/lib/dpkg/updates/': No such file
or directory
> when I try and use dpkg (-i or -C, for instance).
You replied:
Here is the relevant bit
Ok, so here's how things look to me at present:
dpkg is failing because of an ENOENT error return from scandir(3).
scandir is getting this error value from readdir().
I do not know enough about libc to easily determine whether the
readdir() used by scandir is readdir(2) or readdir(3). However,
One more bit of information: this problem occurs with libc-4.6.27
--
Raul
This problem definitely occurs in the umsdos file system code.
Further investigation indicates it also occurs in the msdos, nfs, and
smbfs file system code.
I'm reassigning this bug to the image package (or should it be the
source package? modules?).
I'll be submitting a patch in a few hours.
There's a problem with the umsdos file system that prevents scandir(3)
from working right -- it gives ENOENT instead of EOF upon successful
termination. This occurs because readdir returns ENOENT upon reaching
the end of the directory. The msdos file system has the same
problem. Here's a patch:
Turns out smbfs and nfs are clean -- it's only the msdos file systems
which have this problem.
--
Raul
I (Raul) wrote::
> > --- linux-1.3.29/fs/msdos/dir.c.distThu Oct 26 18:11:01 1995
> > +++ linux-1.3.29/fs/msdos/dir.c Thu Oct 26 18:12:34 1995
> > @@ -86,7 +86,7 @@
> > filp->f_pos = 0;
> > }
> > if (filp->f_pos & (sizeof(struct msdos_dir_entry)-1))
> > -
I just sent a bug report to debian-bugs stating that I was going to
submit a bug report on /sbin/clock for the miscutils package. I've
not received an ack on that bug report, and might not check my mail
again till tomorrow.
This is just a note that I'm not going to submit a miscutils bug
report.
Package: timezone
Version: 7.8-1
It looks like something's wrong with the timezone files. I started
poking around when I noticed that my time was daylight savings time.
I could have sworn that it was set right yesterday (I remember setting
a battery powered clock by my computer -- this clock is s
Bill Mitchell:
In my own packages, I've been trying to provide debianized docs
which change references to /usr/local to just plain /usr where it's
clear from the context that this would be incorrect on a debian
system. I've come to think that even this amount of twiddling the
upstre
Chris Fearnley writes ("Bug#1886: cern-httpd 3.0-4: a couple of bugs"):
> In http-conf, section "Users' Public HTML Directories", says that the
> default location for users' pages is in public_html, but the script
> sets the default to public-html.
Ian Jackson:
I'd be inclined to chan
Alvar Bray:
I have heard several other people say they have had corrupt
database files - how do they get corrupted? I have never managed to
corrupt mine (but then I, as the package maintainer, wouldnt would
I)
I imagine one technique might be to have the file system get full
during a d
Package: tcl
Version: 7.3
Revision: 4
tcl.h is in /usr/include/tcl -- yet there are no other files for this
directory. Seems to me it would make more sense to have just plain
/usr/include/tcl.h
--
Raul
Package: tk
Version: 3.6
Revision: 5
tk.h is missing from this development package. This makes in
difficult to build programs which wish to link with tk.
--
Raul
Bill Mitchell:
I think we need a good way to deal with this general situation
which is simple enough to use not to need guru advice from the dpkg
designer.
I agree -- typically the best way of dealling with this situation is
better documentation.
Of course, where documentation fails (as
Martin Schulze:
So the bugreport can be closed, right?
http://www.eg.bucknell.edu/~quinlan/fsstnd/1.2/fsstnd-5.6.html";>
No, wtmp goes in /var/log.
--
Raul
Package: metamail
Version: 2.7
Revision: 1
metamail's mime.types file specifies a program called xloadimage. This
program is not on my machine, and the control file for metamail doesn't
suggest any optional packages that might have this program.
--
Raul
minor correction: it is /etc/mailcap that refers to xloadimage (not
mime.types).
--
Raul
In my Tcl/Tk packages, I have conformed to what I think is the
official Debian convention and renamed the source directories from
to -. Unfortunately,
this causes gratuitous changes in other packages which need to access
the Tcl/Tk source directories. Since I try to make my Tcl/Tk
Raul Miller:
> Make sure that dselect still works right during the initial
> installation.
Mike Dorman:
I'm not sure what you're trying to say here. I mean, I understand
what you're saying, I'm just not sure what scenario you envision
such that this is an
OOPS...
On a retry, I find that the cdtool package was only compressed once.
My fingers must have slipped or something.
I hate it when I make a mistake in a bug report.
--
Raul
A number of people have attempted or succeeded in using
dpkg-nondebbin or a dpkg compiled on their local systems to install
Debian without using the bootstrap floppies. As far as I am aware,
this will yield a system that is broken in various ways (non-debian
files in the system direc
Something ought to be done though, since more(1) can't be made to
go backwards through manpages. This is rather a serious
deficiency.
Perhaps /bin/pager, done by update-alternatives ? Hmm, not too good.
Another option might be to have man point more at the catman file
rather than at
Perhaps we should adopt a different naming convention for unreleased
versions. E.g. instead of 1.0, call it 0.93+0.07, or 0.9x-unstable.
--
Raul
Another possibility is to have an unreadable directory named 1.0, with
instructions in the README file on how to navigate through it. The
idea being, if you don't read the instructions you don't see the
files.
--
Raul
Emilio C. Lopes:
IMHO, the problem is with "more" not with "man". One must not try
to adapt a good program just to make it work together with a
deficient one (still IMHO, of course).
This is more a matter of interface definition than anything else.
more can go backwards only on seekable f
Package: miscutils
Version: 1.3
Revision: 5
run-parts should probably not do what it normally does, when a laptop
doesn't have AC power. This could be implemented with something along
the lines of:
die "helpful message\n"
unless system "grep 'AC: off line' /proc/apm 2>/dev/null";
Presum
Can someone point me at the cannonical source for RPM and its
documentation? [My net connection is a bit flakey at the moment.]
Thanks,
--
Raul
I've sent a similar file to Ian, but I'm not sure if he received it.
Since the bug isn't closed, I'm taking the liberty of resending this
report, with a broader distribution.
Ian Jackson:
Err, boggle. Can you repeat this ? I can't (of course).
I'd like to see the output of
dpkg -D33
What does AC power have to do with run-parts ??
run-parts is just a utility to run all the scripts in a directory.
I think you should think where else this problem should be solved -
possible the answer is to modify your /etc/crontab.
Yes. On second thought I shouldn't be running cr
Juhana K Kouhia:
umsdos with windows '95 filesystem might be a problem... With
linux's msdos-fs I were not able to delete a directory; only got
'directory is not empty'-message even the directory were empty.
Are you sure this is because of w95?
You can also get a directory into this sta
apache-httpd provides httpd (as does cern-httpd) so dpkg won't
install one until the other is removed.
This isn't completely optimal (for the people who want to use apache
but also need a proxy server). Ideally, someone should write up a
mini-howto on how to work around this simplicity feat
Raul Miller:
> I think there's a good answer to this question, but I doubt the
> above workaround to the current package implementation of cron
> will occur to very many people.
Ian Jackson:
How about taking cron out of rc*.d ?
Plausible.
Remember, this is a space-
Simon Shapiro:
And why do we want this brain dead file system (which even M$ does
not use for its own 1980 eras OS's) to boot a Unix O/S with?
Please note that we shouldn't drop a user base just because Microsoft
has stopped supporting them.
More to the point, while "DOS" is a lousy operati
Richard Kettlewell:
Actually I think it would be a good thing if we could support
Debian entirely over UMSDOS - being able to run Linux without
having to mess around repartitioning hard discs is going to make a
lot of people a lot more willing to try it.
Unfortunately, UMSDOS isn't rea
Since I don't really have anything invested in this debate, I'll
throw in my last two cents and shut up. It seems to me that
changing the very few packages which don't already conform to such
a naming scheme would be much less disruptive than renaming every
package.
Also, a cheap w
Is there any point in establishing an init runlevel for "undocked"
operation - that is, using a laptop away from AC power? Some
laptops are capable of sensing when they go on and off of AC and
could change the run level on their own. I can think of situations
where you would want cr
Once we decide on a package naming standard, we should tell the
rest of the free software world what it is and encourage the
upstream maintainers to stick to that format.
Tell them without asking for comments? :-) [What was that about
committees?]
I lean towards Bill Mitchell's idea.
[
Brian White:
(the above is csh code... sorry!)
I've not been following this discussion very closely, but here's a
fairly literal translation of Brian's speedup to sh:
for FILE in `sed -e 's/\(.*\)-\([^-]*\)-\([^.-]*\)\.\([^-]*\)$/\1/\2/\3/\4/'`
do (
set `echo $FILE|tr / ' '`
i
Also, don't forget about architecture-independent binaries...
--
Raul
The US debian-bugs mirror seems to be fairing worse than normal...
Linkname: Not Found
URL: http://www.cps.cmich.edu/~streeter/debian-bugs/
Owner(s): None
size: 5 lines
mode: normal
--
Raul
Package: lynx
Version: 2.4.2
Revision: 1
lynx -source always fails.
--
Raul
Simon Shapiro:
How many people never compile their kernel and why?
I generally try and use a debian kernel image until I have a specific
reason not to. Then, I generally try to use the debian source until I
have a specific reason not to. Then, I generally try to use one of
Linus's snap shots
Matthew Bailey:
> For those out there that are interested. I will make space available for
> these ports, and allow each group to maintain uploads for the subtree.
>
> Please contact me if you are in need of an account for this use.
Ian Murdock:
Please don't do this. I'd rather t
Ian Murdock:
I doubt there'll be a substantial number of architecture-neutral
packages; we can either copy or link them into all of the trees.
I suppose this depends on what you mean by substantial... Here's a
list of packages that appear to be architecture-neutral, by cursory
examination o
Juergen Menden:
any package which needs to be compiled is of course not
arch-independent. on my system here (sunos, not debian ;-)) at
least the following are partially compiled:
> ii dvips5.58f 2TeX DVI-driver for Postscript
> ii fort77 1.6 1An f2
Ian Jackson:
Perhaps savelog should be moved into another package, then ?
This seems like a very good idea.
--
Raul
Raul Miller:
> I think this is a bug in the debian packaging mechanisms.
Ian Jackson:
Well, I could change dpkg so that it would barf in this situation,
rather than going ahead and removing the files from the earlier
package, but I think that would have been less helpful.
How ab
On May 13, David Engel wrote
> This problem is not that simple. With the current dpkg, there is no
> way to fix this even with a statically linked cp or ln. This is
> because dpkg will remove ld-linux.so.1 before any postinst script gets
> a chance to repair the damage.
How about putting somethi
Andy Mortimer <[EMAIL PROTECTED]> writes:
> > There has just been a long list of bugs against packages using `bashisms'
> > in their scripts, and I can certainly remember this issue coming up
> > before. But I don't know about anyone else, but I certainly have no idea
> > what features are availabl
On May 19, Brian C. White wrote
> 9259: j1 - Unresolved dependency report for j1
A fixed version of j1 is sitting in ~moth on master.debian.org
and has been since last week.
When I uploaded it, Incoming was not writeable, so I uploaded
a copy to my home directory and sent email to
On May 21, Chris Walker wrote
If I could get notification on a bug that I was particularly
concerned with, I guess I'd use it about once a quarter.
[That's about how often I run into bugs of that nature.]
It would probably save me about 8-16 hours per quarter.
--
Raul
--
TO UNSUBSCRIBE FROM
On May 20, Buddha Buck wrote
> Even with this, I can't get it to work. I'm running into the same
> problem Mr. Hess reported. Using dir: /debian dist: unstable, I have
> been able to get hamm, but no combination I've tried has allowed me to
> get hamm/non-free or hamm/contrib. I can get the p
On May 21, Darren/Torin/Who Ever... wrote
> I'd really appreciate your input on these issues, so that I can go
> forward with the Perl package.
Don't let this slow down your work, but: one thing I've been
itching for is a mechanism for CPAN installation to interoperate
with the Debian package mana
I'm putting together a couple of debian systems tonight, and I've
a couple problems
(1) floppy installation forces you to re-install all floppies if
there's any problems (e.g. checksum). So far, I've had one bad
base disk 2, two bad base disk 3s, and a bad disk 4. That means
that, for example, I
> '=?iso-8859-1?Q?Nicol=E1s_Lichtmaier?= wrote:'
> > So I say: PS1="[\\u] \\h:\\w\\$ " =D
On May 21, Chris Fearnley wrote
> No, PS1='[EMAIL PROTECTED]:\w\$ ' !
>
> I guess this will become a flame war. So I'd prefer to leave prompt
> alone. Or maybe the boot disks can have a dialog scr
Any chance of getting the ethernet drivers listed as "supported"
in the ethernet howto, but stored at cesdis.gsfc.nasa.gov instead
of in the main linux kernel, included in the base debian kernel
distribution?
--
Raul
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EM
201 - 300 of 513 matches
Mail list logo
