Hi freebsd-current, I noticed there are some threads about virtio drivers for FreeBSD and NetBSD on this mailing list, so I would like to post my virtio drivers. I've worked on these drivers for a few months to understand para-virtalized drivers. I sent early versions to Rusty Russel, the author of virtio, since I attended to Rusty's virtio session at LinuxCon 2010 Tokyo and decided to work on it. My virtio-net & virtio-blk driver is not complete just now, but it looks working fine. I ...

On Mon, Jan 03, 2011 at 01:21:10PM +0200 I heard the voice of Shoot, I missed that going by. Sorry for the noise; I guess I've got a good excuse to go upgrade now 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. _______________________________________________ freebsd-current@freebsd.org mailing ...

OK, this has happened a couple times now. I'm running a mid-Oct -CURRENT, and at around 25 days uptime (not exact but consistently in that vicinity), things start getting very choppy. It's easily visible in playing videos; things get very jerky and slow, but all sorts of things start acting like they're happening in little chunks of time; keyboard repeats get very slow, things that often take notable time take much more, etc. It's accompanied by a big spat of "calcru: runtime went backwards" ...

I had code that adds strerror() to the kernel in one of my old p4 branches. Error messages like the one above look much better this way, but I didn't have time to push it into the tree, and there is a risk of yet another i18n discussion. If someone is interested - let me know; I'll try to find it. -- If you cut off my head, what would I say? Me and my head, or me and my body? _______________________________________________ freebsd-current@freebsd.org mailing ...

And you can use grep tricks :-) $ errno '[dD]evice' #define ENXIO 6 /* Device not configured */ #define ENOTBLK 15 /* Block device required */ #define EBUSY 16 /* Device busy */ #define EXDEV 18 /* Cross-device link */ #define ENODEV 19 /* Operation not supported by device */ #define ENOTTY 25 /* Inappropriate ioctl for device */ #define ENOSPC 28 ...

I prefer mine: $ errno () { grep "^#.*\\<$*\\>" /usr/include/sys/errno.h } $ errno 5 #define EIO 5 /* Input/output error */ $ errno EIO #define EIO 5 /* Input/output error */ _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

In kernel ? There is no strerror, and there is no great need to import the sys_errlist.

Heh -- didn't realize that someone made a userland app for that libcall already :D... You learn new things everyday I guess :). In that case IMO nothing needs to be done minus (if you're interested) creating a parser that data mines stuff to make it more human readable in a common format, i.e. error: 5 (Input/output error) <subsystem specific information does here> Thanks! -Garrett_______________________________________________ freebsd-current@freebsd.org mailing ...