8 juin 2021 13:15:50 Michael Gmelin :
>
>
> On Mon, 7 Jun 2021 22:35:20 +0200
> Baptiste Daroussin wrote:
>
>> On Mon, Jun 07, 2021 at 12:30:46AM -0700, Mark Millard wrote:
>>> On 2021-Jun-6, at 13:25, Mark Millard wrote:
>>>
Baptiste Daroussin wrote on
Date: Sun, 6 Jun 2021 10:53
On Mon, 7 Jun 2021 22:35:20 +0200
Baptiste Daroussin wrote:
> On Mon, Jun 07, 2021 at 12:30:46AM -0700, Mark Millard wrote:
> > On 2021-Jun-6, at 13:25, Mark Millard wrote:
> >
> > > Baptiste Daroussin wrote on
> > > Date: Sun, 6 Jun 2021 10:53:49 +0200 :
> > >
> > >> What has happende
On Mon, Jun 07, 2021 at 12:30:46AM -0700, Mark Millard wrote:
> On 2021-Jun-6, at 13:25, Mark Millard wrote:
>
> > Baptiste Daroussin wrote on
> > Date: Sun, 6 Jun 2021 10:53:49 +0200 :
> >
> >> What has happended:
> >> plan A: we migrated everything off mailman/pipermail seamlessly with
> >>
On 2021-Jun-6, at 13:25, Mark Millard wrote:
> Baptiste Daroussin wrote on
> Date: Sun, 6 Jun 2021 10:53:49 +0200 :
>
>> What has happended:
>> plan A: we migrated everything off mailman/pipermail seamlessly with
>> redirection
>> and so on. We patched the new archiver to produce the same file
Baptiste Daroussin wrote on
Date: Sun, 6 Jun 2021 10:53:49 +0200 :
> What has happended:
> plan A: we migrated everything off mailman/pipermail seamlessly with
> redirection
> and so on. We patched the new archiver to produce the same file names has
> pipermail
>
> Plan A worked fine up to a li
Hi Steve,
Am 06.06.21 um 01:13 schrieb Steve Kargl:
> On Sun, Jun 06, 2021 at 01:00:40AM +0200, Michael Gmelin wrote:
>>
>>
>>> On 6. Jun 2021, at 00:53, Steve Kargl
>>> wrote:
>>>
>>> It seems someone has tried to migrate the mailing lis
On Sat, Jun 05, 2021 at 05:43:01PM -0600, Warner Losh wrote:
> On Sat, Jun 5, 2021, 5:29 PM Steve Kargl
> wrote:
>
> > On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
> > >
> > > p.s. If you go to https://lists.freebsd.org/mailman/listinfo, click
> > FreeBSD-net and then "Archives
On 06/06/2021 00:28, Steve Kargl wrote:
Hundreds of emails from me are now gone or sufficiently hidden that
I cannot find them. More importantly, Bruce Evans often replied
with reviews of libm patch's I sent the list. Those reviews and
his detailed analysis of the libm code are now gone or suff
There is also this useful and efficient form of archive/mirror to include
in the update so that it does not remain broken for too long...
https://lists.freebsd.org/pipermail/freebsd-questions/2021-June/294104.html
https://lists.freebsd.org/archives/freebsd-hubs/2021-June/00.html
> On 6. Jun 2021, at 01:44, Warner Losh wrote:
>
>
>
>
>> On Sat, Jun 5, 2021, 5:29 PM Steve Kargl
>> wrote:
>> On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
>> >
>> > p.s. If you go to https://lists.freebsd.org/mailman/listinfo, click
>> > FreeBSD-net and then "Archiv
On Sat, Jun 5, 2021, 5:29 PM Steve Kargl
wrote:
> On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
> >
> > p.s. If you go to https://lists.freebsd.org/mailman/listinfo, click
> FreeBSD-net and then "Archives from mailman’s time", you get to a list that
> brings you to https://lists
On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
>
> p.s. If you go to https://lists.freebsd.org/mailman/listinfo, click
> FreeBSD-net and then "Archives from mailman’s time", you get to a list that
> brings you to https://lists.freebsd.org/pipermail/freebsd-net/. So the old
> ar
On Sun, Jun 06, 2021 at 01:00:40AM +0200, Michael Gmelin wrote:
>
>
> > On 6. Jun 2021, at 00:53, Steve Kargl
> > wrote:
> >
> > It seems someone has tried to migrate the mailing list archives
> > from mailman to some new fangle code. This has broken t
> On 6. Jun 2021, at 01:00, Michael Gmelin wrote:
>
>
>
>
>>> On 6. Jun 2021, at 00:53, Steve Kargl
>>> wrote:
>>>
>> It seems someone has tried to migrate the mailing list archives
>> from mailman to some new fangle code. This ha
> On 6. Jun 2021, at 00:53, Steve Kargl
> wrote:
>
> It seems someone has tried to migrate the mailing list archives
> from mailman to some new fangle code. This has broken the archives
> for at least freebsd-numerics@, freebsd-office@, freebsd-net@
>
> As a
It seems someone has tried to migrate the mailing list archives
from mailman to some new fangle code. This has broken the archives
for at least freebsd-numerics@, freebsd-office@, freebsd-net@
As a comparison, simply go to
https://lists.freebsd.org/mailman/listinfo
and follow the links to
On Sat, Apr 9, 2011 at 5:15 AM, Adrian Chadd wrote:
> Hi all,
>
> I've just organised a new mailing list for wireless related development,
> discussion and bug fixing.
>
> Please subscribe to freebsd-wirel...@freebsd.org and ask wireless related
> things there.
>
&
On Sat, Apr 09, 2011 at 11:15:51AM +0800, Adrian Chadd wrote:
>Hi all,
>
>I've just organised a new mailing list for wireless related development,
>discussion and bug fixing.
>
>Please subscribe to freebsd-wirel...@freebsd.org and ask wireless related
>things there.
>
Hi all,
I've just organised a new mailing list for wireless related development,
discussion and bug fixing.
Please subscribe to freebsd-wirel...@freebsd.org and ask wireless related
things there.
Although I (and others) keep an eye on the other mailing lists, you'll be
more likel
On Mon, Mar 21, 2011 at 08:17:23AM -0400, Etienne Robillard wrote:
> Google "cognitive dissonance" for more info...
Google "plonk" for more info.
mcl
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
On 21/03/11 08:12 AM, owner-freebsd-secur...@freebsd.org wrote:
> Your request to the freebsd-security mailing list
>
> Posting of your message titled "[CFR] Multiple remote and local
> vulnerabilities of high-speed USB WLAN
> ethernet devices using high-speed OFD
Hello everybody,
The last couple of months we've been seeing quite a lot of traffic on
several of the FreeBSD mailing lists (especially on current@) related to
compilers, linkers, debuggers, etc. This is why Brooks Davis and I
decided it would be a good thing to create a new mailing list. B
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Subscribe
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, Aug 18, 2001 at 05:18:55PM -0400, Buzz Megg wrote:
> I'm getting an error when attempting to send to [EMAIL PROTECTED] from an
> address that used to work.
>
> Has anything changed recently on the mailing list server?
Not that I know of.
But you should fix the nam
I'm getting an error when attempting to send to [EMAIL PROTECTED] from an
address that used to work.
Has anything changed recently on the mailing list server?
Thanks,
-a
- Transcript of session follows -
... while talking to hub.freebsd.org.:
>>>RCPT To:<[EMAIL PR
Add me to your mailing list !
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
> I am interested in joining the mailing list for freebsdcurrent.
>
> This can be e-mailed to:
> [EMAIL PROTECTED]
> or
> [EMAIL PROTECTED]
Hi,
I'm a mail robot for this list. Unfortunately currently I'm on vacation, so
your request could n
I am interested in joining the mailing list for freebsdcurrent.
This can be e-mailed to:
[EMAIL PROTECTED]
or
[EMAIL PROTECTED]
Thanks,
Aaron Pickett -- Scorch
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 11 Jan 2000, °í¹ü¼® wrote:
> how do i.? :)
http://www.freebsd.org/support.html#mailing-list
Chuck Robey| Interests include C & Java programming,
New Year's Resolution: I |
how do i.? :)
--MIME Multi-part separator--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Not this way.
Send email to "[EMAIL PROTECTED]" with the following two lines in
the body of the message:
subscribe freebsd-current
subscribe cvs-all
You should consider this action very carefully as you will start
receiving approximately 200 messages each day.
I would suggest that you only su
On Wednesday, 1 December 1999 at 16:40:33 -0600, tonymb wrote:
> HELLO MY NAME IS TONY. I HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP
>A SYSTEM WITH THIS OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO
>BENEFIT FROM THE EXPERIENCE OTHERS AND EXPERT
On Wed, Dec 01, 1999, tonymb wrote:
> HELLO MY NAME IS TONY. I HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP
>A SYSTEM WITH THIS OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO
>BENEFIT FROM THE EXPERIENCE OTHERS AND EXPERTISE TO MAKE MY TRANSITION
HELLO MY NAME IS TONY. I
HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP A SYSTEM WITH THIS
OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO BENEFIT FROM THE
EXPERIENCE OTHERS AND EXPERTISE TO MAKE MY TRANSITION SMOOTH.PLEASE USE
THIS E-MAIL ADDRESS [EMAIL PROT
Hello FreeBSD person!
We now have a mailing list for the discussion of the FreeBSD
Audit Project. Thanks to Jon Bresler, our postmaster!
All of you who want to contribute to this project, please
sign up. There was a very heartening response to the
announcement, and a few slowcoaches even got
[.]
> I removed the `set openmode passive' and got
[.]
How about ``set openmode active 5''. The problem you're seeing is
that the other side is `reflecting' you data back because it hasn't
yet turned ECHO off on the port. By the time the peer wakes up and
does something, everything's
Brian Somers writes:
> > Well, I'd hoped I'd be able to do a little more before bothering the list,
> > but...
> >
> > I'd last built world around the end of April, with no problems. I then
> > grew a fairly heavy workload, and so didn't get a chance to build world
> > again until 2 days ag
> Well, I'd hoped I'd be able to do a little more before bothering the list,
> but...
>
> I'd last built world around the end of April, with no problems. I then
> grew a fairly heavy workload, and so didn't get a chance to build world
> again until 2 days ago (May 24). During that time, somethin
Well, I'd hoped I'd be able to do a little more before bothering the list,
but...
I'd last built world around the end of April, with no problems. I then
grew a fairly heavy workload, and so didn't get a chance to build world
again until 2 days ago (May 24). During that time, something changed wi
> Yes, and:
>
> feral.com > ping freefall.freebsd.org
Separate problem - we're working on it. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Sat, 3 Apr 1999, Chuck Robey wrote:
> On Sat, 3 Apr 1999, Pierre Y. Dampure wrote:
>
> >
> > I know this is the -current list, but... I haven't received a single
> > message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup
> > just gave me a loads of commits today... this does
On Sat, 3 Apr 1999, Pierre Y. Dampure wrote:
>
> I know this is the -current list, but... I haven't received a single
> message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup
> just gave me a loads of commits today... this does not seem to be a
> local issue, since I receive -cu
I know this is the -current list, but... I haven't received a single
message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup
just gave me a loads of commits today... this does not seem to be a
local issue, since I receive -current normally (or so it seems, at
least).
Any clues?
47 matches
Mail list logo
