On Mon, Mar 27, 2000, Doug Barton wrote:
One solution that was experimented with a while back, and referenced
again in PR 17595 was to put a checkpoint variable in
/etc/defaults/rc.conf which would prevent it from being recursively
sourced. There are two problems with this strategy.
On Thu, Mar 30, 2000, Assar Westerlund wrote:
I would appreciate some feedback (in the form of commits also works)
on two small issues (I've also opened PR's on these).
1. Due to vnode_if.h not getting installed, you need to have kernel
source (namely vnode_if.src and vnode_if.pl) to
On Mon, Apr 03, 2000, Matthew Dillon wrote:
:
:
:Matt,
:
:When I mailed arch@ about this change I got no response from anybody
:but Bruce.
:
:I talked to Kirk about it in Malmø and got his approval.
:
:This is not unplanned.
:
:This is also not untested, I have two complete
I've ported the NetBSD fsck wrapper to compile and run under FreeBSD.
Its probably still very rough, but I'm going to spend the next few
days tidying it up. I have also modified our fsck (and renamed it
fsck_ffs) to fit this new framework.
The source tarball can be found at:
On Mon, Jun 19, 2000, David O'Brien wrote:
On Mon, Jun 19, 2000 at 01:42:33PM +0200, Adrian Chadd wrote:
I've ported the NetBSD fsck wrapper to compile and run under FreeBSD.
Can you summerize what this does, or does better than what we do today?
The idea is the same as mount and its
On Tue, Jun 20, 2000, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Anatoly Vorobey writes:
On Mon, Jun 19, 2000 at 01:42:33PM +0200, Adrian Chadd wrote:
* the rest of the system treats ffs filesystems as "ufs". Besides the
fact that I dislike this, I decid
On Tue, Jun 20, 2000, Bruce Evans wrote:
On Mon, 19 Jun 2000, Adrian Chadd wrote:
Watching my machine boot, the parallel nature of this fsck is now
confusing the output, eg:
Automatic reboot in progress...
** /dev/ad0s1a
** Last Mounted on /
** Root file system
** Phase 1
one object if this was brought over from NetBSD ?
Adrian
--
Adrian ChaddBuild a man a fire, and he's warm for the
[EMAIL PROTECTED]rest of the evening. Set a man on fire and
he's warm for the rest of his life.
To Unsubscribe:
On Thu, Jun 22, 2000, Brad Knowles wrote:
At 10:30 AM +0200 2000/6/22, Adrian Chadd wrote:
I like this. Would anyone object if this was brought over from NetBSD ?
If you're asking for a vote, you've got mine.
Hmm, Kirk has valid points for leaving a softupdates filesystem
I've integrated fsck and fsck_ffs into my local world tree, and
make buildworld/installworld seems to work ok. I've shifted the
tarball and diff to http://www.freebsd.org/~adrian/fsck/ . Can
people please prod it and see what I've missed ?
Thanks,
Adrian
--
Adrian Chadd
. If these issues are still
valid, I'll withdrawl the idea :)
Adrian
--
Adrian ChaddBuild a man a fire, and he's warm for the
[EMAIL PROTECTED]rest of the evening. Set a man on fire and
he's warm for the rest of his life.
To Unsubscribe
they just do the right thing, the better.
There we go. If someone has a better argument against this, feel free
to post it to the list. I'm calling this one dead.
Thanks, Kirk.
Adrian
--
Adrian ChaddBuild a man a fire, and he's warm for the
[EMAIL PROTECTED]rest
Hi,
I have a tunnel setup which requires me to rewrite the next hop of packets
going from the tunneled network out to the internet to go out via the
tunnel (rather than going out the default route, who drops the packets
(validly) because it thinks I'm trying to IP spoof.)
The trouble is that
"YES"
and so on .. ?
Adrian
--
Adrian ChaddBuild a man a fire, and he's warm for the
[EMAIL PROTECTED]rest of the evening. Set a man on fire and
he's warm for the rest of his life.
To Unsubscribe: send mail to [EMAIL PROT
On Thu, Jul 06, 2000, Adrian Chadd wrote:
And its actually very useful IMHO. Thats what rc.conf is for though, right?
enable_pkg_apache="YES"
enable_pkg_qmail="YES"
enable_pkg_mysql="YES"
and so on .. ?
Before people start going "huh?" .. tha
is too hardware and implementation dependant.
ifconfig -a ?
Adrian
--
Adrian ChaddNow 17-year-olds can't play a _video game_
[EMAIL PROTECTED]because its called violent -
and real violence is still called dinner
it publicly,
what happens to the manufacturer there?
Can they now take they took relevant steps as a defence in a law court?
Adrian
--
Adrian Chaddangryskul learning is bad
[EMAIL PROTECTED] angryskul it just makes the people around you
dumber
(angryskul
be released with the full 64 bit code?
Adrian
--
Adrian Chaddangryskul learning is bad
[EMAIL PROTECTED] angryskul it just makes the people around you
dumber
(angryskul == [EMAIL PROTECTED])angryskul
Oops. I should have sent this to -current :-P
adrian
- Forwarded message from Adrian Chadd [EMAIL PROTECTED] -
Date: Fri, 7 Feb 2003 16:10:56 +0800
From: Adrian Chadd [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: adduser change: telling you when a group isn't there
User-Agent
..)
Adrian
--
Adrian Chaddangryskul learning is bad
[EMAIL PROTECTED] angryskul it just makes the people around you
dumber
(angryskul == alfred@irc) angryskul :(
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
don't see anything
wrong with the patch, and the last time I applied it and tested it my
box stopped panicing under a test. :)
Adrian
--
Adrian Chadd"The main reason Santa is so jolly is
[EMAIL PROTECTED] because he knows where all the bad
ta section} - "KERNBASE" {*UND* section} at file address 928.
I get that too on a source tree cvsupped about an hour or two ago.
Adrian
--
Adrian Chadd"The main reason Santa is so jolly is
[EMAIL PROTECTED] because he know
!
Adrian
--
Adrian Chadd"The main reason Santa is so jolly is
[EMAIL PROTECTED] because he knows where all the bad girls
live." -- Random IRC quote
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
On Fri, Dec 22, 2000, Adrian Chadd wrote:
I've updated my fsck wrappers patchset to the latest netbsd and freebsd
fsck patches. I'd appreciate some feedback on them before I run off
and commit them (with my mentor, of course.)
For those who aren't in the know, the general idea
On Fri, Sep 22, 2000, Boris Popov wrote:
On Sat, 23 Dec 2000, Adrian Chadd wrote:
So now is a problem which I'm sure the NetBSD people came up against.
The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed
this by creating a new list 'mountnames[]', which maps the fs
On Fri, Dec 22, 2000, Adrian Chadd wrote:
I've updated my fsck wrappers patchset to the latest netbsd and freebsd
fsck patches. I'd appreciate some feedback on them before I run off
and commit them (with my mentor, of course.)
For those who aren't in the know, the general idea
On Fri, Sep 22, 2000, Boris Popov wrote:
On Sat, 23 Dec 2000, Adrian Chadd wrote:
On Fri, Sep 22, 2000, Boris Popov wrote:
On Sat, 23 Dec 2000, Adrian Chadd wrote:
So now is a problem which I'm sure the NetBSD people came up against.
The fstypenames are names like 4.2BSD
On Sat, Sep 23, 2000, Bruce Evans wrote:
On Sat, 23 Dec 2000, Adrian Chadd wrote:
Here's the patch:
--- fsck.c.orig Sat Dec 23 11:13:30 2000
+++ fsck.c Sat Dec 23 11:13:34 2000
@@ -501,7 +501,7 @@
errx(1, "partition `%s' is not of a legal vf
ke the raw disk device and figure out which
FS type it is, and then which fsck program to run?
Adrian
--
Adrian Chadd"The main reason Santa is so jolly is
[EMAIL PROTECTED] because he knows where all the bad girls
live.
On Sun, Sep 24, 2000, Adrian Chadd wrote:
On Sun, Sep 24, 2000, Kris Kennaway wrote:
The trouble is that some of the FS strings have spaces in their filenames.
This might confuse a few people.
How about mapping spaces to '_' characters - I doubt it would cause any
/~adrian/ifs/ . Please take a look and comment as
I am looking to commit this sometime within the next week or two into
-current.
Thanks!
Adrian
--
Adrian Chadd"The main reason Santa is so jolly is
[EMAIL PROTECTED] because he knows where all the bad
. This
forces fsck to NOT consider the FS for fsck-on-boot, and should make things
quieter.
Note that swap / procfs in /etc/fstab already use dump/pass = 0, but this is
just to make sure.
Just FYI,
Adrian
--
Adrian Chadd"The main reason Santa is so jolly is
[EMAIL PROT
--
Adrian Chadd"Programming is like sex:
[EMAIL PROTECTED] One mistake and you have to support for
a lifetime." -- rec.humor.funny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
files).
Its weird though, I would have thought a vinum device would be type
FSTYPE (eg BSD4.3) rather than VINUM, which I'd associate with
the underlying devices ..
Adrian
--
Adrian Chadd"Programming is like sex:
[EMAIL PROTECTED] One mistake and you
On Mon, Oct 30, 2000, David O'Brien wrote:
On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote:
cd /crash/usr/src/sys/modules env
MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules
KMODDIR=/crash/boot/kernel make install
Don't explicitly add DESTDIR to KMODDIR
--
Adrian Chadd"Programming is like sex:
[EMAIL PROTECTED] One mistake and you have to support for
a lifetime." -- rec.humor.funny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
that idea better.
adrian
--
Adrian Chadd"Programming is like sex:
[EMAIL PROTECTED] One mistake and you have to support for
a lifetime." -- rec.humor.funny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
m also one of those people who see evilnesses in going
take raw data - generate text - parse text - get raw data, but
is this really an interface we need blindingly fast?
(My 2c, I might run off and commit a proof of concept "stat" file to
procfs this week..)
Adri
to be the directory that I have been mounting it under for
a
couple of years. /var/ftp/release If I make it shorter like, /mnt. it
works
fine.
Not a big deal, easy to work around and I haven't made a release since the
begining of February :-).
Blame Adrian Chadd ([EMAIL PROTECTED
that aio_ only does read/write/lseek, whilst
open() and close() are still sync, and open() can take quite a while..)
Adrian
--
Adrian Chadd"Programming is like sex:
[EMAIL PROTECTED] One mistake and you have to su
On Wed, May 02, 2001, Robert Watson wrote:
On Tue, 1 May 2001, Jordan Hubbard wrote:
Say, FreeBSD is usually pretty safe, even in CURRENT.
Has something near this magnitude of Really Bad Stuffage snuck into the
codebase before?
No, it's not common, and it generally takes a Dane
On 5 August 2013 07:59, Bryan Venteicher bry...@daemoninthecloset.org wrote:
What I've done in my drivers is:
* Lock the core mutex
* Clear IFF_DRV_RUNNING
* Lock/unlock each queue's lock
.. and I think that's the only sane way of doing it.
I'm going to (soon) propose something
09:15, Luigi Rizzo wrote:
On Mon, Aug 5, 2013 at 5:46 PM, Adrian Chadd adr...@freebsd.org wrote:
On 5 August 2013 07:59, Bryan Venteicher bry...@daemoninthecloset.org
wrote:
What I've done in my drivers is:
* Lock the core mutex
* Clear IFF_DRV_RUNNING
* Lock/unlock each queue's lock
.. and I bet it's not a design pattern, and this is total conjecture on my part:
* the original drivers weren't SMP safe;
* noone really sat down and figured out how to correctly synchronise
all of this stuff;
* people did the minimum amount of work to keep the driver from
immediately crashing,
No, brian said two things:
* the flag, protected by the core lock
* per-queue flags
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
Can you go over some previous versions in -HEAD and see when it was introduced?
-adrian
On 8 August 2013 11:10, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
The most recent CURRENT doesn't work with the x11/nvidia-driver (which
is at 319.25 in the ports and 325.15 from nVidia).
After
Woo! Tell Jeff! File a PR! Set everything on fire!
-adrian
On 8 August 2013 14:39, Sean Bruno sean_br...@yahoo.com wrote:
On Thu, 2013-08-08 at 11:30 -0700, Adrian Chadd wrote:
Can you go over some previous versions in -HEAD and see when it was
introduced?
-adrian
On 8 August 2013
.. and it's not just about saturate the port with traffic.
It's also about what happens if I shut down the MAC whilst I'm in the
process of programming in new RX/TX descriptors?
The ath(4) driver had a spectacular behaviour where if you mess things
up the wrong way it will quite happily DMA crap
Hi!
Hm, resurrecting this thread, I'll try this on my X230 tomorrow and
see if it makes the (non-xorg, console only) video work on resume.
If it does, what will it take to automatically determine that this
kind of work-around is needed?
Thanks!
-adrian
On 14 June 2013 16:00, matt
in X.
I think since ssh still works, that just the display or graphics port
is off.
It may be worth trying to do some acpi_calls via ssh to try to hack
the display back on...
Matt
On 08/09/13 08:57, John Baldwin wrote:
On Friday, August 09, 2013 4:37:50 am Adrian Chadd wrote:
Hi!
Hm
Hi,
I'll test out the iwn patch, thanks!
-adrian
On 9 August 2013 20:56, Scott Long sco...@samsco.org wrote:
All,
Subversion rev 250418 affected approximately 63 drivers by making them
vulnerable to resource allocation failures on motherboards with buggy BIOSes.
The revision itself
Try running the svnlite version of svn upgrade.
(svnlite upgrade)
-adrian
On 10 August 2013 07:02, Lev Serebryakov l...@freebsd.org wrote:
Hello, Freebsd-current.
You wrote 10 августа 2013 г., 15:18:46:
LS Latest revisions of -CURRENT built with nanobsd script haven't
revision
LS in
Hi,
I can reproduce it locally, purely by booting an unchanged amd64 GENERIC.
Are you testing it against an _unmodified_ GENERIC, on amd64?
If it doesn't panic for you but it does panic for me (and I'll go and
get the svn version once I reboot to the old kernel and test) then
there may be a
On 10 August 2013 19:19, AN a...@neu.net wrote:
Hi All:
I am having a major problem on current at the moment, and I could really use
some help. I am at R253966 on amd64, my problem is the machine is panicing
with: ffs_valloc: dup alloc
I have booted into single user mode and run fsck, it
... bug peter. And alfred. Alfred broke this stuff. :)
-adrian
On 12 August 2013 21:33, Sean Bruno sean_br...@yahoo.com wrote:
On Mon, 2013-08-12 at 21:36 -0600, Scott Long wrote:
On Aug 12, 2013, at 1:43 PM, Sean Bruno sean_br...@yahoo.com wrote:
Hi,
This (and maybe more?) events are applicable to both the sandy bridge and
sandy bridge xeon CPUs.
This is from the Intel SDM June 2013 Volume #3.
David/Jim, does this look fine to you?
Thanks,
ndex: sys/dev/hwpmc/hwpmc_core.c
Hm, do we disable building the base with ICONV support in -HEAD?
I'd like to trim it out so I can slim down embedded builds.
Thanks!
-adrian
On 10 August 2013 10:33, Peter Wemm pe...@wemm.org wrote:
I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2.
Oh, _this_ is the cause! Cool. I wondered about it.
Thanks for chasing this down!
-adrian
On 15 August 2013 11:13, Dimitry Andric d...@freebsd.org wrote:
On Jul 28, 2013, at 15:15, Dmitry Morozovsky ma...@rinet.ru wrote:
...
on my builder I have consistent error:
Attempt #2:
http://people.freebsd.org/~adrian/netflix/20130816-hwpmc-sbx-1.diff
I've verified that I get counter events from this! But I need to load up a
system more to trigger contention to validate that they're doing the right
thing.
Unfortunately there's an erratum on this which we need to
Yes! Please file a PR!
-adrian
On 19 August 2013 12:33, Vitja Makarov vitja.maka...@gmail.com wrote:
Hi!
Recently I was playing with small socket timeouts. setsockopt(2)
SO_RCVTIMEO and found a problem with it: if timeout is small enough
read(2) may return before timeout is actually
Hi!
If firewire code doesn't build on clang correctly, have you filed a bug so
it gets looked at before 10.0 is released? that's pretty broken
code/behaviour.
-adrian
On 23 August 2013 04:46, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian
Hi,
I'd like to commit this to -10. It migrates the if_lagg locking from a rw
lock to a rm lock. We see a bit of contention between the transmit and
receive sides of lagg during traffic loads (10+ gigabit per second.) Using
rmlocks eliminate this.
Sorry, I meant line contention rather than lock contention. Yes, you're
right.
-adrian
On 24 August 2013 07:16, Robert Watson rwat...@freebsd.org wrote:
On Sat, 24 Aug 2013, Alexander V. Chernikov wrote:
On 24.08.2013 00:54, Adrian Chadd wrote:
I'd like to commit this to -10
.. well, where'd you point it to?
-adrian
On 23 August 2013 23:04, Hideki Yamamoto hyam...@gmail.com wrote:
Hi,
I solved my problem by myself.
I update PACKAGESITE in /usr/local/etc/pkg.conf in accordance with
the information in another expert web site.
---
2013/8/24 Hideki
You know, I could be a total jerk and say:
If you push gcc out to a port, and you have the 'external compiler'
toolchain support working correctly enough to build with this, why don't we
just push clang out to a port, and be done with it?
... just saying.
-adrian
Hihi,
There's two parts to my patch:
* one is migrating the rwlock to rmlock - not because of counters, but
because the lock is protecting consistency when changing the lagg config
* one is adding a new lock specifically to ensure that the callout is
atomically created/called/destroyed
The
Hm!
Is there a Linux driver for this SSD? Does Linux approximately boot on this
thing?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
Hm! Are they dynamically loaded if you insert the cards?
(Ie, has devd been taught about them as appropriate?)
-adrian
On 29 August 2013 02:15, Kimmo Paasiala kpaas...@gmail.com wrote:
In reference to this FreeBSD forums post:
http://forums.freebsd.org/showpost.php?p=231135postcount=4
.. after tinkering in the USB world, i wonder what's wrong with this:
* created a basic markup / description language to encapsulate what PCI/USB
probing requires;
* generated both config files _and_ .c / .h files for drivers to include;
* have the kernel build process do .device_description -
... well, this is why Peter committed svnlite to -HEAD. To avoid this kind
of not-easy-to-recover-from breakage..
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
I've begun trying to hunt down someone at Broadcom to talk about the 11ac
driver.
Wish me luck.
(And install/run FreeBSD on mac hardware..)
-adrian
On 30 August 2013 09:25, Lundberg, Johannes johan...@brilliantservice.co.jp
wrote:
Hi
I thought I'd give a progress report on running
On 31 August 2013 11:44, Lundberg, Johannes johan...@brilliantservice.co.jp
wrote:
Hi Adrian
That's great! Good luck to you :)
Yup. I hope I get some positive responses from Broadcom. I really don't
want to port the Linux driver(s), it's just plain silly.
-adrian
Hi!
How do i cross-build a mips world/kernel with clang?
ie, how do I tell the build system to build a mips targetted clang instead
of gcc and use that to build everything?
Thanks,
-adrian
___
freebsd-current@freebsd.org mailing list
did you contribute this stuff back up to the linux driver?
-adrian
On 31 August 2013 21:30, Jason Birch jbi...@jbirch.net wrote:
Yup. I hope I get some positive responses from Broadcom. I really don't
want to port the Linux driver(s), it's just plain silly.
I've noticed a hell of a lot
On 2 September 2013 00:47, David Chisnall thera...@freebsd.org wrote:
On 2 Sep 2013, at 03:01, John-Mark Gurney j...@funkthat.com wrote:
b/crtn.o: warning: linking PIC files with non-PIC files
I think that this is an issue in our import of clang. I'll have to check
whether I upstreamed
On 2 September 2013 09:48, Gary Palmer gpal...@freebsd.org wrote:
While not helpful in getting a native driver working, does the device
work under the NDIS emulation layer with the Windows driver?
I don't know. But the wifi NDIS stuff has evolved quite significantly over
the years and I
Hi!
On 7 September 2013 13:38, Ian Lepore i...@freebsd.org wrote:
I keep trying to say this, and I keep getting the feeling that it just
doesn't register with anyone I say it to, like I'm speaking some
language from another planet or something...
There may be NO entropy of any sort
[snip]
ok. So I can work around this for these MIPS AP images by echoing something
into /dev/random ?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
[mailto:owner-freebsd-
m...@freebsd.org] On Behalf Of Joe Holden
Sent: 15 September 2013 23:28
To: 'Adrian Chadd'; 'freebsd-current'; freebsd-m...@freebsd.org
Subject: RE: how do i cross build world/kernel with clang?
Are you still playing with this? Reason I ask is that I tried to build
The results are interesting. On amd64:
- devd suddenly becomes 500 KB in size, instead of a megabyte,
- init's size drops from 900 KB to 600 KB,
- clang becomes a megabyte smaller.
.. so, I'd like to know specific information as to why these three are now
smaller. So what's going on?
... can you post the boot messages?
Can you boot with verbose turned on?
-adrian
On 15 September 2013 22:54, Lundberg, Johannes
johan...@brilliantservice.co.jp wrote:
Hi
Installing current on a MacBook Air 2013 model from USB memstick (special
build) works fine but booting from the
On 16 September 2013 21:01, Garrett Cooper yaneurab...@gmail.com wrote:
On Sep 16, 2013, at 6:12 PM, Glen Barber wrote:
On Mon, Sep 16, 2013 at 04:53:14PM -0700, Garrett Cooper wrote:
Can people PLEASE build/test their changes on
and off on multiple VMs?
Welcome to the world two weeks
... I'd rather see if we can actually separate out things some more so
these builds can shrink.
Eg, if there's malloc related functions that aren't used, maybe we should
break malloc down into a directory full of functions.
I'm not surprised libc++ is doing .. that. It's likely better on the
On 17 September 2013 16:22, Ian Lepore i...@freebsd.org wrote:
On Tue, 2013-09-17 at 14:56 -0700, Adrian Chadd wrote:
... I'd rather see if we can actually separate out things some more so
these builds can shrink.
Eg, if there's malloc related functions that aren't used, maybe we should
Hi,
You should add:
* a loop counter, to break out after a while;
* a DELAY(1) or something.
-adrian
On 7 October 2013 12:54, Zbigniew Bodek z...@freebsd.org wrote:
Hello.
I would like to present a patch for ns8250 serial that I would like to
commit in the near future (if there are no
2013 13:26, Ian Lepore i...@freebsd.org wrote:
On Mon, 2013-10-07 at 13:15 -0700, Adrian Chadd wrote:
Hi,
You should add:
*[snip]
* a DELAY(1) or something.
Why? Why oh why do people write
while (!read_some_status_register())
DELAY(n);
when DELAY() is implemented
.. don't be surprised how many people do exactly this; then compile what
handful of things they need from source in order to make a server.
-adrian
On 7 October 2013 14:53, David Chisnall thera...@freebsd.org wrote:
On 7 Oct 2013, at 22:14, Lyndon Nerenberg lyn...@orthanc.ca wrote:
Hi!
Then you and others should stand up and provide feedback like this far, far
earlier in the development process.
If everyone who communicates says x and no-one says anything about the
other letters a-w, y, z, then we as developers don't really have a
good cross-section of what people actually
I've asked on IRC to figure out when this was first proposed. I'll see if
it was announced anywhere or if Eitan snuck it in.
-a
On 7 October 2013 16:46, Julian Elischer jul...@freebsd.org wrote:
On 10/8/13 7:37 AM, Adrian Chadd wrote:
Hi!
Then you and others should stand up and provide
On 7 October 2013 16:58, Lyndon Nerenberg lyn...@orthanc.ca wrote:
On 2013-10-07, at 4:49 PM, Adrian Chadd adr...@freebsd.org wrote:
I've asked on IRC to figure out when this was first proposed.
Adrian, something to keep in mind is that the majority of your code's
users will never use
Hi,
Note the noise floor differences.. wonder why that is.
Rui ported the uwrtn stuff, right? He may be able to help. The driver is
recent and its likely there are bugs to shake out.
-adrian
On Oct 8, 2013 2:49 PM, Julian H. Stacey j...@berklix.com wrote:
I too am seeing
urtwn0:
I think that's great. But, as we are increasingly finding, theres no stable
ports snapshot, so unless we as a project change how packages are managed,
there may not really be a stable, predictable version of things once
they're moved from base to a package. A number of users and companies like
I've iterated my views on these things a few times.
I honestly am not all _that_ interested in trying to build a polished OS.
I'd rather participate in building an OS toolkit that let's PCBSD, pfsense,
that storage appliance I keep forgetting the name of (heh), etc all build
OSes on top of it.
On 9 October 2013 11:28, Bruce Cran br...@cran.org.uk wrote:
On 10/9/2013 3:17 PM, Alfred Perlstein wrote:
Only a few years ago you could take a dvd or memstick of FreeBSD and have
1000s of packages to choose from during your install. That is broken now?
At some point it was decided that
Hi all,
I'd like to remove the NDISulator. I've had many requests to update it to
the latest NDIS version and support more of the 64 bit wifi drivers. But,
to be perfectly honest, I have no desire to keep hacking at this. The world
has changed quite a bit - we can port/reimplement drivers from
Hi,
On 18 October 2013 13:53, Steve Wills swi...@freebsd.org wrote:
I would love to have a native driver for this:
none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4
rev=0x01 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM4313 802.11b/g/n
bwn(4) requires a lot more than just an additional PCI ID.
The driver is somewhat architected for all the different RF and PHY modules
that plug into the internal bus (the whole SIBA thing) but it does sorely
need updating.
Thanks,
-adrian
On 18 October 2013 14:04, Nathan Whitehorn
I don't know how many times i can say it needs a maintainer and it needs
updating.
So yeah, it needs (a) a maintainer, (b) updating.
-adrian
On 18 October 2013 15:47, Alfred Perlstein bri...@mu.org wrote:
On 10/18/13 2:04 PM, Nathan Whitehorn wrote:
On 10/18/13 16:01, Steve Kargl wrote:
On 21 October 2013 12:59, Andrey V. Elsukov bu7c...@yandex.ru wrote:
On 19.10.2013 10:01, Thomas Mueller wrote:
I too would like to see more effort writing new Ethernet and wifi
drivers and porting from other operating systems.
But I would like to keep the NDISulator/NDISwrapper as a
, we should keep it.
Yes, best keep it while it helps some people.
Adrian Chadd adr...@freebsd.org wrote:
It's honestly about time that these were updated, fixed and/or ported to
FreeBSD.
So, I'm still going forward with the plan. I won't be killing it during
the
10 lifecycle
1 - 100 of 1248 matches
Mail list logo
