In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes:
>In a message dated 10/13/01 3:15:31 PM Eastern Daylight Time,
>[EMAIL PROTECTED] writes:
>
>> >> etinc is not recommendable.
>> >>
>> >
>> >Everyone knows that PHK has a grudge against etinc. How childish.
>>
>> No, I don't have
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
> > dennis can be brusk, but he knows WAN better than anyone I've ever worked
> > with or for.
> >
> > Bryan
>
> 1) Dennis, who is etinc for all practical purposes, used to post
>off-topic and abusive messages on the freebsd.org mailing
>
The virtues or foibles of individual personalities are outside the
scope of this list. Anyone interested in further information is welcome to
search the archives of just about any of the FreeBSD lists. Meanwhile,
let's get back to our regularly scheduled bikesheds.
Thanks,
Doug
--
"
>-Original Message-
>From: Matt Dillon [mailto:[EMAIL PROTECTED]]
>Sent: Saturday, October 13, 2001 6:33 PM
>To: Ted Mittelstaedt
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: RE: RE: Imagestream WanIC-520 interface cards
>
>
>:on the Internet has been routers costing in the $100
Here's a wierd problem i ran into with regcomp, using the attached
test program linked against libefence. Am I missing something obvious,
other than the fact that it is a "not-so-correct" regex? Also, the
stranger part is that when the /10 is replaced with /11 (YMMV) the
problem doesn't occur.
[EMAIL PROTECTED] writes:
> I dont see how driving away commercial vendors with such a ridiculous
> attitude benefits the FreeBSD community. Very unprofessional.
Verbal abuse, violation of AUPs, and theft of service are also
unprofessional.
More to the point, FreeBSD isn't driving etinc.com away
[EMAIL PROTECTED] wrote:
> dennis can be brusk, but he knows WAN better than anyone I've ever worked
> with or for.
>
> Bryan
1) Dennis, who is etinc for all practical purposes, used to post
off-topic and abusive messages on the freebsd.org mailing
lists, under the address [EMAIL PROTECTED]
:on the Internet has been routers costing in the $100,000 range. Now, maybe
:BEST Internet is now wealthy enough that you can blow that kind of money on
:Cisco gear without thinking about it, but a lot of smaller ISP's are not.
:
:If you look at what happened last weekend on Sunday, and the numbe
In a message dated 10/13/01 3:15:31 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> >> etinc is not recommendable.
> >>
> >
> >Everyone knows that PHK has a grudge against etinc. How childish.
>
> No, I don't have a grudge against Dennis or Etinc, I merely point
> out that somebo
I am writing this mailing list in a desperate attempt to find out how to
restore my hdd with out loosing all the data on it. Recently I added two
additional hard drives to my freebsd 4.2 system. Once I booted up my system
and dl'ed some things with wget a bunch of errors occurred resulting in
"k
>-Original Message-
>From: Matt Dillon [mailto:[EMAIL PROTECTED]]
>Sent: Friday, October 12, 2001 10:40 PM
>To: Ted Mittelstaedt
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: RE: Imagestream WanIC-520 interface cards
>
>
>The Cisco 2600 series is great for T1's. A 2620 with
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Saturday, October 13, 2001 11:57 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: Imagestream WanIC-520 interface cards
>
>
>>
>> You know I really think your baiting me. You know perfectly well
Hi there,
I hope I am posting to the right place. I have
been a user only and not a kernel developer.
I built myself a custom kernel with the kernel
config file attached at the end of this email.
It works. However, if I remove some of the
unused NICs (for example fxp, r
On Sat, Oct 13, 2001 at 10:17:21AM -0700, Matt Dillon wrote:
> Nobody in their right mind uses a struct sockaddr_in or any other
> struct sock* type of structure without zeroing it first.
Nobody in their right mind requires to fill any data except these
used in given call. If no one
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes:
>> etinc is not recommendable.
>>
>
>Everyone knows that PHK has a grudge against etinc. How childish.
No, I don't have a grudge against Dennis or Etinc, I merely point
out that somebody who has caused so much grief in our mailing list
In a message dated 10/13/2001 2:51:55 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> >> sbei.com has single-port PCI cards with on-board csu/dsu. I could run
4
> >or
> >> 6 of those. and they support FreeBSD.
>
> They also have a 4 port card which is supported by FreeBSD (but
> > Erm, this would make this the first report of "interference effects"
> > I've ever heard, certainly. Doesn't make it untrue, just subject to a
> > bit more initial skepticism. Is this truly the only variable that's
> > changing? Are we sure that the drives in question aren't simply
> > b
In a message dated 10/13/2001 1:24:14 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
> >> You tell your supplier that since the 405 is being "phased out" that he
> >> should sell you a bunch of them at closeout prices.
> >>
> >
> >Perhaps the fact that the (incredibly slow) 2501 has b
On Sat, 13 Oct 2001, Paolo Pisati wrote:
>
> Someone can tell me why this piece of code doesn't work?
>
> #include
> #include
> #include
> #include
> #include
> #include
> #include
>
> int main(void) {
> int mib[5], *count;
Here you define 'count' as an uninitialised pointer to an inte
In the last episode (Oct 13), Paolo Pisati said:
> Someone can tell me why this piece of code doesn't work?
The sysctl(3) manpage says that arg 4 is a pointer to the length of the
storage area pointed to by arg 3. In fact, there's an example in the
manpage:
mib[0] = CTL_KERN;
In article <[EMAIL PROTECTED]>,
Matt Dillon <[EMAIL PROTECTED]> wrote:
> Nobody in their right mind uses a struct sockaddr_in or any other
> struct sock* type of structure without zeroing it first.
That's definitely true in reality, but I'm not sure it's a desirable
situation. It runs
+ <[EMAIL PROTECTED]>, Cyrille Lefevre wrote:
>> I add script call features to newsyslog. This adds a one field to
>> newsyslog.conf. When newsyslog processed log file, this can execute
>> arbitrary program.
>>
>> Situation to assume:
>> * For the log file which cannot use signal.
>> * Cases t
Someone can tell me why this piece of code doesn't work?
#include
#include
#include
#include
#include
#include
#include
int main(void) {
int mib[5], *count;
mib[0]=CTL_NET;
mib[1]=PF_LINK;
mib[2]=NETLINK_GENERIC;
mib[3]=IFMIB_SYSTEM;
mib[4]=IFMIB_IFCOUNT;
sysctl(mib, 5, co
:
:The following was initially formatted as PR, but I suppose it is reasonable
:to discuss first here. There were some vague mentions that sin_zero field
:of struct sockaddr_in may be used in future for some extensions; but this
:future is already expired;) without any real step.
:If the verdict
Vadim Vygonets wrote:
>
> We are working on integration of network-booted FreeBSD system to
> our envoronment. Naturally, different machines need different
> kernels, so we pass the kernel paramater in DHCP response.
> However, it gets overwritten in /boot/defaults/loader.conf. We
> decided tha
We are working on integration of network-booted FreeBSD system to
our envoronment. Naturally, different machines need different
kernels, so we pass the kernel paramater in DHCP response.
However, it gets overwritten in /boot/defaults/loader.conf. We
decided that commenting out the assignment of
In message <[EMAIL PROTECTED]> Yar Tikhiy writes:
: Oh, I see. Given that the only issue about the period in user names
: is compatibility, should pw(8) and adduser(8) still reject it or accept
: it and print a warning? I think printing a warning is better since
: the validity check is by no mea
The following was initially formatted as PR, but I suppose it is reasonable
to discuss first here. There were some vague mentions that sin_zero field
of struct sockaddr_in may be used in future for some extensions; but this
future is already expired;) without any real step.
If the verdict will be
On Sat, Oct 13, 2001 at 02:30:50AM -0700, Crist J. Clark wrote:
> On Sat, Oct 13, 2001 at 01:05:10PM +0400, Yar Tikhiy wrote:
> > On Fri, Oct 12, 2001 at 07:24:57PM +0300, Peter Pentchev wrote:
> > > On Fri, Oct 12, 2001 at 09:52:10AM -0600, Warner Losh wrote:
> > > > In message <[EMAIL PROTECTED]
On Sat, Oct 13, 2001 at 01:05:10PM +0400, Yar Tikhiy wrote:
> On Fri, Oct 12, 2001 at 07:24:57PM +0300, Peter Pentchev wrote:
> > On Fri, Oct 12, 2001 at 09:52:10AM -0600, Warner Losh wrote:
> > > In message <[EMAIL PROTECTED]> Yar Tikhiy writes:
> > > : Is there any reason to omit the period ('.'
On Fri, Oct 12, 2001 at 07:24:57PM +0300, Peter Pentchev wrote:
> On Fri, Oct 12, 2001 at 09:52:10AM -0600, Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Yar Tikhiy writes:
> > : Is there any reason to omit the period ('.') from the list of valid
> > : characters? With the period included
Thank you Terry for your comments!
On Fri, Oct 12, 2001 at 11:31:01AM -0700, Terry Lambert wrote:
> Yar Tikhiy wrote:
> >
> > The current utmp(5) manpage language (not markup)
> > has a number of drawbacks and errors:
> >
> > o There is no information for programmers on the actual structure
> >
In message <[EMAIL PROTECTED]>, Len Conrad
writes:
>
>http://www.sbei.net/hw400p.htm
I am pretty sure that the musycc driver in FreeBSD almost supports
this card. This is the SBE card which almost matches the old
LMC 1504 card.
I've tried to make them send me one so I could adapt the driver
bu
33 matches
Mail list logo
