F A S T T R A C K D E G R E E P R O G R A M Obtain the degree you deserve, based on your present knowledge and life experience. A prosperous future, money earning power, and the Admiration of all. Degrees from an Established, Prestigious, Leading Institution. Your Degree will show exactly what you really can do. Get the Job, Promotion, Business Opportunity and Social Advancement you Desire! Eliminates classrooms and traveling. Achieve your Bachelors, Masters, ...

It was suggested that this list may be a better place to post my request. I have started work on a WinBond chip driver (currently only the W83627HF chip) to provide access to the chips watchdog timer and sensors. I have never written a driver before and my C is rather rusty so I figured I would post what I currently have in hopes that some kind soul would take pity on me. What I have so far is located here: http://freebsd.tamu.edu/wbio/ The driver does attach and the ...

oh.. you DID say "microseconds" .. i was going to assume complete ignorance in pointing out that "u" is used because it looks remotely like the greek letter "mu" which is the metric abbreviation for "micro" wich is 10^-6 *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster ...

Such as? If you are talking about having the process suspended instead of the thread then this is dependent on the threading library and the thread attributes and is no more or less surprising than any If you bothered to read what Sharad had said, the man page or the source, you would find that usleep(3) _is_ implemented using nanosleep(2) so there is no point in using nanosleep() instead of usleep(). --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to ...

Sharad, Additionally, this C routine is considered obsolete (unlike shell command by the same name). The interaction of this function with SIGALRM and other timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is unspecified. Additionally, its use in multi-threaded programs can lead to somewhat surprising results. Use nanosleep(2) or setitimer(2) instead. -- Sincerely, Andrew Pogrebennyk _______________________________________________ freebsd-hackers@freebsd.org ...

[Empty message]

Sounds good to me. I'll give it a try this weekend as well, but let me know if it works for you. I'll commit it and MFC it to 6/7-STABLE then. Regards, -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send ...

There is also kern.msgbuf_clear. However, this is a sysctl, which means if set to 1 in /etc/sysctl.conf, you'd lose your dmesg output after the OS had started. Bummer. It would be useful if there was a loader.conf variable which was the equivalent of msgbuf_clear. In fact, I'm wondering why the message buffer isn't cleared on shutdown/immediately prior to reboot... Interesting tidbit: We have one production machine which when booted into single-user via serial console for a world ...

Jeremy Chadwick wrote: > Oliver Fromme wrote: > > [...] > Either way, it's a feature with major security implications. So, for > those of us who are concerned about master.passwd changes via > mergemaster being stuffed into msgbuf, how do we disable said feature? > (Before answering, see below as well). > > > sysctl security.bsd.unprivileged_read_msgbuf=0 > > No can do -- we have many users who look at dmesg for a reason: logging > of coredumped binaries (kern.logsigexit=1), and ...

I suggest just making a loader tunable to do this. I think the following should do it (untested): --- subr_prf.c 2007-03-08 07:44:34.000000000 +0100 +++ subr_prf.new.c 2008-02-22 11:21:53.000000000 +0100 @@ -913,14 +913,20 @@ msgbufinit(void *ptr, int size) { char *cp; + char *rv; static struct msgbuf *oldp = NULL; size -= sizeof(*msgbufp); cp = (char *)ptr; msgbufp = (struct msgbuf *)(cp + size); - msgbuf_reinit(msgbufp, cp, ...

> DEVACTB

Marcel Moolenaar wrote: > [Oliver explains bitblit, then Marcel explains bitblt.] OK, so we mean the same thing, bascially. > The higher lever TTY code simply calls bitblt with a > bit mask of the glyph to be printed and doesn't need to > know about the details of the display. As such, simple > console output works at any resolution and with any > color depth. > > At the same time the VGA driver is abstracted from any > high-level details, like fonts or character sets. This > ...