FreeBSD in good standing in netcraft survey
We're doing quite fine in the "max uptime" survey: http://uptime.netcraft.com/today/isp.max.html -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
phk wrote: > We're doing quite fine in the "max uptime" survey: > > http://uptime.netcraft.com/today/isp.max.html Glad you like it - pity we got slashdotted so early :) Although the uptime survey's are new on the site, they have quite a large database to gather from, and will get better as more people use the whats queries. Be nice when freefall has enough data to plot a graph for :) -- Jonathan Perkin <[EMAIL PROTECTED]> Voice: +44 (01225) 404422 ech`echo xiun | tr nu oc | sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol System Administrator - Netcraft, Bath, UK - http://www.netcraft.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
Have you checked out www.uptime.net ? --- www.nul.cjb.net --- The Power to Crash! --- www.FreeBSD.org --- The Power to Serve! On Wed, 1 Nov 2000, Poul-Henning Kamp wrote: > > We're doing quite fine in the "max uptime" survey: > > http://uptime.netcraft.com/today/isp.max.html > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
In message <[EMAIL PROTECTED]>, P eter writes: >Have you checked out www.uptime.net ? Yes, and ? It looks like some random company... >On Wed, 1 Nov 2000, Poul-Henning Kamp wrote: > >> >> We're doing quite fine in the "max uptime" survey: >> >> http://uptime.netcraft.com/today/isp.max.html >> >> -- >> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >> [EMAIL PROTECTED] | TCP/IP since RFC 956 >> FreeBSD committer | BSD since 4.3-tahoe >> Never attribute to malice what can adequately be explained by incompetence. >> >> >> To Unsubscribe: send mail to [EMAIL PROTECTED] >> with "unsubscribe freebsd-hackers" in the body of the message >> >> > > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
Yes, and is this your idea of spamming / advertising ?!?! Where is any relevant information on this subject? On Wed, 01 Nov 2000, you wrote: > Have you checked out www.uptime.net ? > > > --- www.nul.cjb.net --- The Power to Crash! > --- www.FreeBSD.org --- The Power to Serve! > > On Wed, 1 Nov 2000, Poul-Henning Kamp wrote: > > > > > We're doing quite fine in the "max uptime" survey: > > > > http://uptime.netcraft.com/today/isp.max.html > > > > -- > > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > [EMAIL PROTECTED] | TCP/IP since RFC 956 > > FreeBSD committer | BSD since 4.3-tahoe > > Never attribute to malice what can adequately be explained by incompetence. > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. === email: [EMAIL PROTECTED] web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile:+44 (0)7779 646 529 === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
On Wed, Nov 01, 2000 at 04:09:34PM +0100, Poul-Henning Kamp wrote: >>Have you checked out www.uptime.net ? > Yes, and ? It looks like some random company... I suppose he means www.uptimes.net. Cheers, -- Anders. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
In message <[EMAIL PROTECTED]>, Anders Nordby writes: >On Wed, Nov 01, 2000 at 04:09:34PM +0100, Poul-Henning Kamp wrote: >>>Have you checked out www.uptime.net ? >> Yes, and ? It looks like some random company... > >I suppose he means www.uptimes.net. Ahh, that thing. That is an opt-in scheme, and therefore the result is as scientific and reliable as asking Congress how well the president is doing... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
> Yes, and is this your idea of spamming / advertising ?!?! > > Where is any relevant information on this subject? oh please, if you're going to call that spam, it was the most beniegn spam I've ever seen. It wasn't even worth a reply. Try setting flame_enabled="false" in your rc.conf To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
Guys, sorry did not mean to spam, but there used to be a site called uptime.net (I'm pretty sure of it) It basically did what netcraft is doing, except it only kept the uptimes. They had some wonderful uptimes of several years. As far as I remember, NETBSD was 1st place and FreeBSD was in second. sorry about the spam, was not aware that the site has gone away. --- www.nul.cjb.net --- The Power to Crash! --- www.FreeBSD.org --- The Power to Serve! On Wed, 1 Nov 2000, Jamie Heckford wrote: > Yes, and is this your idea of spamming / advertising ?!?! > > Where is any relevant information on this subject? > > > On Wed, 01 Nov 2000, you wrote: > > Have you checked out www.uptime.net ? > > > > > > --- www.nul.cjb.net --- The Power to Crash! > > --- www.FreeBSD.org --- The Power to Serve! > > > > On Wed, 1 Nov 2000, Poul-Henning Kamp wrote: > > > > > > > > We're doing quite fine in the "max uptime" survey: > > > > > > http://uptime.netcraft.com/today/isp.max.html > > > > > > -- > > > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > > [EMAIL PROTECTED] | TCP/IP since RFC 956 > > > FreeBSD committer | BSD since 4.3-tahoe > > > Never attribute to malice what can adequately be explained by incompetence. > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > -- > Jamie Heckford > Chief Network Engineer > Psi-Domain - Innovative Linux Solutions. Ask Us How. > > === > email: [EMAIL PROTECTED] > web: http://www.psi-domain.co.uk/ > > tel: +44 (0)1737 789 246 > fax: +44 (0)1737 789 245 > mobile: +44 (0)7779 646 529 > === > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
No worries, you just forgot the 's' at the end ;) The site is still there, it's just "uptimes.net" not "uptime.net". > Guys, sorry did not mean to spam, but there used to be a site called > uptime.net (I'm pretty sure of it) It basically did what netcraft is > doing, except it only kept the uptimes. They had some wonderful uptimes > of several years. As far as I remember, NETBSD was 1st place and FreeBSD > was in second. > > sorry about the spam, was not aware that the site has gone away. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
Hi all! > Guys, sorry did not mean to spam, but there used to be a site called > uptime.net (I'm pretty sure of it) It basically did what netcraft is > doing, except it only kept the uptimes. They had some wonderful uptimes > of several years. As far as I remember, NETBSD was 1st place and FreeBSD > was in second. I didn't follow the whole thread *shame*, but the side you possibly mean is called uptimes.net (don't forget the "s"). And my Box is reporting to this side, too (HID: 7068 (munwme)). Best Regards, Freddy -- Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv = Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FreeBSD, NetBSD, OpenBSD, Tru64, OpenVMS, Ultrix, BeOS, Linux To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
Possibly off topic, possibly not. Am I the only one who doesn't really care about uptimes? It would be far more productive to get a top 100 (or whatever) of availability... More interesting would be to test availability based on some dynamic content, a given request with an expected outcome a la F5? I may be forced to hack this together, where's my damn cable modem!!! Dave :) BTW, we didn't fare very well at all in the top *average* uptimes. Sun, OTOH, did. Bugger. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
irq status
Is their a tool out their or does anyone have a quick bit of code / hack that will "probe" all of the irqs on my box and tell me which ones are used / available?? Thanks, -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. === email: [EMAIL PROTECTED] web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile:+44 (0)7779 646 529 === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: irq status
On Wed, 1 Nov 2000, Jamie Heckford wrote: > Is their a tool out their or does anyone have a quick bit of code / hack that > will "probe" all of the irqs on my box and tell me which ones are used / > available?? dmesg | grep irq Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: irq status
ok, is their anyway to probe for base addresses? This is an unusual card, a Dialogic D41/E Computer Telephony card. It *will* work under BSD, just need a base address value now. thanx for help so far btw. On Wed, 01 Nov 2000, you wrote: > vmstat -i > coupled with > dmesg | grep irq > > should find them all. > > tonym -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. === email: [EMAIL PROTECTED] web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile:+44 (0)7779 646 529 === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: irq status
Their is no corresponding device in the kernel !!! These drivers work as a thrid party module, and have seen working before, but need the base address value. On Wed, 01 Nov 2000, you wrote: > What device does it correspond to in kernel config file? > If the device is in the kernel I would have thought the card would > be seen at boot up with a probed IO address. > > tonym -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. === email: [EMAIL PROTECTED] web: http://www.psi-domain.co.uk/ tel:+44 (0)1737 789 246 fax:+44 (0)1737 789 245 mobile: +44 (0)7779 646 529 === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: irq status
> Is their a tool out their or does anyone have a quick bit of code / hack that > will "probe" all of the irqs on my box and tell me which ones are used / > available?? No. You can glean some of this information from various metaconfiguration interface, but the question you're asking suggests that you're trying to do something wrong anyway. Why don't you tell us a bit more about what you want this information for? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Add a system call
On Wednesday, 1 November 2000 at 20:47:18 +0100, flag wrote: > On Tue, 31 Oct 2000, Raymond Law wrote: > >> Can someone list the steps on how to add a system call in FreeBSD 4 please? > [mega-snip] > > The response to this question seems to be great material for a FAQ. > Anybody out there would like to create it? It's also a little off-topic for questions. I'm sure you'll get better answers from -hackers, so I've replied there. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
David Preece writes: > Possibly off topic, possibly not. Am I the only one who doesn't really care > about uptimes? I certainly am not impressed by uptimes over about 100 days. They show that the site does not care about keeping current. If it made sense to have several hundred days of uptime, what is the point of all the development work done by the FreeBSD (and other OS) developers? These people work hard to improve the system and it makes sense to at least run the latest production release. In the case of FreeBSD, this means a reboot at least every three to four months when the CDs are released. -- Greg Black <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
Just curious, since I can't find the info on the site...what method is being used to determine uptimes on these systems? How can I turn reporting on in FreeBSD? L Jonathan Perkin wrote: > > phk wrote: > > > We're doing quite fine in the "max uptime" survey: > > > > http://uptime.netcraft.com/today/isp.max.html > > Glad you like it - pity we got slashdotted so early :) > > Although the uptime survey's are new on the site, they have quite a > large database to gather from, and will get better as more people use > the whats queries. Be nice when freefall has enough data to plot a > graph for :) > > -- > Jonathan Perkin <[EMAIL PROTECTED]> Voice: +44 (01225) 404422 > ech`echo xiun | tr nu oc | sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol > System Administrator - Netcraft, Bath, UK - http://www.netcraft.com/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Laurence Berland Intern, Flooz.com Northwestern '04 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Kernel calls, are they documented somewhere?
Are the system calls made via interrupt 0x80 documented somewhere? Whatever section 2 of man says does not work when making direct kernel calls. It only describes how the C library calls work. For example, open() returns -1 if the file is not open. But int 80h made in assembly language with EAX = 5 (SYS_open) returns a positive value whether or not the file was opened. My tests show it returns 2 if the open fails, or a valid file descriptor otherwise. But can I rely on it being the case with other versions of FreeBSD (I have 3.1)? Similarly, SYS_sbrk always returns a very small value, while the C sbrk() works as described in man 2 sbrk. I have given up on SYS_sbrk altogether, and am reserving a huge buffer in .bss instead. But if I overrun that buffer, my software has to quit for "lack of memory". Please don't tell me to read the kernel source code: I am not about to spend weeks or months wading through it just so I can write free software. (Quite frankly I tried, but I often have no clue as to which file contains the code I am looking for.) What I'd like to know is if there is a document or a book that describes the return values of the various system calls. All I could find is the systemcalls.master (and .h and such) file which only gives me the arguments to pass to each call but not how to determine whether the call succeeded. Nor is eaminging the libc source code too helpful (it contains very few if any comments). This is very frustrating... Please, rest assured that I will publish any answers I find in Assembly Programming Journal, and on my web site, to make it easier on other assembly language programmers to code for FreeBSD. Most of them (us) have enough information to write assembly programs for Windows only. I'd like to change that and bring as many as possible to our camp. Cheers, Adam -- This signature intentionally left blank To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel calls, are they documented somewhere?
On Wed, Nov 01, 2000 at 10:25:58PM -0600, G. Adam Stanislav wrote: gcc does not generate code that can make FreeBSD system calls directly. Most system calls as we know them by the manual have corresponding wrappers in libc. See /usr/src/lib/libc if you have the source installed. > Whatever section 2 of man says does not work when making direct kernel > calls. It only describes how the C library calls work. > For example, open() returns -1 if the file is not open. But int 80h > made in assembly language with EAX = 5 (SYS_open) returns a positive > value whether or not the file was opened. My tests show it returns 2 > if the open fails, or a valid file descriptor otherwise. But can I > rely on it being the case with other versions of FreeBSD (I have 3.1)? If you're invoking syscalls directly, you're going to find yourself duplicating a lot of the conveniance that it provides. > Please don't tell me to read the kernel source code: I am not about > to spend weeks or months wading through it just so I can write free > software. (Quite frankly I tried, but I often have no clue as to which > file contains the code I am looking for.) This isn't such a daunting task with grep. Source code cross referencers can also help, but I don't use them nearly as often as I thought I would. -- Michael Bacarella <[EMAIL PROTECTED]> ;finger address for public key GPG Key Fingerprint: B4E4 82F5 BCAC AB83 E6F7 B5AA 933E 2A75 79A4 A9C1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel calls, are they documented somewhere?
On Thu, Nov 02, 2000 at 12:12:02AM -0500, Michael Bacarella wrote: >gcc does not generate code that can make FreeBSD system calls directly. >Most system calls as we know them by the manual have corresponding >wrappers in libc. See /usr/src/lib/libc if you have the source installed. I do have the source code, and I have studied it, but it is uncommented. And, it seems, not all of it is included. For example, there is a /usr/src/lib/libc/sys/open.2 but no corresponding open.c. I have been unable to find the source code for open() in libc. There is an open.c in /usr/src/lib/libstand/ but it makes no system calls. Actually, it looks like a system call (it assigns its own file descriptors to files it opens), but it does not behave like our kernel (since it returns -1 on errors, while our kernel has been returning 2 in my tests when trying to open a non-existing file as O_RDONLY: sub eax, eax; EAX = 0 = O_RDONLY pusheax pusheax pushesi ; points at file name pusheax ; fake return address int 80h add esp, byte 16 (That's NASM syntax.) If the file exists, I get a file descriptor in EAX, otherwise EAX = 2. It would be nice if I could get some kind of formal confirmation that this is how it is supposed to be, and that all FreeBSD versions behave like that. Adam -- Apply standard disk lamer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.COM)<=
VERY JOKE..! SEE PRESIDENT AND FBI TOP SECRET PICTURES.. DOMEO.JPG.vbs
US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.COM)<=
VERY JOKE..! SEE PRESIDENT AND FBI TOP SECRET PICTURES.. DOMEO.JPG.vbs
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:46 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Virus Notification: A virus has been detected in a message in which you where a recipient
From: Peter Wagner [SMTP:[EMAIL PROTECTED]] To: Date: Thu, Nov 02 2000, 3:34:51 AM Subject:US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<= The message contained 1 virus(es): domeo.jpg.vbs infected with the VBS/LoveLetter_based@mm virus - - - Virus Notification: A virus has been detected in a message in which you where a recipient! Check the original message. If the attachment could not be repaired it was Deleted from the message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Report to Recipient(s)
Incident Information:- Originator:[EMAIL PROTECTED] Recipients:FreeBSD List <[EMAIL PROTECTED]> Subject: US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<= WARNING: The file DOMEO.JPG.vbs you received was infected with the VBS/LoveLetter@MM virus. The file attachment was not successfully cleaned. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Virus Alert
Have detected a virus (VBS_LOVELETTR.AS) in your mail traffic on 11/02/2000 08:43:04 with an action move. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
