[no subject]

Äîðîãîé äðóã! Èçâèíè, ÷òî îòáèðàþ òâîå âðåìÿ íà ÷òåíèå äàííîãî ïîñëàíèÿ,òàê êàê ìû âñå óñòàëè îò áåñêîíå÷íûõ ðåêëàìíûõ ðàññûëîê è âñÿ÷åñêîãî ìóñîðà,íî ÿ íàäåþñü, ÷òî íåñêîëüêî ìèíóò çàòðà÷åííîãî âðåìåíè ñìîãóò îêóïèòüñÿ, åñëè òû ðåøèøüñÿ èçìåíèòü ñâîé âçãëÿä íà îêðóæàþùóþ òåáÿ äåéñòâèòåëüíîñòü.

Re: Bugmeister discussion list

I thought it was normal process for a new FreeBSD mailing list to be hosted on another site until it was deemed beneficial to have @FreeBSD.org host it. Cheers, Andrew On Thu, 22 Nov 2001, Doug Barton wrote: :On 22 Nov 2001, Dag-Erling Smorgrav wrote: : :> [apologies to those who receive mu

Re: Bugmeister discussion list

On 22 Nov 2001, Dag-Erling Smorgrav wrote: > [apologies to those who receive multiple copies of this message] > > I've set up a [EMAIL PROTECTED] mailing list Any reason this can't/shouldn't be a freebsd.org mailing list? -- "We will not tire, we will not falter, and we will not fa

Re: sysctls for hardware monitoring?

Harti Brandt <[EMAIL PROTECTED]> types: > MM>Harti Brandt <[EMAIL PROTECTED]> types: > MM>> On Thu, 22 Nov 2001, Mike Meyer wrote: > MM>> MM>Linux uses a device driver that's a directory full of files holding > MM>> MM>sensor information. That doesn't seem to be the right direction for > MM>> MM>F

fujitsu MO drive: DA_Q_NO_SYNC_CACHE

L.S. I submitted a bugreport & patch for 3.3 /4.1 a year ago, but on installing 4.4 a while back, I found it had not been incorporated. Here it is again as a diff to 4.4. Please apply. Regards, Wouter --- /usr/src/sys/cam/scsi/scsi_da.c.origMon Jul 30 02:48:20 2001 +++ /usr/src/sys/c

Re: sysctls for hardware monitoring?

On Thu, 22 Nov 2001, Harti Brandt wrote: > What's bad about using files? Just to be different? Isn't it easier to > select, poll, kqueue, what ever on files than on sysctls? /proc files are horrible if you sample at reasonable rates, say 10-100 hz. We found (on Linux, maybe fbsd is better) that

Re: meteor driver problems

> > My guess every computer that you used to test the card uses the > > PCI 2.x chipset. > > Correct. In fact, they're all identical: Asus P2B-D(S) dual PII > mainboards (at various clock speeds), so I'm a bit surprised that > I'm only having issues with two of them (so far, *knocking on wood*).

VIRUS IN YOUR MAIL

V I R U S A L E R T Our viruschecker found the 'W32/Aliz-A' virus(es) in your email to the following recipient(s): -> <[EMAIL PROTECTED]> Please check your system for viruses, or ask your system administrator to do so. For your reference, here are the head

Re: many shit check (ITS A VIRUS!!!)

hey guys... dont open this file... it containes a virus/worm... if possible, barge this email address from all the mailing lists, because the same email address was used to send a virus previously... thanks... = regards, Hiten Pandya <[EMAIL PROTECTED]> -

Re: dummynet "pipe show" problem

On Wed, Nov 21, 2001 at 03:02:49PM -0800, rick norman wrote: > Hi, > I'm still running into lots of problems with this on 4.3. Is it neccessary > to introduce a delay in the pipe ? Would a delay of zero work ? > Has this been fixed in 4.4 ? Thinking about it, I believe it might be a problem wit

const char *tsptype[TSPTYPENUMBER] in "protocols/timed.h" ?

Hello, hackers. What do you think about change the type of tsptype in src/include/protocols/timed.h from (char *) to (const char *) ? $ grep -r protocols/timed.h /usr/src /usr/src/bin/date/netdate.c:#include /usr/src/usr.sbin/timed/timed/byteorder.c: * messages. Protocol is defined in /usr/in

Re: sysctls for hardware monitoring?

On Thu, Nov 22, 2001 at 05:51:10PM +0100, Harti Brandt wrote: > Taking a Linux driver to argue against > something doesn't really make sense. There is so many crap in the Linux > kernel, that you can argue against anything: "The crappy unix domain > sockets don't work in Linux. Oh yeah, they are a

Re: sysctls for hardware monitoring?

On Fri, 23 Nov 2001, Joerg Micheel wrote: JM>On Thu, Nov 22, 2001 at 12:08:16PM +0100, Harti Brandt wrote: JM>> It's just annoying to need a special program to get at the values. For JM>> some parts of the MIB, like the interface MIB, even sysctl doesn't help - JM>> you need to write a program to

Re: sysctls for hardware monitoring?

On Thu, Nov 22, 2001 at 12:08:16PM +0100, Harti Brandt wrote: > It's just annoying to need a special program to get at the values. For > some parts of the MIB, like the interface MIB, even sysctl doesn't help - > you need to write a program to look at these. I still think, its easier to > read the

Re: meteor driver problems

> the original meteor card's PCI chipset had a known and uncorrectable > hardware incompatibility with PCI 2.0 chipsets that caused lockup. > [...] oh. I'm guessing that it is the Meteor card that locks up; this does make sense. I've realized that since tsleep is called with METPRI (which does i

Re: meteor driver problems

> i've been experiencing weird problems with the Meteor device driver.. > on two machines of the seven we've installed, the METEOR_CAP_SINGLE > ioctl locks up the process once in a while (every few hours). [deletion] the original metoer card's PCI chipset had a known and uncorrectable hardware in

sysctl and MAXDSIZ

I have a need dynamicaly to change maxdatasize limit for user in order to make some experiences on my work. Give me some advise for non-reboot change to do this? I found 'options MAXDSIZ' in LINT that helps me at that moment but as I so at kern/subr_param.c there is : TUNABLE_QUAD_FETCH("ker

Re: Bugmeister discussion list

Gary Jennejohn <[EMAIL PROTECTED]> writes: > This seems like a fatal name for the list considering what > buggers means. I know perfectly well what it means. I did say the list was informal, didn't I? :) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROT

Re: Bugmeister discussion list

On Thursday 22 November 2001 13:22, Dag-Erling Smorgrav wrote: > [apologies to those who receive multiple copies of this > message] > > I've set up a [EMAIL PROTECTED] mailing list with the following > charter: > This seems like a fatal name for the list considering what buggers means. -- Gary

Bugmeister discussion list

[apologies to those who receive multiple copies of this message] I've set up a [EMAIL PROTECTED] mailing list with the following charter: Discussions pertaining to the FreeBSD PR system. The purpose of this list is to serve as an informal forum for discussing policies and mechanisms fo

Re: sysctls for hardware monitoring?

On Thu, 22 Nov 2001, Mike Meyer wrote: MM>Harti Brandt <[EMAIL PROTECTED]> types: MM>> On Thu, 22 Nov 2001, Mike Meyer wrote: MM>> MM>Linux uses a device driver that's a directory full of files holding MM>> MM>sensor information. That doesn't seem to be the right direction for MM>> MM>FBSD, thoug

meteor driver problems

hi, i've been experiencing weird problems with the Meteor device driver.. on two machines of the seven we've installed, the METEOR_CAP_SINGLE ioctl locks up the process once in a while (every few hours). after attaching gdb (or breaking into it if the process has been started from gdb), a simple

Re: sysctls for hardware monitoring?

Harti Brandt <[EMAIL PROTECTED]> types: > On Thu, 22 Nov 2001, Mike Meyer wrote: > MM>Linux uses a device driver that's a directory full of files holding > MM>sensor information. That doesn't seem to be the right direction for > MM>FBSD, though. An option that enabled a set of sysctls to collect t

Re: sysctls for hardware monitoring?

On Thu, 22 Nov 2001, Mike Meyer wrote: MM>In looking over the various options for monitoring the health of the MM>hardware, I notice that it's pretty much a mess. All the software in MM>question runs privileged and grovels through memory in some way. MM> MM>Linux uses a device driver that's a dir

many shit to check

peace

Re: add some constraints in cpufunc.h

According to GCC manual of inline assembler instruction, it says if your instruction changes condition code register(on X86, it's cpu flag register, and a simple addl instruction can affect it), you'd put cc there, I have reviewed some source header files of bus management, they all have cc c