ns in both aligned and unaligned access forms. After these functions
> are there, I'd like us to unify use of them and remove driver-private
> versions.
Sounds good, though would be more appropriate unless
they're MD.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [
x27;m not sure if there
would be an advantage to moving the geom byte ordering functions to
(I guess phk didn't either).
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
e solved administratively.
Obviously he is intending his changes to be committed; hence, the
patches will be applicable to -CURRENT. This is an area where FreeBSD
is lacking. I can't understand why you wish to stifle his work.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Ashutosh S. Rajekar <[EMAIL PROTECTED]> writes:
[...]
> GPL conflicts with FreeBSD's artistic license.
[...]
FreeBSD is actually licensed under a much less restrictive license,
the BSD license. See any source file out of src/gnu for details.
Best regards,
Mike Barcroft
To Uns
calls _kldload(2).
o kldload(8) uses kldload(3)
o kldunload(8) uses kldunload(2)
The main advantage of this design is that it allows a Unix programmer
to utilize it. :)
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
; /* XXX: this doesn't work. */
%%%
If that's not black magic, I'd like to know what is. I'd like to
refer you to the kldload(2) manual, but unfortunately it doesn't
document how kldload(2) works. :(
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
o make me cringe. The way
in which it locates a module to load appears to be black magic.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
cussion mistakenly took place on a FreeBSD
mailing list intended for administrative-only issues, so it isn't
publicly available on our end. Luckily, a Samba mailing list was
on the CC line. You should be able to find it on the
<[EMAIL PROTECTED]> archives circa September 2001.
Best regards,
ver, No mixer control
> with any app that I have tried; aumix, xmms, etc. (which all worked before
> the sup)
You're half way there. Now, just add the name/model of your sound
card, when it broke, and you've got a PR.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL
Paul Halliday <[EMAIL PROTECTED]> writes:
> My soundcard on my lappy has been broken since 4.4. And to be
> brutally honest, it's really starting to piss me off.
Enough to open a PR?
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &qu
4.4. Care to
elaborate?
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
sition of Webmin by Caldera, all past and future
versions of Webmin are available under the BSD license."
Perhaps Caldera would be interested in releasing this gem into the
open source community.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Rafter Man <[EMAIL PROTECTED]> writes:
> 2. I hope that in the furture the FreeBSD developers will rewrite the system in C++.
I think you're alone on that one.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers&
Warner Losh <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]> Mike Barcroft writes:
> : 386 support has been removed from -CURRENT. -CURRENT also doesn't
> : support 486SX's out of the box, one is required to load a kernel
> : module from the loader
in a cracker jack box should be able
> to click the 'use an obscene amount of memory to make everything
> faster' button, without having to understand the 300+ things he
> could tune in a kernel, or loader.conf, or whereever else you can
> set things.
Great, I'd love to s
n removed from -CURRENT. -CURRENT also doesn't
support 486SX's out of the box, one is required to load a kernel
module from the loader if they need FPU emulation.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Wilko Bulte <[EMAIL PROTECTED]> writes:
> On Wed, Dec 05, 2001 at 11:51:02AM -0500, Mike Barcroft wrote:
> > Jim Durham <[EMAIL PROTECTED]> writes:
> > > Duh... right. OGS..(Old Guy Syndrome). I actually just did a cvsup to
> > > RELENG_4_4 and it didn
ecurity fixes only. Consider using -STABLE if you
require additional improvements.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
e to -java and one to -hackers.
>
> I'm open to other ideas on how to get this port committed.
The best advice I can give is to just be patient.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
riate discussion for -hackers so you're unlikely to
find a response here.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
er
>
> If I didn't want syslogd to log something, I would not have it in
> syslog.conf.
syslog.conf would require fields for user:group and permissions in
order for that to work, otherwise syslogd would have no idea how you
want your log files created.
Best regards,
Mike B
Mike Barcroft <[EMAIL PROTECTED]> writes:
> void <[EMAIL PROTECTED]> writes:
> > On Fri, Oct 26, 2001 at 08:04:36PM -0700, Kris Kennaway wrote:
> > > I assume you mean "as soon as the configuration file is modified"?
> > > That would be a big viol
ation dance goes something like:
>
> mv log log.0
> touch log
> kill -1 `cat /var/run/syslogd.pid`
> gzip log.0
>
> I'm suggesting that the "kill" could be left out if syslogd got the same
> smarts as "tail -F".
I recommend using newsyslog(8) f
gards,
Mike Barcroft
strnstr.diff
Add a new libc function, strnstr(3), which allows one to limit the
number of characters that are searched. This is especially useful
with file operations and non-NUL terminated strings.
Index: lib/libc/string/Makefil
. 1.68 (and Rev 1.36 of Makefile)? You will
ofcourse have to relogin to see whether the w(1) output has changed.
BTW, I can't reproduce this problem locally. Is there any special
about your local configuration, particularly regarding PAM?
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
?
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Mike Barcroft <[EMAIL PROTECTED]> writes:
> I would appreciate comments on the following patch:
> http://testbed.q9media.net/freebsd/whois.20010622.patch
>
> It does the following:
>
> o Implement recursive IP Address searches based on the results of
> a query to A
you want to find out who owns an IP block, you want to type
'whois (dotted-quad)' without having to know which country it was assigned
to. Similarly, if you want to know who owns a .com, you're not going to be
required to know which registrar they chose. whois(1) is an information
gathe
e expected results.
[Requested by joe and phk]
o Update documentation to reflect this.
o Clean up some grammar nearby.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
this work. From looking at
your patch, your using an old copy of my work. The newest one is available
at: http://testbed.q9media.net/freebsd/whois.patch and will be committed
very-shortly-now(tm).
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
30 matches
Mail list logo
