pthread_cancel
Hi, Is anyone working on pthread_cancel? ; Bodo -- Bodo Rüskamp, b...@rueskamp.com, 51°55' N 7°41' E (1) Elvis is alive. (2) Dinosaurs too. http://www.lochness.scotland.net/camera.htm (3) The next millenium starts on January 1st 2000. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: vinum performance
Greg Lehey g...@lemis.com wrote: On Thursday, 17 June 1999 at 3:43:10 -0400, David E. Cross wrote: I have a drive that is rated at ~16 Meg/second, and indeed it delivers on t he order of 15+ Meg/second. If I use Vinum to create a concatinated device of 2 such units performance drops to 2.5 Meg/sec. This seems like a drastic drop in performance. Indeed, if you're comparing apples with apples. Possible marginally-related data point: with the 3.1-RELEASE vinum, and with striped drives (yes, I know the original user is using concatenated devices), I saw pretty bad write performance with the default filesystem frag size. Increasing the frag size (via newfs), increased performance substantially. -- Darryl Okahata darr...@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Beware of UnixWare 7
Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I tried installing it on a machine with two other systems installed. It failed to install (looped trying to install drivers it didn't need). When I rebooted, I found that it had overwritten the Master Boot Record (which is silly, since it knew there were two other systems on the disk), and it also rewrote the partition table: it changed the numbers of the partitions. This is particularly difficult for FreeBSD, which has the partition number explicitly in the device name. In my case, FreeBSD was on partition 2, devices /dev/rwd0s2a and /dev/rwd0s2e. It was moved to partition 3, so the device names changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have device nodes for these devices, I was unable to remount the root file system, and I had to use the fixit floppy to rewrite the partition table. Nothing got lost, but it was a real pain. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: vinum performance
[Format recovered--see http://www.lemis.com/email/email-format.html] On Friday, 18 June 1999 at 1:14:20 -0700, Darryl Okahata wrote: Greg Lehey g...@lemis.com wrote: On Thursday, 17 June 1999 at 3:43:10 -0400, David E. Cross wrote: I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the order of 15+ Meg/second. If I use Vinum to create a concatinated device of 2 such units performance drops to 2.5 Meg/sec. This seems like a drastic drop in performance. Indeed, if you're comparing apples with apples. Possible marginally-related data point: with the 3.1-RELEASE vinum, and with striped drives (yes, I know the original user is using concatenated devices), I saw pretty bad write performance with the default filesystem frag size. Increasing the frag size (via newfs), increased performance substantially. That shouldn't have anything to do with it. If you see anything unusual in Vinum performance, please tell me. It's easy to come to incorrect conclusions about the cause of performance problems, and disseminating them doesn't help. Follow the links at http://www.lemis.com/vinum.html for a discussion of Vinum performance. The biggest factor influencing Vinum performance on striped plexes is the stripe size, which should be at least 256 kB. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I ... When I rebooted, I found that it had overwritten the Master Boot Record (which is silly, since it knew there were two other systems on the disk), and it also rewrote the partition table: it changed the numbers of the partitions. This is particularly difficult for FreeBSD, which has the partition number explicitly in the device name. which is not much smarter... /dev/rwd0s2e. It was moved to partition 3, so the device names changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have device nodes for these devices, I was unable to remount the root file system, and I had to use the fixit floppy to rewrite the partition table. Nothing got lost, but it was a real pain. hit a similar problem the other day, i think i managed to fix it withouth the floppy by mounting again the root partition on /mnt and there acting appropriately. cheers luigi ---+- Luigi RIZZO, lu...@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ First International Workshop on Networked Group Communication ---+- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Friday, 18 June 1999 at 8:29:10 +0200, Luigi Rizzo wrote: Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I ... When I rebooted, I found that it had overwritten the Master Boot Record (which is silly, since it knew there were two other systems on the disk), and it also rewrote the partition table: it changed the numbers of the partitions. This is particularly difficult for FreeBSD, which has the partition number explicitly in the device name. which is not much smarter... /dev/rwd0s2e. It was moved to partition 3, so the device names changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have device nodes for these devices, I was unable to remount the root file system, and I had to use the fixit floppy to rewrite the partition table. Nothing got lost, but it was a real pain. hit a similar problem the other day, i think i managed to fix it withouth the floppy by mounting again the root partition on /mnt and there acting appropriately. Nice one. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
Greg Lehey wrote: Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. SCO has been a real pain in the bum about partition tables for as long as I can remember. Don't even try installing it anywhere other than on your normal boot disk either. I've never had any luck getting SCO OpenServer onto a secondary disk of any kind. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Friday, 18 June 1999 at 18:44:50 +0930, Mark Newton wrote: Greg Lehey wrote: Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. SCO has been a real pain in the bum about partition tables for as long as I can remember. To be fair, this is UnixWare (ex Novell, ex Univel, ex USL), not OpenDeathtrap. I always thought it a little better, but I never tried to share disks with it before. Don't even try installing it anywhere other than on your normal boot disk either. I've never had any luck getting SCO OpenServer onto a secondary disk of any kind. That wouldn't surprise me. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
It seems Greg Lehey wrote: FreeBSD, which has the partition number explicitly in the device name. In my case, FreeBSD was on partition 2, devices /dev/rwd0s2a and /dev/rwd0s2e. It was moved to partition 3, so the device names changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have device nodes for these devices, I was unable to remount the root file system, and I had to use the fixit floppy to rewrite the partition table. Nothing got lost, but it was a real pain. Thats the reason why I always use /dev/rwd0a etc, ie without the slicenumbers in it, that way it will always use the FreeBSD slice no matter what number is has gotten. Of cause that only works if you only have one FreeBSD slice, but that is most normal I guess... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Friday, 18 June 1999 at 11:29:53 +0200, Soren Schmidt wrote: It seems Greg Lehey wrote: FreeBSD, which has the partition number explicitly in the device name. In my case, FreeBSD was on partition 2, devices /dev/rwd0s2a and /dev/rwd0s2e. It was moved to partition 3, so the device names changed to devices /dev/rwd0s3a and /dev/rwd0s3e. Since I didn't have device nodes for these devices, I was unable to remount the root file system, and I had to use the fixit floppy to rewrite the partition table. Nothing got lost, but it was a real pain. Thats the reason why I always use /dev/rwd0a etc, ie without the slicenumbers in it, that way it will always use the FreeBSD slice no matter what number is has gotten. Of cause that only works if you only have one FreeBSD slice, but that is most normal I guess... Yup, I prefer the compatibility slice names too. They're not as fussy as the strict slice names, and they look less System V.4-ish. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: help with CD-Rom
bush doctor wrote: Once morpheus_...@depechemode.com aka (morpheus_...@depechemode.com) said: Yesterday I was able to mount my CD-ROM just fine. Today after a lot of kernel hacking I am not. I am fairly new at this so this may be a really easy answer. I have an entry in the fstab file that references my cdrom /dev/wcd0c /cdromro, noauto 0 0 but when I goto mount /cdrom I get an error that says /dev/wcd0c: Device not configured Any ideas as to what I am doing or have done wrong here No ideas as to what you're doing :-) However, Check your kernel config file and make sure you have the following device wcd0#IDE CD-ROM I see an acd0 device line in my 3.2 GENERICS config file. Could someone please explain the diffrence between wcd0 and acd0 devices? What has changed? Thanks in advance. Milon -- pape...@pvt.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
Greg Lehey wrote: On Friday, 18 June 1999 at 18:44:50 +0930, Mark Newton wrote: SCO has been a real pain in the bum about partition tables for as long as I can remember. To be fair, this is UnixWare You mean UnixSwear, don't you? :-) - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: pthread_cancel
Bodo Rueskamp wrote: Is anyone working on pthread_cancel? I've got some stale patches for it which I'll bring up to date. But to implement the POSIX cancelable functions correctly will take some hacking of libc. I can do this also, but it needs further discussion as to how it _should_ be done. See the -hackers and -current mailing list archives, and pay particular attention to Derek Seaman's posts. Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: pthread_cancel
On Fri, 18 Jun 1999, Daniel Eischen wrote: Bodo Rueskamp wrote: Is anyone working on pthread_cancel? I've got some stale patches for it which I'll bring up to date. But to implement the POSIX cancelable functions correctly will take some hacking of libc. I can do this also, but it needs further discussion as to how it _should_ be done. See the -hackers and -current mailing list archives, and pay particular attention to Derek Seaman's posts. Do you mean Richard? Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: pthread_cancel
Brian Fundakowski Feldman wrote: See the -hackers and -current mailing list archives, and pay particular attention to Derek Seaman's posts. Do you mean Richard? Oops. My sincere apologies to Richard Seaman (whom I actually meant - is it who or whom?). Derek is another fellow who happens to have the same last name. Sorry again, Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Fri, 18 Jun 1999, Greg Lehey wrote:
Those of you who were at Usenix may have picked up a free copy of a
UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I
tried installing it on a machine with two other systems installed. It
failed to install (looped trying to install drivers it didn't need).
When I rebooted, I found that it had overwritten the Master Boot
Record (which is silly, since it knew there were two other systems on
Greg,
Now that you've recovered I can wax rhetoical (briefly ;-).
I have run UnixWare since day 1 - when Novell bought it from USL.
It had bad kernel code in version 1.1 - panic on every shutdown
when it couldn't flush dirty pages.
SCO cleaned that up but everything that used to be free on UW1.1 is
now activated by a licence key and $$$. It's approx $795 to turn on
anything (even netscape)...
I run 2.1.2 on a production box - at least for now. (Moving
to Slackware soon on this box...) The lamest implementation of
Unix I've ever seen.
Many conf tasks remain non-trivial as compared to BSD or Linux due
to inexpertise on SCO's end...as the red Sytem Admin Handbook once
stated (Neveth, Snyder et al.) SCO Unix* is `perverse'.
An example of clumsiness: the sendmail.cf file that comes stock with
2.1.2 is for OpenServer hence all paths are wrong. And, for whatever
reason SCO didn't see fit to build makemap so making a mailertable is
tougher than it should be...on and on...
I got UW 7 in the mail (kind of like America Online). It makes a
lovely ashtray. (And you can rest a pint there as well!)
Cheers,
Tom
--- North Richmond Community Mental Health Center ---
Thomas Good MIS Coordinator
Vital Signs: tomg@ { admin | q8 } .nrnet.org
Phone: 718-354-5528
Fax: 718-354-5056
/* Member: Computer Professionals For Social Responsibility */
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Inetd and wrapping.
Sheldon and myself have been looking at the wrapping support in inetd, and
I'd be interested to hear what people think on the following issues.
David.
Making wrapping a run time option:
It seems strange to make wrapping a compile time option,
when it could be a command line option, or a per service
option in inetd.conf? I'd suggest that we have two command
line options, one which disables wrapping all together and
one which disables it for internal services.
Wrapping dgram services:
If our inetd wrapping is to replace tcpd we need to be able
to wrap the initial connection to udp based services. The
man page should make it clear that it can only check the
first connection to the service, and after that the service
is on its own.
An interesting question is, should we try to do this in a
clever fashion, or should we stick with something simple.
The simple implimentation looks like:
fork(); if( rejected ) exit() else provide_serivce();
The clever implimentation would look like:
fork; while( rejected !timedout ) { get new packet };
if( timedout ) exit() else provide_service();
The clever one reduces forks, but as inetd isn't the place
where high performance services are provided from the extra
complexity may not be worth it.
Making internal services cleverer if they have forked:
If an internal udp service has forked it could provide its
service using a similar loop to the one for clever UDP
wrapping. This would reduce the amount of forking. Is it
worth the extra complexity?
Trying to wrap stream/wait services:
Doing this would involve being able to find the address of
the next connection on a listening socket without calling
accept. AFAIK this isn't possible with the normal socket
interface, and isn't supported by tcpd. We should probably
just say this isn't possible in the man page?
Wrapping of weirder types:
According to the inetd man page we support sockets of type:
``stream'', ``dgram'', ``raw'', ``rdm'', or ``seqpacket''.
I (personally) have never seen any inetd services using
raw, rdm or seqpacket - is it worth providing wrapping for
these socket types?
Adding wrapper support to wait daemons:
Daemons that use the wait class can only have their first
successful connection wrapped by inetd, and then they are
free to accept or reject subsequent connections themselves
until they exit. Usually they have a timeout (identd,
talkd), or only serve one connection (tftpd, rpc.rstatd).
Should we go around and try to add wrapper support into
these services?
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Inetd and wrapping.
On Fri, 18 Jun 1999 14:11:26 +0100, David Malone wrote: Sheldon and myself have been looking at the wrapping support in inetd, and I'd be interested to hear what people think on the following issues. Is the general consensus that we absolutely must have wrapper support built into inetd? What we've got right now isn't doing a fantastic job, and trying to wedge in the job tcpd did before is getting progressively uglier. :-( Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Inetd and wrapping.
On Fri, Jun 18, 1999 at 03:30:03PM +0200, Sheldon Hearn wrote: Is the general consensus that we absolutely must have wrapper support built into inetd? What we've got right now isn't doing a fantastic job, and trying to wedge in the job tcpd did before is getting progressively uglier. :-( I think we may almost be there, and we've unearther problems with inetd that were there anyway - but not as obvious without wrapping. While the process is painful I think the end result may be OK. David. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Buffer overflows question
Hello. Would you, please, comment the kernel message below: sio0: 478 more tty-level buffer overflows (total 478) I use FreeBSD 2.2.8; there is a modem (without hardware flow control) on /dev/cua0; I have a leased line with 38400 bps full duplex; there is PPP (user mode) tunnel to my ISP. Can you answer what are these buffers (kernel or UART 16550A) and how can I fight with these buffer overflows. Thank you. -- Malinin A. G.
Dual boot with LINUX
Can linux be booted using the freebsd boot manager? Lilo always seems to want to install itself. Dennis To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
Many conf tasks remain non-trivial as compared to BSD or Linux due
to inexpertise on SCO's end...as the red Sytem Admin Handbook once
stated (Neveth, Snyder et al.) SCO Unix* is `perverse'.
I enjoy reading the section in that book on network hardware whenever I
need a good laugh. People shouldnt attempt to write about things that they
so clearly know nothing about.
Dennis
An example of clumsiness: the sendmail.cf file that comes stock with
2.1.2 is for OpenServer hence all paths are wrong. And, for whatever
reason SCO didn't see fit to build makemap so making a mailertable is
tougher than it should be...on and on...
I got UW 7 in the mail (kind of like America Online). It makes a
lovely ashtray. (And you can rest a pint there as well!)
Cheers,
Tom
--- North Richmond Community Mental Health Center ---
Thomas Good MIS Coordinator
Vital Signs: tomg@ { admin | q8 } .nrnet.org
Phone: 718-354-5528
Fax: 718-354-5056
/* Member: Computer Professionals For Social Responsibility */
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
dd(1) changes (review please)
Would someone (being more experienced than I) review these modifications to
FreeBSD (HEAD)'s bin/dd? In my changes, I've tried to convert every random
int, u_long, etc. to the proper types (off_t, u_int64_t, {,s}size_t,
and keeping the ints that SHOULD be ints), which I am pretty sure I've
done properly. I've also removed bogus casts, added new ones, and generally
cleaned up the code into a more maintainable lump.
I suppose by learning the code and doing the cleanups/fixes, I've designated
myself as the maintainer of dd(1), haven't I? *grin*
Brian Fundakowski Feldman _ __ ___ ___ ___ ___
gr...@freebsd.org _ __ ___ | _ ) __| \
FreeBSD: The Power to Serve!_ __ | _ \._ \ |) |
http://www.FreeBSD.org/ _ |___/___/___/
dd.patch.gz
Description: Binary data
Re: Introduction
On Fri, 18 Jun 1999, Ruslan Ermilov wrote: On Fri, Jun 18, 1999 at 12:24:16PM -0400, Brian Fundakowski Feldman wrote: Hello, I'm Brian Feldman, a new committer to the FreeBSD source tree! Some of the things I'll be working on are: - maintaining and improving IPFW (cleanups too, of course) Let's join our efforts in this area! IPFW code is very ugly... Which is basically due to it being hacked on for years without a cleanup. Now's the time (between major versions) to do this, I think. How's this: let's organize a small group to bounce ideas off eachother, first of all (I'm forwarding this to hackers to perhaps elicit a response of more people.) We should get ideas on what people think is wrong with the current implementation, what new features should be added, and where we should rearchitect. IPFW is reasonably small enough to redesign/reimplement in a few weeks (with multiple intelligent people working on it, of course =), so I think this is a worthwhile project. So Ruslan, why don't we organize a small group that will be doing this (this being the rewrite, and BTW I really want the external interface to IPFW to be backward-compatible)? We should then look through any relevant PRs and make sure to have all the info we need before undertaking this. I hope this is the kind of thing Jordan wanted! John Birrell (IIRC). Everyone would always appreciate some introduction :) Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.freebsd.org _ |___/___/___/ -- Ruslan ErmilovSysadmin and DBA of the r...@ucb.crimea.uaUnited Commercial Bank, r...@freebsd.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.orgThe Power To Serve http://www.oracle.com Enabling The Information Age Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Obtaining client host IP before accept()
Hi folks,
I found a thread in the freebsd-hackers archive from 1997 that covered
my question, but the answers didn't nail it down to a yes or no
satisfactorily.
We could save ourselves a lot of angst in the work we're doing on inetd
if we could determine the client IP address of a TCP socket before
calling accept(). Alternatively, we'd love a way to accept() without
acknowledging a connection, so that the connection request could be left
for a child that expected to do its own socket() and bind() calls.
My take on the previous thread is that this is impossible in userland.
I'd appreciate it someone who knows the answer for a fact could look at
the code below and answer the following question:
Will the IP address of the client host ever enter buf[] if the
accept() is _not_ uncommented?
I don't need portability, since this is for use within the FreeBSD inetd
exclusively.
Thanks,
Sheldon.
#include err.h
#include errno.h
#include netdb.h
#include stdio.h
#include unistd.h
#include netinet/in.h
#include arpa/inet.h
#include sys/param.h
#include sys/types.h
#include sys/socket.h
/*
* Use an arbitrary port that you know isn't in use on the system. I
* don't run ircd, so this is safe for me.
*/
#define LISTEN_PORT (6667)
#define BUFSIZE (1500)
int
main(void)
{
int ctl;
int peek;
int i = 1;
int port = LISTEN_PORT;
char buf[BUFSIZE];
struct sockaddr_in server_addr;
struct sockaddr_in client_addr;
struct in_addr bind_address;
struct msghdr msg;
if ((ctl = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) 0)
err(errno, error creating socket);
printf(socket number %d created\n, ctl);
if (setsockopt(ctl, SOL_SOCKET, SO_REUSEADDR, (char *)i, sizeof(i)))
err(errno, error setsockopt(SO_REUSEADDR): );
if (setsockopt(ctl, SOL_SOCKET, SO_REUSEPORT, (char *)i, sizeof(i)))
err(errno, error setsockopt(SO_REUSEPORT): );
printf(setsockopt(SO_REUSEADDR|SO_REUSEPORT) successful\n);
bind_address.s_addr = htonl(INADDR_ANY);
server_addr.sin_family = AF_INET;
server_addr.sin_addr = bind_address;
server_addr.sin_port = htons(port);
if (bind(ctl, (struct sockaddr *)server_addr, sizeof(server_addr)))
err(errno, error (%d) bind(%lu:%d), errno,
server_addr.sin_addr.s_addr, port);
printf(bound to port %d\n, port);
if (listen(ctl, 0))
err(errno, error listening: );
printf(listening...\n);
/*
i = sizeof(client_addr);
if (peek = accept(ctl, (struct sockaddr *)client_addr, i) 0)
err(errno, accept() failed: );
printf(connection accepted from %s\n,
inet_ntoa(client_addr.sin_addr));
*/
msg.msg_name = (void *)server_addr;
msg.msg_namelen = sizeof(server_addr);
msg.msg_iovlen = 0;
msg.msg_control = (caddr_t)buf;
msg.msg_controllen = 1;
while (recvmsg(ctl, msg, MSG_PEEK) 0) {
warn(recvmsg failed: );
printf(msg_flags = %i\n, msg.msg_flags);
sleep(2);
}
printf(recvmsg successful, wtf?\n);
close(ctl);
/*
close(peek);
*/
return(0);
}
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
new-IPFW (was Re: Introduction)
I also want new-IPFW to be modular. This would mean that, for instance, DUMMYNET would be just one plug-in to IPFW. More would be created in an extensible manner, rather than the current hack to do DUMMYNET. Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: vinum performance
Greg Lehey g...@lemis.com wrote: On Friday, 18 June 1999 at 1:14:20 -0700, Darryl Okahata wrote: Possible marginally-related data point: with the 3.1-RELEASE vinum, and with striped drives (yes, I know the original user is using concatenated devices), I saw pretty bad write performance with the default filesystem frag size. Increasing the frag size (via newfs), increased performance substantially. That shouldn't have anything to do with it. If you see anything unusual in Vinum performance, please tell me. It shouldn't, perhaps, have anything to do with it, but it did. I'm simply reporting empirical results, where I kept the stripe size constant and varied the filesystem frag size. I was able to get around a 2X improvement in write speed by increasing the frag size. Why, I don't know. I do know that I saw what I saw. ;-) This was, however, using 128K stripe sizes. Perhaps there's an interaction between small stripes and frag sizes? Also, I'm still stuck using the 3.1-RELEASE vinum. I want to upgrade to something newer, but I can't do so until I manage to backup my system (and I've got a lot of files to backup). ;-( It's easy to come to incorrect conclusions about the cause of performance problems, and disseminating them doesn't help. Follow the links at It's not so much of a conclusion as a data point. I'm simply reporting what I saw. Note that I am NOT saying that varying the frag size is the most significant way of improving performance. I'm sure that you're correct in your recommendations. However, I was able to significantly affect write performace simply by changing the frag size. As I've said, I don't know why, but it happened. I don't know how reproducible this is; maybe it's related to rotational latencies, the particular drive type, drive firmware, CPU speed, etc.. I don't know -- but I do know that it happened, and I'm simply reporting a data point. This is just a single data point, and we all know how dangerous it is to extrapolate from a single data point. ;-) However, if others report their findings, we may or may not find a trend. -- Darryl Okahata darr...@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Heavily loaded nfs/amd gets stuck
No action on this in -current for a few days, so let's try
hackers. In response to some suggestions I tried raising the number of
nfsiod's to 20 (the max) and increasing the sysctl cache value to 10,
still no joy.
I'm using amd to automount directories on sun (sol 2.6) server to
my freebsd-current client machine. Details below, any help appreciated.
Doug
On Thu, 17 Jun 1999, Studded wrote:
Also, should I be considering a move to -current for this box? Is
-current stable enough right now to run a fairly heavily loaded web
server? If the NFS in -current is going to be doing better than what's in
-stable it will be worth a little headache to change, since our structure
depends on it heavily.
Well I went ahead and tried -current, and got better results, but
the same crash. With the following map:
/defaults type:=nfs;opts:=rw,nosuid,vers=3,intr,proto=udp,noconn
* rhost:=IP${key};rfs:=/Space/${key}
It went MUCH farther through the script (mounted about 60 out of 80
directories) but it crashed just the same. Kernel stack trace looked like
this:
stuff
Xresume1()
--- interrupt
bcmp()
mountnfs()
nfs_mount()
mount()
syscall()
Xint0x80syscall()
Ok, another interesting development. What the script I'm running
does is go through each user account on our sun servers, reads a file,
then uses certain values from that file to print out conf files on the
local freebsd server that's acting as an NFS client (and crashing). So
it's mounting a directory, reading 250 files, mounting the next directory,
reading the next 250 files, and so on for a total of 80 directories.
I changed the script so that after each reading the 250 files for
each directory it did a 'sleep 10' before it started again. This allowed
the script to run through to completion.
So, I'm still open to new things to try here. Does anyone have any
suggestions? I've been looking at nfsiod, all I had started was the
default 4 because I thought they would spawn more if they needed more, but
apparently they don't. Would more of those help? Would turning them off
altogether help? I *really* need help with this since my boss is
(justifiably I think) loathe to put this box into service without a little
more concrete evidence that NFS can hold up. Would it be better to send
this to -hackers? Maybe file a PR? I don't mean to sound like a pest, and
yes I know that we're all volunteers, etc. But after wheedling for 4
months to try freebsd I'm kind of feeling the pinch here. :-/
Thanks for any help you can provide,
Doug
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Introduction
On Fri, Jun 18, 1999 at 01:50:09PM -0400, Brian Fundakowski Feldman wrote: On Fri, 18 Jun 1999, Ruslan Ermilov wrote: On Fri, Jun 18, 1999 at 12:24:16PM -0400, Brian Fundakowski Feldman wrote: Hello, I'm Brian Feldman, a new committer to the FreeBSD source tree! Some of the things I'll be working on are: - maintaining and improving IPFW (cleanups too, of course) Let's join our efforts in this area! IPFW code is very ugly... Which is basically due to it being hacked on for years without a cleanup. Now's the time (between major versions) to do this, I think. How's this: let's organize a small group to bounce ideas off eachother, first of all (I'm forwarding this to hackers to perhaps elicit a response of more people.) We should get ideas on what people think is wrong with the current implementation, what new features should be added, and where we should rearchitect. Agreed. So, Jonathan, could you please create i...@freebsd.org for us? IPFW is reasonably small enough to redesign/reimplement in a few weeks (with multiple intelligent people working on it, of course =), so I think this is a worthwhile project. So Ruslan, why don't we organize a small group that will be doing this (this being the rewrite, and BTW I really want the external interface to IPFW to be backward-compatible)? We should then look through any relevant PRs and make sure to have all the info we need before undertaking this. I've closed a number of ipfw's PRs last week, most of them were for ipfw(8). Cheers, -- Ruslan Ermilov Sysadmin and DBA of the r...@ucb.crimea.ua United Commercial Bank, r...@freebsd.orgFreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Introduction
On Fri, 18 Jun 1999, Brian Fundakowski Feldman wrote: On Fri, 18 Jun 1999, Ruslan Ermilov wrote: Let's join our efforts in this area! IPFW code is very ugly... Which is basically due to it being hacked on for years without a cleanup. Now's the time (between major versions) to do this, I think. How's this: let's organize a small group to bounce ideas off eachother, first of all (I'm forwarding this to hackers to perhaps elicit a response of more people.) We should get ideas on what people think is wrong with the current implementation, what new features should be added, and where we should rearchitect. What about support for protocol verification ?? (Example : Blocking of malformed ftp commands.) Wich layer would it be logically to implement this in ? Is a userland proxy the only way ? Nicolai Petri WM-data BFC To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: help with CD-Rom
Papezik Milon wrote: I see an acd0 device line in my 3.2 GENERICS config file. Could someone please explain the diffrence between wcd0 and acd0 devices? What has changed? The name. ATAPI CD-ROMs are now called acd. MAKEDEV will typically make wcd-acd symlinks in the /dev directory for hysterical raisins. -- Where am I, and what am I doing in this handbasket? Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Introduction
On Fri, 18 Jun 1999, Nicolai Petri wrote: On Fri, 18 Jun 1999, Brian Fundakowski Feldman wrote: On Fri, 18 Jun 1999, Ruslan Ermilov wrote: Let's join our efforts in this area! IPFW code is very ugly... implementation, what new features should be added, and where we should rearchitect. What about support for protocol verification ?? (Example : Blocking of malformed ftp commands.) I don't like the idea of implementing protocols MEANT for userland in the kernel. Doing this leads to code duplication (a LOT of it) and unnecessary complexity. This would just lead to people wanting an entire ftpd in the kernel (which wouldn't be a good idea, even after having built the parsers/state machine (or worse) into the kernel). This is entirely impractical, and without a hybrid user/kernel model impossible. Wich layer would it be logically to implement this in ? This should be done in the user land. Is a userland proxy the only way ? Nicolai Petri WM-data BFC Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: help with CD-Rom
On Fri, Jun 18, 1999 at 12:57:40PM -0600, Wes Peters wrote: Could someone please explain the diffrence between wcd0 and acd0 devices? What has changed? The name. ATAPI CD-ROMs are now called acd. MAKEDEV will typically make wcd-acd symlinks in the /dev directory for hysterical raisins. ^ I understand - it will create symlinks to stop users getting hysterical as their CD-ROM isn't working anymore ;). bye, Harold -- Shabby Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Introduction
On Thu, Jun 17, 1999 at 02:34:55PM -0400, Ugen Antsilevitch wrote: The part that obviously interests me is IPFW - if you guys are interested to put some effort in real i.e. stateful firewall to be developed i'd love to offer any help i can. Great! How we should proceed -- that's the question. My plan: * Clean the existing code (both userland and kernel) (10-20% done) * Re-design the ipfw's API * Port the existing functionality to the new API * Proceed with new features -- Ruslan Ermilov Sysadmin and DBA of the r...@ucb.crimea.ua United Commercial Bank, r...@freebsd.orgFreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Remote serial gdb--status?
Greg Lehey wrote: I've been away from work for several weeks, and I now find that I can no longer start remote serial gdb. I am using sio0 on the debugged machine side, and sio1 on the debugging machine side. Here are the relevant dmesg outputs: panic (debugged machine): sio0: system console sio0: gdb debugging port ... sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A freebie (debugging machine): sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 I can communicate fine using cu, and a breakout box shows all modem signals asserte (DCD, DTR, DSR, RTS, CTS). When I go into remote debug on panic, RxD flashes, and when freebie tries to attach to panic, TxD flashes, so I'm obviously addressing the correct ports. I've checked the bit rate and configuration of the ports before going into debug, and they look right (9600 bps, cs8, -istrip, -parenb). I don't know what else to look for. Any ideas? I think you need flags 0x50 (instead of 0x90) on panic. From sio(4): Meaning of flags: ... 0x00010 device is potential system console 0x00020 device is forced to become system console 0x00040 device is reserved for low-level IO (e. g. for remote kernel debugging) ... -- Where am I, and what am I doing in this handbasket? Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Dual boot with LINUX
Dennis wrote: Can linux be booted using the freebsd boot manager? Lilo always seems to want to install itself. Provided you install Linux in a primary fdisk partition (slice 1-4), it should work OK. The RedHat default is to install to an extended fdisk partition, and we don't support booting from those. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: vinum performance
I have a drive that is rated at ~16 Meg/second, and indeed it delivers on the order of 15+ Meg/second. If I use Vinum to create a concatinated device of 2 such units performance drops to 2.5 Meg/sec. This seems like a drastic drop in performance. Indeed, if you're comparing apples with apples. Any ideas what I am doin incorrectly? No. You haven't really given any details. Most of the performance testing I have done has been with striped plexes (which offer the potential for better performance), and I've found that in massively concurrent situations the performance is roughly what you would expect (almost n * normal disk performance, where n is the number of disks in the stripe set. I'd expect performance of a concatenated plex to be pretty close to that of the raw disk. How are you measuring performance? I'd recommend rawio (ftp://ftp.lemis.com/pub/rawio.tar.gz). Ok, I am terribly sorry I didn't provide more information. I was very tired (it has been a long week; after the NFS work the main NFS server that has been having all of the problems decided that its main OS partion was going to have a hardware failure...) Anyway, here is some more information... bash-2.03$ df Filesystem1K-blocks UsedAvail Capacity Mounted on /dev/da0s1a 99183215266972324%/ /dev/da0s1e 2032623 1062270 80774457%/usr /dev/da0s1f 198399 3466 179062 2%/var /dev/vinum/concat 29077993 252757 26498997 1%/mnt bash-2.03$ cd /var/tmp bash-2.03$ df -k . Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/da0s1f 198399 3466 179062 2%/var bash-2.03$ dd bs=64k if=/dev/zero of=foo count=2048 2048+0 records in 2048+0 records out 134217728 bytes transferred in 10.218804 secs (13134387 bytes/sec) bash-2.03$ cd /mnt bash-2.03$ df -k . Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/vinum/concat 29077993 252757 26498997 1%/mnt bash-2.03$ dd bs=64k if=/dev/zero of=foo count=2048 2048+0 records in 2048+0 records out 134217728 bytes transferred in 59.653922 secs (2249940 bytes/sec) bash-2.03$ vinum info Can't open history file /var/tmp/vinum_history: Permission denied (13) Can't open /dev/vinum/Control: Permission denied bash-2.03$ su - hostname# vinum info Flags: 0x80204 Total of 21 blocks malloced, total memory: 9552 Maximum allocs: 1264, malloc table at 0xc3583ad4 hostname# vinum printconfig # Vinum configuration of hostname, saved at Fri Jun 18 16:08:56 1999 drive drive1 device /dev/da0s1h drive drive2 device /dev/da1s1h volume concat plex name concat.p0 org concat vol concat sd name concat.p0.s0 drive drive1 plex concat.p0 len 27597000b driveoffset 265b plexoffset 0b sd name concat.p0.s1 drive drive2 plex concat.p0 len 32405704b driveoffset 265b plexoffset 27597000b If you need anything else it can probably be provided. Oh, this is 3.2-STABLE from last week. -- David Cross | email: cro...@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
3.1 panic: vm_page_unwire: invalid wire count: 0
Hello ..
I'm getting the following panic on a P90 running 3.1-RELEASE. This system
is one of our routers and crashes every week or so. I can't find any
reference if this was fixed or not. If someone's been playing in this
area recently I can schedule an upgrade to 3.2 or -STABLE if it would
help.
The panic appears to be a problem inside of procfs, although I'm not sure
it's just an innocent victim to a previous corruption. It doesn't help
that the kernel can't keep time on this box; see PR 12022.
I can make the core files and debugged kernel available if desired.
Some time before this (in this case ~4hrs) this message is logged:
/kernel: vm_page_free: freeing wired page
Here is ye olde stack trace:
#0 boot (howto=256) at ../../kern/kern_shutdown.c:285
285 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:285
#1 0xf012abf8 in at_shutdown (function=0xf0209c25 cvtbsdprot.232+717,
arg=0x0, queue=-193525184) at ../../kern/kern_shutdown.c:446
#2 0xf01cf3f3 in vm_page_unwire (m=0xf043f594, activate=1)
at ../../vm/vm_page.c:1346
#3 0xf0157851 in procfs_rwmem (curp=0xf4861ba0, p=0xf476c3c0,
uio=0xf4868f40)
at ../../miscfs/procfs/procfs_mem.c:256
#4 0xf0157928 in procfs_domem (curp=0xf4861ba0, p=0xf476c3c0,
pfs=0xf0c1c900,
uio=0xf4868f40) at ../../miscfs/procfs/procfs_mem.c:305
#5 0xf01581cf in procfs_rw (ap=0xf4868efc)
at ../../miscfs/procfs/procfs_subr.c:279
#6 0xf0153de1 in vn_read (fp=0xf0bebf80, uio=0xf4868f40, cred=0xf0c15900)
at vnode_if.h:303
#7 0xf0135469 in read (p=0xf4861ba0, uap=0xf4868f94)
at ../../kern/sys_generic.c:121
#8 0xf01ed07b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi =
-272642048,
tf_esi = 4096, tf_ebp = -272644136, tf_isp = -192507932, tf_ebx = 0,
tf_edx = 0, tf_ecx = -272642048, tf_eax = 3, tf_trapno = 8, tf_err =
2,
tf_eip = 134548752, tf_cs = 31, tf_eflags = 659, tf_esp =
-272645204,
tf_ss = 39}) at ../../i386/i386/trap.c:1100
#9 0xf01e145c in Xint0x80_syscall ()
#10 0x804b002 in ?? ()
#11 0x804b2c0 in ?? ()
#12 0x804b30a in ?? ()
#13 0x8049dd7 in ?? ()
#14 0x8049eb9 in ?? ()
#15 0x8049b03 in ?? ()
#16 0x80480e9 in ?? ()
And here be the screwy part:
(kgdb) frame 2
#2 0xf01cf3f3 in vm_page_unwire (m=0xf043f594, activate=1)
at ../../vm/vm_page.c:1346
1346panic(vm_page_unwire: invalid wire count: %d\n,
m-wire_count);
(kgdb) print *m
$6 = {pageq = {tqe_next = 0x705f6d76, tqe_prev = 0x5f656761}, hashq = {
tqe_next = 0x69776e75, tqe_prev = 0x203a6572}, listq = {
tqe_next = 0x61766e69, tqe_prev = 0x2064696c}, object = 0x65726977,
pindex = 1970234144, phys_addr = 540701806, queue = 25637, flags = 10,
pc = 28022, wire_count = 28767, hold_count = 26465, act_count = 101 'e',
busy = 95 '_', valid = 99 'c', dirty = 97 'a'}
(kgdb) print m
$7 = (struct vm_page *) 0xf0209c25
(kgdb) frame 3
#3 0xf0157851 in procfs_rwmem (curp=0xf4861ba0, p=0xf476c3c0,
uio=0xf4868f40)
at ../../miscfs/procfs/procfs_mem.c:256
256 vm_page_unwire(m, 1);
(kgdb) print m
$8 = (struct vm_page *) 0x100
Thoughts? Hints? Buttons to push? Thanks!
Doug White
Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve
http://gladstone.uoregon.edu/~dwhite| www.freebsd.org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Dual boot with LINUX
At 10:07 PM 6/18/99 +0200, you wrote: Dennis wrote: Can linux be booted using the freebsd boot manager? Lilo always seems to want to install itself. Provided you install Linux in a primary fdisk partition (slice 1-4), it should work OK. The RedHat default is to install to an extended fdisk partition, and we don't support booting from those. Well the problem with *should* is that lilo installs itself whenever you run it, and you have to run it to install a new kernel. So I was hoping to find someone that has actually done it. Dennis -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Dual boot with LINUX
Dennis wrote: At 10:07 PM 6/18/99 +0200, you wrote: Dennis wrote: Can linux be booted using the freebsd boot manager? Lilo always seems to want to install itself. Provided you install Linux in a primary fdisk partition (slice 1-4), it should work OK. The RedHat default is to install to an extended fdisk partition, and we don't support booting from those. Well the problem with *should* is that lilo installs itself whenever you run it, and you have to run it to install a new kernel. So I was hoping to find someone that has actually done it. Should just implies YMMV: I have booted Linux with the freebsd boot manager. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
M$ using Linux?
What do you think about that: [r...@beta ~]# nmap -vv -p119 -P0 -sT -O betanews.microsoft.com snip Sequence numbers: E6E23C4C E7368B4F E6E0CC8D E79B4DEC E7A43C4E E76D208A Remote operating system guess: Linux 2.1.122 - 2.1.132; 2.2.0-pre1 - 2.2.2 OS Fingerprint: TSeq(Class=RI%gcd=1%SI=3A46A8) T1(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) T2(Resp=N) T3(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) T4(Resp=Y%DF=N%W=0%ACK=O%Flags=R%Ops=) T5(Resp=N) T6(Resp=N) T7(Resp=N) PU(Resp=N) Nmap run completed -- 1 IP address (1 host up) scanned in 20 seconds /snip and that? [r...@beta ~]# telnet betanews.microsoft.com 119 Trying 207.46.180.35... Connected to betanews.msn.com. Escape character is '^]'. 200 cpmsblns02.microsoft.com InterNetNews NNRP server INN 2.2 21-Jan-1999 ready (posting ok). INN running on NT? And the most interesting: Quoting Alan Cox from the linux-kernel developer list: someone asking: I guess that they run windows-2000 on the beta site, and then I guess is that they have stolen IP-code from Linux. Im right, yes ?! quote on Unlikely. Judging by the window 2000 beta traces they run a BSD stack derivative close to freebsd - and the BSD license permits such use quote off -- Markus Doehr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 190 e-Mail: doe...@aubi.de MD1139-RIPE * To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Dual boot with LINUX
On Fri, Jun 18, 1999 at 04:29:39PM -0400, Dennis wrote: At 10:07 PM 6/18/99 +0200, you wrote: Dennis wrote: Can linux be booted using the freebsd boot manager? Lilo always seems to want to install itself. Provided you install Linux in a primary fdisk partition (slice 1-4), it should work OK. The RedHat default is to install to an extended fdisk partition, and we don't support booting from those. Well the problem with *should* is that lilo installs itself whenever you run it, and you have to run it to install a new kernel. So I was hoping to find someone that has actually done it. Just to say it: I have done it. I used BootEasy to dual-boot RH5.2 and FBSD-3.2-R. RH gets grabby, though: you have to take great pains to a) install it's root partition in a primary partition, and b) not grab the rest of the disk as a 'logical' (ha!) partition, then leave a mess of it marked as 'unused'. I installed FreeBSD first, then RedHat. With RedHat, use fdisk (rather than DiskDruid) to massage the partition table. DiskDruid _might_ work, but it thwarted me once, and I was getting impatient. I recall that I also had to use the 'Partition' utility from FBSD /stand/sysinstall to manually mark the Linux root partition as active (all of the other tools on hand would only let me set one partition as active, I wanted them all to be marked as such). This may not been neccessary, but the BootEasy manager assuredly could see the Linux partition thereafter. When you install LILO, have it do so on the boot block of the partition, not the MBR. Upon installation, LILO noticed that there was another partition, and offered to set up a label for it. I did; and now, when I bring up the Linux half, I can re-jump to the FreeBSD half. -- Brian 'you Bastard' Reichertreich...@numachi.com 37 Crystal Ave. #303Current daytime number: (603)-434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Inetd and wrapping.
Around Today, David Malone wrote : DM I think we may almost be there, and we've unearther problems with inetd DM that were there anyway - but not as obvious without wrapping. While the DM process is painful I think the end result may be OK. As a user, I'd say that it would certainly be nice to have TCPWrapper support in the inetd, but there's no reason why it has to explicitly be made part of inetd. The support (after the patches Sheldon brought in) now is pretty good; is there any reason why the existing functionality should be extended ? A RedHat installation I used yonks ago had TCP/Wrappers installed as is on installation, and had no integration with the inetd; it was basically inetd and the TCP/Wrappers port installed. We're already better than that right now. --- Khetan Gajjar (!kg1779) * khe...@os.org.za http://khetan.os.org.za/ * Talk/Finger khe...@khetan.os.org.za FreeBSD enthusiast* http://www2.za.freebsd.org/ Reference : 19990618143617.a43...@bell.maths.tcd.ie Date : Jun 18, 1999, 2:36pm To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: M$ using Linux?
I heard that Windows-2000 IS linux :-) Dennis At 11:08 PM 6/18/99 +0200, Markus Döhr wrote: What do you think about that: [r...@beta ~]# nmap -vv -p119 -P0 -sT -O betanews.microsoft.com snip Sequence numbers: E6E23C4C E7368B4F E6E0CC8D E79B4DEC E7A43C4E E76D208A Remote operating system guess: Linux 2.1.122 - 2.1.132; 2.2.0-pre1 - 2.2.2 OS Fingerprint: TSeq(Class=RI%gcd=1%SI=3A46A8) T1(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) T2(Resp=N) T3(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) T4(Resp=Y%DF=N%W=0%ACK=O%Flags=R%Ops=) T5(Resp=N) T6(Resp=N) T7(Resp=N) PU(Resp=N) Nmap run completed -- 1 IP address (1 host up) scanned in 20 seconds /snip and that? [r...@beta ~]# telnet betanews.microsoft.com 119 Trying 207.46.180.35... Connected to betanews.msn.com. Escape character is '^]'. 200 cpmsblns02.microsoft.com InterNetNews NNRP server INN 2.2 21-Jan-1999 ready (posting ok). INN running on NT? And the most interesting: Quoting Alan Cox from the linux-kernel developer list: someone asking: I guess that they run windows-2000 on the beta site, and then I guess is that they have stolen IP-code from Linux. Im right, yes ?! quote on Unlikely. Judging by the window 2000 beta traces they run a BSD stack derivative close to freebsd - and the BSD license permits such use quote off -- Markus Doehr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 190 e-Mail: doe...@aubi.de MD1139-RIPE * To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Friday, 18 June 1999 at 7:17:14 -0400, Thomas Good wrote: On Fri, 18 Jun 1999, Greg Lehey wrote: Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. I tried installing it on a machine with two other systems installed. It failed to install (looped trying to install drivers it didn't need). When I rebooted, I found that it had overwritten the Master Boot Record (which is silly, since it knew there were two other systems on Now that you've recovered I can wax rhetoical (briefly ;-). I have run UnixWare since day 1 - when Novell bought it from USL. It had bad kernel code in version 1.1 - panic on every shutdown when it couldn't flush dirty pages. I used it right from the beginning. The problems I recall were disappearing files and failing NFS config; the latter was crucial for the work I was doing, and the only way I found to fix it was to reinstall NFS. SCO cleaned that up but everything that used to be free on UW1.1 is now activated by a licence key and $$$. It's approx $795 to turn on anything (even netscape)... I thought the licenses were free. I got the main license for free, anyway. I run 2.1.2 on a production box - at least for now. (Moving to Slackware soon on this box...) The lamest implementation of Unix I've ever seen. It looks like you haven't used OpenServer. I think UnixWare is better. Many conf tasks remain non-trivial as compared to BSD or Linux due to inexpertise on SCO's end...as the red Sytem Admin Handbook once stated (Neveth, Snyder et al.) SCO Unix* is `perverse'. This is Open[Server,Deathtrap], not UnixWare. A completely different system. An example of clumsiness: the sendmail.cf file that comes stock with 2.1.2 is for OpenServer hence all paths are wrong. And, for whatever reason SCO didn't see fit to build makemap so making a mailertable is tougher than it should be...on and on... Right, they have a different mailer which they prefer. But it does look clumsy, agreed. I've tried twice more to install UnixWare. It makes all the right noises, but on reboot it just hangs. I'm giving up now. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Fri, 18 Jun 1999, Dennis wrote:
Many conf tasks remain non-trivial as compared to BSD or Linux due
to inexpertise on SCO's end...as the red Sytem Admin Handbook once
stated (Neveth, Snyder et al.) SCO Unix* is `perverse'.
I enjoy reading the section in that book on network hardware whenever I
need a good laugh. People shouldnt attempt to write about things that they
so clearly know nothing about.
Dennis
Argumentum ad hominem? Or simply ad absurdum?
You won't find many SCO fans amongst those who've used more than
one implementation of unix...and Novell getting out of the Unix
business (and taking a beating for doing it) speaks volumes.
--- North Richmond Community Mental Health Center ---
Thomas Good MIS Coordinator
Vital Signs: tomg@ { admin | q8 } .nrnet.org
Phone: 718-354-5528
Fax: 718-354-5056
/* Member: Computer Professionals For Social Responsibility */
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
SMP and Celerons...
Heya, sorry I tried this one on -stable and -questions and noone seems to know, and they actually go so far as to ask me how I got two celerons in a motherboard... so I ask here. I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket 1 adaptors... a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) I boot an SMP kernel, it gets right past autoboot... then panics the message was that it could not find local apic... its kinda strange because essentially with these adaptors, the celerons should be 1) SMP capable, and 2) the same as a PII, except no L2 cache I know others that ran FreeBSD SMP with celerons... anyone know if theres some kind of patch I need or modification I have to make to get either -CURRENT or -STABLE working on this machine? Right now it is running a UP kernel instead of the SMP one and runs fine. -Pat ___ Pat Lynch ly...@rush.net ly...@bsdunix.net Systems Administrator Rush Networking ___ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Sat, 19 Jun 1999, Greg Lehey wrote:
I have run UnixWare since day 1 - when Novell bought it from USL.
I used it right from the beginning. The problems I recall were
disappearing files and failing NFS config; the latter was crucial for
the work I was doing, and the only way I found to fix it was to
reinstall NFS.
I found that with Sendmail too. They forgot about makemap, as I
said. They also didn't include any m4 macros. And so on. And
trying to conf UUCP over TCP is also quite a bit of fun. Installing
Taylor helps there. I have a long list of things that I can do on
other implementations (even Solaris) that take three times as long on
UW...
SCO cleaned that up but everything that used to be free on UW1.1 is
now activated by a licence key and $$$. It's approx $795 to turn on
anything (even netscape)...
I thought the licenses were free. I got the main license for free,
anyway.
Well, I can't comment on UW 7 and its licencing scheme but on 2.1.2
Netscape Fast Track expires and then demands a cash infusion.
Similarly, I got DOS Merge for about 30 days before he expired.
Morningstar PPP demanded a financial jumpstart before I could even
fire it up.
I run 2.1.2 on a production box - at least for now. (Moving
to Slackware soon on this box...) The lamest implementation of
Unix I've ever seen.
It looks like you haven't used OpenServer. I think UnixWare is
better.
Actually, I have...in one respect it is better than UW. It is one system
as opposed to the soup that is UnixWare. USL, Novell and now SCO.
UW is the quintessential white elephant and it shows. Maybe UW 7 is
better but I stopped caring awhile back. BSD is our choice for mail
servers and Slackware is my option for my PostgreSQL servers...it is
very obvious to me (using Slackware since 2.3) that Patrick is ultra
scrupulous about testing everything before he issues a new release.
I also install BSD and *expect* that everything will work. Because it
always has...
Many conf tasks remain non-trivial as compared to BSD or Linux due
to inexpertise on SCO's end...as the red Sytem Admin Handbook once
stated (Neveth, Snyder et al.) SCO Unix* is `perverse'.
This is Open[Server,Deathtrap], not UnixWare. A completely different
system.
True - but SCO has a very heavy hand...as mentioned above I *almost*
prefer OpenServer. I'm rather pleased that my shop will move our last
database from PROGRESS on UW to PostgreSQL on Slackware 01 July 99.
That will end our relationship with SCO and PROGRESS.
I've tried twice more to install UnixWare. It makes all the right
noises, but on reboot it just hangs. I'm giving up now.
So you won't be wanting a subscription to SCO World for father's day, eh?
Cheers,
Tom
--- North Richmond Community Mental Health Center ---
Thomas Good MIS Coordinator
Vital Signs: tomg@ { admin | q8 } .nrnet.org
Phone: 718-354-5528
Fax: 718-354-5056
/* Member: Computer Professionals For Social Responsibility */
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: SMP and Celerons...
Pat Lynch wrote: Heya, sorry I tried this one on -stable and -questions and noone seems to know, and they actually go so far as to ask me how I got two celerons in a motherboard... Couple of things. freebsd-smp is probably the best list. I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket 1 adaptors... a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) I boot an SMP kernel, it gets right past autoboot... then panics the message was that it could not find local apic... its kinda strange because essentially with these adaptors, the celerons should be 1) SMP capable, and 2) the same as a PII, except no L2 cache I have two PPGA Celereon 300A's over clocked to 450 on MSI6905 rev 1.1 boards on a ASUS P2B-D MB. The standard kernel works great for me. Is jumper J3 closed? to support Dual? I also added the following lines to my kernel. # Mandatory: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults plus 1: options NCPU=2 # number of CPUs options NBUS=2 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24# number of INTs I know you said you added the top two. I added the bottom just because I don't like trusting defaults. mptable verified that they are right, but I know for SURE what is being used. Jim -- James E. HousleyPGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: page...@notepage.com 7C F0 B5 BF 27 8B 92 FE The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Introduction
In some email I received from Nicolai Petri, sie wrote: On Fri, 18 Jun 1999, Brian Fundakowski Feldman wrote: On Fri, 18 Jun 1999, Ruslan Ermilov wrote: Let's join our efforts in this area! IPFW code is very ugly... Which is basically due to it being hacked on for years without a cleanup. Now's the time (between major versions) to do this, I think. How's this: let's organize a small group to bounce ideas off eachother, first of all (I'm forwarding this to hackers to perhaps elicit a response of more people.) We should get ideas on what people think is wrong with the current implementation, what new features should be added, and where we should rearchitect. What about support for protocol verification ?? (Example : Blocking of malformed ftp commands.) Surely you jest... Wich layer would it be logically to implement this in ? 5 and above. Is a userland proxy the only way ? With a 100% reliability, yes. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Introduction
Ok...i guess i would be the wrong person for cleaning the code since i kinda responsible for the damn thing being a mess in the first place. I can try:) I however have some ideas on how to make a better API (as in more hooks to userland, which btw now after i have read an FTP requests comment, migh even make more sence). One thing though - if we (you :) will really work on this - can we set up some tiny mailing list for IPFW ? Should we? (Or tell me if i have everyone who was interested on this e-mail To list and forget this request:) --Ugen Ruslan Ermilov wrote: On Thu, Jun 17, 1999 at 02:34:55PM -0400, Ugen Antsilevitch wrote: The part that obviously interests me is IPFW - if you guys are interested to put some effort in real i.e. stateful firewall to be developed i'd love to offer any help i can. Great! How we should proceed -- that's the question. My plan: * Clean the existing code (both userland and kernel) (10-20% done) * Re-design the ipfw's API * Port the existing functionality to the new API * Proceed with new features -- Ruslan Ermilov Sysadmin and DBA of the r...@ucb.crimea.uaUnited Commercial Bank, r...@freebsd.org FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: M$ using Linux?
On Fri, 18 Jun 1999, [iso-8859-1] Markus Döhr wrote: What do you think about that: [r...@beta ~]# nmap -vv -p119 -P0 -sT -O betanews.microsoft.com snip Sequence numbers: E6E23C4C E7368B4F E6E0CC8D E79B4DEC E7A43C4E E76D208A Remote operating system guess: Linux 2.1.122 - 2.1.132; 2.2.0-pre1 - 2.2.2 OS Fingerprint: TSeq(Class=RI%gcd=1%SI=3A46A8) T1(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) T2(Resp=N) T3(Resp=Y%DF=Y%W=7F53%ACK=S++%Flags=AS%Ops=MENNTNW) T4(Resp=Y%DF=N%W=0%ACK=O%Flags=R%Ops=) T5(Resp=N) T6(Resp=N) T7(Resp=N) PU(Resp=N) Nmap run completed -- 1 IP address (1 host up) scanned in 20 seconds /snip and that? [r...@beta ~]# telnet betanews.microsoft.com 119 Perhaps you sent this to the wrong list, or are looking for someone to flame you? :) It's cool that Linux is being used by MS, more power to you. -Alfred (someone who knows a lot of the people on the Hotmail team) :) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: SMP and Celerons...
In reply: Heya, sorry I tried this one on -stable and -questions and noone seems to know, and they actually go so far as to ask me how I got two celerons in a motherboard... so I ask here. I have two PPGA(Socket 370) Celeron 333A's that are on MSI6905 Dual Socket 1 adaptors... a Tyan Thunder 2 motherboard (onboard scsi, sound, etc.) there is a problem with the freebsd sound support for this board, but i am told it is being worked on [?]. I boot an SMP kernel, it gets right past autoboot... then panics the message was that it could not find local apic... its kinda strange because essentially with these adaptors, the celerons should be 1) SMP capable, and 2) the same as a PII, except no L2 cache I know others that ran FreeBSD SMP with celerons... anyone know if theres some kind of patch I need or modification I have to make to get either -CURRENT or -STABLE working on this machine? Right now it is running a UP kernel instead of the SMP one and runs fine. strangeness. i run the same board with dual pII-333's, Tyan Thunder2, S1696DLUA. when i boot, i show two cpus and an apic. i have two theories: 1). these boards have a problem with celery. 2). you have a flaky mb. granted, i haven't heard about too many of them being flaky, but that they have an above average reliability level. but then, there is always someone that get s flake sooner or later. My experience [of about 12 days so far] is that this is a quality midrange system, as configured here, and is maybe even a tad more reliable than my workhorse p133 [which has had three spontaneous reboots in the same period, but running an older -current by a few weeks]. Unless you have some weird boards, -current currently works fine on my system [although -current is subject to overnight changes that produce catastrophic failures every now and then, always check which way the wind is blowing in the -current mailing list before doing a make installworld]. Can you borrow a couple of pII's? It would be interesting to see if the Thunder2's have a problem sith celery. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #41: Tue Jun 15 10:59:11 CDT 1999 jbry...@wahoo:/usr/src/sys/compile/WAHOO Timecounter i8254 frequency 1192991 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = GenuineIntel Id = 0x650 Stepping=0 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268435456 (262144K bytes) avail memory = 257720320 (251680K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 . . . APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 . . . changing root device to da0s1a [and normal boot] jim -- All opinions expressed are mine, if you| I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered! - #1, The Prisoner -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
firewalling (Was Re: Introduction)
How do you feel about (after getting it fixed in -CURRENT) helping with converting ipfw(8) to just a front-end to ipf? I think it's worth discussing whether it's actually worth it to rewrite IPFW or just work on improving ipfilter. (discussion moved to -hackers) Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: firewalling (Was Re: Introduction)
In some email I received from Brian Fundakowski Feldman, sie wrote: How do you feel about (after getting it fixed in -CURRENT) helping with converting ipfw(8) to just a front-end to ipf? I think it's worth discussing whether it's actually worth it to rewrite IPFW or just work on improving ipfilter. (discussion moved to -hackers) I imagine they might be fighting words to some ;) As I see it, if you added hooks for divert to ipfilter in FreeBSD and maybe added the rule number bits (I *know* there are going to be people who'd just die without it) then I can't see why you'd need ipfw. I imagine that would be a hell of a lot less work than bringing the features of ipfilter into ipfw. It'd also be one of those steps forward in compatibility between the various BSDs... Darren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
802.1q vlans supported ?
I notice that there are paches for Linux to implement VLANS. Do we support it? Joe Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: firewalling (Was Re: Introduction)
On Sat, 19 Jun 1999, Darren Reed wrote: In some email I received from Brian Fundakowski Feldman, sie wrote: How do you feel about (after getting it fixed in -CURRENT) helping with converting ipfw(8) to just a front-end to ipf? I think it's worth discussing whether it's actually worth it to rewrite IPFW or just work on improving ipfilter. (discussion moved to -hackers) I imagine they might be fighting words to some ;) As I see it, if you added hooks for divert to ipfilter in FreeBSD and maybe added the rule number bits (I *know* there are going to be people who'd just die without it) then I can't see why you'd need ipfw. I imagine that would be a hell of a lot less work than bringing the features of ipfilter into ipfw. It'd also be one of those steps forward in compatibility between the various BSDs... Yes, and I know it might take some work. I'd like to have something good be the default in FreeBSD, and I feel that maybe if ipfilter can be brought to the foreground well and made backward compatible (i.e. ipfw(8) to translate (perl? /bin/sh? idunno)), it will be a winning thing. I'd of course like to add UID/GID support to ipfilter like I did to IPFW (but didn't commit). IPFW is nearing the end of its maintainable life. It needs a pretty large rewrite or full replacement pretty soon. If we can get ipfilter in src/contrib kept up-to-date and working, supplying a replacement for ipfw(8) as a front-end, I don't see why ipfilter can't be the FreeBSD firewall. Darren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Sat, Jun 19, 1999 at 08:54:44AM +0930, Greg Lehey wrote: [[ ... ]] I've tried twice more to install UnixWare. It makes all the right noises, but on reboot it just hangs. I'm giving up now. Maybe you should check out Limux 6.0. I just saw it shrink-wrapped (RedHat + MacMillan[?]) at Costco. Warehouse chain. gary To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
On Friday, 18 June 1999 at 20:38:08 -0700, Gary Kline wrote: On Sat, Jun 19, 1999 at 08:54:44AM +0930, Greg Lehey wrote: [[ ... ]] I've tried twice more to install UnixWare. It makes all the right noises, but on reboot it just hangs. I'm giving up now. Maybe you should check out Limux 6.0. I just saw it shrink-wrapped (RedHat + MacMillan[?]) at Costco. Warehouse chain. I can't use that to develop UnixWare software. In fact, I *did* install (Debian) Linux on the system, just to make sure that it wasn't some silly boot problem. I also installed NetBSD, all on the same partition (overwriting the previous ones, of course). NetBSD had the nicest install, but Debian was alright as well, though it's a pain that Linux needs one (Microsoft) partition per file system or swap. Both NetBSD and Linux installed and booted fine. They also booted from CD-ROM, while UnixWare required no fewer than 3 boot floppies, which had to be made from the CD-ROM. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
