From owner-freebsd-hackers Sun Nov 1 03:03:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14033 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 03:03:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13998 for ; Sun, 1 Nov 1998 03:03:10 -0800 (PST) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.RNOC-dialup.urc.ac.ru [193.233.85.127]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id QAA13794; Sun, 1 Nov 1998 16:02:34 +0500 (ES) (envelope-from joy@urc.ac.ru) Message-ID: <363C3FBE.A693DB54@urc.ac.ru> Date: Sun, 01 Nov 1998 16:02:22 +0500 From: Konstantin Chuguev Organization: Southern Ural Regional Center of FREEnet X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru,en MIME-Version: 1.0 To: Doug Russell CC: freebsd-hackers@FreeBSD.ORG Subject: Re: make installworld over NFS References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Russell wrote: > > > Then I'd prefer just to run "make DESTDIR=/net/${HOST} installworld", > > assuming all other hosts export their /,/usr,/var to the build server. > > I do it the other way around all the time. NFS mount /usr/obj and > /usr/src from the build server on the minibox to be updated, then do a > make installworld on the minibox. > > Works great. I use it to update my bedroom machine all the time. It I see. I did the same earlier. Certainly, it worked great. The trick is not to export the build server's filesystems to other hosts at all. Suppose they are less secure then the buildserver. In my case, they are backbone routers and regional Internet servers (with a transit traffic and several Internet services) and the buildserver is a box inside the NOC LAN. I don't like even to export its filesystems read-only :-) -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 03:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15472 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 03:11:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15452 for ; Sun, 1 Nov 1998 03:10:41 -0800 (PST) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.RNOC-dialup.urc.ac.ru [193.233.85.127]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id QAA13890; Sun, 1 Nov 1998 16:10:11 +0500 (ES) (envelope-from joy@urc.ac.ru) Message-ID: <363C4189.57365D34@urc.ac.ru> Date: Sun, 01 Nov 1998 16:10:01 +0500 From: Konstantin Chuguev Organization: Southern Ural Regional Center of FREEnet X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru,en MIME-Version: 1.0 To: Chris Shenton CC: Doug Russell , freebsd-hackers@FreeBSD.ORG Subject: Re: make installworld over NFS References: <86iuh194iq.fsf@samizdat.uucom.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Shenton wrote: > > My minibox is a lowly 486sx-16 or -33 with only 5MB RAM so building > the OS on it is out of the question. It's also at a lights-out ISP > site so getting to it physically is difficult. > > Any suggestions on how to do this when the minibox is a 28.8 POTS line > away? Would the NFS be reliable enough? > Yes mostly, but only TCP NFS. I did it many times. > It's currently at 2.2.1-RELEASE and I'd like to bring it up to 2.2-STABLE. > I don't remember, was there AMD in 2.2.1, anyway, it didn't support NFS over TCP before ~2.2.7. So you have to mount filesystems manually with -o tcp. Be careful and install the STABLE kernel first, before installing the whole distribution (just to have both kernel versions in case when installation is broken due to accidental line disconnect). -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 03:30:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19155 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 03:30:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19143 for ; Sun, 1 Nov 1998 03:30:11 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:2wtTrl8lcd6Dep9DVPl7a84DhrFCh2nj@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id UAA28011; Sun, 1 Nov 1998 20:30:03 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id UAA15844; Sun, 1 Nov 1998 20:31:26 +0900 (JST) Message-Id: <199811011131.UAA15844@zodiac.mech.utsunomiya-u.ac.jp> To: Christopher Masto cc: hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Some curiosity about syscons In-reply-to: Your message of "Mon, 26 Oct 1998 23:02:08 EST." <19981026230208.A8159@netmonger.net> References: <19981026230208.A8159@netmonger.net> Date: Sun, 01 Nov 1998 20:31:24 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] >Rather than back up and start over with a different approach, I added >a tiny ioctl to syscons to call scrn_update(). With that and some >fudging, I actually have the damned thing working. Um, scrn_update() can be called on certain conditions. See scrn_timer() for correct timing. All in all, it is very difficult to guarantee that the screen is update at precisely 60Hz. >If anyone is still following this, and particularly if you Know From >Experience, perhaps you can comment on some of these architectural >issues. I need a 60Hz vertical refresh rate, and I need to be able to >display 18 lines of text every frame. This needs to happen during the >vertical retrace interval, as a single glitched frame will cause a >failure. Ideally I would like the cursor not to be present, but it >isn't actually a problem if I can make sure it is always at the top or >bottom of the screen. You have to poll a CRTC status port for vertical retrace period. As Mike has already suggested, it is probably best to do this sort of things as a screen saver LKM. The screen saver can do whatever it wants (just like DOS programs... :-) The tricky thing is that syscons will instantly deactivate the screen saver LKM as soon as a key is pressed (or mouse is moved). Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 04:55:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01740 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 04:55:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from henoch.cc.fh-lippe.de (henoch.cc.fh-lippe.de [193.16.112.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01726; Sun, 1 Nov 1998 04:55:12 -0800 (PST) (envelope-from lkoeller@cc.fh-lippe.de) Received: from spock.cc.fh-lippe.de([193.16.118.120]) (7271 bytes) by henoch.cc.fh-lippe.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sun, 1 Nov 1998 13:55:07 +0100 (MET) (Smail-3.2.0.101 1997-Dec-17 #3 built 1998-Feb-3) Received: from odie.lippe.de by spock.cc.fh-lippe.de with smtp (Smail3.1.29.1 #2) id m0zZx29-0006z8C; Sun, 1 Nov 98 13:55 MET Received: from odie.lippe.de (localhost [127.0.0.1]) by odie.lippe.de (8.9.1/8.8.8) with ESMTP id NAA08576; Sun, 1 Nov 1998 13:45:40 +0100 (CET) (envelope-from lkoeller@odie.lippe.de) Message-Id: <199811011245.NAA08576@odie.lippe.de> X-Mailer: exmh version 2.0.2 2/24/98 From: Lars =?iso-8859-1?Q?K=F6ller?= To: freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: RE: SOLUTION: Still freeze with 3.0-RELEASE X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ # This allows you to actually store this configuration file into > # the kernel binary itself, where it may be later read by saying: > # strings /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL > # > options INCLUDE_CONFIG_FILE # Include this file in kernel > = > options USERCONFIG #boot -c editor 31a40,41 > = > # KTRACE enables the system-call tracing facility ktrace(2). 101a112,122 > = > = > # > # Audio drivers: `snd', `sb', `pas', `gus', `pca' > # > controller snd0 > device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > device awe0 at isa? port 0x620 I've seen the same behavior with 2.2.7 and some versions of oss from = 4Front Tecnologies. I'm still using OSS 3.8s which is rock stable! Regards Lars -- = E-Mail: | Lars Koeller Lars.Koeller@Uni-Bielefeld.DE | UNIX Sysadmin lkoeller@cc.fh-lippe.de | Computing Center PGP-key: | University of Bielefeld= http://www.nic.surfnet.nl/pgp/pks-toplev.html | Germany ----------- FreeBSD, what else? ---- http://www.freebsd.org -------------= --==_Exmh_4525908870 Content-Type: text/plain ; name="TEST"; charset=iso-8859-1 Content-Description: TEST Content-Disposition: attachment; filename="TEST" Content-Transfer-Encoding: quoted-printable # # ODIE kernel config file # machine "i386" cpu "I586_CPU" cpu "I686_CPU" # aka Pentium Pro(tm) ident TEST maxusers 32 config kernel root on da1 options SMP #Smmetric Multiprocessor Kernel options APIC_IO #Smmetric (APIC) I/O # Lets always enable the kernel debugger for SMP. options DDB options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options MAXCONS=3D8 #Number of max. allowed virt. consoles options QUOTA #enable disk quotas options SYSVSHM #System V shared memory support options SYSVSEM #System V Semophore support options SYSVMSG #System V Message support options UCONSOLE #Allow ordinary users to take the #console - this is useful for X. options XSERVER #include code for XFree86 options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #kernel tracing # # ISA devices # controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # # PCI devices # controller pci0 options SCSI_DELAY=3D15000 # Be pessimistic about Joe SCSI device= # Adaptec 2940[U/UW] SCSI Adapter controller ahc0 controller ahc1 # Devices connected device ch0 device da0 device sa0 device cd0 device pass0 # The syntax for wiring down devices is: # AH2940 U controller scbus0 at ahc0 # Seagate ST15150N disk da0 at scbus0 target 0 disk da1 at scbus0 target 1 # Seagate Python 28388, DDS2 tape sa0 at scbus0 target 3 # PIONEER CD-ROM DR-U12X auf ID 4 device cd0 at scbus? # Adic Autochanger mit HP DAT, DDS2 device ch0 at scbus0 target 5 tape sa1 at scbus0 target 6 # AH 2940 UW controller scbus1 at ahc1 # Seagate ST32171W disk da2 at scbus1 target 8 disk da3 at scbus1 target 9 # ps2 mouse device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options SC_HISTORY_SIZE=3D512 # number of history buffer line= s device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxi= ntr # sio1 (dcf-77) # serial console options BREAK_TO_DEBUGGER # a BREAK on a comconsole goes to DDB options CONSPEED=3D19200 #default speed for serial console (defa= ult 9600) device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr pseudo-device loop pseudo-device ether pseudo-device ccd 4 pseudo-device bpfilter 4 pseudo-device pty 128 pseudo-device snp 3 #Snoop device - to look at pty/vty/e= tc.. pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a d= evice) # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver)= # note that the ``options'' and ``device'' lines must BOTH be defined ! # Teles S0/16.3 options "TEL_S0_16_3" device isic0 at isa? port 0xd80 net irq 10 flags 0x04 vector isicintr # i4b passive cards D channel handling # Q.921 pseudo-device "i4bq921" # Q.931 pseudo-device "i4bq931" # common passive and active layer 4 # layer 4 pseudo-device "i4b" # userland driver to do ISDN tracing (for passive cards oly) pseudo-device "i4btrc" 4 # userland driver to control the whole thing pseudo-device "i4bctl" # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # userland driver for telephony pseudo-device "i4btel" 2 # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 pseudo-device sppp 4 --==_Exmh_4525908870-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 05:19:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06126 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 05:19:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06119 for ; Sun, 1 Nov 1998 05:19:13 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id OAA21309; Sun, 1 Nov 1998 14:13:36 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199811011313.OAA21309@ocean.campus.luth.se> Subject: Re: kld screensavers In-Reply-To: from Doug Rabson at "Oct 30, 98 09:44:35 am" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 1 Nov 1998 14:13:36 +0100 (CET) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, jhay@mikom.csir.co.za, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Doug Rabson: > Thats more or less what I was suggesting. Simple screen savers wouldn't > even need an event handler. Maybe something like: [suggestion removed] While this is being discussed, I'd like to bring something up that I've wanted for a long time, and brought up before. Why not make to so that each screensaver register itself with a timeout, a priority and a flag that says if it's fallthrough or not? That way you can have multiple screensavers installed, and they get called as approriate. I haven't looked at the current code, I'm affraid, so go easy on me. Example: Three screensavers: (say default prio is 5) lock: prio 1, 10 minutes, fallthrough (Demands password to release screen) green: prio 4, 20 minutes (Turn screen off) stars: prio 5, 5 minutes (Twinkle, twinkle, little star) Right... So this happens if you idle: After 5 minutes the stars saver kicks in and the screen gets full of stars. After 2 minutes you press a key and the screen is returned to normal. After 5 more minutes the stars saver kicks back in. After 5 more minutes the lock saver kicks in, steals the "release" event, and then does nothing... Stars saver "twinkle" routine is still getting called as usual, but lock's "twinkle" routine gets called first, and just returns "ok to fallthrough", which make the stars one continue. After 10 more minutes the green saver kicks in, and demands to be run. It gets scheduled after lock, because of its prio and therefor the screen is turned off, since lock's "twinkle" is still returning "ok to fallthrough", and the fallthrough now calls "green", which just sees to that the screen is off, and keeps off. Now you're back from your coffee break, hit a key, and the lock saver gets the event to return screen to normal. It steals the display and asks for a password, and doesn't give the screen back until you type the right password. End example... Now, thinking about this a bit I can see a problem with a lock saver and the chain of calls that have to be done to wake up, etc... But I hope you see the picture, and maybe have a good architecture to solve this. It sure would be very nice. I don't know my way around syscons's internals to do the architecturing myself, however. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 09:36:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07941 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 09:36:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07936 for ; Sun, 1 Nov 1998 09:36:24 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA09241; Sun, 1 Nov 1998 12:36:10 -0500 (EST) Message-ID: <19981101123610.A7850@netmonger.net> Date: Sun, 1 Nov 1998 12:36:10 -0500 From: Christopher Masto To: Kazutaka YOKOTA Cc: hackers@FreeBSD.ORG Subject: Re: Some curiosity about syscons References: <19981026230208.A8159@netmonger.net> <199811011131.UAA15844@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811011131.UAA15844@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Sun, Nov 01, 1998 at 08:31:24PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 01, 1998 at 08:31:24PM +0900, Kazutaka YOKOTA wrote: > You have to poll a CRTC status port for vertical retrace period. > > As Mike has already suggested, it is probably best to do this sort of > things as a screen saver LKM. The screen saver can do whatever > it wants (just like DOS programs... :-) > > The tricky thing is that syscons will instantly deactivate the > screen saver LKM as soon as a key is pressed (or mouse is moved). Doesn't the screen saver only get run periodically? Hmm.. Anyway, I have something which works a lot more reliably than my original call-scrn_update()-excessively hack. Of course, this is about four hacks in one. Because I stubbornly didn't want to get involved in graphics mode, but I found out that unfortunately, the lines I need to draw are slightly closer together than one 16-pixel character (so I couldn't just use the "IBM line drawing" character 196), I am making a special font that has two lines per cell, in various spacings, so I can put the right one down to simulate graphics. I'm using syscons to load the font, and mmap to get access to the video memory directly to update the screen. I then found out about the bizzaro design of text modes where there are 8 pixels across per character, but put into a 9-pixel cell. The VGA hardware leaves a one-pixel gap between characters, _except_ for the magic range of the standard IBM line drawing characters, where it duplicates the 8th column into the 9th. So I futz with the VGA registers (thank you, /dev/io) behind syscons' back.. after using syscons to request 80x30, because I need a 60Hz screen. Finally, busy-waiting for the vertical retrace completes the evil picture, and it all comes together. Then it's just a matter of putting the pieces back together so the console is again usable. Here are the preliminary functions.. I know that this is not entirely kosher, but it's a stupid little program that runs for ten seconds while the user holds their watch up to the screen. I'm not yet dealing with issues like mono vs. color screens, but other than that, I don't think I'll get yelled at for too much. There is the slight matter of not disabling interrupts while programming one of the VGA registers, but this is a user level program.. I take my chances. :-) [...] #define WAIT_RETRACE { while (inb(0x3DA) & 0x08); \ while (!(inb(0x3DA) & 0x08)); } u_short *vmem; unsigned char font[16*256], oldfont[16*256]; [...] void txt_init(void) { int p1, p2, l, i=0; unsigned char b; struct rtprio rtp; // Set realtime priority rtp.type = RTP_PRIO_REALTIME; rtp.prio = 0; if (rtprio(RTP_SET, 0, &rtp)) { perror("Couldn't set realtime priority; rtprio()"); exit(-1); } // Get I/O privileges fd = open("/dev/io", O_RDONLY, 0777); if (fd == -1) { perror("Couldn't open /dev/io"); exit(-1); } // Map video memory vmem = (u_short *)mmap(0, 0x8000, PROT_READ|PROT_WRITE, 0, 0, 0x18000); if (vmem == MAP_FAILED) { perror("mmap()"); exit(-1); } // Save the current font if (ioctl(0, GIO_FONT8x16, oldfont) < 0) { perror("Saving font failed; ioctl()"); exit(-1); } // Change syscons mode to 80x30 (60hz) if (ioctl(0, SW_VGA_C80x30) < 0) { perror("Can't change to 80x30; ioctl()"); exit(-1); } // 640 pixel mode b=inb(0x3CC); outb(0x3C2, b & 0xf3); // 8 dot clocks outb(0x3C4, 0x01); b=inb(0x3C5); outb(0x3C5, b | 0x01); sleep(2); // Let monitor resync // Generate font for (p1 = 0; p1 < 16; p1++) for (p2 = 0; p2 < 16; p2++) for (l = 0; l < 16; l++) font[i++] = (l == p1 || l == p2) ? 0xff : 0x00; for (l = 16; l < 32; l++) font[l] = 0x00; // Install font if (ioctl(0, PIO_FONT8x16, font) < 0) { perror("ioctl()"); exit(-1); } WAIT_RETRACE; clear_screen(); } [...] void draw_2line(int y, int l1, int l2) { int start, stop; u_short b; start = y * 80; stop = start + 80; b = (0x0f << 8) | ((l1 << 4) + l2); while (start < stop) vmem[start++] = b; } -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ Microsoft, I think, is fundamentally an evil company. - JAMES H. CLARK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 10:53:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16503 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 10:53:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16497 for ; Sun, 1 Nov 1998 10:53:52 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id NAA14143; Sun, 1 Nov 1998 13:53:46 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA22438; Sun, 1 Nov 1998 13:53:46 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id NAA15179; Sun, 1 Nov 1998 13:53:46 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199811011853.NAA15179@bb01f39.unx.sas.com> Subject: Re: nfs/amd hangs / getattr request flood problem In-Reply-To: From David G Andersen at "Oct 30, 98 03:37:02 pm" To: danderse@cs.utah.edu (David G Andersen) Date: Sun, 1 Nov 1998 13:53:46 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've sent mail to -current a few times... Try the following change on your FreeBSD client machine(s): /usr/src/sys/nfs/nfs_vnops.c: 273c273 < int v3 = NFS_ISV3(vp); --- > int v3 = 0; /* NFS_ISV3(vp); */ ie: Turn off the 'access' portion of the v3 protocol. I have a build farm of about 50 266Mhz machines talking to Network Appliance fileservers. Without the above change, the network is swamped... Good Luck! John > We're in the process of configuring some new machines (for personal and > distributed build farm use), and we're seeing some atrocities with amd. > The machines are running 3.0-RELEASE (plus the last few days of checked in > fixes). They receive AMD maps via NIS and a static map, but disabling NIS > doesn't affect things. We've made significant tweaks to the rest of the > system configuration (disabling nis, mfs, slowing things down, etc) and > tried it on multiple systems, and the problem keeps popping up. This > behavior isn't exhibited in 2.2.x. > > We have AMD looking at /n/{machine}/path, with the actual mounts on > /a/{machine}. When compiling with a source tree on /n/machine/path and an > object tree on local /z, AMD can use up to 50% of the processor. Ktrace > and tcpdump output shows that it's handling around 150 getattr requests > per second, on "/n" and "/n/machine", and the ktrace indicates that that's > the _only_ thing it's doing. > > The result of this is some serious slowdowns, and reproducible system > freezes (kernel alive and pingable, no userland activity whatsoever). > Unfortunately, we don't have a simple way of reproducing the hangs yet - > it happens while running the Linux suse Matrox Xserver and the FreeBSD > netscape (entering, then leaving, and then re-entering Netscape frequently > triggers the hang). > > There don't seem to be any references to this in gnats or on the lists. > We're working on forward-porting the 2.2.x amd to 3.0 to see if the > behavior still exists, but in the meantime, if anyone has suggestions / > thoughts / knows what's wrong and wants to clue me in, it'd be greatly > appreciated. :) > > -Dave > > - -- > work: danderse@cs.utah.edu me: angio@pobox.com > University of Utah http://www.angio.net/ > Department of Computer Science > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 11:39:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22669 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 11:39:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22656 for ; Sun, 1 Nov 1998 11:39:29 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA18552; Sun, 1 Nov 1998 11:32:34 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdF18541; Sun Nov 1 19:32:32 1998 Date: Sun, 1 Nov 1998 11:31:46 -0800 (PST) From: Julian Elischer To: Robert Swindells cc: joelh@gnu.org, kline@thought.org, hackers@FreeBSD.ORG Subject: Re: Memory leak location tool? In-Reply-To: <199810311420.OAA00539@fdy2.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG don't forget 'mprof' very good for this. On Sat, 31 Oct 1998, Robert Swindells wrote: > > >> Are there any free tools to detect likely memory leaks? Tools > >> like Purify aren't quite what I'm looking for. > >> Anybody? > > >"more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the > >following: > > > >* The Boehm-Weiser garbage collecting malloc (boehm-gc) includes a leak > > detector. > > > >* Doug Lea's malloc (libdlmalloc) and libmalloc include hooks to add > > leak detection. > > > >* S-Lang (libslang) says that it includes "a malloc debugging > > package". I'm not sure whether they mean something to help debug > > malloc, or a malloc that helps you debug your code. > > There is also a simple one as part of X11R6.3. > > It is in xc/utils/memleak. > > I can't tell if the 386 support came as standard, or with the XFree86 > patches. > > Robert Swindells > ------------------------------------- > Robert Swindells - GenRad Ltd > rjs@genrad.co.uk - Work > rjs@fdy2.demon.co.uk - Home > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 11:48:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24331 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 11:48:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24310 for ; Sun, 1 Nov 1998 11:48:09 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id LAA07876; Sun, 1 Nov 1998 11:47:54 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id LAA00579; Sun, 1 Nov 1998 11:47:43 -0800 (PST) From: Gary Kline Message-Id: <199811011947.LAA00579@tao.thought.org> Subject: Re: Memory leak location tool? In-Reply-To: from Julian Elischer at "Nov 1, 98 11:31:46 am" To: julian@whistle.com (Julian Elischer) Date: Sun, 1 Nov 1998 11:47:42 -0800 (PST) Cc: rjs@fdy2.demon.co.uk, joelh@gnu.org, kline@thought.org, hackers@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Julian Elischer: > don't forget 'mprof' > very good for this. > Right. So far I've used memleak and mprof. The outputs of both are a bit obscure, but I've fixed two programs. They had almost insignificant leaks, and now none. Can anyone send me a brief test file and Makefile that works (demonstrates something) for gc? thanks, gary > > On Sat, 31 Oct 1998, Robert Swindells wrote: > > > > > >> Are there any free tools to detect likely memory leaks? Tools > > >> like Purify aren't quite what I'm looking for. > > >> Anybody? > > > > >"more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the > > >following: > > > > > >* The Boehm-Weiser garbage collecting malloc (boehm-gc) includes a leak > > > detector. > > > > > >* Doug Lea's malloc (libdlmalloc) and libmalloc include hooks to add > > > leak detection. > > > > > >* S-Lang (libslang) says that it includes "a malloc debugging > > > package". I'm not sure whether they mean something to help debug > > > malloc, or a malloc that helps you debug your code. > > > > There is also a simple one as part of X11R6.3. > > > > It is in xc/utils/memleak. > > > > I can't tell if the 386 support came as standard, or with the XFree86 > > patches. > > > > Robert Swindells > > ------------------------------------- > > Robert Swindells - GenRad Ltd > > rjs@genrad.co.uk - Work > > rjs@fdy2.demon.co.uk - Home > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 12:39:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03082 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 12:39:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03075 for ; Sun, 1 Nov 1998 12:39:21 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id NAA10826; Sun, 1 Nov 1998 13:39:15 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd010776; Sun Nov 1 13:39:09 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id NAA25357; Sun, 1 Nov 1998 13:39:01 -0700 (MST) From: Terry Lambert Message-Id: <199811012039.NAA25357@usr05.primenet.com> Subject: Re: FW: Can't get rid of my mbufs. To: toasty@home.dragondata.com (Kevin Day) Date: Sun, 1 Nov 1998 20:39:01 +0000 (GMT) Cc: dg@root.com, syang@directhit.com, opsys@mail.webspan.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199810280934.DAA05514@home.dragondata.com> from "Kevin Day" at Oct 28, 98 03:34:24 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Thanks for the info. One question remains. Suppose netstat -m tells me > > >that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the > > >important processes and let the machine stay idle for 2 hours. Why does > > >netstat -m still tell me that 7900/8050 mbuf clusters are in use? > > >Basically, I'd wish it would say something like 99/8050 mbuf clusters in > > >use instead. I already have MAXUSERS set to 512. > > > > What does "netstat -n" show? > > > > For what it's worth.... I've got something similar.... [ ... lot of FIN_WAIT_2 to port 80 ... ] You have WinSock clients which are failing to call shutdown() before closing the socket. These clients are in error. There is a design flaw in the TCP/IP protocol, in that it has a case where a single request is supposed to elicit two responses: one for FIN_WAIT_1, and the second for FIN_WAIT_2. NT gets around this problem by pretending that it did not get the first response (an ACK); basically, it backs up, and potentially reenters FIN_WAIT_2 2 MSL later. This happens when the server does the close first. From RFC 793: TCP A TCP B 1. ESTABLISHED ESTABLISHED 2. (Close) FIN-WAIT-1 --> --> CLOSE-WAIT 3. FIN-WAIT-2 <-- <-- CLOSE-WAIT 4. (Close) TIME-WAIT <-- <-- LAST-ACK 5. TIME-WAIT --> --> CLOSED 6. (2 MSL) CLOSED The backup is grep state 3 to state 2 -- the is resent, if the LAST-ACK takes more than 2 MSL come back. This is precisely what would happen if the: was lost. If the remote side has no record of the connection (since it has disassembled it without a shutdown() before the close()), then the TCP A will get an RST, and should act as if a successful close had occurred. If the remote side still has a record of the connection, then the: Is resent, and the TCP A goes back to sleep for another 2 MSL. In this way, the protocol design flaw is worked around. I have suggested for a number of months now (actually, 13 of them) that FreeBSD should have a sysctl for NT_bug_compatible to turn on this behaviour, and that the current FIN-WAIT-2 discard clock is, in fact, an *error*, since it allows the discard of valid connections with extrememely long drain delays -- which may be legitimate natural phenomenon. A secondary problem is that you appear to have a hell of a lot of DNS LISTEN's going on, but since this may be intentional, I'll refrain from commenting one them further. For a workaround for the first problem, you should delay the server close of the HTTP connection for at least 4 MSL, such that the shutdown is initiated by the client instead. In general, a "sleep( 2);" before the socket close will suffice for this purpose for most clients. You may want to consider unsetting the SO_LINGER, which is intended to allow a drain-to-client after close, in combination with the sleep. Note that if the client drain takes more than 2 seconds, clients may be presented with incomplete HTML documents, if you do this (which is why the FIN-WAIT-2 state exists in the first place). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 13:07:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06677 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 13:07:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06666 for ; Sun, 1 Nov 1998 13:07:54 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA02784; Sun, 1 Nov 1998 14:07:45 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd002770; Sun Nov 1 14:07:42 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA26376; Sun, 1 Nov 1998 14:07:40 -0700 (MST) From: Terry Lambert Message-Id: <199811012107.OAA26376@usr05.primenet.com> Subject: Re: s/bpfilter/bpf/ To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 1 Nov 1998 21:07:40 +0000 (GMT) Cc: finrod@ewox.org, hackers@FreeBSD.ORG In-Reply-To: <5159.909675209@time.cdrom.com> from "Jordan K. Hubbard" at Oct 29, 98 07:33:29 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > While in Arnhem, I discussed renaming the bpfilter pseudo-device to > > bpf. There seemed to be agreement that it would be more consistent > > (amongst other items, the device nodes are named /dev/bpf*, and the > > man page is bpf(4)). > > I agree that this change is overdue, but I also wonder whether or not > you could do this so that ``pseudo-device bpfilter'' would continue to > be a synonym for bpf. It wouldn't appear in any documentation or be > suggested, but would at least continue to work for those with old > config files. When do deperecated things get removed? It seems that there is not an overall list of deprecated stuff such that things which are deprecated actually end up going away at some point. In other words, it seems that the answer to this question is "never, we just accumulate cruft until our head explodes". I would suggest one release cycle. I would also suggest managing this automatically, with something like (note the use of the word "like"): --------------------------------------------------------------------- #include #if (DEPRECATED > 2) #warning "This file contains obsolete code which should" #warning "be removed from the source repository." #else /* This code will be obsolete in release deprecation cycle 3*/ ... /* warn the user that (whatever) is going away next release*/ fprintf( stderr, "option 'bpfilter' is deprecated; use 'bpf' instead\n"); ... #endif /* DEPRECATED*/ --------------------------------------------------------------------- You would increment the value of the manifest constant DEPRECATED each time there is a release. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 13:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06996 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 13:10:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06989 for ; Sun, 1 Nov 1998 13:10:21 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA17143; Sun, 1 Nov 1998 14:10:17 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd017131; Sun Nov 1 14:10:14 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA26441; Sun, 1 Nov 1998 14:10:14 -0700 (MST) From: Terry Lambert Message-Id: <199811012110.OAA26441@usr05.primenet.com> Subject: Re: s/bpfilter/bpf/ To: archie@whistle.com (Archie Cobbs) Date: Sun, 1 Nov 1998 21:10:14 +0000 (GMT) Cc: finrod@ewox.org, hackers@FreeBSD.ORG In-Reply-To: <199810291922.LAA27011@bubba.whistle.com> from "Archie Cobbs" at Oct 29, 98 11:22:38 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > While in Arnhem, I discussed renaming the bpfilter pseudo-device to > > bpf. There seemed to be agreement that it would be more consistent > > (amongst other items, the device nodes are named /dev/bpf*, and the > > man page is bpf(4)). > > While you're at it, could you also fix the /dev/MAKEDEV script > so if you say sh MAKEDEV bpf3 it makes bpf0, bpf1, and bpf2 as > well? > > It does this for tunX but not bpfX, for some reason.. why the > inconsistency? /dev/MAKEDEV is deprecated. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 13:42:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10893 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 13:42:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10887 for ; Sun, 1 Nov 1998 13:42:15 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA12404; Sun, 1 Nov 1998 14:42:06 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd012387; Sun Nov 1 14:42:05 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA27464; Sun, 1 Nov 1998 14:42:04 -0700 (MST) From: Terry Lambert Message-Id: <199811012142.OAA27464@usr05.primenet.com> Subject: Re: scanf in the kernel? To: dennis@etinc.com (Dennis) Date: Sun, 1 Nov 1998 21:42:04 +0000 (GMT) Cc: archie@whistle.com, hackers@FreeBSD.ORG In-Reply-To: <199810301830.SAA28485@etinc.com> from "Dennis" at Oct 30, 98 06:44:25 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Also- > >Seems like the kernel was missing memmove(), memcpy(), and/or memset() > >at some point. I like using these better than bcopy()/bzero() because > >they are more ANSI and portable... Not that this matters in kernel code, since FreeBSD is not portable to non-FreeBSD systems. 8-). > #define memcpy(d,s,n) bcopy(s,d,n) > > not exactly rocket science :-) Actually, bcopy is closer to memmove, since it supports overlapping ranges as its arguments. I really hate memcpy because of its non-guarantee inre: overlapping arguments. It's intentional stupidity which suffers vendors existing implementations, for no good reason other than to compromise with fools. Stupid ANSI Committe, bend over and pick up that draft standard for me, will you? Why yes, that committe member *was* at Shawshank for a while; why do you ask? If the vendor has a faster implementation that works with their processor instruction set, but only for non-overlapped regions, let them test for overlap, and then use their weenie instruction. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 13:47:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11227 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 13:47:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11221 for ; Sun, 1 Nov 1998 13:47:04 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA11898; Sun, 1 Nov 1998 14:46:59 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd011884; Sun Nov 1 14:46:54 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA27534; Sun, 1 Nov 1998 14:46:38 -0700 (MST) From: Terry Lambert Message-Id: <199811012146.OAA27534@usr05.primenet.com> Subject: Re: scanf in the kernel? To: mike@smith.net.au (Mike Smith) Date: Sun, 1 Nov 1998 21:46:38 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199810300813.AAA01726@dingo.cdrom.com> from "Mike Smith" at Oct 30, 98 00:13:48 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just wondering what the general feeling would be about having scanf in > the kernel? As we move towards more abstract representations of things > (eg. device names), it's becoming more important to be able to parse > strings inside the kernel. > > Doing this in hand-rolled code is tedious, error-prone and results in > code that can be hard to read and maintain (as everyone does it their > own way). > > If this isn't totally repulsive, I'll roll a somewhat smaller version > of the libc vfscanf for general approval. I have to say that it's repulsive. In general, the only place strings should probably be used in the kernel at all are in filesystem namespace exposures. Even then, I have to say that NFS is utterly bogus in the use of pushing strings across the user/kernel boundary for the exported FS list. In general, I have to say that I rather like the fact that Linux has one use of copyinstr -- and does nto have a general copyinstr as a result, but only a copy in for the path data for an FS path lookup. I think it is a mistake for FreeBSD to turn into Plan9. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 13:49:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11507 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 13:49:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11501 for ; Sun, 1 Nov 1998 13:49:19 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA06889; Sun, 1 Nov 1998 14:49:15 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd006879; Sun Nov 1 14:49:11 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id OAA27625; Sun, 1 Nov 1998 14:49:09 -0700 (MST) From: Terry Lambert Message-Id: <199811012149.OAA27625@usr05.primenet.com> Subject: Re: FreeBSD arm port To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 1 Nov 1998 21:49:09 +0000 (GMT) Cc: mike@smith.net.au, sepotvin@videotron.ca, Hackers@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Oct 30, 98 10:43:04 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Also, some pointers as to what are the main steps for doing such a port > > > (FreeBSD port as a whole) would be greatly appreciated. > > > > Crucial to bringing up any new port is the ability to tighten the build/ > > debug cycle. If you have an emulator, that's excellent. If you can > > boot diskless, that's almost as good. Copying kernels onto floppies and > > lugging them back and forth gets old _really_ quick. > > The best debugging environment is definately a simulator (but only if it > has good hooks into gdb). Netbooting with serial-line debugging runs a > close second. I think for ARM, the best debugging environment would be the ARM system on a PCI card, which Intel makes available. Plug the card into an existing Intel/Alpha FreeBSD box, and do your loading and debugging via a device driver. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 14:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13881 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 14:04:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13876 for ; Sun, 1 Nov 1998 14:04:21 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA17948; Sun, 1 Nov 1998 15:04:17 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd017908; Sun Nov 1 15:04:07 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA27908; Sun, 1 Nov 1998 15:04:02 -0700 (MST) From: Terry Lambert Message-Id: <199811012204.PAA27908@usr05.primenet.com> Subject: Re: Possible bug in freopen()? To: Arjan.deVet@adv.iae.nl (Arjan de Vet) Date: Sun, 1 Nov 1998 22:04:02 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199810302139.WAA13889@adv.iae.nl> from "Arjan de Vet" at Oct 30, 98 10:39:02 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I may have found a bug in freopen() while testing INN 2.2-stable. > > Consider the following program: > > #include > #include > > main () { > FILE *f, *g; > long i; > > g = fopen("/tmp/test", "a"); > f = freopen("/tmp/test", "a", g); > i = ftell(f); > printf("%d\n", i); > fprintf(f, "test"); > i = ftell(f); > printf("%d\n", i); > close(f); > } > > Start with an empty /tmp/test file and run the program three times > consecutively. The results on BSD/OS 3.0, FreeBSD 2.2.7-stable and Solaris > 2.6 are: > > BSDI 3.0 FreeBSD 2.2.7 Solaris > ----------------------------------------------------------------------------- > 0 0 0 > 4 4 4 > > 0 0 4 > 8 4 8 > > 0 0 8 > 12 4 12 > > Hmm... Quite different. I think Solaris shows the correct behaviour. In each > case /tmp/test contains "testtesttest" after the running the program three > times. Realize that stdio buffers are not required to be flushed to disk unless you explicitly call fclose on the FILE's. Notice, also, that you are calling "close" on "f", which does nothing. Also, you should not expect that an fopen and a freopen on the same file will use the same user space stdio buffer space, merely because the are connected to the same file. The buffer space is set associative with the FILE, not with the underlying fd. That said, if you correct your program to do the right fclose, it looks as if: ``a'' Open for writing. The file is created if it does not exist. The stream is positioned at the end of the file. Is not being obeyed by the freopen() in either BSDI or FreeBSD, and that the seek is delayed until after the write attempt, so the first ftell fails on both FreeBSD and BSDI. So it looks like a missing set of the offset to the file size. It's interesting to note that both Solaris and BSDI do the write, even though you don't properly close the file. This is probably bogus, since it implies at best that they are resource tracking the stdio buffers in an implementation dependent way, and at worst that their stdio isn't very efficient. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 14:05:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14284 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 14:05:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles355.castles.com [208.214.167.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14278 for ; Sun, 1 Nov 1998 14:05:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA06090; Sun, 1 Nov 1998 14:04:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811012204.OAA06090@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Sun, 01 Nov 1998 21:46:38 GMT." <199811012146.OAA27534@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Nov 1998 14:04:54 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Just wondering what the general feeling would be about having scanf in > > the kernel? As we move towards more abstract representations of things > > (eg. device names), it's becoming more important to be able to parse > > strings inside the kernel. > > > > Doing this in hand-rolled code is tedious, error-prone and results in > > code that can be hard to read and maintain (as everyone does it their > > own way). > > > > If this isn't totally repulsive, I'll roll a somewhat smaller version > > of the libc vfscanf for general approval. > > I have to say that it's repulsive. > > In general, the only place strings should probably be used in the > kernel at all are in filesystem namespace exposures. You're internally inconsistent. Last time you decided you liked strings over manifest constants. > I think it is a mistake for FreeBSD to turn into Plan9. I think it's a mistake for us to make any technical decisions on emotional or us'n'them grounds. There are instances where it's clearly useful to be able to process string format data (eg. the SCSI quirk code). The necessity for this combined with the lack of formal string parsing has led to the implementation of any number of ad-hoc solutions. If you want to argue for the removal of all string processing in the kernel, you need to explain how all of these existing functions are going to work. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 14:25:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16824 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 14:25:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16815 for ; Sun, 1 Nov 1998 14:25:16 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA20098; Sun, 1 Nov 1998 15:25:11 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd020086; Sun Nov 1 15:25:07 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA28667; Sun, 1 Nov 1998 15:25:05 -0700 (MST) From: Terry Lambert Message-Id: <199811012225.PAA28667@usr05.primenet.com> Subject: Re: scanf in the kernel? To: mike@smith.net.au (Mike Smith) Date: Sun, 1 Nov 1998 22:25:05 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199811012204.OAA06090@dingo.cdrom.com> from "Mike Smith" at Nov 1, 98 02:04:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In general, the only place strings should probably be used in the > > kernel at all are in filesystem namespace exposures. > > You're internally inconsistent. Last time you decided you liked > strings over manifest constants. I like strings *out*. I believe the "last time" to which you refer is the mount fstype argument, in which I thought it was stupid to limit yourself to defined FS's in mount.h. This does *not* necessarily mean that I want the fstype name's passed into the kernel directly; rather, I'd like the integration of /sbin/fstyp, and the use of /sbin/"_", using the list of returned supported types. So installing a new FS type installs commands in /sbin, and hving installed commands in /sbin, the list is known via a traversal of sbin, without even asking the kernel. > > I think it is a mistake for FreeBSD to turn into Plan9. > > I think it's a mistake for us to make any technical decisions on > emotional or us'n'them grounds. I'm not saying that. I'm saying that there is a recent tendency to bloat in the direction of Plan9-style interfaces. > There are instances where it's clearly useful to be able to process > string format data (eg. the SCSI quirk code). The necessity for this > combined with the lack of formal string parsing has led to the > implementation of any number of ad-hoc solutions. If you want to argue > for the removal of all string processing in the kernel, you need to > explain how all of these existing functions are going to work. I'll be happy to address the architectural issues on a case-by-case basis, to any level of detail you want. One does wonder how you would boot from a "quirked" drive if you had to allow pushing the data over the user/kernel boundary to be able to recognize the quirks. One could easily claim that the use of strings in sysctl is bogus, and that the parsing should be to MIB identifiers, and take place in user space to keep the kernel lean. Etc.. Feel free to propose other cases, I'll be happy to discuss them. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 14:39:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18197 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 14:39:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thinkbank.COM (Thinkbank.COM [207.33.53.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18191 for ; Sun, 1 Nov 1998 14:39:32 -0800 (PST) (envelope-from jordan@Thinkbank.COM) Received: (from smap@localhost) by Thinkbank.COM (8.8.5/8.7.5) id OAA24313; Sun, 1 Nov 1998 14:39:27 -0800 (PST) Received: from blood.thinkbank.com(192.168.1.2) by oceanvu.thinkbank.com via smap (V1.3) id sma024311; Sun Nov 1 14:39:21 1998 Received: by blood.Thinkbank.COM (4.1/Othar) id AA03494; Sun, 1 Nov 98 14:39:21 PST Date: Sun, 1 Nov 98 14:39:21 PST From: jordan@Thinkbank.COM (Jordan Hayes) Message-Id: <9811012239.AA03494@blood.Thinkbank.COM> To: hackers@FreeBSD.ORG Subject: Stand-alone diskless system ... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm looking for any experiences that people here have had with truely diskless machines: not booting over the network, but from say flash memory or even a disk that is subsequently powered off. The goal is quiet operation and low-heat generation. The machine will not be saving any "interesting" data, so total loss on power-outtage is fine. I'm not on this list, so please direct responses to me. I'll summarize is necessary. Thanks, /jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 14:56:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20746 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 14:56:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.alpha-intra.net (NS1.ALPHA-INTRA.NET [209.127.104.245]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20739 for ; Sun, 1 Nov 1998 14:56:51 -0800 (PST) (envelope-from brohde@alphainternet.net) Received: from alphainternet.net (pmattos@AIS-ws3.alphainternet.net [209.127.104.236]) by ns1.alpha-intra.net (8.9.1/8.9.1) with ESMTP id QAA00724 for ; Sun, 1 Nov 1998 16:53:47 -0600 (CST) Message-ID: <363CE67A.EA848E74@alphainternet.net> Date: Sun, 01 Nov 1998 16:53:46 -0600 From: Bruce Rohde X-Mailer: Mozilla 4.06 [en] (Win98; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: make world crash Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Help! I followed the instuctions on CVsup to update my tree from 2.2.1 to 2.2-STABLE. The command was: cvsup -g -L 2 stable-supfile. After that finnished I went to /usr/src and did a "make world". It ran for a few minutes and stopped, Error code 1 Below is the last couple of pages ... Thanks in advance! --------cut----------------- -------------------------------------------------------------- Rebuilding tools needed to build the libraries -------------------------------------------------------------- cd /usr/src/usr.bin/xinstall && make depend all install cleandir obj rm -f .depend files=""; if [ "$files" != "" ]; then mkdep -a $files; fi files="/usr/src/usr.bin/xinstall/../../bin/ls/stat_flags.c /usr/src/usr.bin/xinstall/xinstall.c"; if [ "$files" != "" ]; then mkdep -a $files; fi files=" "; if [ "$files" != " " ]; then mkdep -a $files; fi cc -O -c /usr/src/usr.bin/xinstall/../../bin/ls/stat_flags.c cc -O -c /usr/src/usr.bin/xinstall/xinstall.c cc -O -o xinstall stat_flags.o xinstall.o (cd /usr/src/usr.bin/xinstall; install -c -o bin -g bin -m 444 install.1 /usr/share/man/man1) compressing in /usr/share/man/man1: install.1 -> install.1.gz install -c -s -o bin -g bin -m 555 xinstall /usr/bin/install rm -f .depend /usr/src/usr.bin/xinstall/tags rm -f a.out [Ee]rrs mklog xinstall stat_flags.o xinstall.o rm -f /usr/src/usr.bin/xinstall/tags .depend cd /usr/src/usr.bin/xinstall; rm -rf obj; /usr/src/usr.bin/xinstall -> /usr/obj/usr.bin/xinstall cd /usr/src/gnu/usr.bin/ld && make depend all install cleandir obj rm -f .depend files=""; if [ "$files" != "" ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 $files; fi files="/usr/src/gnu/usr.bin/ld/ld.c /usr/src/gnu/usr.bin/ld/symbol.c /usr/src/gnu/usr.bin/ld/lib.c /usr/src/gnu/usr.bin/ld/shlib.c /usr/src/gnu/usr.bin/ld/warnings.c /usr/src/gnu/usr.bin/ld/etc.c /usr/src/gnu/usr.bin/ld/rrs.c /usr/src/gnu/usr.bin/ld/xbits.c /usr/src/gnu/usr.bin/ld/i386/md.c"; if [ "$files" != "" ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 $files; fi files=" "; if [ "$files" != " " ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 $files; fi ===> ldconfig rm -f .depend files=""; if [ "$files" != "" ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 $files; fi files="/usr/src/gnu/usr.bin/ld/ldconfig/ldconfig.c /usr/src/gnu/usr.bin/ld/ldconfig/../shlib.c /usr/src/gnu/usr.bin/ld/ldconfig/../etc.c"; if [ "$files" != "" ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 $files; fi files=" "; if [ "$files" != " " ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 $files; fi ===> ldd rm -f .depend files=""; if [ "$files" != "" ]; then mkdep -a $files; fi files="/usr/src/gnu/usr.bin/ld/ldd/ldd.c"; if [ "$files" != "" ]; then mkdep -a $files; fi files=" "; if [ "$files" != " " ]; then mkdep -a $files; fi ===> rtld rm -f .depend files="/usr/src/gnu/usr.bin/ld/rtld/../i386/mdprologue.S"; if [ "$files" != "" ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -DRTLD $files; fi files="/usr/src/gnu/usr.bin/ld/rtld/rtld.c /usr/src/gnu/usr.bin/ld/rtld/malloc.c /usr/src/gnu/usr.bin/ld/rtld/../shlib.c /usr/src/gnu/usr.bin/ld/rtld/../etc.c /usr/src/gnu/usr.bin/ld/rtld/../i386/md.c"; if [ "$files" != "" ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -DRTLD $files; fi files=" "; if [ "$files" != " " ]; then mkdep -a -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -DRTLD $files; fi cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/ld.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/symbol.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/lib.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/shlib.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/warnings.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/etc.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/rrs.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/xbits.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -c /usr/src/gnu/usr.bin/ld/i386/md.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -Xlinker -Bstatic -o ld ld.o symbol.o lib.o shlib.o warnings.o etc.o rrs.o xbits.o md.o -lgnumalloc ld: -lgnumalloc: no match *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 15:56:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28730 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 15:56:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28716 for ; Sun, 1 Nov 1998 15:56:43 -0800 (PST) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co ([168.176.3.37]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with ESMTP id AAA25339 for ; Sun, 1 Nov 1998 18:59:20 +0500 Message-ID: <363CF482.9730ED0F@bachue.usc.unal.edu.co> Date: Sun, 01 Nov 1998 18:53:38 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: HBench-OS Operating System Benchmarks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This seems interesting: from http://www.eecs.harvard.edu/~vino/perf/hbench/ HBench-OS is a suite of portable benchmarks designed to measure the performance of primitive functionality provided by an operating system/hardware platform. HBench-OS was designed primarily as a research tool for the systems research and OS development communities, and thus its major design goal is to provide a flexible system for reproducible, accurate, and statistically-sound performance analysis and evaluation. These characteristics make it ideal for both performance research as well as more traditional consumer-oriented performance measurement and analysis. ___ enjoy, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 15:57:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28781 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 15:57:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28772 for ; Sun, 1 Nov 1998 15:57:10 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id SAA15180; Sun, 1 Nov 1998 18:57:13 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Sun, 1 Nov 1998 18:57:13 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Jordan Hayes cc: hackers@FreeBSD.ORG Subject: Re: Stand-alone diskless system ... In-Reply-To: <9811012239.AA03494@blood.Thinkbank.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Nov 1998, Jordan Hayes wrote: > Hi, > > I'm looking for any experiences that people here have had with truely > diskless machines: not booting over the network, but from say flash > memory or even a disk that is subsequently powered off. The goal is > quiet operation and low-heat generation. The machine will not be > saving any "interesting" data, so total loss on power-outtage is fine. > > I'm not on this list, so please direct responses to me. I'll summarize > is necessary. > > Thanks, > > /jordan It works really well. A week ago I helped some undergrads run an ACM programming contest. Since we weren't allowed to convert a dozen of the public access NT boxes to unix machines (aw shucks ;-), I brought in our own server, and made a DOS boot floppy using the stuff in /sys/i386/boo/biosboot. We booted these machines completely diskless with kernels stripped down to only network and console IO drivers. This added to running everything addressed in 10.x.x.x made for a pretty nice and limiting contest envrioment. We ran X and everything else you would want, and saw no performance problems. Adding a new machine was as simple as adding an entry to bootptab and making a private area to mount the volatile filesytems from, e.g. /var and /tmp. Check out the FreeBSD web pages. There is a little in the handbook, a little more in the tutorials section and I even found a page on NetBSD's site illuminating. It should be enough to figure it out. That's what I had to do for the contest. If you run into any specific problems, you could e-mail me, or maybe people on the questions list instead of the hackers list. When I get a break, I may submit my notes to the handbook or FAQ, but not just yet. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 16:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04680 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 16:21:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles33.castles.com [208.214.165.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04671 for ; Sun, 1 Nov 1998 16:21:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA06721; Sun, 1 Nov 1998 16:20:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811020020.QAA06721@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Sun, 01 Nov 1998 22:25:05 GMT." <199811012225.PAA28667@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Nov 1998 16:20:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > In general, the only place strings should probably be used in the > > > kernel at all are in filesystem namespace exposures. > > > > You're internally inconsistent. Last time you decided you liked > > strings over manifest constants. > > I like strings *out*. > > I believe the "last time" to which you refer is the mount fstype > argument, in which I thought it was stupid to limit yourself to > defined FS's in mount.h. So you want more binary clutter and interface dependency just to translate FSNAME to FSNUMBER? > So installing a new FS type installs commands in /sbin, and hving > installed commands in /sbin, the list is known via a traversal of > sbin, without even asking the kernel. Er. And who do you ask to do the traversal of /sbin? > > > I think it is a mistake for FreeBSD to turn into Plan9. > > > > I think it's a mistake for us to make any technical decisions on > > emotional or us'n'them grounds. > > I'm not saying that. I'm saying that there is a recent tendency > to bloat in the direction of Plan9-style interfaces. ... and you're attaching an implicit value judgement to that "tendency". > > There are instances where it's clearly useful to be able to process > > string format data (eg. the SCSI quirk code). The necessity for this > > combined with the lack of formal string parsing has led to the > > implementation of any number of ad-hoc solutions. If you want to argue > > for the removal of all string processing in the kernel, you need to > > explain how all of these existing functions are going to work. > > I'll be happy to address the architectural issues on a case-by-case > basis, to any level of detail you want. > > One does wonder how you would boot from a "quirked" drive if you > had to allow pushing the data over the user/kernel boundary to > be able to recognize the quirks. You're the one agonising over passing data across the user/kernel boundary. My primary agenda for string parsing is to free us from the chore of versioning binary interfaces (primarily with the boot code) in favour of using extensible string-based constructs. You'll note I've also been using self-describing binary structures in situations where they're appropriate. > One could easily claim that the use of strings in sysctl is bogus, > and that the parsing should be to MIB identifiers, and take place > in user space to keep the kernel lean. This might have been fine when the MIB was a static object produced at compile time. As an approach for name translation in a dynamic tree it's simply not workable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 17:22:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11325 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 17:22:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11318 for ; Sun, 1 Nov 1998 17:22:45 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem11.masternet.it [194.184.65.21]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id CAA11838; Mon, 2 Nov 1998 02:19:51 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <199811020119.CAA11838@scotty.masternet.it> From: "Gianmarco Giovannelli" To: hackers@FreeBSD.ORG Date: Tue, 3 Nov 1998 12:30:25 +0100 MIME-Version: 1.0 Content-type: Multipart/Mixed; boundary=Message-Boundary-30653 Subject: perl guru needed Reply-to: gmarco@giovannelli.it CC: freebsd@scotty.masternet.it X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Message-Boundary-30653 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body (I hope to be in the right Mailing lists... ) Hello, I am writing some perl scripts (in attach) to generate on the fly the contents of the port dir, with some additions to the plain README.html generated by a make readmes in the ports dir Now I am encountering some little obstacles that are too much for me ... so I ma searching for some help here :-) The main problem is the way the cgi passes the param on the url ... Some names in the port contain the + sign with seems to interfere with the parsing routines of the perl. Btw... If you would give them a look they are attached here... Any feedback is greatly appreciated... Thanks for attention... Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" --Message-Boundary-30653 Content-type: text/plain; charset=US-ASCII Content-disposition: inline Content-description: Attachment information. The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any another MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance. ---- File information ----------- File: portdirpl.tgz Date: 2 Nov 1998, 2:16 Size: 4086 bytes. Type: Unknown --Message-Boundary-30653 Content-type: Application/Octet-stream; name="portdirpl.tgz"; type=Unknown Content-disposition: attachment; filename="portdirpl.tgz" Content-transfer-encoding: BASE64 H4sIAPIHPTYAA+1a6XbbRpbOX+IpaiB2CMQQQGo9kZpqy5LsKG0pPhI74xzL44BAkcQRCCBY RLPVyrP3d6uwkaIs2o6dmWmWF2KpulvdvXBxcnh8dmKm79NvvtjotNs7W1vsG0ajTb+d3e12 fs/YxlZnm7Gdnc7uRruzu7OJ152Njd1vWPvLkVSNLEntmLFv4jD8oAiGYzt2wq9B0VcdP3Df Dw02nrLAHnPmJeyFZweCV2YHLktHeIS3Ay9OUmanKR9HKUtDNravOUvCMceMYMgmXjpir3js m6apKL0R3jmxF6UJi/lvmRdzQGOjNI1cQ0zbFtCPXpya0Zhpk5HnjJgDaBUgRlOmE3uqm8rp gE3DjGUJlwRFcTiM7TELA/Y85vzZ5THbMDfWL3uHz16eGCzyuY2pzog711jAWewNRynzQ8dO PawJBbiYRRKNliWZ7ftTZmVJbNEs3+p7gUWvdWawPndsiZozlw/szE/lUlCyZbZzfqWEJNck oDgLaMLY9gLXi83IVw6FPHks5cYim1hIR3bKHAinTwTbwZC7zAuY7bphQItmhTmyb/LV/WyY sD1F6ejslE3shAUh9qfvczblAj9gubgjWAzimGLSVLJgjwMgicI4FZsOMOt6TkcYpLZY0XrS wtLEcyXbNM9gSRoTgcANDHEmX4GNlCRaTJOQBiH0aiIePmGul9hRxGFnkxEP5BbSLtpJAkLs RIqCpzxOCkjO0DPZaQousDBIGL/BQm/AvLS20gvE3EEYj2ndnuKZ3FRu7Jjo6LbCgD+J/Cxp KcqGzioxEoQbHk+J3UFGgPpTNsauelCcXCQAB6pTwVAo0SR07XsBL/CSCQw8LNF8D8Yw9MZR R1eUTZ1d0g6NbSeGEWG7aWvy7cDmGExMb94eH/ZO7komvBw31GkLELKYQyNtKK2QbkiKkzBh XdAIO7hOiG9Yl+2S/ZE1ZQldwVglmyaxHAubDkLwGk2lGWB3oO0lVzAEhycm+wUGRnrohvke jLFbmIt7sj2iGTti1PzDCy+8sYMAHsQzGFSZ2Ix5EoVBIhQRYGDBpG/2UOhKUikyYRIuRHCU 2zfJSjIh0IO9iR0IZRaK6aSMtDC37gHnPhvA+mffE3t7ivTWT4cVhaaXKsoP0Cba9nGUpYSG kJf8KMqf7Yz/hFH4mS+Jo4r/Rdyfif9bm3iZx/+Nnc0Oxf/tzc2vHP8fi+//T+P/GnuFOCAD FLtpmx1ljT2bLjZypi00Kx1LKLgL20qy+Ma7oeCaO/I9vH21fmxPDXYkf57JnxP5cyF/fK+P jQhculPW6A+7hD+FFzmCk/aGuCd3VxGLB5ilFNnFyXuKZzzeV5S1NbAAD/EcPgHJhu1cw/3Q zaX3T7iPY544xZ3S7A+S7sY+U5qRuFCarvyVUMLY5SUnqXBqSlP89sWrbjufeRQmiF+ekyjN AWAPbId31Z957NqBbTAkWTf01lYJU3/ohH4Yd9U127U732+rwHqDuHLdVYdwZ4Fa4wHkIx0i zkW4ButYj+cRHndVka/Qi0TdbyAu0LJPGALbz3bshVmCDexTxjMhX0yOVaQk5MdlntfnFNYp rpD8Pw2dAhyMuBDR9VZpaE03G4+n3ea7N+23Ouv+zpI18ztrbS3ZVxoxT7M4YHLKvnInlyOT e5/S2nyp9iueMAHgV33hqo+jUeBAcE2R3xIa/ClxpSON3a7bvjcMugctnw/S1p1B267drifQ qu4BaZHB1oUaHJQacWdIBnUTED4ZQOdzAWwAwH0JkYg+XoXqcnIhJwjpKWUysOWUdRn9aEC5 9ZYwPnVtbNRlFhjsLMR/vQzm+N8cFUFvlBnI5JFGXNqpmDoGxaOu9qONec85VPLMjg12GMV0 BX/xI0H5MfPxLBtiGY8M9pMDez8Pb8jGHZ2siB3ZvsN8m0oXB1lOwnremCukcWMPAJojeCr8 jF2C2RwTVc0pJ1TNCZ5BF5HcUUGQYp2mlbzpb76HFN90jA1j09gyto2dtzDttQZAuJBFt4nF bwSIt6bKVFNgyK+Iszf0k78ifGC5WLrMdLqS/AnRs57Laurp3tcNW7sdxXzQPVBNSyjh3+BK ZJYsVKqlzutP9EH9gQa62nIKJ9n6iBUeacwmIVmspaRyEigp3CJ1a5O6La9tf4iyNZTP16lO e4FS1WRQ1yljGaXKpYW6zYuCSPqx+842jS12FV+lV4FluYtljgBxzsmAbJRNVXFJpFc1X149 JqhanhRljXhLy0+p7AuuqYDLq10btYefiYKcCkqPSg2eBK2UTcL4uiq5ZM1T8vEb2GBzXHR/ Bw+thdTf/Uem9UuPqj3x5XAg/9/d3n6w/7e5vbNb5P+bu5ttkf9vdFb9v68x1v5LJJFFu4ut T5T/lSWBwhRqwR29OGW/TbQ98cKOXX2fsbIGUItilmJjk7xrTJubwt/STaLDVSDXdsIsQKUA N0zZe5QlI+1pHE4So8j3NPUIv8MwnqqGekZL8UtlA7Uu4K5UikwgCGk5t50Ra8om0F/LzNz6 7kAnZ+sNmLbu5u+//Ta/CEBpNZUaqj7QJepDM6gPJWKEqiPeNRoFA93i4klnnx4XGXW3uNAE NNC6xuYGESZR8d8eQtVowGm3XNmsgssX1diYB0ilRB1yD2gxmi5EBemqV2/YcQGQlrCrt6hT APbG45NCGdz6DGy6TVuztw4NajTo3x3jfiKqBMQucEnAuyL711TBghVdD62jn87OTs57Kpid J0cAwW6J9fd329XUqFR31SiliGhduySsRr47Ii+5Q2CRKTBKNBRIL3jAY9ldLqqcKPYgrBG3 UShqOnVPoYvvRunY19ZTLwWk7gFTydYS1I++zx2hXEiJigrxoKgVsXrU0VRqYRb97nvrdIPo nc2w+gszLEBjIyJJUZaZbigs0tRf8v4c4rwohsOo2EFRgCKJ4NxUCSbNfo6K1QuoMZt33OEM qB0csqKRXq0qGnp+GF4T+BaxOc9eiyXyosBayIEykT6tVEFnmea2aKf2LNnMH4VJKrxcMgIH lhs6VrGqvDBpX5Aoq8AgzgbCSXW2MIaVewFXGSSnhvEsJjrUAKbJZGJSN7KfuGYYDysMgtEC PHxUOkP+hCOt8VIOyRWyO/ST0CATpZboJMz8ygYpw4o9ZEuUPQUwItEVgKwH3ntyuPw9rInK 9DCA1hKdai5c0Aq7Agggh4p9HPmAWDDQeiXv2YvMczl1w5OWTngonZvdoTHEzpwsjslnlHIG o8TkD9SZFj2GETXY+bporLuVky1PAlSzrxWeTkdyC0sFnjD2eLIn9S3XZabIFo1GVn+7nndo Dur9Guhyo9GLtTfCBbzVFSaFbkgQIOyWFaWTKrrlqIsSYcgDTRWGPqwMnSID22N/MTcGxHui GlWcWa/FHx2g8ZcHrrR++I8/O+yXA87zC3d/H8v/Op32bpn/tdubW3jU3tnZWuV/X2P8n8n/ FqZ/bI8MapPtBTxNHDuiZOeBdFB0TGUBqYnjRk3NWyAinROhvZu/oGtKJR5OIlHs56uNJnlI utK7SeR7qWZdWZYh8AkQ9YSlathaYsJ87qKEEQ+0s/xc0ZiZn+OzSnxWMY9WTkYiB20KN9pl fy3eHejUI6Wn3bwLIOdQDiOyQLngd2b9z/HpZe/88Oyka3m0iErs/AS0K5cUjdkuNWYps6K8 ah7KyevexeFR793lP56/lpDmEzKtmWQDBKxFUMvJd7UEbh7Fq7+/mKUTUnyITNB4H8DZ4WXv 5OLd5Wnv5PIhGsd2QufRXroYbDGxUZtIHagMOhvXVxttA+HD5e9nHqoWaV2DqFtqLNys56cv H6a/zKuXFfMCJGeHp+c9/Du5eFhKnuj5UDWyLJoPcHmnKIKEfENFdYJShFU7XKjkPqbKuiWf Wsk+f1ITfPFEXZdSLx54QUJtw7JeGvphH0Z6Y8eW2xe2WUfxnaz76gQKAPNE0sOueh6m9AFF aiODddX9grO6tkDEMJNzUkNLv61rnDoQSVmSBXRrZoFjcjezoqxvvfSC7H3pDQjwQrivj346 712cPlsM2Il90+WO6YRjAfR1p2PlueXjoF+c/2Mx1CjmkWl75thLS3KHQfY4xFcnFy/fHb06 PF8MF/+brjf0IMuSYtTMMmJZYt04dDPoutWfrsvLx5H2Tl6/O+p9AGeO2XHjcFziTfl7y0H0 eRz+348f2FUCmiXmtctFpk1Qcf1BgELF2L/+xe5hefnT0eFLS2e3s36ohqqe1ROuvPKo1fo1 5SysOVdq1ritPwRcEYyuntaAlvRKr15bmT/AKhMR1Bz+s5xaFf3V7OpZl5VmbuZAChLXEdZr QbFcYzVnuiSN8hY6CeOGPf5CHZZ9pWon3J9yHooZ8iSVPeNDL2BzOf9yVb0o6inbKflgV2XC cKU/UOIry9fvivJYO2CPlfoEIh1O1ZM22tDUkiR4M4MpSv5KVk6ofoqySW0TmRPPRdp0oH7f /otKxRNqJ+qk3DvKeeC0CN50tm+mG3I1EIHrJLKp0NoAaLbcYRIlUwKILon5OFrO7FyTP0TJ UoRU52kwDz8N92pmotKhV3mn5+Qi1udRjsiej3wfxQTU8gf6wIx0U3KyANzn8lXzJ5Kh4g41 uKWaCyfWrZA2q7iZoZEuaesaH6tIObTa3i2pMxUZtAuN+vloWeQvBQpUnAazHUv2N6bqpqfN exP907X01fXwXNrnx/GZpx+VZn8Gk3newvZy7mqpTU2hFbqMjAjXs26k8hvbpd9oiKEsLYn6 kXV1SgVo6oU84RMfIcMWotIMPgl21f0tz8RL1zmDrHhaIZRJ8ychFW2XCiEVg9+KErQs6oD7 Z+qTV1Xep7M4i60l0LUkvpdhMCSvWuKjB+IjqT8OocBHCI78EMGX0KilgeginMXUFcvTkPIM RITy2bOKShq35D9kNK4rX63z1+q07gwNqresCcF2Nfkh0b1CvcD7qy6HOAIoXNosiaVEF1RM X41eKl6OTy6PLiqCy2IM/lcc6ktiam3J5aq0esH2Z7evVuMzR+X9vhyOR87/N3Y7W7Xz/y1x /r+9s+r/fo3xH9P/LWIR+0APuDhYb3+w9bvwi4HzUHwl8ODXAvPfCizq7MqvBupBpf7xQJV/ UGiEfxcfDDCqiKtzcOHyRdhs1L5zKC+fsMc+FVjihJ09eI4uoj64r3rVBfz6wXr9MD0PpNX3 uZ91mi4P079OeX1Vcnml0jGkPEFc7jy9dpwehJPiU7niYHMqjzxz6HTkiSzcvB/nCyHXdudX kZBr6iGIvCnO2AnN3CGqOKhf7hSWvj0Xmov6bpxIWr2kInavZD4ylCL9f+DsdT59qJ/ENiid VvKT2BqoooahD1lVoywsEFOoshDF1UytI+bd6yf8sTXGY5XVA9j+gIPkoo6+f6S8SsZWYzVW YzVWYzVWYzVWYzVWYzVWYzVWYzVWYzVWY278G25WwO8AUAAA --Message-Boundary-30653-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 18:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15549 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 18:16:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15526 for ; Sun, 1 Nov 1998 18:16:45 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA22122; Mon, 2 Nov 1998 12:46:17 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810301644.IAA00468@dingo.cdrom.com> Date: Mon, 02 Nov 1998 12:46:16 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: FreeBSD arm port Cc: Hackers@FreeBSD.ORG, "Stephane E. Potvin" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Oct-98 Mike Smith wrote: > I think you'll find intense interest; certainly from those of us with > embedded-systems backgrounds. There are plenty of neat SA-based devices > out there that would be even more fun to play with under FreeBSD. > > What I want *now* is for someone to do a Palm Pilot clone using a > processor with a PMMU. 8) Well, AFAIK newer mobile phones have SA chips in them... Nokia 9000 eat your heart out ;) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 21:30:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09710 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 21:30:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09702 for ; Sun, 1 Nov 1998 21:30:46 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40354>; Mon, 2 Nov 1998 16:30:01 +1100 Date: Mon, 2 Nov 1998 16:30:29 +1100 From: Peter Jeremy Subject: Re: sync writes with softupdates enabled To: hackers@FreeBSD.ORG Message-Id: <98Nov2.163001est.40354@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: >Now that this has been committed, can we have some feedback from people >using mmap heavily on -current? There are no longer any sync writes as a result of using an MMAP'd history file in inn. There is no obvious corruption of history file or associated .pag file. Note that there is a similar bug in 2.2.x. The fix is similar, but needs some thought since there appears to be a problem with the parameters to vm_object_page_clean(). In particular, `syncio' is defined as boolean_t, as passed as the `waitfor' argument to VOP_FSYNC() - which is MNT_ASYNC or MNT_SYNC elsewhere. I haven't had the time to work out the correct definitions. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 21:43:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10932 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 21:43:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isi.co.jp (ns.isi.co.jp [202.214.62.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10926; Sun, 1 Nov 1998 21:43:35 -0800 (PST) (envelope-from john@isi.co.jp) Received: by ns.isi.co.jp id <21889>; Mon, 2 Nov 1998 14:41:59 +0900 Date: Mon, 2 Nov 1998 23:40:57 +0900 From: john cooper X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: Barrett Richardson CC: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jabley@clear.co.nz, tfujii@isi.co.jp Subject: Re: Request help with packet forwarding problem [2.2.7].. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <98Nov2.144159jst.21889@ns.isi.co.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Barrett, Your eyes are better than mine. Sure enough I screwed-up the IP address for the static route on machine B. Works fine now. In the future I'll avoid making such requests at midnight. :) Thanks again, -john Barrett Richardson wrote: > > Look at this route on machine B: > > 203.214.62 202.214.62.40 UGSc 0 596 vx0 > ^^^ > > I think it probably should be > > 203.168.62 202.214.62.40 UGSc 0 596 vx0 > > Are you sure you were running the tcpdump on FW and not B? With no route > to 203.168.62 on B, the ISP router and B should have played ping pong > with the echo request until it died. > > Also check the netmask on vx0 on FW. It is not showing a 202.214.62/25 > route like B is. > -- John Cooper Consulting Engineer Integrated Systems Japan Ltd. TEL +81-3-3492-3171 Asahi Bank Gotanda Bldg. FAX +81-3-3492-3066 1-23-9 Nishi Gotanda EMAIL john@isi.co.jp Shinagawa-ku Tokyo 141 JAPAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 22:07:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14656 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 22:07:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA14638 for ; Sun, 1 Nov 1998 22:07:36 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zaD9A-00021T-00; Sun, 1 Nov 1998 23:07:24 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id XAA00655 for ; Sun, 1 Nov 1998 23:06:57 -0700 (MST) Message-Id: <199811020606.XAA00655@harmony.village.org> To: freebsd-hackers@FreeBSD.ORG Subject: Ariel Faigon: The Holloween Document (fwd) Date: Sun, 01 Nov 1998 23:06:57 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got this on a linux list that I'm on and thought I'd forward it to this group. It seems relevant. It will likely make you mad. Warner ------- Forwarded Message From: ariel@oz.engr.sgi.com (Ariel Faigon) Subject: The Holloween Document (fwd) To: linux@cthulhu.engr.sgi.com (SGI/Linux mailing list) [This is significant. It details an internal (and confidential) Microsoft sanctioned memo on how to fight the Open Source movement and Mainly Linux. ] Read carefully and Please distribute widely. The document is long I just quote some crucial parts of it] http://www.tuxedo.org/~esr/halloween.html - ------------------------------------------------------------------------ Here are some notable quotes from the document, ``OSS'' is the author's abbreviation for ``Open Source Software''. Vinod Valloppillil (VinodV) Aug 11, 1998 ¨C v1.00 Microsoft Confidential [only a few excerpts follow, read the link above for the full details.] * OSS poses a direct, short-term revenue and platform threat to Microsoft, particularly in server space. Additionally, the intrinsic parallelism and free idea exchange in OSS has benefits that are not replicable with our current licensing model and therefore present a long term developer mindshare threat. * Recent case studies (the Internet) provide very dramatic evidence ... that commercial quality can be achieved / exceeded by OSS projects. * ...to understand how to compete against OSS, we [Microsoft] must target a *process* rather than a company. * OSS is long-term credible ... FUD tactics can not be used to combat it. * Linux and other OSS advocates are making a progressively more credible argument that OSS software is at least as robust ¨C if not more ¨C than commercial alternatives. The Internet provides an ideal, high-visibility showcase for the OSS world. * Linux has been deployed in mission critical, commercial environments with an excellent pool of public testimonials. ... Linux outperforms many other UNIXes ... Linux is on track to eventually own the x86 UNIX market ... * Linux can win as long as services / protocols are commodities. * OSS projects have been able to gain a foothold in many server applications because of the wide utility of highly commoditized, simple protocols. By extending these protocols and developing new protocols, we can deny OSS projects entry into the market. * The ability of the OSS process to collect and harness the collective IQ of thousands of individuals across the Internet is simply amazing. More importantly, OSS evangelization scales with the size of the Internet much faster than our own evangelization efforts appear to scale. - -- Peace, Ariel ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 1 22:52:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20693 for freebsd-hackers-outgoing; Sun, 1 Nov 1998 22:52:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20675 for ; Sun, 1 Nov 1998 22:52:45 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA09126; Mon, 2 Nov 1998 17:22:08 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA24329; Mon, 2 Nov 1998 17:21:40 +1030 (CST) Message-ID: <19981102172140.J354@freebie.lemis.com> Date: Mon, 2 Nov 1998 17:21:40 +1030 From: Greg Lehey To: Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Microsoft's Open Source strategy (was: Ariel Faigon: The Holloween Document (fwd)) References: <199811020606.XAA00655@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: <199811020606.XAA00655@harmony.village.org>; from Warner Losh on Sun, Nov 01, 1998 at 11:06:57PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [following up to -chat] On Sunday, 1 November 1998 at 23:06:57 -0700, Warner Losh wrote: > I got this on a linux list that I'm on and thought I'd forward it to > this group. It seems relevant. It will likely make you mad. This isn't -hackers material. I'm currently reading the full version (which I've tidied up a bit of remnants of Microsoft formatting and put at http://www.lemis.com/microsoft-tactics.html). It doesn't make me mad. And maybe the stuff below is misleading. It's an interesting (if long) document, but I haven't got to the end, where I expect to find some recommendations. Greg > Read carefully and Please distribute widely. The document is long > I just quote some crucial parts of it] > > http://www.tuxedo.org/~esr/halloween.html > > - ------------------------------------------------------------------------ > Here are some notable quotes from the document, ``OSS'' is the > author's abbreviation for ``Open Source Software''. > > Vinod Valloppillil (VinodV) > Aug 11, 1998 ¨C v1.00 > Microsoft Confidential > [only a few excerpts follow, read the link above for the full details.] > > * OSS poses a direct, short-term revenue and platform threat > to Microsoft, particularly in server space. Additionally, the > intrinsic parallelism and free idea exchange in OSS has benefits > that are not replicable with our current licensing model and > therefore present a long term developer mindshare threat. > > * Recent case studies (the Internet) provide very dramatic > evidence ... that commercial quality can be achieved / exceeded > by OSS projects. > > * ...to understand how to compete against OSS, we [Microsoft] > must target a *process* rather than a company. > > * OSS is long-term credible ... FUD tactics can not be used to combat it. > > * Linux and other OSS advocates are making a progressively more > credible argument that OSS software is at least as robust ¨C if > not more ¨C than commercial alternatives. The Internet provides > an ideal, high-visibility showcase for the OSS world. > > * Linux has been deployed in mission critical, commercial > environments with an excellent pool of public testimonials. > ... Linux outperforms many other UNIXes ... Linux is on track to > eventually own the x86 UNIX market ... > > * Linux can win as long as services / protocols are commodities. > > * OSS projects have been able to gain a foothold in many server > applications because of the wide utility of highly commoditized, > simple protocols. By extending these protocols and developing > new protocols, we can deny OSS projects entry into the market. > > * The ability of the OSS process to collect and harness the > collective IQ of thousands of individuals across the Internet > is simply amazing. More importantly, OSS evangelization scales > with the size of the Internet much faster than our own evangelization > efforts appear to scale. -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 00:07:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29018 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 00:07:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29012 for ; Mon, 2 Nov 1998 00:07:52 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA01993; Mon, 2 Nov 1998 00:02:09 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdZS1985; Mon Nov 2 08:02:07 1998 Date: Mon, 2 Nov 1998 00:01:43 -0800 (PST) From: Julian Elischer To: Greg Lehey cc: Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Re: Microsoft's Open Source strategy (was: Ariel Faigon: The Holloween Document (fwd)) In-Reply-To: <19981102172140.J354@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, Greg Lehey wrote: > [following up to -chat] > > On Sunday, 1 November 1998 at 23:06:57 -0700, Warner Losh wrote: > > I got this on a linux list that I'm on and thought I'd forward it to > > this group. It seems relevant. It will likely make you mad. > > This isn't -hackers material. I'm currently reading the full version > (which I've tidied up a bit of remnants of Microsoft formatting and > put at http://www.lemis.com/microsoft-tactics.html). I doubt this document has come from microsoft. It smells of "linux fanatic's daydream" to me.. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 01:40:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10599 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 01:40:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mypad.MYPAD.COM ([209.218.33.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10593 for ; Mon, 2 Nov 1998 01:40:49 -0800 (PST) (envelope-from joe_fp@ucsd.com) From: joe_fp@ucsd.com Received: from mypad (209.218.33.127) by mypad.MYPAD.COM (NPlex 3.0.036) for hackers@freebsd.org; Mon, 2 Nov 1998 01:36:29 -0800 Message-ID: <3633F2C50002E011@mypad.MYPAD.COM> (added by postmaster@mypad.MYPAD.COM) Date: Mon, 02 Nov 1998 01:36:28 -0800 Subject: inquiry To: hackers@FreeBSD.ORG X-Mailer: WinNT's Blat ver 1.7.1 http://www.interlog.com/~tcharron Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How could I join into developing team of freebsd? Tell me please... I'm interesting to use and develop the freebsd. I look forward to hear you soon. Thank's for your attention. Joe Fivara P ___________________________________________________ Get Your Free Email at http://www.friendlyemail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 02:46:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18353 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 02:46:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18347 for ; Mon, 2 Nov 1998 02:46:32 -0800 (PST) (envelope-from martti.kuparinen@lmf.ericsson.se) Received: from lmf.lmf.ericsson.se (umail.lmf.ericsson.se [131.160.11.2]) by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/WIREfire-1.2) with ESMTP id LAA03232 for ; Mon, 2 Nov 1998 11:46:27 +0100 (MET) Received: from tosb0323 by lmf.lmf.ericsson.se (8.8.8+Sun/SMI-SVR4) id MAA19950; Mon, 2 Nov 1998 12:46:24 +0200 (EET) Message-Id: <3.0.6.32.19981102124453.02ce8b30@openmail.lmf.ericsson.se> X-Sender: lmfmara@openmail.lmf.ericsson.se X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 02 Nov 1998 12:44:53 +0200 To: hackers@FreeBSD.ORG From: Martti Kuparinen Subject: Pseudo-device as a LKM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to implement a pseudo-device as LKM. But the question is where to find a working example? I've looked at e.g. the if_tun device, but the unload is not successful: # modload /lkm/if_tun_mod.o # modunload -n if_tun_mod modunload: LMUNLOAD: Device busy So please give any pointers. I'm using 2.2.7-R but I could jump into 3.0 if that's what needed. Martti To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 03:39:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25107 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 03:39:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25101 for ; Mon, 2 Nov 1998 03:39:50 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id DAA23664; Mon, 2 Nov 1998 03:40:03 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: joe_fp@ucsd.com cc: hackers@FreeBSD.ORG Subject: Re: inquiry In-reply-to: Your message of "Mon, 02 Nov 1998 01:36:28 PST." <3633F2C50002E011@mypad.MYPAD.COM> (added by postmaster@mypad.MYPAD.COM) Date: Mon, 02 Nov 1998 03:40:03 -0800 Message-ID: <23661.910006803@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How could I join into developing team of freebsd? Please see chapter 19 of the FreeBSD handbook: http://www.freebsd.org/handbook/handbook.html Thanks.. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 05:14:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08445 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 05:14:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08439 for ; Mon, 2 Nov 1998 05:14:18 -0800 (PST) (envelope-from etxgnon@etxb.ericsson.se) Received: from avx6 (avx6-unix2.etxb.ericsson.se [130.100.190.16]) by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/WIREfire-1.2) with SMTP id OAA03916 for ; Mon, 2 Nov 1998 14:14:09 +0100 (MET) Received: from avc354.etxb.ericsson.se by avx6 (SMI-8.6/LME-2.2.6) id OAA08882; Mon, 2 Nov 1998 14:14:04 +0100 Received: from etxb.ericsson.se by avc354.etxb.ericsson.se (SMI-8.6/client-1.6) id OAA19813; Mon, 2 Nov 1998 14:14:03 +0100 Message-ID: <363DB01B.56CD6035@etxb.ericsson.se> Date: Mon, 02 Nov 1998 14:14:03 +0100 From: Gunnar Olsson Organization: ETX-DN-SL X-Mailer: Mozilla 4.05 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, etxgnon@etxb.ericsson.se Subject: MPPP, multilink PPP Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, my name is Gunnar Olsson, working for Ericsson Research in Sweden. We are looking on delay requirements for IP packets over PPP. I want to segment long data packets on PPP level, to minimize the "waiting time" for a real time packet. I was planning to use the segmentation algorithm in Multilink PPP, MPPP. For performance issue I am doing everything in kernel. So, the question is, have someone implemented MPPP in kernel???? Please let me know! Send me a mail: gunnar.olsson@ericsson.com Regz Gunnar Olsson -- wwwww g( o o )g --oOO--(_)---OOo-------------------------------------------- MVH/ Gunnar Olsson, ÄV/ETX/DN/SL, 7192413 E-mail: gunnar.olsson@ericsson.com .ooo0 0ooo. MEMO: ETX.ETXGNON ( ) ( ) ----\ (---) /----------------------------------------------- \_) (_/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 08:24:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02912 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 08:24:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02904 for ; Mon, 2 Nov 1998 08:24:06 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id RAA13214; Mon, 2 Nov 1998 17:23:53 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA03675; Mon, 2 Nov 1998 17:23:48 +0100 (MET) Message-ID: <19981102172348.46633@follo.net> Date: Mon, 2 Nov 1998 17:23:48 +0100 From: Eivind Eklund To: Gunnar Olsson , freebsd-hackers@FreeBSD.ORG Subject: Re: MPPP, multilink PPP References: <363DB01B.56CD6035@etxb.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <363DB01B.56CD6035@etxb.ericsson.se>; from Gunnar Olsson on Mon, Nov 02, 1998 at 02:14:03PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 02, 1998 at 02:14:03PM +0100, Gunnar Olsson wrote: > Hi there, > my name is Gunnar Olsson, working for Ericsson Research in Sweden. > We are looking on delay requirements for IP packets over PPP. > I want to segment long data packets on PPP level, to minimize > the "waiting time" for a real time packet. I was planning to use > the segmentation algorithm in Multilink PPP, MPPP. > For performance issue I am doing everything in kernel. > So, the question is, have someone implemented MPPP in kernel???? There is no multilink implementation for the FreeBSD kernel, no. What you _could_ do is work with Brian to segregate the user-interface and the protocol handling in the userland PPP, making it possible to compile the protocol handling itself into the kernel. This could be very useful, as it provide a good development-environment (userland), while making it possible to exploit the performance boost of having the code in the kernel. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 08:57:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07246 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 08:57:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07236 for ; Mon, 2 Nov 1998 08:57:23 -0800 (PST) (envelope-from Parag.Gandhi@Digital.com) Received: from ns1.digital.com.sg (ns1.digital.com.sg [203.127.158.130]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA24696 for ; Mon, 2 Nov 1998 08:57:23 -0800 (PST) Received: from qcaexc1.qca.dec.com (qcaexc1.qca.dec.com [16.180.0.248]) by ns1.digital.com.sg (8.8.8/8.8.8/WV1.0c) with ESMTP id AAA05558 for ; Tue, 3 Nov 1998 00:56:25 +0800 (SST) Received: by qcaexc1.qca.dec.com with Internet Mail Service (5.5.2232.9) id ; Mon, 2 Nov 1998 22:26:16 +0530 Message-ID: <4974E68113C7D1118F5D0000F878AB68080341@XFMEXC1.xfm.dec.com> From: Parag Gandhi To: "'freebsd-hackers@freefall.cdrom.com'" Subject: tell me what it is all about ? Date: Mon, 2 Nov 1998 19:54:31 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 09:21:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09864 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 09:21:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09858 for ; Mon, 2 Nov 1998 09:21:26 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from lal.cs.utah.edu (lal.cs.utah.edu [155.99.192.110]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id KAA18385; Mon, 2 Nov 1998 10:21:21 -0700 (MST) From: David G Andersen Received: (from danderse@localhost) by lal.cs.utah.edu (8.8.8/8.8.8) id KAA01674; Mon, 2 Nov 1998 10:21:33 -0700 (MST) Message-Id: <199811021721.KAA01674@lal.cs.utah.edu> Subject: Re: nfs/amd hangs / getattr request flood problem To: jwd@unx.sas.com (John W. DeBoskey) Date: Mon, 2 Nov 1998 10:21:33 -0700 (MST) Cc: danderse@cs.utah.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199811011853.NAA15179@bb01f39.unx.sas.com> from "John W. DeBoskey" at Nov 1, 98 01:53:46 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope - we're seeing a different problem. The only "huge quantities of traffic" we're getting are traffic from the kernel to the local 'amd'. Your patch doesn't change that (just tested it). I'm about to grab the previous AMD out of the attic as Mike suggested, and we'll see how that goes. -Dave Lo and behold, John W. DeBoskey once said: > > Hi, > > I've sent mail to -current a few times... Try the following > change on your FreeBSD client machine(s): > > /usr/src/sys/nfs/nfs_vnops.c: > 273c273 > < int v3 = NFS_ISV3(vp); > --- > > int v3 = 0; /* NFS_ISV3(vp); */ > > ie: Turn off the 'access' portion of the v3 protocol. > > I have a build farm of about 50 266Mhz machines talking to Network > Appliance fileservers. Without the above change, the network is > swamped... > > Good Luck! > John > > > > We're in the process of configuring some new machines (for personal and > > distributed build farm use), and we're seeing some atrocities with amd. > > The machines are running 3.0-RELEASE (plus the last few days of checked in > > fixes). They receive AMD maps via NIS and a static map, but disabling NIS > > doesn't affect things. We've made significant tweaks to the rest of the > > system configuration (disabling nis, mfs, slowing things down, etc) and > > tried it on multiple systems, and the problem keeps popping up. This > > behavior isn't exhibited in 2.2.x. > > > > We have AMD looking at /n/{machine}/path, with the actual mounts on > > /a/{machine}. When compiling with a source tree on /n/machine/path and an > > object tree on local /z, AMD can use up to 50% of the processor. Ktrace > > and tcpdump output shows that it's handling around 150 getattr requests > > per second, on "/n" and "/n/machine", and the ktrace indicates that that's > > the _only_ thing it's doing. > > > > The result of this is some serious slowdowns, and reproducible system > > freezes (kernel alive and pingable, no userland activity whatsoever). > > Unfortunately, we don't have a simple way of reproducing the hangs yet - > > it happens while running the Linux suse Matrox Xserver and the FreeBSD > > netscape (entering, then leaving, and then re-entering Netscape frequently > > triggers the hang). > > > > There don't seem to be any references to this in gnats or on the lists. > > We're working on forward-porting the 2.2.x amd to 3.0 to see if the > > behavior still exists, but in the meantime, if anyone has suggestions / > > thoughts / knows what's wrong and wants to clue me in, it'd be greatly > > appreciated. :) > > > > -Dave > > > > - -- > > work: danderse@cs.utah.edu me: angio@pobox.com > > University of Utah http://www.angio.net/ > > Department of Computer Science > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > -- work: danderse@cs.utah.edu me: angio@pobox.com University of Utah http://www.angio.net/ Department of Computer Science To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 09:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12797 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 09:47:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12778 for ; Mon, 2 Nov 1998 09:47:00 -0800 (PST) (envelope-from marcs@znep.com) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.9.1a/8.9.1) with UUCP id KAA11756; Mon, 2 Nov 1998 10:46:46 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with ESMTP id JAA05631; Mon, 2 Nov 1998 09:42:35 -0800 (PST) Date: Mon, 2 Nov 1998 09:42:35 -0800 (PST) From: Marc Slemko To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-Reply-To: <199811012142.OAA27464@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Nov 1998, Terry Lambert wrote: > > #define memcpy(d,s,n) bcopy(s,d,n) > > > > not exactly rocket science :-) > > Actually, bcopy is closer to memmove, since it supports overlapping > ranges as its arguments. bcopy doesn't support overlapping ranges on all systems. eg. IRIX 6.2 man page: NOTE The use of overlapping buffers with bcopy is not guaranteed to work. Use the memmove(3C) function if the buffers might overlap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 10:23:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15527 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 10:23:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15522 for ; Mon, 2 Nov 1998 10:23:46 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA06475; Mon, 2 Nov 1998 11:23:40 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd006422; Mon Nov 2 11:23:37 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA00418; Mon, 2 Nov 1998 11:23:35 -0700 (MST) From: Terry Lambert Message-Id: <199811021823.LAA00418@usr05.primenet.com> Subject: Re: scanf in the kernel? To: marcs@znep.com (Marc Slemko) Date: Mon, 2 Nov 1998 18:23:35 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: from "Marc Slemko" at Nov 2, 98 09:42:35 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > #define memcpy(d,s,n) bcopy(s,d,n) > > > > > > not exactly rocket science :-) > > > > Actually, bcopy is closer to memmove, since it supports overlapping > > ranges as its arguments. > > bcopy doesn't support overlapping ranges on all systems. > > eg. IRIX 6.2 man page: > > NOTE > The use of overlapping buffers with bcopy is not guaranteed to work. Use > the memmove(3C) function if the buffers might overlap. IRIX is SVR4 derived, so that's no surprise; bcopy is probably a #define for memcpy. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 10:40:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16745 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 10:40:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16736 for ; Mon, 2 Nov 1998 10:40:39 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from elle.ifi.uio.no (2602@elle.ifi.uio.no [129.240.64.210]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id TAA26031; Mon, 2 Nov 1998 19:40:19 +0100 (MET) Received: from localhost (dag-erli@localhost) by elle.ifi.uio.no ; Mon, 2 Nov 1998 18:40:18 GMT Mime-Version: 1.0 To: sthaug@nethelp.no Cc: nate@mt.sri.com, dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd References: <199810302033.NAA24629@mt.sri.com> <2701.909779780@verdi.nethelp.no> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 02 Nov 1998 19:40:16 +0100 In-Reply-To: sthaug@nethelp.no's message of "Fri, 30 Oct 1998 21:36:20 +0100" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA16741 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no writes: > > > I cant find this in the tree anywhere. Is there a package or port of ttcp > > > somewhere? > > > > TTCP is part of the kernel, and enabled via sysctl's. > > He's probably talking about ttcp, not T/TCP. As in: > > NAME > ttcp - test TCP and UDP performance > [...] > It's extremely useful. It's also extremely ugly. It has about a dozen printf format errors, a handful of unprototyped functions, a smattering of pointer errors and a valueless return from a non-void function. OTOH, I guess that's not too bad considering it's age. Since it's in the public domain, there's nothing to stop us from cleaning it up and sticking it into the tree. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 10:46:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17287 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 10:46:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17276 for ; Mon, 2 Nov 1998 10:46:14 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from lal.cs.utah.edu (lal.cs.utah.edu [155.99.192.110]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id LAA21855; Mon, 2 Nov 1998 11:45:58 -0700 (MST) From: David G Andersen Received: (from danderse@localhost) by lal.cs.utah.edu (8.8.8/8.8.8) id LAA05127; Mon, 2 Nov 1998 11:46:10 -0700 (MST) Message-Id: <199811021846.LAA05127@lal.cs.utah.edu> Subject: Re: nfs/amd hangs / getattr request flood problem To: mike@smith.net.au (Mike Smith) Date: Mon, 2 Nov 1998 11:46:10 -0700 (MST) Cc: danderse@cs.utah.edu, hackers@FreeBSD.ORG, sclawson@cs.utah.edu, mike@fast.cs.utah.edu In-Reply-To: <199810310018.QAA02943@dingo.cdrom.com> from "Mike Smith" at Oct 30, 98 04:18:57 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lo and behold, Mike Smith once said: > > This may be related to a known defect in the BSD NFS code; we don't > cache getattr requests nor do we cache access requests. > > > There don't seem to be any references to this in gnats or on the lists. > > We're working on forward-porting the 2.2.x amd to 3.0 to see if the > > behavior still exists, but in the meantime, if anyone has suggestions / > > thoughts / knows what's wrong and wants to clue me in, it'd be greatly > > appreciated. :) > > 2.2 has the same problems, although it's amd may not suffer the > consequences. You can save yourself a lot of effort by resurrecting > the 3.0 AMD from the attic (check out the relevant directories a few > days before the new AM-utils stuff went in). Effort saved - thanks again. Interestingly enough, the AMD from pre-8/23/1998 does not exhibit any of the symptoms we see in the 3.0-rel amd; there's no excessive getattr traffic, and (so far) we haven't been able to replicate the system hang behavior. Life seems fairly happy with the backed out AMD, but I do strongly suspect that there's some bug tickling going on with the august amd. If people experience stability problems and filesystem hangs with 3.0 and AMD, I'd suggest trying the older version. -Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 10:51:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17919 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 10:51:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17911 for ; Mon, 2 Nov 1998 10:51:35 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id LAA16141; Mon, 2 Nov 1998 11:51:28 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd016103; Mon Nov 2 11:51:20 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA01338; Mon, 2 Nov 1998 11:51:14 -0700 (MST) From: Terry Lambert Message-Id: <199811021851.LAA01338@usr05.primenet.com> Subject: Re: scanf in the kernel? To: mike@smith.net.au (Mike Smith) Date: Mon, 2 Nov 1998 18:51:14 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199811020020.QAA06721@dingo.cdrom.com> from "Mike Smith" at Nov 1, 98 04:20:08 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I like strings *out*. > > > > I believe the "last time" to which you refer is the mount fstype > > argument, in which I thought it was stupid to limit yourself to > > defined FS's in mount.h. > > So you want more binary clutter and interface dependency just to > translate FSNAME to FSNUMBER? Given a choice between user space bloat and kernel bloat, I choose user space bloat. > > So installing a new FS type installs commands in /sbin, and hving > > installed commands in /sbin, the list is known via a traversal of > > sbin, without even asking the kernel. > > Er. And who do you ask to do the traversal of /sbin? In the limit, /sbin/fstyp. This is not an ideal soloution, but consider that the VFS KLD(s) for a given filesystem may not be in the kernel. For a given mount attempt without an FS type specified, the following occurs: o user types "mount /dev/sd3a /mnt" o mount calls "fstyp /dev/sd3a" o fstyp calls each "/sbin/*_fstyp" until one exits non-zero o mount calls "/sbin/_mount" o /sbin/_mount calls "mount(2)" o If the VFS is not present in the kernel, its KLD is demand-loaded o The FS is mounted. > > > > I think it is a mistake for FreeBSD to turn into Plan9. > > > > > > I think it's a mistake for us to make any technical decisions on > > > emotional or us'n'them grounds. > > > > I'm not saying that. I'm saying that there is a recent tendency > > to bloat in the direction of Plan9-style interfaces. > > ... and you're attaching an implicit value judgement to that "tendency". Actually, I was quite explicit: I think it is a mistake for FreeBSD to turn into Plan9. And with the "I think" in there, it's obviously an opinion. But it's an opinion based on experience, not emotion. > You're the one agonising over passing data across the user/kernel > boundary. Yes, I am. Every time I have to recompile libkvm and ps, w, finger, netstat, etc., etc., I agonize over the externalization of kernel internal data as defacto interfaces. > My primary agenda for string parsing is to free us from the > chore of versioning binary interfaces (primarily with the boot code) in > favour of using extensible string-based constructs. You'll note I've > also been using self-describing binary structures in situations where > they're appropriate. They are apropriate anywhere their data is externalized directly instead of procedurally (an FS is a good place to convert data references into procedural references, if you need that sort of thing, hence procfs). > > One could easily claim that the use of strings in sysctl is bogus, > > and that the parsing should be to MIB identifiers, and take place > > in user space to keep the kernel lean. > > This might have been fine when the MIB was a static object produced at > compile time. As an approach for name translation in a dynamic tree > it's simply not workable. So basically, you are denying the reality of IBM's SNMPv2 implementation, which allows dynamic (de/)registration of manageable hierarchies of exposed data? I have to say, having used the reference implementation 4 years ago on Solaris, I don't think that it has quit working in the interim... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 11:10:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20149 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 11:10:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA20054; Mon, 2 Nov 1998 11:10:00 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA07892; Mon, 2 Nov 1998 14:15:13 -0500 From: Bill Paul Message-Id: <199811021915.OAA07892@skynet.ctr.columbia.edu> Subject: Call for testers for Macronix fast ethernet driver To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Date: Mon, 2 Nov 1998 14:15:11 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a call for testers for those with Macronix 98713, 98715 and 98725 ethernet cards. There is now a driver for these cards available at the following location: http://www.freebsd.org/~wpaul/Macronix/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/Macronix/2.2 source for FreeBSD 2.2.x The Macronix PMAC chips are tulip clones. So far I have run tests with both a 98713A and a 98715A. The 98725 reports the same PCI device ID as the 98715 part, however it's revision is 0x3x where the 98715's revision is 0x2x. The original 98713 (without the A) appears to support an MII bus for external transceivers, however the 98713A and up all use an internal transceiver with NWAY support. For the interested, datasheets and app notes can be had at www.macronix.com. One should read carefully the app note for the 98715A. It explains that in order to put the PMAC chips in proper operating mode, you have to write a magic value to CSR16 (there's one value for the 98713 and another for all the other models). The app note tells you what values to write but doesn't say what the various magic bits mean. Of the two boards I have, the 98713A is made by NDC and is called a SOHOware fast ethernet card. The 98715A was supplied to me by Macronix and has no vendor name on it, but its ethernet address appears to contain Accton's OUI. To add the driver to an existing system, do the following: - Unpack your kernel source code under /usr/src. - Download the corrent version of if_mx.c and if_mxreg.h for your system (3.0 or 2.2.x) and copy them to /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_mx.c optional mx device-driver - Edit your kernel config file (e.g. /sys/i386/conf/GENERIC) and add a line that says: device mx0 - Config and compile a new kernel and boot it. As usual, please send success or failure reports to wpaul@skynet.ctr.columbia.edu. NOTE: I still have not received a lot of feedback on the PNIC or Winbond drivers, or even the RealTek driver for that matter. If you are using one of these drivers, please let me know. If you are using one of these at 100Mbps, I'd be especially interested to hear what sort of performance you observe. In my tests, I typically see about 9.5MB/sec on transmit, which seems a bit weak. The Winbond does a bit better than this (10MB/sec). Remember folks: I'm waiting for feedback from _you_ so that I can judge when a driver is stable enough to merge into the repository. The more information you give me, the faster I can add these drivers to the system. Actually, I'm also interested in performance stats for real DEC tulip chips with the de driver. I'm wondering how real DEC chips do at 100Mbps modes. Next on the hit parade: the VIA Rhine! -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 11:12:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20614 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 11:12:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20609 for ; Mon, 2 Nov 1998 11:12:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00716; Mon, 2 Nov 1998 11:11:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811021911.LAA00716@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Mon, 02 Nov 1998 18:51:14 GMT." <199811021851.LAA01338@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Nov 1998 11:11:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I like strings *out*. > > > > > > I believe the "last time" to which you refer is the mount fstype > > > argument, in which I thought it was stupid to limit yourself to > > > defined FS's in mount.h. > > > > So you want more binary clutter and interface dependency just to > > translate FSNAME to FSNUMBER? > > Given a choice between user space bloat and kernel bloat, I choose > user space bloat. And given the opportunity to trade large user-space bloat and management headaches for miniscule kernel bloat? > > > So installing a new FS type installs commands in /sbin, and hving > > > installed commands in /sbin, the list is known via a traversal of > > > sbin, without even asking the kernel. > > > > Er. And who do you ask to do the traversal of /sbin? > > In the limit, /sbin/fstyp. And what does it use? You're overloading the filesystem namespace to perform a translation from FSNAME to FSNUMBER, using an inefficient interface with no guarantee that the translation space is representative of the state of the kernel. > This is not an ideal soloution, but consider that the VFS KLD(s) > for a given filesystem may not be in the kernel. Of course I've considered that. By passing in an arbitrary key string for the VFS type, you have a direct translation to a module filename, which you can demand load in a transparent fashion, rather than requiring an error return, user-space module load and recall. > For a given mount attempt without an FS type specified, the > following occurs: > > > o user types "mount /dev/sd3a /mnt" > > o mount calls "fstyp /dev/sd3a" > > o fstyp calls each "/sbin/*_fstyp" until one exits non-zero > > o mount calls "/sbin/_mount" > > o /sbin/_mount calls "mount(2)" > > o If the VFS is not present in the kernel, its KLD is > demand-loaded > > o The FS is mounted. Fine. None of this has anything to do with passing the key over the user:kernel boundary, which you do in the mount phase in order to reliably locate the module responsible for the VFS. > > > > > I think it is a mistake for FreeBSD to turn into Plan9. > > > > > > > > I think it's a mistake for us to make any technical decisions on > > > > emotional or us'n'them grounds. > > > > > > I'm not saying that. I'm saying that there is a recent tendency > > > to bloat in the direction of Plan9-style interfaces. > > > > ... and you're attaching an implicit value judgement to that "tendency". > > Actually, I was quite explicit: > > I think it is a mistake for FreeBSD to turn into Plan9. > > And with the "I think" in there, it's obviously an opinion. But it's > an opinion based on experience, not emotion. It's an implicit opinion, offered with no justification other than an other implicit "you should trust me (because I'm a loud dog)". > > You're the one agonising over passing data across the user/kernel > > boundary. > > Yes, I am. Every time I have to recompile libkvm and ps, w, finger, > netstat, etc., etc., I agonize over the externalization of kernel > internal data as defacto interfaces. You're facing the wrong way. Using self-describing and robust interface formats reduces the need for this. At the moment, the biggest problems faced by the above tools is that they depend on manifest constants and implicit structure definitions. None of this will be helped by your stance. > > My primary agenda for string parsing is to free us from the > > chore of versioning binary interfaces (primarily with the boot code) in > > favour of using extensible string-based constructs. You'll note I've > > also been using self-describing binary structures in situations where > > they're appropriate. > > They are apropriate anywhere their data is externalized directly > instead of procedurally (an FS is a good place to convert data > references into procedural references, if you need that sort of > thing, hence procfs). Yes; I'm actually teaching myself about the VFS model by writing what I've grandly called metafs, which aims to be a framework into which various non-file-objects can register themselves in order to appear as a filesystem. The major design flaws with both procfs and kernfs are that they are essentially static. The original goal was to produce an emulation of the linux procfs, however it became clear that I needed to understand the VFS framework and provide infrastructure for the many pieces of junk they aggregate there. > > > One could easily claim that the use of strings in sysctl is bogus, > > > and that the parsing should be to MIB identifiers, and take place > > > in user space to keep the kernel lean. > > > > This might have been fine when the MIB was a static object produced at > > compile time. As an approach for name translation in a dynamic tree > > it's simply not workable. > > So basically, you are denying the reality of IBM's SNMPv2 implementation, > which allows dynamic (de/)registration of manageable hierarchies of > exposed data? > > I have to say, having used the reference implementation 4 years ago > on Solaris, I don't think that it has quit working in the interim... There is no information here. I can't read your mind. The issues: - Only the MIB manager knows the contents of the MIB. - Objects are added to the MIB via the MIB manager. - Only the object provider knows what the object is. - Objects may be renumbered at effectively arbitrary times. - We don't have a predefined list of all the possible objects. Tell me how you plan to export the mapping between MIB numbers and names from the MIB manager. Tell me how this is not a name-to-number lookup interface. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 11:26:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21930 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 11:26:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from kahlo.gda.itesm.mx (kahlo.gda.itesm.mx [132.254.51.220]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21913 for ; Mon, 2 Nov 1998 11:26:17 -0800 (PST) (envelope-from alexv@sui.gda.itesm.mx) Received: from sui.gda.itesm.mx (gdl2-107.telmex.net.mx [148.233.176.107]) by kahlo.gda.itesm.mx (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id NAA22462 for ; Mon, 2 Nov 1998 13:27:19 -0600 Message-ID: <363E0747.FEA14658@sui.gda.itesm.mx> Date: Mon, 02 Nov 1998 13:26:00 -0600 From: "Alejandro Vázquez C." Organization: SUI - ITESM Campus Guadalajara X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: VGA 90-columns text mode... Content-Type: multipart/mixed; boundary="------------E452EE5FE1B86F4C51B8C0BB" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------E452EE5FE1B86F4C51B8C0BB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Everyone: I don't know where to send this, but I'm sure you are interested. This weekend I found a utility to setup a 90-column text mode. Using a "vga-register" grabber I took the CRT values and I was playing arround with them. After writing a small dos program to setup diferent cominations of Columns/Rows in text mode, I decided to extend the "sc0" driver in FreeBSD to support those modes. I've attached the corresponding "diffs" so you can test it out. They are for the 2.2.7-RELEASE and I don't know if they could work for any other version. The modified files are "/usr/src/sys/i386/isa/syscons.c", "/usr/src/sys/i386/include/console.h" (this file is the same at /usr/include/machine/console.h so you must update both files), and "/usr/src/usr.sbin/vidcontrol/vidcontrol.c". The new modes added are "VGA_90x25", "VGA_90x30", "VGA_90x43", "VGA_90x50", "VGA_90x60", and can be selected from vidcontrol. The extention setups the VGA to display a 720pixels wide screen with a 8pixels wide font (so 720/8=90). This is possible for each height the VGA supports (350, 400, 480 lines). Those modes should work on most VGA cards (even those "plain VGA"). I've tested these modes (succesfully) with a Trident ProVidia 9685 (PCI) and a "plain VGA" Cirrus Logic GD5320 (ISA). The author of the program I found on the net stated that those modes where undocumented by IBM but worked in the original IBM VGA. However I haven't done any other kind of test to the code, so use it at your own risk. Some applications seems to be sticked to 80-columns so they do not use the extra columns ("ee" is the most significant case). "bash" seems to read a "COLUMNS" environment variable at startup. "lynx" looks great at 90x30 (the text is easier to read on some pages) without any extra effort. I haven't tested any other application. Mail me for comment.... -alexv --------------E452EE5FE1B86F4C51B8C0BB Content-Type: text/plain; charset=us-ascii; name="syscons.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="syscons.c.diff" *** /sys/i386/isa/syscons.c.orig Tue Jul 7 00:23:22 1998 --- /sys/i386/isa/syscons.c Mon Nov 2 01:17:58 1998 *************** *** 294,299 **** --- 294,300 ---- #ifdef SC_SPLASH_SCREEN static void toggle_splash_screen(scr_stat *scp); #endif + static void setup_mode90(char *mp); /* alexv */ struct isa_driver scdriver = { scprobe, scattach, "sc", 1 *************** *** 1500,1505 **** --- 1501,1512 ---- case SW_ENH_B80x43: case SW_ENH_C80x43: case SW_EGAMONO80x25: + case SW_VGA_C90x25: case SW_VGA_M90x25: /* alexv */ + case SW_VGA_C90x30: case SW_VGA_M90x30: + case SW_VGA_C90x43: case SW_VGA_M90x43: + case SW_VGA_C90x50: case SW_VGA_M90x50: + case SW_VGA_C90x60: case SW_VGA_M90x60: + if (!crtc_vga) return ENODEV; mp = get_mode_param(scp, cmd & 0xff); *************** *** 1520,1525 **** --- 1527,1580 ---- else i = 0; switch (cmd & 0xff) { + + case M_VGA_C90x25: case M_VGA_M90x25: /* alexv */ + scp->status |= UNKNOWN_MODE; + scp->xsize = 90; + scp->ysize = 25; + scp->font_size = mp[2]; + break; + + case M_VGA_C90x30: case M_VGA_M90x30: /* alexv */ + scp->status |= UNKNOWN_MODE; + scp->xsize = 90; + scp->ysize = 30; + scp->font_size = mp[2]; + break; + + case M_VGA_C90x43: case M_VGA_M90x43: /* alexv */ + if (!(fonts_loaded & FONT_8)) { + splx(s); + return EINVAL; + } + scp->status |= UNKNOWN_MODE; + scp->xsize = 90; + scp->ysize = 43; + scp->font_size = 8; + break; + + case M_VGA_C90x50: case M_VGA_M90x50: /* alexv */ + if (!(fonts_loaded & FONT_8)) { + splx(s); + return EINVAL; + } + scp->status |= UNKNOWN_MODE; + scp->xsize = 90; + scp->ysize = 50; + scp->font_size = 8; + break; + + case M_VGA_C90x60: case M_VGA_M90x60: /* alexv */ + if (!(fonts_loaded & FONT_8)) { + splx(s); + return EINVAL; + } + scp->status |= UNKNOWN_MODE; + scp->xsize = 90; + scp->ysize = 60; + scp->font_size = 8; + break; + case M_VGA_C80x60: case M_VGA_M80x60: if (!(fonts_loaded & FONT_8)) { splx(s); *************** *** 3371,3376 **** --- 3426,3441 ---- { M_VGA_C80x50, M_VGA_C80x25 }, { M_VGA_M80x60, M_VGA_M80x25 }, { M_VGA_C80x60, M_VGA_C80x25 }, + { M_VGA_C90x25, M_VGA_C80x25 }, /* alexv { */ + { M_VGA_M90x25, M_VGA_M80x25 }, + { M_VGA_C90x30, M_VGA_C80x25 }, + { M_VGA_M90x30, M_VGA_M80x25 }, + { M_VGA_C90x43, M_ENH_C80x25 }, + { M_VGA_M90x43, M_ENH_C80x25 }, + { M_VGA_C90x50, M_VGA_C80x25 }, + { M_VGA_M90x50, M_VGA_M80x25 }, + { M_VGA_C90x60, M_VGA_C80x25 }, + { M_VGA_M90x60, M_VGA_M80x25 }, /* } alexv */ { M_VGA_MODEX, M_VGA_CG320 }, }; int i; *************** *** 4171,4176 **** --- 4236,4252 ---- } void + setup_mode90(char *modetable) /* alexv */ + { + modetable[5] |= 0x1; + modetable[9] = (modetable[9] & 0xf3) | 0x4; + modetable[10] = 0x6a; modetable[11] = 0x59; + modetable[12] = 0x5a; modetable[13] = 0x8d; + modetable[14] = 0x63; modetable[15] = 0x88; + modetable[29] = 0x2d; modetable[54] = 0x0; + } + + void set_mode(scr_stat *scp) { char special_modetable[MODE_PARAM_SIZE]; *************** *** 4193,4203 **** --- 4269,4283 ---- /* setup video hardware for the given mode */ switch (scp->mode) { + case M_VGA_C90x60: case M_VGA_M90x60: /* alexv */ + setup_mode90(special_modetable); case M_VGA_C80x60: case M_VGA_M80x60: special_modetable[2] = 0x08; special_modetable[19] = 0x47; goto special_480l; + case M_VGA_C90x30: case M_VGA_M90x30: /* alexv */ + setup_mode90(special_modetable); case M_VGA_C80x30: case M_VGA_M80x30: special_modetable[19] = 0x4f; special_480l: *************** *** 4210,4225 **** --- 4290,4311 ---- special_modetable[32] = 0x04; goto setup_mode; + case M_VGA_C90x43: case M_VGA_M90x43: + setup_mode90(special_modetable); case M_ENH_C80x43: case M_ENH_B80x43: special_modetable[28] = 87; goto special_80x50; + case M_VGA_C90x50: case M_VGA_M90x50: /* alexv */ + setup_mode90(special_modetable); case M_VGA_C80x50: case M_VGA_M80x50: special_80x50: special_modetable[2] = 8; special_modetable[19] = 7; goto setup_mode; + case M_VGA_C90x25: case M_VGA_M90x25: /* alexv */ + setup_mode90(special_modetable); case M_VGA_C40x25: case M_VGA_C80x25: case M_VGA_M80x25: case M_B40x25: case M_C40x25: --------------E452EE5FE1B86F4C51B8C0BB Content-Type: text/plain; charset=us-ascii; name="console.h.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="console.h.diff" *** /sys/i386/include/console.h.orig Fri Jan 30 04:47:24 1998 --- /sys/i386/include/console.h Mon Nov 2 01:16:34 1998 *************** *** 351,356 **** --- 351,367 ---- #define M_VGA_CG640 36 /* vga 640x400 256 color */ #define M_VGA_MODEX 37 /* vga 320x240 256 color */ + #define M_VGA_M90x25 40 /* alexv check for conflicts { */ + #define M_VGA_C90x25 41 + #define M_VGA_M90x30 42 + #define M_VGA_C90x30 43 + #define M_VGA_M90x43 44 + #define M_VGA_C90x43 45 + #define M_VGA_M90x50 46 + #define M_VGA_C90x50 47 + #define M_VGA_M90x60 48 + #define M_VGA_C90x60 49 /* } alexv */ + #define M_ENH_B80x43 0x70 /* ega black & white 80x43 */ #define M_ENH_C80x43 0x71 /* ega color 80x43 */ *************** *** 393,398 **** --- 404,421 ---- #define SW_VGA_M80x30 _IO('S', M_VGA_M80x30) #define SW_VGA_M80x50 _IO('S', M_VGA_M80x50) #define SW_VGA_M80x60 _IO('S', M_VGA_M80x60) + + #define SW_VGA_M90x25 _IO('S', M_VGA_M90x25) /* alexv { */ + #define SW_VGA_C90x25 _IO('S', M_VGA_C90x25) + #define SW_VGA_M90x30 _IO('S', M_VGA_M90x30) + #define SW_VGA_C90x30 _IO('S', M_VGA_C90x30) + #define SW_VGA_M90x43 _IO('S', M_VGA_M90x43) + #define SW_VGA_C90x43 _IO('S', M_VGA_C90x43) + #define SW_VGA_M90x50 _IO('S', M_VGA_M90x50) + #define SW_VGA_C90x50 _IO('S', M_VGA_C90x50) + #define SW_VGA_M90x60 _IO('S', M_VGA_M90x60) + #define SW_VGA_C90x60 _IO('S', M_VGA_C90x60) /* } alexv */ + #define SW_VGA11 _IO('S', M_VGA11) #define SW_BG640x480 _IO('S', M_VGA11) #define SW_VGA12 _IO('S', M_VGA12) --------------E452EE5FE1B86F4C51B8C0BB Content-Type: text/plain; charset=us-ascii; name="vidcontrol.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="vidcontrol.c.diff" *** /usr/src/usr.sbin/vidcontrol/vidcontrol.c.orig Sat Jul 18 06:37:54 1998 --- /usr/src/usr.sbin/vidcontrol/vidcontrol.c Mon Nov 2 01:28:34 1998 *************** *** 277,282 **** --- 277,292 ---- mode = SW_ENH_C80x25; else if (!strcmp(argv[*index], "EGA_80x43")) mode = SW_ENH_C80x43; + else if (!strcmp(argv[*index], "VGA_90x25")) /* alex { */ + mode = SW_VGA_C90x25; + else if (!strcmp(argv[*index], "VGA_90x30")) + mode = SW_VGA_C90x30; + else if (!strcmp(argv[*index], "VGA_90x43")) + mode = SW_VGA_C90x43; + else if (!strcmp(argv[*index], "VGA_90x50")) + mode = SW_VGA_C90x50; + else if (!strcmp(argv[*index], "VGA_90x60")) + mode = SW_VGA_C90x60; /* } alexv */ else return; if (ioctl(0, mode, NULL) < 0) --------------E452EE5FE1B86F4C51B8C0BB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 11:37:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22878 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 11:37:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22870 for ; Mon, 2 Nov 1998 11:37:45 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA29498; Mon, 2 Nov 1998 12:37:38 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd029398; Mon Nov 2 12:37:26 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA02997; Mon, 2 Nov 1998 12:37:25 -0700 (MST) From: Terry Lambert Message-Id: <199811021937.MAA02997@usr05.primenet.com> Subject: Re: sync writes with softupdates enabled To: peter.jeremy@auss2.alcatel.com.au (Peter Jeremy) Date: Mon, 2 Nov 1998 19:37:25 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <98Nov2.163001est.40354@border.alcanet.com.au> from "Peter Jeremy" at Nov 2, 98 04:30:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Now that this has been committed, can we have some feedback from people > >using mmap heavily on -current? > > There are no longer any sync writes as a result of using an MMAP'd > history file in inn. There is no obvious corruption of history file > or associated .pag file. > > Note that there is a similar bug in 2.2.x. The fix is similar, but > needs some thought since there appears to be a problem with the > parameters to vm_object_page_clean(). In particular, `syncio' is > defined as boolean_t, as passed as the `waitfor' argument to > VOP_FSYNC() - which is MNT_ASYNC or MNT_SYNC elsewhere. I haven't > had the time to work out the correct definitions. I have a problem with this. Has msync(2) been updated to "do the right thing" with regard to uncommitted data in an mmapped region? If so, how? I was pretty sure that it was impossible to identify the mapping object backing ranges -- or so the comments in the msync code imply. I don't think you can arbitrarily change these to async references; specifically, I think there is a problem with dirty page write through. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 11:55:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24801 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 11:55:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24796 for ; Mon, 2 Nov 1998 11:55:01 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id MAA15823; Mon, 2 Nov 1998 12:54:54 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd015782; Mon Nov 2 12:54:53 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA03757; Mon, 2 Nov 1998 12:54:52 -0700 (MST) From: Terry Lambert Message-Id: <199811021954.MAA03757@usr05.primenet.com> Subject: Re: Ariel Faigon: The Holloween Document (fwd) To: imp@village.org (Warner Losh) Date: Mon, 2 Nov 1998 19:54:52 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: advocacy@FreeBSD.ORG In-Reply-To: <199811020606.XAA00655@harmony.village.org> from "Warner Losh" at Nov 1, 98 11:06:57 pm Followup-To: advocacy@freebsd.org X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I got this on a linux list that I'm on and thought I'd forward it to > this group. It seems relevant. It will likely make you mad. [ ... ] > http://www.tuxedo.org/~esr/halloween.html It seems to me a bit too conveniently supportive of ESR's commentary and the whole "Microsoft Pheeeeeeerz Linux" mentality. There are also some gross historical errors with regard to BSD, in particular the organization of the family tree, what constitutes a factionalization, and the total disregard of the existance of Bill Jolitz. In short, it looks like it was written by someone with a rosy view of Linux, a less rosy view of BSD, a paranoid fixation on Microsoft, an agenda about what they felt "needs fixing" (phrased as an observation of "weakness"), and a near total lack of understanding of market dynamics and game theory. In short, not someone that Microsoft would ever pay to analyze what the document purports to analyze. As a memetic virus attempt, it's nearly perfect in that no matter how Microsoft does or doesn't respond, it will create a lot of Press fervor in the vein "Microsoft Pheeeeeeerz Linux in memo". I think it's likely to have what I believe is its intended effect: more press coverage for Linux in the mainstream media. All in all, we should commision Brett Glass to write one for FreeBSD. Followups to FreeBSD-advocacy. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 12:20:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28438 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 12:20:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28427 for ; Mon, 2 Nov 1998 12:20:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01148; Mon, 2 Nov 1998 12:19:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811022019.MAA01148@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Martti Kuparinen cc: hackers@FreeBSD.ORG Subject: Re: Pseudo-device as a LKM In-reply-to: Your message of "Mon, 02 Nov 1998 12:44:53 +0200." <3.0.6.32.19981102124453.02ce8b30@openmail.lmf.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Nov 1998 12:19:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I want to implement a pseudo-device as LKM. But the question is where > to find a working example? I've looked at e.g. the if_tun device, > but the unload is not successful: > > # modload /lkm/if_tun_mod.o > # modunload -n if_tun_mod > modunload: LMUNLOAD: Device busy > > So please give any pointers. I'm using 2.2.7-R but I could jump into 3.0 > if that's what needed. If you plan to have your device live for any length of time, 3.0 is the way to go. Look in /sys/modules for examples. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 12:23:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28821 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 12:23:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28809 for ; Mon, 2 Nov 1998 12:23:01 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id VAA29097; Mon, 2 Nov 1998 21:28:17 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 2 Nov 1998 21:28:16 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: ADRIAN Filipi-Martin cc: Jordan Hayes , hackers@FreeBSD.ORG Subject: Re: Stand-alone diskless system ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Nov 1998, ADRIAN Filipi-Martin wrote: > On Sun, 1 Nov 1998, Jordan Hayes wrote: > > I'm looking for any experiences that people here have had with truely > > diskless machines: not booting over the network, but from say flash [snip] > It works really well. A week ago I helped some undergrads run an > ACM programming contest. Since we weren't allowed to convert a dozen of [snip] > Check out the FreeBSD web pages. There is a little in the > handbook, a little more in the tutorials section and I even found a page > on NetBSD's site illuminating. It should be enough to figure it out. You should read www.freebsd.org pages more carefully :-) For more info follow the URL in my sig. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 13:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05079 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 13:10:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from calvin.saturn-tech.com ([207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05056 for ; Mon, 2 Nov 1998 13:10:16 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id OAA27440; Mon, 2 Nov 1998 14:07:47 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Mon, 2 Nov 1998 14:07:47 -0700 (MST) From: Doug Russell To: Konstantin Chuguev cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make installworld over NFS In-Reply-To: <363C3FBE.A693DB54@urc.ac.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 1 Nov 1998, Konstantin Chuguev wrote: > Doug Russell wrote: > > > > I do it the other way around all the time. NFS mount /usr/obj and > > /usr/src from the build server on the minibox to be updated, then do a > > make installworld on the minibox. > I see. I did the same earlier. Certainly, it worked great. > The trick is not to export the build server's filesystems to other > hosts at all. Suppose they are less secure then the buildserver. If you don't need to do it often (and you probably don't :) ), you could always just add the lines to exports and kill -hup mountd when you are ready to use it, then remove them again afterwards. If you need it even more secure than using a seperate filesystem completely for the "network" copies of /usr/src and /usr/obj, you could always use a seperate box to hold the exportable systems. Something's got to be readable and writable. :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 13:37:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09723 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 13:37:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09715 for ; Mon, 2 Nov 1998 13:37:43 -0800 (PST) (envelope-from chuckr@mat.net) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id NAA10603 for ; Mon, 2 Nov 1998 13:37:40 -0800 (PST) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id QAA01968; Mon, 2 Nov 1998 16:36:35 -0500 (EST) Date: Mon, 2 Nov 1998 16:36:34 -0500 (EST) From: Chuck Robey To: Parag Gandhi cc: "'freebsd-hackers@freefall.cdrom.com'" Subject: Re: tell me what it is all about ? In-Reply-To: <4974E68113C7D1118F5D0000F878AB68080341@XFMEXC1.xfm.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, Parag Gandhi wrote: Go to http://www.freebsd.org/ and do some reading, it's all there. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 13:41:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10109 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 13:41:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10102 for ; Mon, 2 Nov 1998 13:41:11 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id QAA16740; Mon, 2 Nov 1998 16:43:58 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 2 Nov 1998 16:43:58 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > bcopy doesn't support overlapping ranges on all systems. > > eg. IRIX 6.2 man page: > > NOTE > The use of overlapping buffers with bcopy is not guaranteed to work. Use > the memmove(3C) function if the buffers might overlap. > > Since BSD was the first "implementation" of b{copy|zero} stuff i think our implementation is correct no? Considering IRIX didn't have snprintf in thier c library in their 1997 release says something doesn't it? :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 14:53:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21206 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 14:53:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21198 for ; Mon, 2 Nov 1998 14:53:30 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA11601; Tue, 3 Nov 1998 09:23:09 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA20710; Tue, 3 Nov 1998 09:22:49 +1030 (CST) Message-ID: <19981103092249.W354@freebie.lemis.com> Date: Tue, 3 Nov 1998 09:22:49 +1030 From: Greg Lehey To: Martti Kuparinen , hackers@FreeBSD.ORG Subject: Re: Pseudo-device as a LKM References: <3.0.6.32.19981102124453.02ce8b30@openmail.lmf.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <3.0.6.32.19981102124453.02ce8b30@openmail.lmf.ericsson.se>; from Martti Kuparinen on Mon, Nov 02, 1998 at 12:44:53PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 2 November 1998 at 12:44:53 +0200, Martti Kuparinen wrote: > I want to implement a pseudo-device as LKM. But the question is where > to find a working example? I've looked at e.g. the if_tun device, > but the unload is not successful: > > # modload /lkm/if_tun_mod.o > # modunload -n if_tun_mod > modunload: LMUNLOAD: Device busy > > So please give any pointers. I'm using 2.2.7-R but I could jump into 3.0 > if that's what needed. Well, first, LKMs are going away. The replacement is called KLD (Kernel Loadable Module). Secondly, the question of unloading a module is a matter of implementation. I don't think you should automatically consider it an error if an LKM can't be unloaded. In general, this is a decision made in the unload code. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 15:13:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23648 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 15:13:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23641 for ; Mon, 2 Nov 1998 15:13:15 -0800 (PST) (envelope-from pantzer@speedy.ludd.luth.se) Received: from speedy.ludd.luth.se (speedy.ludd.luth.se [130.240.16.164]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id AAA27182; Tue, 3 Nov 1998 00:13:07 +0100 Message-Id: <199811022313.AAA27182@zed.ludd.luth.se> X-Mailer: exmh version 2.0.1 12/23/97 To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd In-Reply-To: Message from dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) of "02 Nov 1998 19:40:16 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 03 Nov 1998 00:13:07 +0100 From: Mattias Pantzare Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA23642 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > He's probably talking about ttcp, not T/TCP. As in: > > > > NAME > > ttcp - test TCP and UDP performance > > [...] > > It's extremely useful. > > It's also extremely ugly. It has about a dozen printf format errors, a > handful of unprototyped functions, a smattering of pointer errors and > a valueless return from a non-void function. OTOH, I guess that's not > too bad considering it's age. > > Since it's in the public domain, there's nothing to stop us from > cleaning it up and sticking it into the tree. Do a search for nttcp-1.3 on ftpsearch.ntnu.no and you will find a more modern version. >From the README: This is README of nttcp-1.3: This program is a much more convient version of the ttcp program. It uses inetd (or simulates its behaviour) to start off the remote side program which will send/receive data. Both sides measure the time and number of bytes transfered. The local side will print the measures. The format of the output can be specified on the commandline. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 15:41:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26620 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 15:41:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26609 for ; Mon, 2 Nov 1998 15:41:34 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA190889977; Mon, 2 Nov 1998 18:39:37 -0500 Date: Mon, 2 Nov 1998 18:39:37 -0500 (EST) From: Bill Fumerola To: Mattias Pantzare Cc: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd In-Reply-To: <199811022313.AAA27182@zed.ludd.luth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, Mattias Pantzare wrote: > > Since it's in the public domain, there's nothing to stop us from > > cleaning it up and sticking it into the tree. Per the recent discussion of this program and it's inclusion in the ports tree I have submitted a port for [net/benchmark]/nttcp, enjoy. ports/8546 is the gnats PR number. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 16:17:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04197 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 16:17:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04168 for ; Mon, 2 Nov 1998 16:17:31 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id TAA17203; Mon, 2 Nov 1998 19:17:16 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Mon, 2 Nov 1998 19:17:16 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Andrzej Bialecki cc: Jordan Hayes , hackers@FreeBSD.ORG Subject: Re: Stand-alone diskless system ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, Andrzej Bialecki wrote: > On Sun, 1 Nov 1998, ADRIAN Filipi-Martin wrote: > > > On Sun, 1 Nov 1998, Jordan Hayes wrote: > > > > I'm looking for any experiences that people here have had with truely > > > diskless machines: not booting over the network, but from say flash > [snip] > > It works really well. A week ago I helped some undergrads run an > > ACM programming contest. Since we weren't allowed to convert a dozen of > [snip] > > Check out the FreeBSD web pages. There is a little in the > > handbook, a little more in the tutorials section and I even found a page > > on NetBSD's site illuminating. It should be enough to figure it out. > > You should read www.freebsd.org pages more carefully :-) For more info > follow the URL in my sig. > > Andrzej Bialecki No offense, but I found the documentation a bit weak. I even installed 3.0 to see if it was easier to configure. It was easier for me to deal with the devil I knew than one I didn't. PicoBSD is pretty neat stuff and I have showm some people the pre-canned versions, but making my own custom one was trickier thant I wanted to deal with at the time. I know it's a new package and growing, so I look forward to future versions. cheers, Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 16:26:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05655 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 16:26:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05647 for ; Mon, 2 Nov 1998 16:26:01 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id TAA12582; Mon, 2 Nov 1998 19:25:31 -0500 (EST) Received: from john.baldwinfamily.org (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id TAA13406; Mon, 2 Nov 1998 19:25:29 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <363E0747.FEA14658@sui.gda.itesm.mx> Date: Mon, 02 Nov 1998 19:25:29 -0500 (EST) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: "Alejandro=?us-ascii?Q?_V=E1zquez?= C." Subject: RE: VGA 90-columns text mode... Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 02-Nov-98 Alejandro Vázquez C. wrote: > Everyone: > > I don't know where to send this, but I'm sure you are > interested. This weekend I found a utility to setup a > 90-column text mode. Using a "vga-register" grabber I took the > CRT values and I was playing arround with them. After writing > a small dos program to setup diferent cominations of > Columns/Rows in text mode, I decided to extend the "sc0" > driver in FreeBSD to support those modes. Check out PR i386/7510. It has an URL for a webpage with patches for /usr/src/usr.sbin/vidcontrol/vidcontrol.c, /usr/src/usr.sbin/vidcontrol/vidcontrol.1, /usr/src/sys/i386/include/console.h, and /usr/src/sys/i386/isa/syscons.c. It was submitted August 6, 1998 and has been waiting for a committer. - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc A feature is a bug with seniority. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNj5Nb4jYza302vYpAQE2IAMAkgEI45F8CXV/t4QpvTTYAfan5++VrJIq Hm+w9w7CakAu6gKy4u50d/NivSbrhxZLJyIKCIJIOAsviN4ChPU4J3rrVdTfq3RK H/5eUGOBwDmjMd/CiL5YjkgRXsRAVQe9 =KHeI -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 16:31:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06590 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 16:31:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from WEBBSD1.turnaround.com.au (webbsd1.turnaround.com.au [203.39.138.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06564 for ; Mon, 2 Nov 1998 16:31:40 -0800 (PST) (envelope-from J_Shevland@TurnAround.com.au) Received: from TurnAround.com.au (dhcp110.turnaround.com.au [192.168.1.110] (may be forged)) by WEBBSD1.turnaround.com.au (8.8.7/8.8.7) with ESMTP id LAA21783 for ; Tue, 3 Nov 1998 11:33:44 +1100 (EST) (envelope-from J_Shevland@TurnAround.com.au) Message-ID: <363E4ED3.24A1D345@TurnAround.com.au> Date: Tue, 03 Nov 1998 11:31:15 +1100 From: Joe Shevland Organization: TurnAround Solutions Pty. Ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Useful Site Links Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, (Should I direct this at -questions?) Just wondering if people could send me pointers to sites with useful information about programming (directly?) related to FreeBSD and other developer's links, or links to links, ad nauseum :). I'm submitting this to the cdrom.com Resources section; anything else of use would certainly be a bonus... Cheers, Joe. -- ---------------------|============================= Joe Shevland | TurnAround Solutions Senior Consultant | Hobart, Australia No unsolicited email | Voice (03) 6224 9146 | http://www.TurnAround.com.au ---------------------|============================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 16:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08460 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 16:48:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08447 for ; Mon, 2 Nov 1998 16:48:50 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id NAA16399; Tue, 3 Nov 1998 13:48:31 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id NAA17704; Tue, 3 Nov 1998 13:48:31 +1300 (NZDT) Message-ID: <19981103134830.B11452@clear.co.nz> Date: Tue, 3 Nov 1998 13:48:30 +1300 From: Joe Abley To: freebsd-hackers@FreeBSD.ORG Cc: jabley@clear.co.nz Subject: Re: FreeBSD for Strongarm? References: <199810190636.AAA20131@harmony.village.org> <199810200922.EAA02322@quark.ChrisBowman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810200922.EAA02322@quark.ChrisBowman.com>; from Christopher R. Bowman on Tue, May 19, 1998 at 04:20:47AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is almost entirely off-topic... but not quite :) Re: announcement copied below - a StrongARM RedHat distribution would give some more background reading for FreeBSD porting, with the usual BSD/GPL caveats. There is also a cool idea brewing in the UK to mount 6 or 8 233MHz StrongARM CPUs on a single dual-bus PCI card, each processor with its own RAM and flash for booting: http://www.chaltech.com/ http://www.pobox.com/~kragen/sa-beowulf Now _that_ would be a compact platform for clustering - a nasty old P90 motherboard to act as an NFS server and router, and 32 x 233MHz StrongARM processors running IP over the PCI bus. All in a single mini-tower chassis. Mmmmmm. That does smell good :) --- October 27, 1998--Corel Computer and Red Hat Software, Inc. today announced an agreement to bring the Red Hat(r) distribution of Linux to the Corel Computer NetWinder(tm)family of thin-clients and thin-servers. Under the three-year agreement, Red Hat will port Red Hat Linux 5.1 and future releases of the software to the StrongARM(r) processor, the underlying architecture of the NetWinder. ``We are pleased to be able to offer our NetWinder customers the benefits of the award-winning Linux distribution from Red Hat,'' said Ron McNab, vice president and general manager of Corel Computer. ``The partnership will allow us to concentrate on our core business>building one of the most powerful and easy-to-use thin-clients and thin-servers on the market.'' The agreement provides Corel Computer with the right to use the Red Hat distribution of Linux including the Red Hat name and logo on the NetWinder products. Additionally, Corel Computer has the rights to distribute Red Hat CD ROMs and printed documentation manuals to customers. ``I am pleased to announce that Red Hat Linux will soon be available on the exciting new NetWinder platform,'' said Robert Young, president of Red Hat Software. ``The partnership between Corel Computer and Red Hat adds to the growing momentum of Linux.'' Currently the NetWinder family is running a custom Linux distribution based on Red Hat 4.2. When available, NetWinder customers will be able to upgrade their systems by either downloading the operating system from Corel Computer or Red Hat, or by purchasing a CD ROM and manual from either vendor. -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 17:08:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11390 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 17:08:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11381 for ; Mon, 2 Nov 1998 17:08:02 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id UAA07042; Mon, 2 Nov 1998 20:10:40 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 2 Nov 1998 20:10:40 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Joe Shevland cc: hackers@FreeBSD.ORG Subject: Re: Useful Site Links In-Reply-To: <363E4ED3.24A1D345@TurnAround.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG get cvsup (it's in the ports) download the freebsd source tree. look at it. :) There is also the book: "Design and Implementation of the 4.4BSD Operating System" it's bit out of date (well very) but still considered by most to be the holy BSD grail. Any book by Richard Stevens is also recommened. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 3 Nov 1998, Joe Shevland wrote: > Hi all, > > (Should I direct this at -questions?) > > Just wondering if people could send me pointers to sites with useful > information about programming (directly?) related to FreeBSD and other > developer's links, or links to links, ad nauseum :). I'm submitting this > to the cdrom.com Resources section; anything else of use would certainly > be a bonus... > > Cheers, > Joe. > > -- > ---------------------|============================= > Joe Shevland | TurnAround Solutions > Senior Consultant | Hobart, Australia > No unsolicited email | Voice (03) 6224 9146 > | http://www.TurnAround.com.au > ---------------------|============================= > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 17:17:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12483 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 17:17:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from WEBBSD1.turnaround.com.au (webbsd1.turnaround.com.au [203.39.138.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12478 for ; Mon, 2 Nov 1998 17:17:50 -0800 (PST) (envelope-from J_Shevland@TurnAround.com.au) Received: from TurnAround.com.au (dhcp110.turnaround.com.au [192.168.1.110] (may be forged)) by WEBBSD1.turnaround.com.au (8.8.7/8.8.7) with ESMTP id MAA22108; Tue, 3 Nov 1998 12:19:48 +1100 (EST) (envelope-from J_Shevland@TurnAround.com.au) Message-ID: <363E599F.EC823A7B@TurnAround.com.au> Date: Tue, 03 Nov 1998 12:17:19 +1100 From: Joe Shevland Organization: TurnAround Solutions Pty. Ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein CC: hackers@FreeBSD.ORG Subject: Re: Useful Site Links References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cheers, but I don't want that kind of info per se :) I'm more after a wad of URLs that can be placed on a web page for others to use a central starting point for information relating to coding under FreeBSD, development projects etc... Actually, now I think about it, the topic of a central point for development projects etc was raised a while back on -hackers. Perhaps this can be tied in somehow (what happened to that?)... Alfred Perlstein wrote: > > get cvsup (it's in the ports) download the freebsd source tree. > > look at it. :) > > There is also the book: > "Design and Implementation of the 4.4BSD Operating System" > it's bit out of date (well very) but still considered by most to be the > holy BSD grail. > > Any book by Richard Stevens is also recommened. > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > On Tue, 3 Nov 1998, Joe Shevland wrote: > > > Hi all, > > > > (Should I direct this at -questions?) > > > > Just wondering if people could send me pointers to sites with useful > > information about programming (directly?) related to FreeBSD and other > > developer's links, or links to links, ad nauseum :). I'm submitting this > > to the cdrom.com Resources section; anything else of use would certainly > > be a bonus... > > > > Cheers, > > Joe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 17:37:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14896 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 17:37:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14868 for ; Mon, 2 Nov 1998 17:37:39 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id BAA09068; Tue, 3 Nov 1998 01:20:39 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id BAA05399; Tue, 3 Nov 1998 01:21:15 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811030121.BAA05399@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Gunnar Olsson , freebsd-hackers@FreeBSD.ORG Subject: Re: MPPP, multilink PPP In-reply-to: Your message of "Mon, 02 Nov 1998 17:23:48 +0100." <19981102172348.46633@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Nov 1998 01:21:14 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Nov 02, 1998 at 02:14:03PM +0100, Gunnar Olsson wrote: > > Hi there, > > my name is Gunnar Olsson, working for Ericsson Research in Sweden. > > We are looking on delay requirements for IP packets over PPP. > > I want to segment long data packets on PPP level, to minimize > > the "waiting time" for a real time packet. I was planning to use > > the segmentation algorithm in Multilink PPP, MPPP. > > For performance issue I am doing everything in kernel. > > So, the question is, have someone implemented MPPP in kernel???? > > There is no multilink implementation for the FreeBSD kernel, no. > > What you _could_ do is work with Brian to segregate the user-interface > and the protocol handling in the userland PPP, making it possible to > compile the protocol handling itself into the kernel. This could be > very useful, as it provide a good development-environment (userland), > while making it possible to exploit the performance boost of having > the code in the kernel. I'd be quite surprised if James Carlson (who I believe is the main pppd engineer) hasn't at least got an MP implementation of pppd underway. > Eivind. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 17:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15013 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 17:38:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15004 for ; Mon, 2 Nov 1998 17:38:23 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id BAA09073; Tue, 3 Nov 1998 01:23:04 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id BAA05424; Tue, 3 Nov 1998 01:23:40 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811030123.BAA05424@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Mon, 02 Nov 1998 16:43:58 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Nov 1998 01:23:39 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > bcopy doesn't support overlapping ranges on all systems. > > > > eg. IRIX 6.2 man page: > > > > NOTE > > The use of overlapping buffers with bcopy is not guaranteed to work. Use > > the memmove(3C) function if the buffers might overlap. > > > > > > Since BSD was the first "implementation" of b{copy|zero} stuff i > think our implementation is correct no? I'd agree. Their implementation is probably no more than a #define of memcpy ! [.....] > -Alfred -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 17:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17792 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 17:57:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17781 for ; Mon, 2 Nov 1998 17:57:14 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:mycqlgrlaXw7DEOW616XzYM92GAsqxeP@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id KAA32032; Tue, 3 Nov 1998 10:56:58 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA00792; Tue, 3 Nov 1998 10:58:22 +0900 (JST) Message-Id: <199811030158.KAA00792@zodiac.mech.utsunomiya-u.ac.jp> To: Christopher Masto cc: hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Some curiosity about syscons In-reply-to: Your message of "Sun, 01 Nov 1998 12:36:10 EST." <19981101123610.A7850@netmonger.net> References: <19981026230208.A8159@netmonger.net> <199811011131.UAA15844@zodiac.mech.utsunomiya-u.ac.jp> <19981101123610.A7850@netmonger.net> Date: Tue, 03 Nov 1998 10:58:21 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Doesn't the screen saver only get run periodically? Hmm.. > >Anyway, I have something which works a lot more reliably than my >original call-scrn_update()-excessively hack. Of course, this is >about four hacks in one. [...] I have one suggestion for your scheme. After setting up the 80x30 text mode, call ioctl(0, KDSETMODE, KD_GRAPHICS); This will tell syscons that the program wants to take full control of video hardware and syscons will not touch video hardware or update screen for this vty. Note that this ioctl command will not actually put your video card in one of graphics modes, nor change the state of video card in any way. It is a simple declaration by the user-land program that the program wants full control of the video card. This ioctl is originally meant for graphics programs (i.e. X server) which need to manipulate video hardware directly. The important thing is that syscons will stay away from the video hardware once this ioctl is called. So, your program can do whatever it wants to the video card. Before quitting the program, call ioctl(0, KDSETMODE, KD_TEXT); then, switch back to the 80x25 text mode (or whatever). Kazu >#define WAIT_RETRACE { while (inb(0x3DA) & 0x08); \ > while (!(inb(0x3DA) & 0x08)); } > >u_short *vmem; >unsigned char font[16*256], oldfont[16*256]; > >[...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 18:34:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22682 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 18:34:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22401 for ; Mon, 2 Nov 1998 18:33:03 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id VAA18013 for ; Mon, 2 Nov 1998 21:35:37 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Mon, 2 Nov 1998 21:35:37 -0500 (EST) From: "Larry S. Lile" To: hackers@FreeBSD.ORG Subject: "panic: free: multiple frees" VM bug? (long) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am working on a token ring driver and I cannot seem to find out why this is happening. I contigmalloc buffers for tranmsitting frames and then free them later when they have been transmitted. I have to use contigmalloc in order to get buffers below the 16M mark for dma. Anyone see what is wrong? Should I not do this? Or have I stumbled over a vm bug? It looks like a vm bug to me, but I have been wrong before. All pertinent information below... Larry Lile lile@stdio.com Please ignore the soft-updates panic, I understand that happens sometimes during a dump. panicstr: page fault panic messages: --- panic: free: multiple frees syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01cdf08 stack pointer = 0x10:0xf024bf14 frame pointer = 0x10:0xf024bf18 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:268 #1 0xf014932f in panic (fmt=0xf0242de9 "page fault") at ../../kern/kern_shutdown.c:430 #2 0xf01f796d in trap_fatal (frame=0xf024bed8) at ../../i386/i386/trap.c:879 #3 0xf01f7648 in trap_pfault (frame=0xf024bed8, usermode=0) at ../../i386/i386/trap.c:772 #4 0xf01f72a7 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -252868608, tf_ebp = -266027240, tf_isp = -266027264, tf_ebx = -265970844, tf_edx = -1073217472, tf_ecx = 0, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -266543352, tf_cs = 8, tf_eflags = 66182, tf_esp = -252868608, tf_ss = -266027208}) at ../../i386/i386/trap.c:396 #5 0xf01cdf08 in acquire_lock (lk=0xf0259b64) at ../../ufs/ffs/ffs_softdep.c:268 #6 0xf01d1929 in softdep_update_inodeblock (ip=0xf0ed8800, bp=0xf368ac30, waitfor=0) at ../../ufs/ffs/ffs_softdep.c:3482 #7 0xf01ccf1c in ffs_update (vp=0xf5ddc0c0, access=0xf024bfd0, modify=0xf024bfd0, waitfor=0) at ../../ufs/ffs/ffs_inode.c:109 #8 0xf01d5f59 in ffs_fsync (ap=0xf024c00c) at ../../ufs/ffs/ffs_vnops.c:252 #9 0xf01d4383 in ffs_sync (mp=0xf0e40a00, waitfor=2, cred=0xf0dd3700, p=0xf028a04c) at vnode_if.h:499 #10 0xf016b2a7 in sync (p=0xf028a04c, uap=0x0) at ../../kern/vfs_syscalls.c:527 #11 0xf0148faa in boot (howto=256) at ../../kern/kern_shutdown.c:201 #12 0xf014932f in panic (fmt=0xf023723e "free: multiple frees") at ../../kern/kern_shutdown.c:430 #13 0xf0146553 in free (addr=0xf5e62000, type=0xf0251980) at ../../kern/kern_malloc.c:334 #14 0xf01febe3 in DriverTransmitFrameCompleted (DriverHandle=0x0, FrameHandle=0xa, TransmitStatus=0) at ../../i386/isa/if_oltr.c:936 #15 0xf022b252 in ReturnCompletedBuffers () #16 0x30001 in ?? () cannot read proc at 0 (kgdb) up 14 #14 0xf01febe3 in DriverTransmitFrameCompleted (DriverHandle=0x0, FrameHandle=0xa, TransmitStatus=0) at ../../i386/isa/if_oltr.c:936 936 free(sc->tx_buffer[frame].frame->TransmitFragment[i].VirtualAddress, M_DEVBUF); (kgdb) list 931 printf("oltr%d: Unused buffer returned *boggle*\n", sc->unit); 932 } else { 933 for (i = 0; i < sc->tx_buffer[frame].frame->FragmentCount; i++) { 934 printf("oltr%d: freeing fragment %d frame %d\n", sc->unit, i, frame); 935 sc->tx_frags--; 936 free(sc->tx_buffer[frame].frame->TransmitFragment[i].VirtualAddress, M_DEVBUF); 937 } 938 } 939 940 printf("Oltr%d: %d total frags in use.\n", sc->unit, sc->tx_frags); (kgdb) I know that I have not called free on the same buffer twice by looking at the debug messages. Nov 2 21:11:43 anarchy /kernel: oltr0: output frame 0 - 1 fragments (1 fragments in use total) Nov 2 21:11:43 anarchy /kernel: iso88025_input: Packet queued. Nov 2 21:11:43 anarchy /kernel: oltr0: transmit complete frame 0 - 1 fragments (1 total fragments in use total) Nov 2 21:11:43 anarchy /kernel: oltr0: freeing fragment 0 frame 0 Nov 2 21:11:43 anarchy /kernel: Oltr0: 0 total frags in use. Nov 2 21:11:56 anarchy /kernel: oltr0: output frame 1 - 1 fragments (1 fragments in use total) Nov 2 21:11:56 anarchy /kernel: iso88025_input: Packet queued. Nov 2 21:11:56 anarchy /kernel: oltr0: transmit complete frame 1 - 1 fragments (1 total fragments in use total) Nov 2 21:11:56 anarchy /kernel: oltr0: freeing fragment 0 frame 1 Nov 2 21:11:56 anarchy /kernel: Oltr0: 0 total frags in use. Nov 2 21:11:56 anarchy /kernel: iso88025_input: Packet queued. Nov 2 21:11:56 anarchy /kernel: oltr0: output frame 2 - 2 fragments (2 fragments in use total) Nov 2 21:11:56 anarchy /kernel: oltr0: transmit complete frame 2 - 2 fragments (2 total fragments in use total) Nov 2 21:11:56 anarchy /kernel: oltr0: freeing fragment 0 frame 2 Nov 2 21:11:56 anarchy /kernel: oltr0: freeing fragment 1 frame 2 Nov 2 21:11:57 anarchy /kernel: Oltr0: 0 total frags in use. Nov 2 21:11:57 anarchy /kernel: iso88025_input: Packet queued. Nov 2 21:11:57 anarchy /kernel: oltr0: output frame 3 - 1 fragments (1 fragments in use total) Nov 2 21:11:57 anarchy /kernel: oltr0: transmit complete frame 3 - 1 fragments (1 total fragments in use total) Nov 2 21:11:57 anarchy /kernel: oltr0: freeing fragment 0 frame 3 Nov 2 21:11:57 anarchy /kernel: Oltr0: 0 total frags in use. Nov 2 21:11:59 anarchy /kernel: oltr0: output frame 4 - 2 fragments (2 fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: transmit complete frame 4 - 2 fragments (2 total fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 0 frame 4 Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 1 frame 4 Nov 2 21:11:59 anarchy /kernel: Oltr0: 0 total frags in use. Nov 2 21:11:59 anarchy /kernel: iso88025_input: Packet queued. Nov 2 21:11:59 anarchy /kernel: oltr0: output frame 5 - 2 fragments (2 fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: transmit complete frame 5 - 2 fragments (2 total fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 0 frame 5 Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 1 frame 5 Nov 2 21:11:59 anarchy /kernel: Oltr0: 0 total frags in use. Nov 2 21:11:59 anarchy /kernel: oltr0: output frame 6 - 2 fragments (2 fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: transmit complete frame 6 - 2 fragments (2 total fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 0 frame 6 Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 1 frame 6 Nov 2 21:11:59 anarchy /kernel: Oltr0: 0 total frags in use. Nov 2 21:11:59 anarchy /kernel: iso88025_input: Packet queued. Nov 2 21:11:59 anarchy /kernel: oltr0: output frame 7 - 2 fragments (2 fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: transmit complete frame 7 - 2 fragments (2 total fragments in use total) Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 0 frame 7 Nov 2 21:11:59 anarchy /kernel: oltr0: freeing fragment 1 frame 7 Nov 2 21:11:59 anarchy /kernel: Oltr0: 0 total frags in use. How the buffers get allocated: void * oltr_malloc(Size, Adapter) ssize_t Size; TRlldAdapterConfig_t *Adapter; { /* If the adapter needs memory below 16M for DMA then use contigmalloc */ if (Adapter->mode & TRLLD_MODE_16M) /* Adapter using ISA DMA buffer below 16M */ return(contigmalloc(Size, M_DEVBUF, M_NOWAIT, 0ul, 0xfffffful, 1ul, 0x10000ul)); else return(malloc(Size, M_DEVBUF, M_NOWAIT)); } Where the frames get built: static void oltr_start(ifp) struct ifnet *ifp; { struct oltr_softc *sc = &oltr_softc[ifp->if_unit]; struct mbuf *m0, *m; struct iso88025_header *th; int len, i, j, k, rc, s; /*printf("oltr%d: oltr_start\n", sc->unit);*/ s = splimp(); /* Check to see if we have enough room to transmit */ if (sc->tx_avail <= 0) { /* No free buffers, hold off the upper layers */ /*printf("oltr%d: transmit queue full.\n", sc->unit);*/ ifp->if_flags |= IFF_OACTIVE; splx(s); return; } IF_DEQUEUE(&ifp->if_snd, m); if (m == 0) { printf("oltr%d: oltr_start NULL packet dequeued.\n", sc->unit); ifp->if_flags &= ~IFF_OACTIVE; splx(s); return; } th = mtod(m, struct iso88025_header *); th->ac = 0x10; th->fc = 0x40; /* Keep a pointer to the head of the packet */ m0 = m; i = (sc->tx_next & TX_LIST_MASK); /* Just to shorten thing up */ if (sc->tx_buffer[i].inuse) { printf("oltr%d: Transmit ring buffer blown!\n", sc->unit); oltr_stop(sc); splx(s); return; } for (len = 0, j = 0; m != 0; m = m->m_next, j++) { sc->tx_frags++; sc->tx_buffer[i].frame->TransmitFragment[j].VirtualAddress = (char *)oltr_malloc(m->m_len, sc->config); if (!sc->tx_buffer[i].frame->TransmitFragment[j].VirtualAddress) { printf("oltr%d: unable to allocate memory.\n", sc->unit); /* Free up the other fragments */ for (k = 0; k < j; k++) { sc->tx_frags--; free(sc->tx_buffer[i].frame->TransmitFragment[k].VirtualAddress, M_DEVBUF); } goto bad; } sc->tx_buffer[i].frame->TransmitFragment[j].PhysicalAddress = kvtop(sc->tx_buffer[i].frame->TransmitFragment[j].VirtualAd dress); sc->tx_buffer[i].frame->TransmitFragment[j].count = m->m_len; bcopy(mtod(m, caddr_t), sc->tx_buffer[i].frame->TransmitFragment[j].VirtualAddress, m->m_len); len += m->m_len; } sc->tx_buffer[i].frame->FragmentCount = j; sc->tx_buffer[i].inuse = 1; rc = TRlldTransmitFrame(sc->TRlldAdapter, (TRlldTransmit_t *)sc->tx_buffer[i].frame, (void *)sc->tx_buffer[i].index); if (rc != TRLLD_TRANSMIT_OK) { printf("oltr%d: TRlldTransmitFrame returned (%x)\n", sc->unit, rc); ifp->if_oerrors++; for (j = 0; j < sc->tx_buffer[i].frame->FragmentCount; j++) { sc->tx_frags--; free(sc->tx_buffer[i].frame->TransmitFragment[j].VirtualAddress, M_DEVBUF); } sc->tx_buffer[i].inuse = 0; goto bad; } printf("oltr%d: output frame %d - %d fragments (%d fragments in use total)\n", sc->unit, i, sc->tx_buffer[i].frame->FragmentC ount, sc->tx_frags); sc->tx_next++; sc->tx_avail--; #if NBPFILTER > 0 if (ifp->if_bpf) bpf_mtap(ifp, m0); #endif bad: m_freem(m); splx(s); return; } Where they get freed; static void DriverCloseCompleted(DriverHandle) void *DriverHandle; { struct oltr_softc *sc = &oltr_softc[(int)DriverHandle]; /*printf("oltr%d: DriverCloseCompleted\n", sc->unit);*/ untimeout(oltr_timeout, (void *)sc->unit, sc->oltr_ch); wakeup_one((void *)sc->unit); if ((sc->hw_state != HW_CLOSING) && (sc->hw_state != HW_CLOSING2) && (sc->hw_state != HW_CLOSED)) { printf("oltr%d: adapter close complete called in wrong state (%d)\n", sc->unit, sc->hw_state); return; } sc->hw_state = HW_CLOSING2; if (sc->config->dmalevel != TRLLD_DMA_PIO) isa_dma_release(sc->config->dmalevel); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 19:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26298 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 19:01:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26290 for ; Mon, 2 Nov 1998 19:01:25 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:isIhNCTKZm2g1tmphW13tSUe1hD66kFj@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA32263; Tue, 3 Nov 1998 12:01:12 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA01789; Tue, 3 Nov 1998 12:02:37 +0900 (JST) Message-Id: <199811030302.MAA01789@zodiac.mech.utsunomiya-u.ac.jp> To: Mikael Karpberg cc: hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: kld screensavers In-reply-to: Your message of "Sun, 01 Nov 1998 14:13:36 +0100." <199811011313.OAA21309@ocean.campus.luth.se> References: <199811011313.OAA21309@ocean.campus.luth.se> Date: Tue, 03 Nov 1998 12:02:37 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >According to Doug Rabson: >> Thats more or less what I was suggesting. Simple screen savers wouldn't >> even need an event handler. Maybe something like: >[suggestion removed] > >While this is being discussed, I'd like to bring something up that I've >wanted for a long time, and brought up before. Why not make to so that >each screensaver register itself with a timeout, a priority and a flag >that says if it's fallthrough or not? That way you can have multiple >screensavers installed, and they get called as approriate. > >I haven't looked at the current code, I'm affraid, so go easy on me. >Example: > >Three screensavers: (say default prio is 5) > >lock: prio 1, 10 minutes, fallthrough (Demands password to release screen >) >green: prio 4, 20 minutes (Turn screen off) >stars: prio 5, 5 minutes (Twinkle, twinkle, little star) [...] I am not sure if we want to have this kind of screen saver stack. It will complicate things a lot: multiple saver module management, priority management, flag checking... Is this worth the effort? If you want to lock the vty with password, you can always use `lock(1)'. And it is easy to modify screen savers, `start' or whatever, and add them the ability to turn off the display after set period (the screen saver can check system time when it is called periodically); it will be far easier than implementing the screen saver stack thingy. Just my two cents. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 19:47:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01401 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 19:47:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01395 for ; Mon, 2 Nov 1998 19:47:45 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA09485; Mon, 2 Nov 1998 19:49:04 -0800 (PST) Message-Id: <199811030349.TAA09485@implode.root.com> To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: "panic: free: multiple frees" VM bug? (long) In-reply-to: Your message of "Mon, 02 Nov 1998 21:35:37 EST." From: David Greenman Reply-To: dg@root.com Date: Mon, 02 Nov 1998 19:49:04 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I am working on a token ring driver and I cannot seem to find >out why this is happening. I contigmalloc buffers for tranmsitting >frames and then free them later when they have been transmitted. >I have to use contigmalloc in order to get buffers below the >16M mark for dma. > >Anyone see what is wrong? Should I not do this? Or have I >stumbled over a vm bug? > >It looks like a vm bug to me, but I have been wrong before. contigmalloc() isn't just a special version of malloc() that allocates contiguous pages. It's actually a special allocator that has nothing to do with malloc() and it is thus entirely incorrect to call free() with a pointer to something that was allocated by contigmalloc(). The proper way to free stuff that was allocated with contigmalloc() is with kmem_free(). contigmalloc() is poorly named and should never have been brought into the kernel that way. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 20:04:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03480 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 20:04:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03475 for ; Mon, 2 Nov 1998 20:04:06 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA12945; Tue, 3 Nov 1998 14:33:42 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id OAA21958; Tue, 3 Nov 1998 14:33:42 +1030 (CST) Message-ID: <19981103143341.X354@freebie.lemis.com> Date: Tue, 3 Nov 1998 14:33:41 +1030 From: Greg Lehey To: Marc Slemko , Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? References: <199811012142.OAA27464@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Marc Slemko on Mon, Nov 02, 1998 at 09:42:35AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 2 November 1998 at 9:42:35 -0800, Marc Slemko wrote: > On Sun, 1 Nov 1998, Terry Lambert wrote: > >>> #define memcpy(d,s,n) bcopy(s,d,n) >>> >>> not exactly rocket science :-) >> >> Actually, bcopy is closer to memmove, since it supports overlapping >> ranges as its arguments. > > bcopy doesn't support overlapping ranges on all systems. > > eg. IRIX 6.2 man page: > > NOTE > The use of overlapping buffers with bcopy is not guaranteed to work. Use > the memmove(3C) function if the buffers might overlap. The bcopy that allows no overlap is not the true bcopy. Must be a System Vism. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 20:36:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08170 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 20:36:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08107 for ; Mon, 2 Nov 1998 20:35:53 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id XAA21414; Mon, 2 Nov 1998 23:38:48 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Mon, 2 Nov 1998 23:38:48 -0500 (EST) From: "Larry S. Lile" To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: "panic: free: multiple frees" VM bug? (long) In-Reply-To: <199811030349.TAA09485@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, David Greenman wrote: > >I am working on a token ring driver and I cannot seem to find > >out why this is happening. I contigmalloc buffers for tranmsitting > >frames and then free them later when they have been transmitted. > >I have to use contigmalloc in order to get buffers below the > >16M mark for dma. > > > >Anyone see what is wrong? Should I not do this? Or have I > >stumbled over a vm bug? > > > >It looks like a vm bug to me, but I have been wrong before. > > contigmalloc() isn't just a special version of malloc() that allocates > contiguous pages. It's actually a special allocator that has nothing to > do with malloc() and it is thus entirely incorrect to call free() with > a pointer to something that was allocated by contigmalloc(). The proper > way to free stuff that was allocated with contigmalloc() is with kmem_free(). > contigmalloc() is poorly named and should never have been brought into > the kernel that way. >From vm_extern.h void kmem_free __P((vm_map_t, vm_offset_t, vm_size_t)); What would my parameters be? More specifically vm_map? Just an example, I know I will have to write a oltr_free to do free/kmem_free based on how the memory was allocated. Thanks Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 20:47:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09501 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 20:47:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09495 for ; Mon, 2 Nov 1998 20:47:04 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id UAA10050; Mon, 2 Nov 1998 20:48:22 -0800 (PST) Message-Id: <199811030448.UAA10050@implode.root.com> To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: "panic: free: multiple frees" VM bug? (long) In-reply-to: Your message of "Mon, 02 Nov 1998 23:38:48 EST." From: David Greenman Reply-To: dg@root.com Date: Mon, 02 Nov 1998 20:48:22 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> contigmalloc() isn't just a special version of malloc() that allocates >> contiguous pages. It's actually a special allocator that has nothing to >> do with malloc() and it is thus entirely incorrect to call free() with >> a pointer to something that was allocated by contigmalloc(). The proper >> way to free stuff that was allocated with contigmalloc() is with kmem_free(). >> contigmalloc() is poorly named and should never have been brought into >> the kernel that way. > >>From vm_extern.h >void kmem_free __P((vm_map_t, vm_offset_t, vm_size_t)); > >What would my parameters be? More specifically vm_map? Just an >example, I know I will have to write a oltr_free to do free/kmem_free >based on how the memory was allocated. contigmalloc() allocates from the kernel_map, so that is what you need to specify to kmem_free(). The offset is just the address that contigmalloc() returned. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 21:06:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12250 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 21:06:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12243 for ; Mon, 2 Nov 1998 21:06:31 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA10465; Mon, 2 Nov 1998 20:57:06 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdz10462; Tue Nov 3 04:57:01 1998 Date: Mon, 2 Nov 1998 20:56:38 -0800 (PST) From: Julian Elischer To: David Greenman cc: "Larry S. Lile" , hackers@FreeBSD.ORG Subject: Re: "panic: free: multiple frees" VM bug? (long) In-Reply-To: <199811030349.TAA09485@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I also doubt if you really want to free them either.. possibly keep a pool of them and recycle them in your own free list. On Mon, 2 Nov 1998, David Greenman wrote: > >I am working on a token ring driver and I cannot seem to find > >out why this is happening. I contigmalloc buffers for tranmsitting > >frames and then free them later when they have been transmitted. > >I have to use contigmalloc in order to get buffers below the > >16M mark for dma. > > > >Anyone see what is wrong? Should I not do this? Or have I > >stumbled over a vm bug? > > > >It looks like a vm bug to me, but I have been wrong before. > > contigmalloc() isn't just a special version of malloc() that allocates > contiguous pages. It's actually a special allocator that has nothing to > do with malloc() and it is thus entirely incorrect to call free() with > a pointer to something that was allocated by contigmalloc(). The proper > way to free stuff that was allocated with contigmalloc() is with kmem_free(). > contigmalloc() is poorly named and should never have been brought into > the kernel that way. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 2 22:56:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27139 for freebsd-hackers-outgoing; Mon, 2 Nov 1998 22:56:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA27134 for ; Mon, 2 Nov 1998 22:56:54 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zaaOO-0002r5-00; Mon, 2 Nov 1998 23:56:40 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id XAA19656; Mon, 2 Nov 1998 23:56:26 -0700 (MST) Message-Id: <199811030656.XAA19656@harmony.village.org> To: Marc Slemko Subject: Re: scanf in the kernel? Cc: Terry Lambert , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Nov 1998 09:42:35 PST." References: Date: Mon, 02 Nov 1998 23:56:26 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Marc Slemko writes: : bcopy doesn't support overlapping ranges on all systems. That's what ovbcopy is for :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 01:41:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15707 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 01:41:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from manchester.genrad.com (x153.genrad.co.uk [195.99.3.153]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15702 for ; Tue, 3 Nov 1998 01:41:02 -0800 (PST) (envelope-from swindellsr@genrad.co.uk) Date: Tue, 3 Nov 1998 01:41:02 -0800 (PST) Message-Id: <199811030941.BAA15702@hub.freebsd.org> Received: from CDP275.uk.genrad.com by manchester.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id VTWQB60N; Tue, 3 Nov 1998 09:40:53 -0000 From: Robert Swindells To: jabley@clear.co.nz CC: freebsd-hackers@FreeBSD.ORG In-reply-to: <19981103134830.B11452@clear.co.nz> (message from Joe Abley on Tue, 3 Nov 1998 13:48:30 +1300) Subject: Re: FreeBSD for Strongarm? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Re: announcement copied below - a StrongARM RedHat distribution would >give some more background reading for FreeBSD porting, with the usual >BSD/GPL caveats. Corel Computer already have Linux on their NetWinder, my reading of the announcement is just that they are making it look the same as RH 5.1. >There is also a cool idea brewing in the UK to mount 6 or 8 233MHz >StrongARM CPUs on a single dual-bus PCI card, each processor with its >own RAM and flash for booting: > > http://www.chaltech.com/ > http://www.pobox.com/~kragen/sa-beowulf > >Now _that_ would be a compact platform for clustering - a nasty old >P90 motherboard to act as an NFS server and router, and 32 x 233MHz >StrongARM processors running IP over the PCI bus. All in a single >mini-tower chassis. Mmmmmm. That does smell good :) Chaltech currently do a single processor ATX motherboard which seems to be one of the cheapest ways to get a development system. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 01:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16354 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 01:48:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16348 for ; Tue, 3 Nov 1998 01:48:08 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id KAA06552; Tue, 3 Nov 1998 10:53:36 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 3 Nov 1998 10:53:35 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: ADRIAN Filipi-Martin cc: Jordan Hayes , hackers@FreeBSD.ORG Subject: Re: Stand-alone diskless system ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, ADRIAN Filipi-Martin wrote: > > You should read www.freebsd.org pages more carefully :-) For more info > > follow the URL in my sig. > > > > Andrzej Bialecki > > No offense, but I found the documentation a bit weak. I even Well, you're right - the documentation needs massive upgrade. The existing one was intended for people who already know quite a bit about FreeBSD. But guess what... It's easier for me to code than to write stories... > PicoBSD is pretty neat stuff and I have showm some people the > pre-canned versions, but making my own custom one was trickier thant I > wanted to deal with at the time. Yes, that's very unfortunate - we're working on making it a lot easier... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 03:34:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24591 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 03:34:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gambit.Msk.SU (gambit.msk.su [194.190.206.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24586 for ; Tue, 3 Nov 1998 03:34:34 -0800 (PST) (envelope-from laskavy@Gambit.Msk.SU) Received: (from laskavy@localhost) by Gambit.Msk.SU (8.0/8.9.1) id OAA11756; Tue, 3 Nov 1998 14:34:13 +0300 (MSK) To: dag-erli@ifi.uio.no (Dag-Erling C. Smørgrav ) Cc: sthaug@nethelp.no, nate@mt.sri.com, dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd References: <199810302033.NAA24629@mt.sri.com> <2701.909779780@verdi.nethelp.no> From: Sergei Laskavy Date: 03 Nov 1998 14:34:13 +0300 In-Reply-To: dag-erli@ifi.uio.no's message of 02 Nov 1998 19:40:16 +0100 Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dag-erli@ifi.uio.no (Dag-Erling C. Smørgrav ) writes: > sthaug@nethelp.no writes: > > He's probably talking about ttcp, not T/TCP. As in: > > NAME > > ttcp - test TCP and UDP performance > > [...] > > It's extremely useful. > It's also extremely ugly. It has about a dozen printf format errors, a > handful of unprototyped functions, a smattering of pointer errors and > a valueless return from a non-void function. OTOH, I guess that's not > too bad considering it's age. > Since it's in the public domain, there's nothing to stop us from > cleaning it up and sticking it into the tree. Why we can't just put it in ports and clean it via ttcp/patches ? -- FreeBSD Project: http://FreeBSD.org/docproj/ Vim: http://www.vim.org/ $_='$6C86:P$^P|2D<2GJPl=2D<2GJp82>3:E^>D<^DFn';tr#P-~\x20-O#\x20-~#;print To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 03:57:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26234 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 03:57:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26229 for ; Tue, 3 Nov 1998 03:57:51 -0800 (PST) (envelope-from Etienne.Debruin@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id MAA20403 for ; Tue, 3 Nov 1998 12:58:42 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa20401; Tue Nov 03 12:58:42 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id MAA10808 for ; Tue, 3 Nov 1998 12:57:01 +0100 Original: Received: (from debruin@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id MAA00990 for freebsd-hackers@freebsd.org; Tue, 3 Nov 1998 12:59:39 +0100 (CET) (envelope-from debruin) From: Etienne de Bruin Message-Id: <199811031159.MAA00990@borg.kryptokom.de> Subject: chaining interrupt handler To: freebsd-hackers@FreeBSD.ORG (Hackers FreeBSD) Date: Tue, 3 Nov 1998 12:59:39 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the saga continuous ... for my PCI device driver, i have installed my interrupt handler using pci_map_int(). my questions is, how does one chain one's interupt handler together with all the other exisiting interupt handler routines? i.e. void fc_pci_intr() { if certain flags set { handle interupt } else { chain interrupt } } any help will do eT -- Etienne de Bruin, KryptoKom(R), Germany, http://www.kryptokom.de/ eT@kryptokom.de or edebruin@iname.com +49 241 963 2635(w) "www.novia.net/~todd/" - Rapture Ready (***** eT), commentary on the events taking place in the world today and how it fits in with Bible Prophecy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 04:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29447 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 04:11:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29428; Tue, 3 Nov 1998 04:11:00 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id SAA02403; Tue, 3 Nov 1998 18:15:39 +0600 (NS) Date: Tue, 3 Nov 1998 18:15:39 +0600 (NS) From: Ustimenko Semen To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Another NTFS RO driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Here is another new Windows NT filesystem (NTFS) driver. It is read-only, and of couse aim to become read-write... If you have any info on NTFS structure and especially on it's $LogFile... i love to have a look at it. Please. source: http://www.iclub.nsu.ru/~semen/ntfs/ntfs-0.1beta.tgz Thank you. P.S. Drop me a message if you tryed this one or have already used another. Please. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 04:19:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00383 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 04:19:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00378 for ; Tue, 3 Nov 1998 04:19:52 -0800 (PST) (envelope-from Etienne.Debruin@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id NAA20579 for ; Tue, 3 Nov 1998 13:20:45 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa20575; Tue Nov 03 13:20:36 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id NAA10956 for ; Tue, 3 Nov 1998 13:18:56 +0100 Original: Received: (from debruin@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id NAA01081 for freebsd-hackers@freebsd.org; Tue, 3 Nov 1998 13:21:34 +0100 (CET) (envelope-from debruin) From: Etienne de Bruin Message-Id: <199811031221.NAA01081@borg.kryptokom.de> Subject: using splxxx() in drivers To: freebsd-hackers@FreeBSD.ORG (Hackers FreeBSD) Date: Tue, 3 Nov 1998 13:21:34 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i am confused as to when to use splxxx() in drivers and what the use of these functions are. my guess is that it is like some sort of semaphore function? anyone please take time to give a short explaination? thanks eT -- Etienne de Bruin, KryptoKom(R), Germany, http://www.kryptokom.de/ eT@kryptokom.de or edebruin@iname.com +49 241 963 2635(w) "www.harpazo.net/news.html" - Harpazo's Headlines (**** eT), news stories relevant to the Last Days, update daily. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 04:20:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00486 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 04:20:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00187; Tue, 3 Nov 1998 04:19:37 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id SAA02517; Tue, 3 Nov 1998 18:24:37 +0600 (NS) Date: Tue, 3 Nov 1998 18:24:37 +0600 (NS) From: Ustimenko Semen To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: SMC9432TX driver (tx) users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! If you use tx driver under FreeBSD, can you send me private message if you have ANY problems useing it. Even if the problem is only tx0: timeout %d packets, ... Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 04:24:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00739 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 04:24:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from qatar.net.qa (qatar.net.qa [194.133.33.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00734 for ; Tue, 3 Nov 1998 04:24:18 -0800 (PST) (envelope-from sodah@qatar.net.qa) Received: from qatar.net.qa (pons@ddfn.qatar.net.qa [194.133.35.153]) by qatar.net.qa (8.8.8/Internet-Qatar) with ESMTP id PAA08863 for ; Tue, 3 Nov 1998 15:24:12 +0300 (GMT) Message-ID: <363EE7DF.4149A4B0@qatar.net.qa> Date: Tue, 03 Nov 1998 14:24:19 +0300 From: Fadi Sodah X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: BRKILL Content-Type: multipart/alternative; boundary="------------D5627DDAFAE7DD57FB46101B" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------D5627DDAFAE7DD57FB46101B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit hi when i try to compile brkill.c (u can find it at http://deep.ee.siue.edu/br/) i get the following pons@lifebook:/home/pons/Code > cc -O2 -o brkill brkill.c -lpcap brkill.c: In function `init_pkt': brkill.c:186: structure has no member named `ip_sum' brkill.c: In function `main': brkill.c:457: structure has no member named `ip_sum' brkill.c:458: structure has no member named `ip_sum' what could be wrong? -- Fadi Sodah sodah@qatar.net.qa Tel: +974-712447 Doha-Qatar --------------D5627DDAFAE7DD57FB46101B Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit hi

when i try to compile  brkill.c (u can find it at http://deep.ee.siue.edu/br/)
i get the following
pons@lifebook:/home/pons/Code > cc -O2 -o brkill brkill.c -lpcap
brkill.c: In function `init_pkt':
brkill.c:186: structure has no member named `ip_sum'
brkill.c: In function `main':
brkill.c:457: structure has no member named `ip_sum'
brkill.c:458: structure has no member named `ip_sum'

what could be wrong? 

-- 
Fadi Sodah
sodah@qatar.net.qa
Tel: +974-712447
Doha-Qatar
  --------------D5627DDAFAE7DD57FB46101B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 04:28:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00901 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 04:28:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00896 for ; Tue, 3 Nov 1998 04:28:03 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id OAA20750; Tue, 3 Nov 1998 14:26:47 +0200 (SAT) From: John Hay Message-Id: <199811031226.OAA20750@zibbi.mikom.csir.co.za> Subject: Re: using splxxx() in drivers In-Reply-To: <199811031221.NAA01081@borg.kryptokom.de> from Etienne de Bruin at "Nov 3, 98 01:21:34 pm" To: Etienne.Debruin@KryptoKom.DE (Etienne de Bruin) Date: Tue, 3 Nov 1998 14:26:47 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i am confused as to when to use splxxx() in drivers and what the use > of these functions are. my guess is that it is like some sort of > semaphore function? anyone please take time to give a short explaination? > man spl ? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 04:31:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01266 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 04:31:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01249 for ; Tue, 3 Nov 1998 04:31:11 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id OAA20788; Tue, 3 Nov 1998 14:28:57 +0200 (SAT) From: John Hay Message-Id: <199811031228.OAA20788@zibbi.mikom.csir.co.za> Subject: Re: chaining interrupt handler In-Reply-To: <199811031159.MAA00990@borg.kryptokom.de> from Etienne de Bruin at "Nov 3, 98 12:59:39 pm" To: Etienne.Debruin@KryptoKom.DE (Etienne de Bruin) Date: Tue, 3 Nov 1998 14:28:57 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > my questions is, how does one chain one's interupt handler together > with all the other exisiting interupt handler routines? > > i.e. > > void fc_pci_intr() > { > if certain flags set { > handle interupt > } > else { > chain interrupt > } > } You shouldn't need the else part. The generic pci handler should do that for you. That way you don't even have to know which device is sharing the interrupt with you. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 05:05:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04557 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 05:05:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04552 for ; Tue, 3 Nov 1998 05:05:47 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id OAA03505; Tue, 3 Nov 1998 14:05:19 +0100 (MET) Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Tue, 3 Nov 1998 14:05:19 +0100 (MET) Mime-Version: 1.0 To: Sergei Laskavy Cc: sthaug@nethelp.no, nate@mt.sri.com, dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd References: <199810302033.NAA24629@mt.sri.com> <2701.909779780@verdi.nethelp.no> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 03 Nov 1998 14:05:18 +0100 In-Reply-To: Sergei Laskavy's message of "03 Nov 1998 14:34:13 +0300" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA04553 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergei Laskavy writes: > dag-erli@ifi.uio.no (Dag-Erling C. Smørgrav ) writes: > > Since it's in the public domain, there's nothing to stop us from > > cleaning it up and sticking it into the tree. > Why we can't just put it in ports and clean it via ttcp/patches ? Because the patches can easily get larger than the source code. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 05:22:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06692 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 05:22:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06687 for ; Tue, 3 Nov 1998 05:22:26 -0800 (PST) (envelope-from Etienne.Debruin@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id OAA21637; Tue, 3 Nov 1998 14:21:18 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa21627; Tue Nov 03 14:20:58 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id OAA11376; Tue, 3 Nov 1998 14:19:18 +0100 Received: (from debruin@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id OAA01476; Tue, 3 Nov 1998 14:21:57 +0100 (CET) (envelope-from debruin) From: Etienne de Bruin Message-Id: <199811031321.OAA01476@borg.kryptokom.de> Subject: Re: chaining interrupt handler In-Reply-To: <199811031228.OAA20788@zibbi.mikom.csir.co.za> from John Hay at "Nov 3, 1998 2:28:57 pm" To: jhay@mikom.csir.co.za (John Hay) Date: Tue, 3 Nov 1998 14:21:57 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG (Hackers FreeBSD) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > void fc_pci_intr() > > { > > if certain flags set { > > handle interupt > > } > > else { > > chain interrupt > > } > > } > > You shouldn't need the else part. The generic pci handler should do that > for you. That way you don't even have to know which device is sharing > the interrupt with you. the reason i ask because the following happens: on a system with one pci network card and my pci device, my device driver's interrupt handler gets called without anyproblems when i issue an interrupt. but on a system with two pci network cards, it seems like my interrupt handler never gets called when i issue my interrupt... any idea as to why this happens? eT -- Etienne de Bruin, KryptoKom(R), Germany, http://www.kryptokom.de/ eT@kryptokom.de or edebruin@iname.com +49 241 963 2635(w) "the promise of love is hard to ignore" - crowded house, private universe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 05:35:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08282 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 05:35:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fredead.systems.pavilion.net (fredead.systems.pavilion.net [194.242.128.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08277 for ; Tue, 3 Nov 1998 05:35:37 -0800 (PST) (envelope-from sam@pavilion.net) Received: (from sam@localhost) by fredead.systems.pavilion.net (8.8.8/8.8.8) id NAA15889; Tue, 3 Nov 1998 13:33:12 GMT (envelope-from sam) Message-ID: <19981103133312.E15717@pavilion.net> Date: Tue, 3 Nov 1998 13:33:12 +0000 From: Sam Eaton To: Julian Elischer , Greg Lehey Cc: Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Re: Microsoft's Open Source strategy (was: Ariel Faigon: The Holloween Document (fwd)) References: <19981102172140.J354@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Julian Elischer on Mon, Nov 02, 1998 at 12:01:43AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 02, 1998 at 12:01:43AM -0800, Julian Elischer wrote: > I doubt this document has come from microsoft. > > It smells of "linux fanatic's daydream" to me.. Just saw this on : http://www.wired.com/news/news/technology/story/15990.html [snip] The memo is dated 11 August and signed by Vinod Valloppillil, a product manager for Microsoft's engineering group. Microsoft product manager Ed Muth confirmed the document's authenticity, but says it does not represent Microsoft's position or strategy in regard to open-source software. [snip] So looks like it might well be for real. Doesn't make it an accurate assement of the state of Open Source Software, but it does make it an interesting explanation of MickySofts world view... Sam. -- ------------------------------------------------------------------------ Sam Eaton Senior Systems Manager, Pavilion Internet Plc "Fortified with essential bitterness and sarcasm" ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 05:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08866 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 05:44:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA08859 for ; Tue, 3 Nov 1998 05:44:05 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 18956 invoked from network); 3 Nov 1998 13:43:54 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 3 Nov 1998 13:43:54 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id HAA11740; Tue, 3 Nov 1998 07:43:51 -0600 Date: Tue, 3 Nov 1998 07:43:51 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199811031343.HAA11740@bonkers.taronga.com> To: hackers@FreeBSD.ORG Subject: Re: Microsoft's Open Source strategy Newsgroups: taronga.freebsd.hackers In-Reply-To: <19981103133312.E15717@pavilion.net> References: <19981102172140.J354@freebie.lemis.com> , Organization: none Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981103133312.E15717@pavilion.net>, Sam Eaton wrote: >Doesn't make it an accurate assement of the state of Open Source >Software, but it does make it an interesting explanation of MickySofts >world view... It's entirely consistent with Microsoft's observed behaviour. Look at their track record with gratuitous file format and protocol changes. Windows 2000's Kerberos and DNS support will be subtly incompatible with standard Kerberos and DNS, for example... I don't believe Microsoft's backpedalling one moment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 06:04:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11302 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 06:04:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fredead.systems.pavilion.net (fredead.systems.pavilion.net [194.242.128.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11296 for ; Tue, 3 Nov 1998 06:04:30 -0800 (PST) (envelope-from sam@pavilion.net) Received: (from sam@localhost) by fredead.systems.pavilion.net (8.8.8/8.8.8) id OAA16006; Tue, 3 Nov 1998 14:03:42 GMT (envelope-from sam) Message-ID: <19981103140341.F15717@pavilion.net> Date: Tue, 3 Nov 1998 14:03:41 +0000 From: Sam Eaton To: Peter da Silva , hackers@FreeBSD.ORG Subject: Re: Microsoft's Open Source strategy References: <19981102172140.J354@freebie.lemis.com> , <19981103133312.E15717@pavilion.net> <199811031343.HAA11740@bonkers.taronga.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811031343.HAA11740@bonkers.taronga.com>; from Peter da Silva on Tue, Nov 03, 1998 at 07:43:51AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 03, 1998 at 07:43:51AM -0600, Peter da Silva wrote: > In article <19981103133312.E15717@pavilion.net>, > Sam Eaton wrote: > >Doesn't make it an accurate assement of the state of Open Source > >Software, but it does make it an interesting explanation of MickySofts > >world view... > > It's entirely consistent with Microsoft's observed behaviour. Look at their > track record with gratuitous file format and protocol changes. Windows > 2000's Kerberos and DNS support will be subtly incompatible with standard > Kerberos and DNS, for example... Oh absolutely, that's what I was trying to say - the halloween document says a lot more about microsoft than it does about open source... An interesting question is whether the lack of understanding by microsoft of various open source projects in any way reflects similar misconceptions in the wider community. Which brings us back to issues of PR (and probably moves this thread to advocacy) ;-> Sam. -- ------------------------------------------------------------------------ Sam Eaton Senior Systems Manager, Pavilion Internet Plc "Fortified with essential bitterness and sarcasm" ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 06:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17637 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 06:53:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailhub1.cuckoo.com (wrangler.cuckoo.com [206.109.5.194]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA17541 for ; Tue, 3 Nov 1998 06:53:01 -0800 (PST) (envelope-from dbaker@cuckoo.com) Received: (qmail 4146 invoked by uid 200); 3 Nov 1998 14:52:54 -0000 Message-ID: <19981103085254.E23407@wrangler.cuckoo.com> Date: Tue, 3 Nov 1998 08:52:54 -0600 From: Daniel Baker To: Sam Eaton , Julian Elischer , Greg Lehey Cc: Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Re: Microsoft's Open Source strategy (was: Ariel Faigon: The Holloween Document (fwd)) References: <19981102172140.J354@freebie.lemis.com> <19981103133312.E15717@pavilion.net> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="ryJZkp9/svQ58syV" X-Mailer: Mutt 0.93.2i In-Reply-To: <19981103133312.E15717@pavilion.net>; from Sam Eaton on Tue, Nov 03, 1998 at 01:33:12PM +0000 X-PGP-Fingerprint: F3 41 B7 EE 96 92 F5 35 5E 3C 02 61 08 22 23 98 X-Operating-System: FreeBSD 3.0-CURRENT i386 X-Distributed: Join the Effort! http://www.distributed.net/ ]:8) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ryJZkp9/svQ58syV Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On 03-Nov-1998, Sam Eaton wrote: > On Mon, Nov 02, 1998 at 12:01:43AM -0800, Julian Elischer wrote: >=20 > > I doubt this document has come from microsoft. [snip] > Just saw this on :=20 > http://www.wired.com/news/news/technology/story/15990.html [snip] > So looks like it might well be for real. =20 >=20 > Doesn't make it an accurate assement of the state of Open Source > Software, but it does make it an interesting explanation of MickySofts > world view... You could be correct, however, it may be that Vinod is an extremist whose is completely attempting to revolutionize Microsoft's business strategy. While quite interesting, I don't find the article incredibly incriminating; had a Linux bigot who wasn't employed by Microsoft written a similar memo, it wouldn't have attracted the huge masses of attention that this memo has simply because the general population views Vinod's opinions as somewh= at more authoritative because he's one of the thousands of people that Micrsofot employees. Warmly, Daniel --=20 dbaker@cuckoo.com - CuckooNet Consultant - www.cuckoo.com --ryJZkp9/svQ58syV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: UwLRf5cGfl70i787RvQJkTYwVN/ae5q4 iQA/AwUBNj8KtakRxAgyUTYnEQLvugCeIysIgvI8P1ZApc/t0o/ELkGx2JAAoLTU f0jgYksSiKL6s/OamoECjcYo =xrXi -----END PGP SIGNATURE----- --ryJZkp9/svQ58syV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 07:00:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18315 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 07:00:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18310 for ; Tue, 3 Nov 1998 07:00:15 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA209325112; Tue, 3 Nov 1998 09:58:32 -0500 Date: Tue, 3 Nov 1998 09:58:32 -0500 (EST) From: Bill Fumerola To: Sergei Laskavy Cc: hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 Nov 1998, Sergei Laskavy wrote: > > Since it's in the public domain, there's nothing to stop us from > > cleaning it up and sticking it into the tree. > > Why we can't just put it in ports and clean it via ttcp/patches ? It was submitted yesterday as ports/8546. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 07:02:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18667 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 07:02:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18645; Tue, 3 Nov 1998 07:02:43 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id PAA01467; Tue, 3 Nov 1998 15:01:59 GMT Message-ID: <363F1AE6.BBBCC89@tdx.co.uk> Date: Tue, 03 Nov 1998 15:01:58 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Baker CC: Sam Eaton , Julian Elischer , Greg Lehey , Warner Losh , freebsd-hackers@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Subject: Re: Microsoft's Open Source strategy (was: Ariel Faigon: The Holloween Document (fwd)) References: <19981102172140.J354@freebie.lemis.com> <19981103133312.E15717@pavilion.net> <19981103085254.E23407@wrangler.cuckoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Baker wrote: > While quite interesting, I don't find the article incredibly incriminating; > had a Linux bigot who wasn't employed by Microsoft written a similar memo, > it wouldn't have attracted the huge masses of attention that this memo > has simply because the general population views Vinod's opinions as somewhat > more authoritative because he's one of the thousands of people that > Micrsofot employees. Why not move this onto -chat? - It looks like it's a thread that's going to run for a while, and -hackers is probably not the best of places? ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 07:48:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23993 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 07:48:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA23988 for ; Tue, 3 Nov 1998 07:48:32 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JRADCPLJ; Tue, 03 Nov 98 15:31:43 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981103163141.009c1860@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 03 Nov 1998 16:31:41 +0100 To: Bill Fumerola , "John C. Place" From: Marius Bendiksen Subject: Re: df hangs on 2.2.6-BETA Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: References: <19981102210818.01660@ka3tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way of doing a true unconditional forcible kill? If not, what would be needed to implement it? (follow-ups to -hackers) --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 08:40:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01435 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 08:40:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01430 for ; Tue, 3 Nov 1998 08:40:17 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id LAA10266; Tue, 3 Nov 1998 11:43:09 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 3 Nov 1998 11:43:09 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Marius Bendiksen cc: hackers@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <3.0.5.32.19981103163141.009c1860@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well afaik fd hangs when a NFS server the machine is a client of goes down, this can be fixed by specifing option "intr" on the mount, the allows processes to be killed if NFS hangs. It's in the spec that processes should hang forever unless this option is specified. Here's what i use for NFS mounts: rw,tcp,bg,nfsv3,-r32768,-w32768,intr readwrite tcp connect mount in background readbuf 32k writebuf 32k intruppable mounts. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 3 Nov 1998, Marius Bendiksen wrote: > > Is there any way of doing a true unconditional forcible kill? > > If not, what would be needed to implement it? > > (follow-ups to -hackers) > --- > Marius Bendiksen, IT-Trainee, ScanCall AS > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 09:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06273 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 09:10:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA06234 for ; Tue, 3 Nov 1998 09:10:01 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JRBBVFRJ; Tue, 03 Nov 98 17:09:46 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981103180944.0096b210@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 03 Nov 1998 18:09:44 +0100 To: Alfred Perlstein From: Marius Bendiksen Subject: Re: df hangs on 2.2.6-BETA Cc: hackers@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981103163141.009c1860@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA06269 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was thinking more along the lines of a generic mechanism for killing *any* part of the system which has gotten hung up on something. .oO[¨ Marius Bendiksen ¨]Oo. Dead girls don't say no. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 09:12:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06711 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 09:12:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06688 for ; Tue, 3 Nov 1998 09:12:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id BAA24579; Wed, 4 Nov 1998 01:11:23 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199811031711.BAA24579@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: sync writes with softupdates enabled In-reply-to: Your message of "Mon, 02 Nov 1998 16:30:29 +1100." <98Nov2.163001est.40354@border.alcanet.com.au> Date: Wed, 04 Nov 1998 01:11:22 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > Mike Smith wrote: > >Now that this has been committed, can we have some feedback from people > >using mmap heavily on -current? > > There are no longer any sync writes as a result of using an MMAP'd > history file in inn. There is no obvious corruption of history file > or associated .pag file. > > Note that there is a similar bug in 2.2.x. The fix is similar, but > needs some thought since there appears to be a problem with the > parameters to vm_object_page_clean(). In particular, `syncio' is > defined as boolean_t, as passed as the `waitfor' argument to > VOP_FSYNC() - which is MNT_ASYNC or MNT_SYNC elsewhere. I haven't > had the time to work out the correct definitions. Use TRUE and FALSE instead of OBJPC_SYNC and 0. > Peter Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 09:23:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08661 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 09:23:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08649 for ; Tue, 3 Nov 1998 09:23:14 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 20118 invoked by uid 1001); 3 Nov 1998 17:16:23 +0000 (GMT) To: wpaul@skynet.ctr.columbia.edu Cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Call for testers for Macronix fast ethernet driver In-Reply-To: Your message of "Mon, 2 Nov 1998 14:15:11 -0500 (EST)" References: <199811021915.OAA07892@skynet.ctr.columbia.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 03 Nov 1998 18:16:23 +0100 Message-ID: <20116.910113383@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, I'm also interested in performance stats for real DEC tulip > chips with the de driver. I'm wondering how real DEC chips do at 100Mbps > modes. Real DEC chips are fully able to saturate a 100 Mbps Ethernet. I measured this with FreeBSD almost two years ago, actually... Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 09:32:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10047 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 09:32:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10028 for ; Tue, 3 Nov 1998 09:32:07 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA261334216; Tue, 3 Nov 1998 12:30:16 -0500 Date: Tue, 3 Nov 1998 12:30:16 -0500 (EST) From: Bill Fumerola To: Alfred Perlstein Cc: Marius Bendiksen , hackers@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, Alfred Perlstein wrote: > It's in the spec that processes should hang forever unless this option > is specified. > > Here's what i use for NFS mounts: > > rw,tcp,bg,nfsv3,-r32768,-w32768,intr One of the programs that came up in this discussion was Sharity Light (/usr/ports/net/sharity-light), I'd have to check if it supports the intr option. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 09:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10751 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 09:38:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10702 for ; Tue, 3 Nov 1998 09:38:01 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id MAA10344; Tue, 3 Nov 1998 12:40:55 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 3 Nov 1998 12:40:55 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Marius Bendiksen cc: hackers@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <3.0.5.32.19981103180944.0096b210@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id JAA10730 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, Marius Bendiksen wrote: > > I was thinking more along the lines of a generic mechanism for killing > *any* part of the system which has gotten hung up on something. I'm only aware of this becoming a problem in two areas: 1) NFS without intr 2) the stupid ATAPI driver (it doesn't do a real reset and hangs processes) Some places might be changed to allow this, but other places it just can't without major design changes. Sometimes waiting for a resource is a good thing. Generally a lot of provisions are made to make sure kill -9 works in all cases, perhaps with a small delay for entry/exit into the kernel. What process specifically hangs for you? only df? is it the NFS issue? you can also configure NFS to pass back an error on a certain timeout of waiting. however this causes problems when coders don't expect what they think are "local" files to return such errors on access. > .oO[¨ Marius Bendiksen ¨]Oo. > Dead girls don't say no. > I hope that's some sort of literary referance. yuk. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 10:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15085 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 10:11:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15079 for ; Tue, 3 Nov 1998 10:11:00 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id KAA21571; Tue, 3 Nov 1998 10:53:15 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd021525; Tue Nov 3 10:53:07 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id KAA29906; Tue, 3 Nov 1998 10:53:05 -0700 (MST) From: Terry Lambert Message-Id: <199811031753.KAA29906@usr05.primenet.com> Subject: Re: scanf in the kernel? To: mike@smith.net.au (Mike Smith) Date: Tue, 3 Nov 1998 17:53:05 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199811021911.LAA00716@dingo.cdrom.com> from "Mike Smith" at Nov 2, 98 11:11:24 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I believe the "last time" to which you refer is the mount fstype > > > > argument, in which I thought it was stupid to limit yourself to > > > > defined FS's in mount.h. > > > > > > So you want more binary clutter and interface dependency just to > > > translate FSNAME to FSNUMBER? > > > > Given a choice between user space bloat and kernel bloat, I choose > > user space bloat. > > And given the opportunity to trade large user-space bloat and > management headaches for miniscule kernel bloat? It's only a management headache if you insist on micro-managing the kernel. Most of the sysctl tunables in the kernel shouldn't be. > > > > So installing a new FS type installs commands in /sbin, and hving > > > > installed commands in /sbin, the list is known via a traversal of > > > > sbin, without even asking the kernel. > > > > > > Er. And who do you ask to do the traversal of /sbin? > > > > In the limit, /sbin/fstyp. > > And what does it use? It goes out and reads the raw partition to determine the format. > You're overloading the filesystem namespace to perform a translation > from FSNAME to FSNUMBER, using an inefficient interface with no > guarantee that the translation space is representative of the state of > the kernel. That's a first revision. The second revision replaces /sbin/nfs_mount with /libexec/fs/nfs.so. The third revision asks the kernel to page in all non-resident VFS's identification routines from their seperate ELF sections in the respective VFS drivers on a device arrival event, and mounts the FS automatically based on the contents of the "last mounted on" string, as long as the "don't automount me" bit isn't set. > > This is not an ideal soloution, but consider that the VFS KLD(s) > > for a given filesystem may not be in the kernel. > > Of course I've considered that. By passing in an arbitrary key string > for the VFS type, you have a direct translation to a module filename, > which you can demand load in a transparent fashion, rather than > requiring an error return, user-space module load and recall. Well, that's obvious, but paging that portion of the kernel not in the paging path, and treating KLD's a nothing more than backing store for kernel pages is even more obvious. [ ... mounting ... ] > Fine. None of this has anything to do with passing the key over the > user:kernel boundary, which you do in the mount phase in order to > reliably locate the module responsible for the VFS. Which was exactly the point of the exercise: to show that key passing is not necessary to implement the code. > > > ... and you're attaching an implicit value judgement to that "tendency". > > > > Actually, I was quite explicit: > > > > I think it is a mistake for FreeBSD to turn into Plan9. > > > > And with the "I think" in there, it's obviously an opinion. But it's > > an opinion based on experience, not emotion. > > It's an implicit opinion, offered with no justification other than an > other implicit "you should trust me (because I'm a loud dog)". You've interpreted this wrong. My intent was to state "You should consider the ultimate consequences of your design decisions before you make them" and "I think this design decision is ill considered". You aren't required to consider my opinions, but I'm likewise not required to not offer them if I think you are going down the wrong primrose path. > > > You're the one agonising over passing data across the user/kernel > > > boundary. > > > > Yes, I am. Every time I have to recompile libkvm and ps, w, finger, > > netstat, etc., etc., I agonize over the externalization of kernel > > internal data as defacto interfaces. > > You're facing the wrong way. Using self-describing and robust > interface formats reduces the need for this. At the moment, the > biggest problems faced by the above tools is that they depend on > manifest constants and implicit structure definitions. None of this > will be helped by your stance. Nor will it be helped by bloating the kernel before you address the existing problems. > > They are apropriate anywhere their data is externalized directly > > instead of procedurally (an FS is a good place to convert data > > references into procedural references, if you need that sort of > > thing, hence procfs). > > Yes; I'm actually teaching myself about the VFS model by writing what > I've grandly called metafs, which aims to be a framework into which > various non-file-objects can register themselves in order to appear as > a filesystem. The major design flaws with both procfs and kernfs are > that they are essentially static. The original goal was to produce an > emulation of the linux procfs, however it became clear that I needed to > understand the VFS framework and provide infrastructure for the many > pieces of junk they aggregate there. Well, I certainly can't disagree with this direction. I think it's the right way to go for most of the MIB data that's in sysctl. If you need a scanf for that, then by all means, it should be part of that VFS module. > > > This might have been fine when the MIB was a static object produced at > > > compile time. As an approach for name translation in a dynamic tree > > > it's simply not workable. > > > > So basically, you are denying the reality of IBM's SNMPv2 implementation, > > which allows dynamic (de/)registration of manageable hierarchies of > > exposed data? > > > > I have to say, having used the reference implementation 4 years ago > > on Solaris, I don't think that it has quit working in the interim... > > There is no information here. I can't read your mind. IBM's SNMPv2 implementation performs name translation in a dynamic tree. > The issues: > > - Only the MIB manager knows the contents of the MIB. IBM's SNMPv2 implementation allows registration of subregions into the MIB by the servers responsible and requring the subregions. As a result, it is dynamic, yet maps precisely, at all time, the current content and configuration requirements. > - Objects are added to the MIB via the MIB manager. > - Only the object provider knows what the object is. > - Objects may be renumbered at effectively arbitrary times. IBM's SNMPv2 implementation is, effectively, a streams MUX. It is relatively trivial to convert from such an implementation to a shared object implementation or a shared memory implementation or a UNIX domain socket implemetnation, etc.. This means: - Objects are added to the MIB by the instancer of the objects, and only procedurally exposed through the MIB manager, instead of being directly exposed through the MIB manager. - Only the objct provider *need* to know what the object is. - Objects may be renumbered at effectively arbitrary times, but this has no impact on the object implementation or th implementation of a management interface, if the management interface is abstracted via addition MIB contents. > - We don't have a predefined list of all the possible objects. > > Tell me how you plan to export the mapping between MIB numbers and > names from the MIB manager. Tell me how this is not a name-to-number > lookup interface. 8) By looking up the names in a different part of the MIB. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 11:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23287 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 11:11:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23282; Tue, 3 Nov 1998 11:11:02 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id LAA25745; Tue, 3 Nov 1998 11:08:02 -0800 (PST) Message-Id: <199811031908.LAA25745@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Ustimenko Semen Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG, current-users@netbsd.org Subject: Re: SMC9432TX driver (tx) users Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 03 Nov 1998 11:08:02 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I've added current-users@netbsd.org, because NetBSD users have seen timeouts with the driver for the EPIC that I wrote, and I believe it is a hardware problem... ] On Tue, 3 Nov 1998 18:24:37 +0600 (NS) Ustimenko Semen wrote: > If you use tx driver under FreeBSD, can you send me private > message if you have ANY problems useing it. > > Even if the problem is only > tx0: timeout %d packets, ... With my 9432TX (in an AlphaStation 500 running NetBSD/alpha) I have seen these device timeouts. Note, NetBSD's "epic" driver is NOT the same as FreeBSD's "tx" driver; I wrote "epic" from scratch. However, I have NOT been able to find the source of these timeouts. People have reported to me that they are more common in 10Mbps mode, apparently. Sometimes the card just wedges completely, and I have to reboot to get it to come back. Sometimes, not even a reboot solves the problem. There is an application note which describes a hardware bug, and a work around for it. Here is the workaround from my "epic" driver: /* * Fixup the clock source on the EPIC. */ void epic_fixup_clock_source(sc) struct epic_softc *sc; { int i; /* * According to SMC Application Note 7-15, the EPIC's clock * source is incorrect following a reset. This manifests itself * as failure to recognize when host software has written to * a register on the EPIC. The appnote recommends issuing at * least 16 consecutive writes to the CLOCK TEST bit to correctly * configure the clock source. */ for (i = 0; i < 16; i++) bus_space_write_4(sc->sc_st, sc->sc_sh, EPIC_TEST, TEST_CLOCKTEST); } This function is called in various places when we think the chip might be catatonic. See src/sys/dev/ic/smc83c170.c in NetBSD-current. This may not be the only problem the hardware has, or I may not be fixing up the clock source in all the right places... I would be VERY interested to know the FreeBSD experience with this hardware, even given the completely different driver software being used. Thanks! Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 11:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27951 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 11:41:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27943 for ; Tue, 3 Nov 1998 11:41:29 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA04914; Tue, 3 Nov 1998 12:41:13 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd004895; Tue Nov 3 12:41:08 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA03979; Tue, 3 Nov 1998 12:41:03 -0700 (MST) From: Terry Lambert Message-Id: <199811031941.MAA03979@usr05.primenet.com> Subject: Re: "panic: free: multiple frees" VM bug? (long) To: julian@whistle.com (Julian Elischer) Date: Tue, 3 Nov 1998 19:41:03 +0000 (GMT) Cc: dg@root.com, lile@stdio.com, hackers@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Nov 2, 98 08:56:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I also doubt if you really want to free them either.. > > possibly keep a pool of them and recycle them in your own free list. Exactly what I was thinking, actually. The problem with allocating and freeing these things is that you could very easily fragment the KVA space to the point where subsequent contigalloc's will fail. FreeBSD can not (currently) relocate pages in physical memory in order to "defrag" the KPA (Kernel Physical Address) space, and thus most drivers that want a contiguous chunk of memory allocate the memory early on -- usually at device attach -- to ensure that the memory will actually be available when they later need it. Yes, it's theoretically possible to resolve these issues, but they haven't been resolved yet, so it's not safe to code as if they have. Even so, assuming these issues *were* resolved, you'd probably *still* want to keep a pool around to avoid the allocator overhead, which is not inconsiderable, and at worst if you insisted on trying to free as much memory back as possible instead of just swallowing it forever like everyone else does, you'd high/low watermark the usage to delay allocations and deallocations in the hopes that they would be unnecessary, on average. This is all more complicated than you should be working with in the current kernel environment for the amount of memory you are likely to be using at any one time. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 11:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28556 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 11:47:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28549 for ; Tue, 3 Nov 1998 11:47:05 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA10508; Tue, 3 Nov 1998 12:46:57 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd010473; Tue Nov 3 12:46:50 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA04230; Tue, 3 Nov 1998 12:46:42 -0700 (MST) From: Terry Lambert Message-Id: <199811031946.MAA04230@usr05.primenet.com> Subject: Documentation upgrade: where are the other humans? To: abial@nask.pl (Andrzej Bialecki) Date: Tue, 3 Nov 1998 19:46:42 +0000 (GMT) Cc: adrian@ubergeeks.com, jordan@Thinkbank.COM, hackers@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Nov 3, 98 10:53:35 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > You should read www.freebsd.org pages more carefully :-) For more info > > > follow the URL in my sig. > > > > No offense, but I found the documentation a bit weak. I even > > Well, you're right - the documentation needs massive upgrade. The existing > one was intended for people who already know quite a bit about FreeBSD. > But guess what... It's easier for me to code than to write stories... You know, I've often wondered why, given that there are people who will code for the fun of it, why none of the Free Software projects have crossed disciplines. You'd think that there would be English Majors and/or Technical Writers who would write documentation for the fun of it, and Marketing people who would do marketing for the fun of it, and Graphic Artists who would do commercial art for the fun of it... Are programmers the only people who enjoy what they intend to make their life's work? Maybe it's just that the majority of people are too busy sitting on their butts hacking code in cave-like computer labs to talk to people in other departments on campus? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 12:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05905 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 12:37:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA05876 for ; Tue, 3 Nov 1998 12:37:06 -0800 (PST) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id PAA05386; Tue, 3 Nov 1998 15:36:35 -0500 Date: Tue, 3 Nov 1998 15:36:35 -0500 (EST) From: Jamie Bowden To: James Buszard-Welcher cc: hackers@FreeBSD.ORG Subject: Re: fvwm2 package (3.0) is 'kerberized' In-Reply-To: <363A5719.AFB449CF@reef.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, James Buszard-Welcher wrote: > The fvwm2 package under 3.0-current is kerberized. > I thought there was something wrong with XFree86 > install... reinstalled it twice... A -lot- of the packages are kerberized and linked against DES for some reason. Jamie Bowden -- Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 12:55:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08713 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 12:55:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08708 for ; Tue, 3 Nov 1998 12:55:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00380; Tue, 3 Nov 1998 12:54:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811032054.MAA00380@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Tue, 03 Nov 1998 17:53:05 GMT." <199811031753.KAA29906@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Nov 1998 12:54:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > I believe the "last time" to which you refer is the mount fstype > > > > > argument, in which I thought it was stupid to limit yourself to > > > > > defined FS's in mount.h. > > > > > > > > So you want more binary clutter and interface dependency just to > > > > translate FSNAME to FSNUMBER? > > > > > > Given a choice between user space bloat and kernel bloat, I choose > > > user space bloat. > > > > And given the opportunity to trade large user-space bloat and > > management headaches for miniscule kernel bloat? > > It's only a management headache if you insist on micro-managing > the kernel. Most of the sysctl tunables in the kernel shouldn't be. It's a management headache because it's a collection of components which can (and will) go stale, maintained without any infrastructure. > > > > > So installing a new FS type installs commands in /sbin, and hving > > > > > installed commands in /sbin, the list is known via a traversal of > > > > > sbin, without even asking the kernel. > > > > > > > > Er. And who do you ask to do the traversal of /sbin? > > > > > > In the limit, /sbin/fstyp. > > > > And what does it use? > > It goes out and reads the raw partition to determine the format. No, it uses the kernel to perform the traversal of the /sbin namespace. I don't see anything logically different here to the kernel doing its own traversal internally. > > You're overloading the filesystem namespace to perform a translation > > from FSNAME to FSNUMBER, using an inefficient interface with no > > guarantee that the translation space is representative of the state of > > the kernel. > > That's a first revision. > > The second revision replaces /sbin/nfs_mount with /libexec/fs/nfs.so. > > The third revision asks the kernel to page in all non-resident VFS's > identification routines from their seperate ELF sections in the > respective VFS drivers on a device arrival event, and mounts the > FS automatically based on the contents of the "last mounted on" > string, as long as the "don't automount me" bit isn't set. ... which is where we're heading. > > > > This is not an ideal soloution, but consider that the VFS KLD(s) > > > for a given filesystem may not be in the kernel. > > > > Of course I've considered that. By passing in an arbitrary key string > > for the VFS type, you have a direct translation to a module filename, > > which you can demand load in a transparent fashion, rather than > > requiring an error return, user-space module load and recall. > > Well, that's obvious, but paging that portion of the kernel not > in the paging path, and treating KLD's a nothing more than backing > store for kernel pages is even more obvious. There's no guarantee that KLDs will be writable as backing store; you'd have to handle paging them to anonymous space too. > > [ ... mounting ... ] > > > Fine. None of this has anything to do with passing the key over the > > user:kernel boundary, which you do in the mount phase in order to > > reliably locate the module responsible for the VFS. > > Which was exactly the point of the exercise: to show that key passing > is not necessary to implement the code. It's necessary to pass *something* in the current toploaded architecture. Until we have the SLICE infrastructure back, there's no viable alternative (fstyp is a bad joke). > > > > ... and you're attaching an implicit value judgement to that "tendency". > > > > > > Actually, I was quite explicit: > > > > > > I think it is a mistake for FreeBSD to turn into Plan9. > > > > > > And with the "I think" in there, it's obviously an opinion. But it's > > > an opinion based on experience, not emotion. > > > > It's an implicit opinion, offered with no justification other than an > > other implicit "you should trust me (because I'm a loud dog)". > > You've interpreted this wrong. My intent was to state "You should > consider the ultimate consequences of your design decisions before > you make them" and "I think this design decision is ill considered". I know. This is why I said you were making an implicit value judgement. > Well, I certainly can't disagree with this direction. I think it's > the right way to go for most of the MIB data that's in sysctl. If > you need a scanf for that, then by all means, it should be part of > that VFS module. No. It should be a general kernel service so that we don't bloat every module that might want to use it with a private copy. > > Tell me how you plan to export the mapping between MIB numbers and > > names from the MIB manager. Tell me how this is not a name-to-number > > lookup interface. 8) > > By looking up the names in a different part of the MIB. Which is a name-to-number translation interface. Provided by the mib manager group entity. Thank you for at last agreeing. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 13:12:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10818 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 13:12:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10807 for ; Tue, 3 Nov 1998 13:12:36 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA11225; Tue, 3 Nov 1998 22:18:00 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 3 Nov 1998 22:18:00 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Marius Bendiksen cc: Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <3.0.5.32.19981103180944.0096b210@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, Marius Bendiksen wrote: > > I was thinking more along the lines of a generic mechanism for killing > *any* part of the system which has gotten hung up on something. AFAIK, the processes which are stuck at kernel priority levels are unkillable by definition. At least [McKusick et al.] say so. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 13:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17295 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 13:53:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17290 for ; Tue, 3 Nov 1998 13:53:09 -0800 (PST) (envelope-from ziggy@wopr.inetu.net) Received: from localhost (ziggy@localhost) by wopr.inetu.net (8.8.8/8.8.5) with SMTP id QAA12894; Tue, 3 Nov 1998 16:53:01 -0500 (EST) Date: Tue, 3 Nov 1998 16:53:01 -0500 (EST) From: Ryan Ziegler To: freebsd-hackers@FreeBSD.ORG cc: Terry Lambert Subject: Re: Documentation upgrade: where are the other humans? In-Reply-To: <199811031946.MAA04230@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, Terry Lambert wrote: > > You know, I've often wondered why, given that there are people > who will code for the fun of it, why none of the Free Software > projects have crossed disciplines. > > You'd think that there would be English Majors and/or Technical > Writers who would write documentation for the fun of it, and > Marketing people who would do marketing for the fun of it, and > Graphic Artists who would do commercial art for the fun of it... When not getting paid, programmers tend to code what they find interesting. We can say the same thing for writers when writing. I would say technical documentation is not the most exciting literary form, nor are the arguments for kmem_free() the most exciting subject matter. What we need are technical writers who feel a severe allegiance to FreeBSD. > Are programmers the only people who enjoy what they intend to make > their life's work? No, but if you enjoy programming, society definately rewards. > Maybe it's just that the majority of people are too busy sitting > on their butts hacking code in cave-like computer labs to talk > to people in other departments on campus? You're not suggesting that we're a tad clannish, are you? :) > Terry Lambert > terry@lambert.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 14:00:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18584 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 14:00:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zephyr.cybercom.net (zephyr.cybercom.net [209.21.146.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18560 for ; Tue, 3 Nov 1998 14:00:07 -0800 (PST) (envelope-from rhuff@cybercom.net) Received: from shell1.cybercom.net (rhuff@shell1.cybercom.net [209.21.136.6]) by zephyr.cybercom.net (8.8.7/8.8.7) with ESMTP id QAA17312 for ; Tue, 3 Nov 1998 16:59:59 -0500 (EST) Received: (from rhuff@localhost) by shell1.cybercom.net (8.8.5/8.8.5) id QAA06386; Tue, 3 Nov 1998 16:59:58 -0500 (EST) Date: Tue, 3 Nov 1998 16:59:58 -0500 (EST) Message-Id: <199811032159.QAA06386@shell1.cybercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Robert Huff To: freebsd-hackers@FreeBSD.ORG Subject: Re: Ariel Faigon: The Holloween Document (fwd) In-Reply-To: <21276782@toto.iv> X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > http://www.tuxedo.org/~esr/halloween.html > > It seems to me a bit too conveniently supportive of ESR's > commentary and the whole "Microsoft Pheeeeeeerz Linux" mentality. The authenticity has been confirmed by _The Boston Globe_ (11/3, page D3). MS claims it represents only the opinion of the author and has not been accepted as policy. > Followups to FreeBSD-advocacy. This got stripped from the digest version. Robert Huff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 14:02:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19164 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 14:02:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from netcom14.netcom.com (netcom14.netcom.com [192.100.81.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19155; Tue, 3 Nov 1998 14:02:23 -0800 (PST) (envelope-from hasty@netcom.com) Received: (from hasty@localhost) by netcom14.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) id OAA13297; Tue, 3 Nov 1998 14:01:40 -0800 (PST) Date: Tue, 3 Nov 1998 14:01:40 -0800 (PST) From: Amancio Hasty Jr Message-Id: <199811032201.OAA13297@netcom14.netcom.com> To: advocacy@FreeBSD.ORG, imp@village.org Subject: Re: Ariel Faigon: The Holloween Document (fwd) Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The e-mail made it to today's San Jose Mercury NewsPaper in the business section. The news article claims that the e-mail was confirmed by Microsoft to be authenticate --- not sure who to believe Microsoft or the Linux camp 8) Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 14:38:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24898 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 14:38:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24891 for ; Tue, 3 Nov 1998 14:38:05 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA26175; Tue, 3 Nov 1998 15:37:57 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd026016; Tue Nov 3 15:37:49 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA22900; Tue, 3 Nov 1998 15:37:48 -0700 (MST) From: Terry Lambert Message-Id: <199811032237.PAA22900@usr09.primenet.com> Subject: Re: scanf in the kernel? To: mike@smith.net.au (Mike Smith) Date: Tue, 3 Nov 1998 22:37:48 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199811032054.MAA00380@dingo.cdrom.com> from "Mike Smith" at Nov 3, 98 12:54:22 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You've interpreted this wrong. My intent was to state "You should > > consider the ultimate consequences of your design decisions before > > you make them" and "I think this design decision is ill considered". > > I know. This is why I said you were making an implicit value judgement. Ugh. I give up. How many times do I have to say, "yes, this is what I said" for what I said to not be considered "implicit" by you? I think we are using different definitions for "implicit". I feel like Andre the Giant trying to explain the correct usage of "inconcievable" to Vizini the Sicilian in "The Princess Bride". > > > Tell me how you plan to export the mapping between MIB numbers and > > > names from the MIB manager. Tell me how this is not a name-to-number > > > lookup interface. 8) > > > > By looking up the names in a different part of the MIB. > > Which is a name-to-number translation interface. Provided by the mib > manager group entity. > > Thank you for at last agreeing. The information is there because it was put there, not because it was translated via scanf, whatever... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 15:38:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04457 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 15:38:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04451 for ; Tue, 3 Nov 1998 15:38:43 -0800 (PST) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (VMailer) with ESMTP id AB44836E; Wed, 4 Nov 1998 00:38:33 +0100 (MET) Received: by ariel.xaa.iae.nl (VMailer, from userid 1008) id 204254296; Wed, 4 Nov 1998 00:38:33 +0100 (CET) Date: Wed, 4 Nov 1998 00:38:33 +0100 From: Mark Huizer To: gmarco@giovannelli.it, hackers@FreeBSD.ORG Cc: freebsd@scotty.masternet.it Subject: Re: perl guru needed Message-ID: <19981104003832.B781@ariel.xaa.iae.nl> Mail-Followup-To: gmarco@giovannelli.it, hackers@FreeBSD.ORG, freebsd@scotty.masternet.it References: <199811020119.CAA11838@scotty.masternet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i In-Reply-To: <199811020119.CAA11838@scotty.masternet.it>; from Gianmarco Giovannelli on Tue, Nov 03, 1998 at 12:30:25PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (I hope to be in the right Mailing lists... ) > > Hello, I am writing some perl scripts (in attach) to generate on the fly > the contents of the port dir, with some additions to the plain > README.html generated by a make readmes in the ports dir > > Now I am encountering some little obstacles that are too much for me > ... so I ma searching for some help here :-) > > The main problem is the way the cgi passes the param on the url ... > Some names in the port contain the + sign with seems to interfere > with the parsing routines of the perl. Use the CGI module in perl5, it will take that burden out of your hands. > > Btw... If you would give them a look they are attached here... > Any feedback is greatly appreciated... I could, maybe, if you still have problems left. -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 16:05:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09639 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 16:05:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from foo.eng.mindspring.net (foo.eng.mindspring.net [207.69.192.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09627 for ; Tue, 3 Nov 1998 16:05:29 -0800 (PST) (envelope-from cnh@foo.eng.mindspring.net) Received: (from cnh@localhost) by foo.eng.mindspring.net (8.9.1/8.8.8) id TAA27624 for freebsd-hackers@freebsd.org; Tue, 3 Nov 1998 19:08:26 -0500 (EST) (envelope-from cnh) Message-ID: <19981103190826.X25583@eng.mindspring.net> Date: Tue, 3 Nov 1998 19:08:26 -0500 From: "Christopher N . Harrell" To: freebsd-hackers@FreeBSD.ORG Subject: corruption of large packets using skip on FreeBSD 2.2-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're using skip to create a secure connection between two machines over the internet. The connection works fine with small packets, but corrupts packets as they get close to the mtu of the outbound interface. (lowering the mtu on the outbound interface decreases the maximum size of functional packets accordingly) We've tried this both over the internet and on the same lan with exactly the same results. Here is a ping from one host to the other with varying packet sizes: dali# /sbin/ping -c1 207.69.192.4 PING 207.69.192.4 (207.69.192.4): 56 data bytes 64 bytes from 207.69.192.4: icmp_seq=0 ttl=255 time=116.032 ms --- 207.69.192.4 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 116.032/116.032/116.032/0.000 ms dali# /sbin/ping -c1 -s 1300 207.69.192.4 PING 207.69.192.4 (207.69.192.4): 1300 data bytes 1308 bytes from 207.69.192.4: icmp_seq=0 ttl=255 time=153.790 ms --- 207.69.192.4 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 153.790/153.790/153.790/0.000 ms dali# /sbin/ping -c1 -s 1500 207.69.192.4 PING 207.69.192.4 (207.69.192.4): 1500 data bytes 1344 bytes from 207.69.192.4: icmp_seq=0 ttl=255 time=158.773 ms wrong data byte #1336 should be 0x38 but was 0x0 cp:6d cc 2d 36 3a 6a c 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 dp:6d cc 2d 36 3a 6a c 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db dc dd de df e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 ca cb cc cd ce cf d0 d1 d2 d3 d4 d5 d6 d7 d8 d9 da db --- 207.69.192.4 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 158.773/158.773/158.773/0.000 ms I'm sure we've overlooking something, but we've been mulling over this for days now without any luck at all. Any insight would be appreciated. cheers, Christopher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 16:42:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16255 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 16:42:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16247 for ; Tue, 3 Nov 1998 16:42:09 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA14882; Wed, 4 Nov 1998 11:11:53 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811030302.MAA01789@zodiac.mech.utsunomiya-u.ac.jp> Date: Wed, 04 Nov 1998 11:11:53 +1030 (CST) From: "Daniel O'Connor" To: Kazutaka YOKOTA Subject: Re: kld screensavers Cc: hackers@FreeBSD.ORG, Mikael Karpberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Nov-98 Kazutaka YOKOTA wrote: > I am not sure if we want to have this kind of screen saver stack. It > will complicate things a lot: multiple saver module management, > priority management, flag checking... Is this worth the effort? It depends how complicated it is to implement. If it works, then hooray, but if its too hard, then a 'normal' system would be OK.. Besides which, its a neat idea, and would give a good example of code for other people to use :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 17:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19541 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 17:09:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (node29.unassigned245.tfs.net [139.146.245.29] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19534 for ; Tue, 3 Nov 1998 17:09:48 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id TAA24878; Tue, 3 Nov 1998 19:09:30 -0600 (CST) From: Jim Bryant Message-Id: <199811040109.TAA24878@unix.tfs.net> Subject: Re: Ariel Faigon: The Holloween Document (fwd) In-Reply-To: <199811032201.OAA13297@netcom14.netcom.com> from Amancio Hasty Jr at "Nov 3, 98 02:01:40 pm" To: hasty@netcom.com (Amancio Hasty Jr) Date: Tue, 3 Nov 1998 19:09:29 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > The e-mail made it to today's San Jose Mercury NewsPaper in the business > section. The news article claims that the e-mail was confirmed by > Microsoft to be authenticate --- not sure who to believe Microsoft or > the Linux camp 8) > > Cheers, > Amancio And just in case someone overlooked it, it also made it's way to the DoJ MickeySoft Task Force email address. The kind of information you can get with a simple phone call is amazing! 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: jbryant@tfs.net AX.25: kc5vdj@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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 3 23:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06264 for freebsd-hackers-outgoing; Tue, 3 Nov 1998 23:18:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06248; Tue, 3 Nov 1998 23:18:35 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id NAA14688; Wed, 4 Nov 1998 13:15:30 +0600 (NS) Date: Wed, 4 Nov 1998 13:15:29 +0600 (NS) From: Ustimenko Semen To: Jason Thorpe cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG, current-users@netbsd.org Subject: Re: SMC9432TX driver (tx) users In-Reply-To: <199811031908.LAA25745@lestat.nas.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, Jason Thorpe wrote: > [ I've added current-users@netbsd.org, because NetBSD users have seen > timeouts with the driver for the EPIC that I wrote, and I believe it > is a hardware problem... ] > > With my 9432TX (in an AlphaStation 500 running NetBSD/alpha) I have seen > these device timeouts. Note, NetBSD's "epic" driver is NOT the same as > FreeBSD's "tx" driver; I wrote "epic" from scratch. However, I have NOT > been able to find the source of these timeouts. People have reported to > me that they are more common in 10Mbps mode, apparently. Sometimes the > card just wedges completely, and I have to reboot to get it to come back. > Sometimes, not even a reboot solves the problem. Not long time ago, there was a problem with card. It hangs just after initialization, on first outgoing packet. I have added check of link status before queueing packets, and the problem (i hope) has disappeared. The problems often appear at slow computers (like 486-DX4 (100)) at 100Mbps under heavy load, like ping -f -s 65000 ... from some quicker station. Internal buffer and rx ring overflow, sometimes following with card shutup. Usually fixed with ifconfig tx0 down up. If only we can make driver spend less time in interrupt... But at least we need to recopy received packet or allocate place for new one. > There is an application note which describes a hardware bug, and a work > around for it. Here is the workaround from my "epic" driver: > ... > Application Note says that we need to set clock source only at initialization... Thank you for pointing me on it, this may be better solution that link checkup before transmition. > I would be VERY interested to know the FreeBSD experience with this > hardware, even given the completely different driver software being > used. They said that this card works fine both at 10 and 100 Mbps. Even without timeouts. But sometimes it fails to autoselect 10Mbps modes, sometimes to force card to 10Mbps mode. I think this is the bug(s) in PHY used (QS6612, have You seen another?). I'll ask OpenBSD users too. Thenk you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 01:08:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21476 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 01:08:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21443 for ; Wed, 4 Nov 1998 01:07:59 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id DAA17250; Wed, 4 Nov 1998 03:07:50 -0600 (CST) Message-ID: <19981104030750.47512@futuresouth.com> Date: Wed, 4 Nov 1998 03:07:50 -0600 From: "Matthew D. Fuller" To: hackers@FreeBSD.ORG Subject: _roff reference? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any reference lying around for _roff -man? Besides the existing man pages, of course. There aren't any helpful manpages I can see, or anything in the doc distribution. Or is this kinda one of those 'here's a cookie, good luck' subjects? Yes, I'm trying to write a man page. Pain is good, right? *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 02:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27660 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 02:05:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA27650 for ; Wed, 4 Nov 1998 02:05:39 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Wed, 4 Nov 1998 21:04:49 +1100 Date: Wed, 4 Nov 1998 21:05:16 +1100 From: Peter Jeremy Subject: MMAP and sync writes (Re: sync writes with softupdates enabled) To: peter@netplex.com.au Cc: hackers@FreeBSD.ORG Message-Id: <98Nov4.210449est.40336@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: >> Note that there is a similar bug in 2.2.x. The fix is similar, but >> needs some thought since there appears to be a problem with the >> parameters to vm_object_page_clean(). In particular, `syncio' is >> defined as boolean_t, as passed as the `waitfor' argument to >> VOP_FSYNC() - which is MNT_ASYNC or MNT_SYNC elsewhere. I haven't >> had the time to work out the correct definitions. > >Use TRUE and FALSE instead of OBJPC_SYNC and 0. I don't think it's that simple. The following is from 2.2.7-RELEASE: Looking at vm_object_page_clean(), all the existing calls use TRUE or FALSE (or 1 or 0, which is equivalent, if less clear). This matches the definition 'boolean_t syncio'. Within vm_object_page_clean(), syncio is only used as: VOP_FSYNC(vp, NULL, syncio, curproc); The problem is that everywhere else, VOP_FSYNC() is called with the third parameter as one of the following: a) MNT_WAIT or MNT_NOWAIT explicitly specified. b) (struct vop_fsync_args).a_waitfor c) the 2nd argument of {fstype}_sync, invoked via VFS_SYNC() and explicitly defined as MNT_WAIT or MNT_NOWAIT in a_waitfor is only assigned from VOP_FSYNC() and is compared against MNT_WAIT/MNT_NOWAIT everywhere except: ffs_inode.c:ffs_update() if (ap->a_waitfor && (ap->a_vp->v_mount->mnt_flag & MNT_ASYNC) == 0) return (bwrite(bp)); lfs_inode.c:lfs_update() error = (ap->a_waitfor & LFS_SYNC ? lfs_vflush(vp) : 0); if(ap->a_waitfor & LFS_SYNC && vp->v_dirtyblkhd.lh_first != NULL) VFS_SYNC() is invoked with the second parameter as one of the following: a) MNT_WAIT or MNT_NOWAIT explicitly specified. b) 1 in lfs_vfsops.c:lfs_unmount() Based on the above, I believe the 4th argument to vm_object_page_clean() should really be an int and all calls should be updated to pass MNT_WAIT or MNT_NOWAIT. These discrepancies would be far more obvious if more of the kernel magic numbers were enum's instead of #defines - the compiler would have some hope of pointing out the inconsistencies. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 02:22:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29821 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 02:22:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.sphere.ru (Sphere-SarnodeNoc-gw.sarnode.ru [194.87.187.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29811 for ; Wed, 4 Nov 1998 02:22:43 -0800 (PST) (envelope-from zau@sphere.ru) Received: by ns.sphere.ru with SMTP id NAA16282 Wed, 4 Nov 1998 13:22:29 +0300 (MSK) Message-ID: <002d01be07dc$6af51a00$1007a8c0@zau.sphere.ru> From: "Zatonski A.U." To: Date: Wed, 4 Nov 1998 13:15:20 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth cfe1b3d5 subscribe freebsd-hackers zau@sphere.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 04:33:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA15472 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 04:33:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA15434 for ; Wed, 4 Nov 1998 04:33:04 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id HAA05403; Wed, 4 Nov 1998 07:32:04 -0500 (EST) Date: Wed, 4 Nov 1998 07:32:04 -0500 (EST) From: Chuck Robey To: "Matthew D. Fuller" cc: hackers@FreeBSD.ORG Subject: Re: _roff reference? In-Reply-To: <19981104030750.47512@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Nov 1998, Matthew D. Fuller wrote: > Is there any reference lying around for _roff -man? Besides the existing > man pages, of course. There aren't any helpful manpages I can see, or > anything in the doc distribution. Or is this kinda one of those 'here's > a cookie, good luck' subjects? > Yes, I'm trying to write a man page. Pain is good, right? Yeah, two good manpages pretty full of examples: mdoc.samples and mdoc. > > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > | FreeBSD; the way computers were meant to be | > * "The only reason I'm burning my candle at both ends, is * > | that I haven't figured out how to light the middle yet."| > * fullermd@futuresouth.com :-} MAtthew Fuller * > | http://keystone.westminster.edu/~fullermd | > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 05:09:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19039 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 05:09:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19021; Wed, 4 Nov 1998 05:09:38 -0800 (PST) (envelope-from Etienne.Debruin@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id OAA31835; Wed, 4 Nov 1998 14:10:18 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa31831; Wed Nov 04 14:10:08 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id OAA16885; Wed, 4 Nov 1998 14:08:31 +0100 Received: (from debruin@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id OAA04022; Wed, 4 Nov 1998 14:11:37 +0100 (CET) (envelope-from debruin) From: Etienne de Bruin Message-Id: <199811041311.OAA04022@borg.kryptokom.de> Subject: interrupt handler discrepancy To: freebsd-hackers@FreeBSD.ORG (Hackers FreeBSD) Date: Wed, 4 Nov 1998 14:11:36 +0100 (CET) Cc: questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i install my interrupt handler using pci_map_int(). when using ioctl call to my pci device driver and issuing an interrupt, the interupt handler gets called - no problem. my crypt device driver gets called from user space in this case. but when using my crypt card together with two network interfaces, when i issue an interrupt, my _intr function does not get called for some reason. my crypt device driver gets called from within the kernel in this case. all i can think is that for some reasons the network cards do splxxx() to such an extent that my interupt handler never gets a chance .. is this possible? please respond to my mail address. eT -- Etienne de Bruin, KryptoKom(R), Germany, http://www.kryptokom.de/ eT@kryptokom.de or edebruin@iname.com +49 241 963 2635(w) "www.harpazo.net/news.html" - Harpazo's Headlines (**** eT), news stories relevant to the Last Days, update daily. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 05:33:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23295 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 05:33:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23286 for ; Wed, 4 Nov 1998 05:33:29 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id VAA00168; Wed, 4 Nov 1998 21:32:48 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199811041332.VAA00168@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Martti Kuparinen cc: hackers@FreeBSD.ORG Subject: Re: Pseudo-device as a LKM In-reply-to: Your message of "Mon, 02 Nov 1998 12:44:53 +0200." <3.0.6.32.19981102124453.02ce8b30@openmail.lmf.ericsson.se> Date: Wed, 04 Nov 1998 21:32:47 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martti Kuparinen wrote: > I want to implement a pseudo-device as LKM. But the question is where > to find a working example? I've looked at e.g. the if_tun device, > but the unload is not successful: > > # modload /lkm/if_tun_mod.o > # modunload -n if_tun_mod > modunload: LMUNLOAD: Device busy > > So please give any pointers. I'm using 2.2.7-R but I could jump into 3.0 > if that's what needed. A couple of things.. There are several classes of LKMs.. With some, the glue is in macros, with others it is generated. The if_tun example you mention is a case of a 'PSEUDO_SET()' module. These do not allow unloading.. Not necessarily because it cannot be done, just because nobody has bothered. A more complete example would be to look at one that has got explicit LKM interface code, and compare that to what is in /usr/include/sys/*. However, if you are thinking longer term, look at 3.0's modules instead. The days of LKM's are numbered in 3.x (for many reasons, which I won't go into here). > Martti Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 06:14:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28814 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 06:14:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28796; Wed, 4 Nov 1998 06:14:23 -0800 (PST) (envelope-from Etienne.Debruin@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id PAA00402; Wed, 4 Nov 1998 15:15:01 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa00398; Wed Nov 04 15:14:54 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id PAA17373; Wed, 4 Nov 1998 15:13:17 +0100 Received: (from debruin@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id PAA04355; Wed, 4 Nov 1998 15:16:25 +0100 (CET) (envelope-from debruin) From: Etienne de Bruin Message-Id: <199811041416.PAA04355@borg.kryptokom.de> Subject: waiting in device driver To: freebsd-hackers@FreeBSD.ORG (Hackers FreeBSD), questions@FreeBSD.ORG (FreeBSD Mailing List) Date: Wed, 4 Nov 1998 15:16:24 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG which is the best way to wait for the DMA routines of a card to complete? should one go in a while loop and test a flag (which gets set by the interrupt handler once completed) or should i go for the tsleep option? eT -- Etienne de Bruin, KryptoKom(R), Germany, http://www.kryptokom.de/ eT@kryptokom.de or edebruin@iname.com +49 241 963 2635(w) "i'll pluck the thorns out from your feet, you and me" - rem, be mine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 06:21:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00335 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 06:21:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA00317; Wed, 4 Nov 1998 06:21:20 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA18582; Wed, 4 Nov 1998 13:19:22 +0100 From: Luigi Rizzo Message-Id: <199811041219.NAA18582@labinfo.iet.unipi.it> Subject: Re: waiting in device driver To: Etienne.Debruin@KryptoKom.DE (Etienne de Bruin) Date: Wed, 4 Nov 1998 13:19:22 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <199811041416.PAA04355@borg.kryptokom.de> from "Etienne de Bruin" at Nov 4, 98 03:16:05 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > which is the best way to wait for the DMA routines of a card to complete? > should one go in a while loop and test a flag (which gets set by the > interrupt handler once completed) or should i go for the tsleep option? do you need to ask ??? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 06:53:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06272 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 06:53:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06260 for ; Wed, 4 Nov 1998 06:53:09 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id PAA11221; Wed, 4 Nov 1998 15:52:37 +0100 (MET) Date: Wed, 4 Nov 1998 15:52:36 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Luigi Rizzo cc: Etienne.Debruin@KryptoKom.DE, FreeBSD hackers mailing list Subject: Re: waiting in device driver In-Reply-To: <199811041219.NAA18582@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Nov 1998, Luigi Rizzo wrote: > > which is the best way to wait for the DMA routines of a card to complete? > > should one go in a while loop and test a flag (which gets set by the > > interrupt handler once completed) or should i go for the tsleep option? > > do you need to ask ??? On the scale of one to $stupid, this answer scores fairly $stupid. The answer might be (but then again I haven't followed the thread): In Linux you would, yes. In FreeBSD, if you expect that the delay would be more than a couple of microseconds, you would call tsleep, see man tsleep Cheers, Nick Loose'95: USB mouse installation: 2 hours, 5 reboots and no joy. FreeBSD: RAID array installation: 10 minutes, 0 reboots and lots. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:19:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26524 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:19:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26508 for ; Wed, 4 Nov 1998 09:19:52 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id MAA14713 for ; Wed, 4 Nov 1998 12:19:41 -0500 (EST) Date: Wed, 4 Nov 1998 12:19:41 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: How sync() gets called every 30 seconds? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Can anyone tell me where in the source code the sync() (in vfs_syscalls.c) is set up to be called every 30 seconds? Thanks a lot. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:38:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29779 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:38:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29773 for ; Wed, 4 Nov 1998 09:38:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA00699 for ; Wed, 4 Nov 1998 09:38:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811041738.JAA00699@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: I2O now vaguely open for business Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Nov 1998 09:38:23 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See the "registered developer" section at www.i2osig.org. Nice to see them caving in to pressure. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:39:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00114 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:39:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29998 for ; Wed, 4 Nov 1998 09:39:44 -0800 (PST) (envelope-from ron@zappa.demon.nl) Received: from [195.173.232.30] (helo=zappa.demon.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 0zb6tg-0000nY-00 for freebsd-hackers@FreeBSD.ORG; Wed, 4 Nov 1998 17:39:09 +0000 Message-ID: <3640918F.5608FE2F@zappa.demon.nl> Date: Wed, 04 Nov 1998 18:40:31 +0100 From: Ron Klinkien X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:42:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00581 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:42:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00412 for ; Wed, 4 Nov 1998 09:42:47 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id BAA01178; Thu, 5 Nov 1998 01:42:20 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199811041742.BAA01178@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: zhihuizhang cc: hackers Subject: Re: How sync() gets called every 30 seconds? In-reply-to: Your message of "Wed, 04 Nov 1998 12:19:41 EST." Date: Thu, 05 Nov 1998 01:42:19 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG zhihuizhang wrote: > > Hi, Can anyone tell me where in the source code the sync() (in > vfs_syscalls.c) is set up to be called every 30 seconds? > > Thanks a lot. In 2.x, there is a process called 'update' that sleeps for 30 seconds and calls sync each time. In 3.x, it is different because of softupdates and not easy to explain :-). For non-softupdates mounts, a 'syncer vnode' is allocated at mount time. It has got some vnode operations including sync_fsync(). This vnode is inserted into the work queue for the new 'syncer' process, and is interleaved with other mounts. For non-softupdates, each filesystem is periodically sync'ed via sync_fsync once every 30 seconds with a fairly even pacing. Theoretically, if you had 3 filesystems, one would get sync'ed every 10 seconds so they were all done in 30, but it doesn't work out that exact. For softupdates, much more is done by the syncer process, it processes "dirty" vnodes periodically to maintain dependency information and maintain metadata write order. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00950 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:45:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00945 for ; Wed, 4 Nov 1998 09:45:51 -0800 (PST) (envelope-from Reinier.Bezuidenhout@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id SAA03023 for ; Wed, 4 Nov 1998 18:46:25 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa03014; Wed Nov 04 18:46:21 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id SAA18649 for ; Wed, 4 Nov 1998 18:44:45 +0100 Original: Received: (from bez@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id SAA05132 for freebsd-hackers@freebsd.org; Wed, 4 Nov 1998 18:47:56 +0100 (CET) (envelope-from bez) From: Reinier Bezuidenhout Message-Id: <199811041747.SAA05132@borg.kryptokom.de> Subject: Malloc in the kernel To: freebsd-hackers@FreeBSD.ORG Date: Wed, 4 Nov 1998 18:47:55 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... If I want to malloc really large space in the kernel, say from 2k up to 1M or maybe more .... wat parameter should 'n give to malloc ?? malloc(1000, ????, M_WAITOK); ? M_DEVBUF if it is possible :) Thanx Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01960 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:52:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01837 for ; Wed, 4 Nov 1998 09:52:00 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id SAA13138; Wed, 4 Nov 1998 18:47:14 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id SAA02575; Wed, 4 Nov 1998 18:46:27 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199811041746.SAA02575@semyam.dinoco.de> To: zhihuizhang cc: hackers , seggers@semyam.dinoco.de Subject: Re: How sync() gets called every 30 seconds? In-reply-to: Your message of "Wed, 04 Nov 1998 12:19:41 EST." Date: Wed, 04 Nov 1998 18:46:27 +0100 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, Can anyone tell me where in the source code the sync() (in > vfs_syscalls.c) is set up to be called every 30 seconds? In vfs_subr.c with a SYSINIT_KT() and an associated struct. This creates a process which consists of sched_sync. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:54:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02574 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:54:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from stone.locallink.net (Stone.LocalLink.Net [204.71.156.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02568 for ; Wed, 4 Nov 1998 09:54:15 -0800 (PST) (envelope-from kpitcher@locallink.net) Received: from Diamond (Diamond.LocalLink.Net [204.71.156.68]) by stone.locallink.net (8.8.8/8.8.7) with SMTP id NAA24300 for ; Wed, 4 Nov 1998 13:00:45 -0500 (EST) (envelope-from kpitcher@locallink.net) From: "Keith Pitcher" To: Subject: RE: SMC9432TX driver (tx) users Date: Wed, 4 Nov 1998 12:53:37 -0500 Message-ID: <000001be081c$0d0524e0$449c47cc@Diamond.LocalLink.Net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <199811041414.GAA28825@hub.freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had similar timeout problems in the past. I had a box of 5 of these cards, put them in 3 different 2.2.6 systems all similarly configured. They were all running at 100Mbps. One of the machines - the most heavily used - would report a device timeout a few times a day. I put in another tx card and the problem stopped occuring. (I ended up putting the problematic card in a win box and it's worked fine for the past number of months.) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Keith Pitcher kpitcher@locallink.net LocalLink - Your Local Link to the World http://www.locallink.net 800 687-2202 616 424-4999 Fax : 616 424-4995 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 09:57:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02853 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 09:57:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA02839 for ; Wed, 4 Nov 1998 09:56:55 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id QAA19119; Wed, 4 Nov 1998 16:54:55 +0100 From: Luigi Rizzo Message-Id: <199811041554.QAA19119@labinfo.iet.unipi.it> Subject: Re: How sync() gets called every 30 seconds? To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Wed, 4 Nov 1998 16:54:54 +0100 (MET) Cc: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG, seggers@semyam.dinoco.de In-Reply-To: <199811041746.SAA02575@semyam.dinoco.de> from "Stefan Eggers" at Nov 4, 98 06:46:08 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, Can anyone tell me where in the source code the sync() (in > > vfs_syscalls.c) is set up to be called every 30 seconds? > > In vfs_subr.c with a SYSINIT_KT() and an associated struct. This > creates a process which consists of sched_sync. speaking of this... is this parametrized ? On a laptop, i wonder if syncing every 30s while doing ordinary activities (e.g. editing) defeats completely the disk auto-shutdown routines. Because power failures are less frequent (i hope!) in that environment, is there any other reason to have frequent SYNCs ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 10:06:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04139 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:06:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04132 for ; Wed, 4 Nov 1998 10:06:47 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id KAA01814; Wed, 4 Nov 1998 10:07:46 -0800 (PST) Message-Id: <199811041807.KAA01814@implode.root.com> To: Reinier Bezuidenhout cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Malloc in the kernel In-reply-to: Your message of "Wed, 04 Nov 1998 18:47:55 +0100." <199811041747.SAA05132@borg.kryptokom.de> From: David Greenman Reply-To: dg@root.com Date: Wed, 04 Nov 1998 10:07:46 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If I want to malloc really large space in the kernel, say from >2k up to 1M or maybe more .... wat parameter should 'n >give to malloc ?? > > malloc(1000, ????, M_WAITOK); > >? M_DEVBUF > >if it is possible :) None of the above since allocations that large will likely be fatal if the kmem_map is even a little fragmented. You could do it at system startup time, however. Anyway, the type is not important. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 10:28:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06722 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:28:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06717 for ; Wed, 4 Nov 1998 10:28:38 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id LAA29219; Wed, 4 Nov 1998 11:28:20 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd029156; Wed Nov 4 11:28:10 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id LAA09234; Wed, 4 Nov 1998 11:28:07 -0700 (MST) From: Terry Lambert Message-Id: <199811041828.LAA09234@usr07.primenet.com> Subject: Re: kld screensavers To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 4 Nov 1998 18:28:06 +0000 (GMT) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, hackers@FreeBSD.ORG, karpen@ocean.campus.luth.se In-Reply-To: from "Daniel O'Connor" at Nov 4, 98 11:11:53 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am not sure if we want to have this kind of screen saver stack. It > > will complicate things a lot: multiple saver module management, > > priority management, flag checking... Is this worth the effort? > > It depends how complicated it is to implement. > > If it works, then hooray, but if its too hard, then a 'normal' system would be > OK.. > > Besides which, its a neat idea, and would give a good example of code > for other people to use :) I personally prefer that code that was posted about on the news group back in 1995, and was available only directly from the author, that would run AfterDark(tm) modules on top of FreeBSD/Linux. I still have an old 486 system that runs the "Spock and the Horta" screen saver. If you are going to design a new screen saver framework, you could do worse than to be ABI compatible with Windows 95. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 10:31:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07218 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:31:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07212; Wed, 4 Nov 1998 10:31:37 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id LAA00928; Wed, 4 Nov 1998 11:31:28 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd000907; Wed Nov 4 11:31:23 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id LAA09360; Wed, 4 Nov 1998 11:31:22 -0700 (MST) From: Terry Lambert Message-Id: <199811041831.LAA09360@usr07.primenet.com> Subject: Re: waiting in device driver To: Etienne.Debruin@KryptoKom.DE (Etienne de Bruin) Date: Wed, 4 Nov 1998 18:31:22 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <199811041416.PAA04355@borg.kryptokom.de> from "Etienne de Bruin" at Nov 4, 98 03:16:24 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > which is the best way to wait for the DMA routines of a card to complete? > should one go in a while loop and test a flag (which gets set by the > interrupt handler once completed) or should i go for the tsleep option? Use tsleep. You do not want to buzz-loop on a condition variable, since it would prevent the processor from doing other useful work while your device was busy. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 10:35:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07555 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:35:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07543 for ; Wed, 4 Nov 1998 10:35:27 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA06422; Wed, 4 Nov 1998 11:35:18 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd006406; Wed Nov 4 11:35:14 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id LAA09570; Wed, 4 Nov 1998 11:35:13 -0700 (MST) From: Terry Lambert Message-Id: <199811041835.LAA09570@usr07.primenet.com> Subject: Re: Malloc in the kernel To: Reinier.Bezuidenhout@KryptoKom.DE (Reinier Bezuidenhout) Date: Wed, 4 Nov 1998 18:35:12 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199811041747.SAA05132@borg.kryptokom.de> from "Reinier Bezuidenhout" at Nov 4, 98 06:47:55 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I want to malloc really large space in the kernel, say from > 2k up to 1M or maybe more .... wat parameter should 'n > give to malloc ?? > > malloc(1000, ????, M_WAITOK); > > ? M_DEVBUF > > if it is possible :) It depends on what you intend to use the memory for. Ideally, you would be prepared to take a page fault, and would allocate pageable memory backed by swap so that you didn't exhaust the physical memory in the system. In general, the kernel is better at deciding what memory it needs when it needs it than a kernel code author. You either trust the locality of reference model upon which VM systems are based, or you don't. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 10:41:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08492 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:41:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08482 for ; Wed, 4 Nov 1998 10:40:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01085; Wed, 4 Nov 1998 10:37:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811041837.KAA01085@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: doconnor@gsoft.com.au (Daniel O'Connor), yokota@zodiac.mech.utsunomiya-u.ac.jp, hackers@FreeBSD.ORG, karpen@ocean.campus.luth.se Subject: Re: kld screensavers In-reply-to: Your message of "Wed, 04 Nov 1998 18:28:06 GMT." <199811041828.LAA09234@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Nov 1998 10:37:26 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If you are going to design a new screen saver framework, you could > do worse than to be ABI compatible with Windows 95. Hah. Win95 screen savers are just Win95 fullscreen programs. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 10:50:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10062 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:50:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10056 for ; Wed, 4 Nov 1998 10:50:34 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA17537; Wed, 4 Nov 1998 11:50:24 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd017454; Wed Nov 4 11:50:12 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id LAA10454; Wed, 4 Nov 1998 11:50:11 -0700 (MST) From: Terry Lambert Message-Id: <199811041850.LAA10454@usr07.primenet.com> Subject: Re: Documentation upgrade: where are the other humans? To: ziggy@wopr.inetu.net (Ryan Ziegler) Date: Wed, 4 Nov 1998 18:50:11 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG, tlambert@primenet.com In-Reply-To: from "Ryan Ziegler" at Nov 3, 98 04:53:01 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You know, I've often wondered why, given that there are people > > who will code for the fun of it, why none of the Free Software > > projects have crossed disciplines. > > > > You'd think that there would be English Majors and/or Technical > > Writers who would write documentation for the fun of it, and > > Marketing people who would do marketing for the fun of it, and > > Graphic Artists who would do commercial art for the fun of it... > > When not getting paid, programmers tend to code what they find > interesting. We can say the same thing for writers when writing. I would > say technical documentation is not the most exciting literary form, nor > are the arguments for kmem_free() the most exciting subject matter. > > What we need are technical writers who feel a severe allegiance to > FreeBSD. Or people who get off on techinical writing, or a professor with an allegiance to FreeBSD in charge of a Technical Writing class. I have to say that there exist people who actually enjoy doing things that the rest of us would find about as enjoyable as home dentistry (those of you with capped teeth, imagine removing your caps with an awl). I have a sister who happens to enjoy double-column bookkeeping. It takes all kinds... I also think that it's very likely that someone who had to take a technical writing class for their CS/CIS/MIS/BIS degree would have classmates who were English Majors or whatever, also looking for writing projects, and that it would be a good idea to encourage them suggesting FreeBSD documentation to their classmates as a potential "project fodder gold mine". I know that if I were to adjunct teach a technical writing class, I'd be please as punch if I could find a never-ending supply of projects, all in the same general problem space; it'd make it a hell of a lot easier to grade on a curve. > > Are programmers the only people who enjoy what they intend to make > > their life's work? > > No, but if you enjoy programming, society definately rewards. Only if you don't suck. 8-). > > Maybe it's just that the majority of people are too busy sitting > > on their butts hacking code in cave-like computer labs to talk > > to people in other departments on campus? > > You're not suggesting that we're a tad clannish, are you? :) Well, this *is* a "free software" project, not a "free product" project... it's kind of self-limiting in its involvement of people not that interested in producing software. The Linux Documentation project has that whole "Young Communist" thing going for it... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 10:54:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11228 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 10:54:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11211 for ; Wed, 4 Nov 1998 10:54:42 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA14777; Wed, 4 Nov 1998 11:54:33 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd014749; Wed Nov 4 11:54:32 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id LAA10702; Wed, 4 Nov 1998 11:54:28 -0700 (MST) From: Terry Lambert Message-Id: <199811041854.LAA10702@usr07.primenet.com> Subject: Re: How sync() gets called every 30 seconds? To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 4 Nov 1998 18:54:28 +0000 (GMT) Cc: seggers@semyam.dinoco.de, bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199811041554.QAA19119@labinfo.iet.unipi.it> from "Luigi Rizzo" at Nov 4, 98 04:54:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hi, Can anyone tell me where in the source code the sync() (in > > > vfs_syscalls.c) is set up to be called every 30 seconds? > > > > In vfs_subr.c with a SYSINIT_KT() and an associated struct. This > > creates a process which consists of sched_sync. > > speaking of this... is this parametrized ? It's parameterized. > On a laptop, i wonder if > syncing every 30s while doing ordinary activities (e.g. editing) defeats > completely the disk auto-shutdown routines. Because power failures are > less frequent (i hope!) in that environment, is there any other reason > to have frequent SYNCs ? There's no reason for sync's at all, if your word processor's pages are all paged in, and you don't have "autosave" turned on. If you have "autosave" on, it's going to happen whether you want it to or not. d in, and you don't have "autosave" turned on. If you have "autosave" on, it's going to happen whether you want it to or not. There may be a case of the access time being updated for executable files being paged from... I seem to remember looking into this very issue a while back and seeing something along those lines. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 12:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26606 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 12:21:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26601 for ; Wed, 4 Nov 1998 12:21:37 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id PAA19474; Wed, 4 Nov 1998 15:24:26 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Wed, 4 Nov 1998 15:24:26 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How sync() gets called every 30 seconds? In-Reply-To: <199811041854.LAA10702@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There may be a case of the access time being updated for executable > files being paged from... I seem to remember looking into this very > issue a while back and seeing something along those lines. > > I'm quite sure someone fixed this a few months back in 3.0, I'm quite sure it was posted about in the lists. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 16:14:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10187 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 16:14:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10181 for ; Wed, 4 Nov 1998 16:14:04 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id BAA06026; Thu, 5 Nov 1998 01:08:10 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199811050008.BAA06026@ocean.campus.luth.se> Subject: Re: kld screensavers In-Reply-To: <199811030302.MAA01789@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Nov 3, 98 12:02:37 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 5 Nov 1998 01:08:10 +0100 (CET) Cc: hackers@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Kazutaka YOKOTA: > >I haven't looked at the current code, I'm affraid, so go easy on me. > >Example: > > > >Three screensavers: (say default prio is 5) > > > >lock: prio 1, 10 minutes, fallthrough (Demands password...) > >green: prio 4, 20 minutes (Turn screen off) > >stars: prio 5, 5 minutes (Twinkle, twinkle, little star) > [...] > > I am not sure if we want to have this kind of screen saver stack. It > will complicate things a lot: multiple saver module management, > priority management, flag checking... Is this worth the effort? > > If you want to lock the vty with password, you can always use > `lock(1)'. And it is easy to modify screen savers, `start' or > whatever, and add them the ability to turn off the display after set > period (the screen saver can check system time when it is called > periodically); it will be far easier than implementing the screen > saver stack thingy. Yes, but I think I could offer to write the stack. I still haven't looked at the current code, and i think I should before I attempt such a project, but the stack itself is a very minor problem, I think. It's just coding. :-) I imagine something with an interface like: called_periodically_from_syscons(); called_by_syscons_at_char_pressed_when_in_screensaver_mode(); register_screensaver(); unregister_screensaver(); list_screensavers(); And have a couple of functions which gets called in the screensavers that are registered, when appropriate. Again I haven't read the code yet, but I guess the screensavers now just attack the hardware directly. This seems undesirable, and I think for this to work well you would have to make a couple of functions available to the screensavers. Syscons should provide something like: screensaver_set_mode(); /* normal (no saver), text, graphics, green */ screensaver_put_char(); /* for text mode */ screensaver_draw_line(); /* for graphics mode */ Umm... I actually can't think of anything else that would be needed. If the screensavers were written to use this interface then syscons would also know exactly what has happened to the screen, and would therefor put it back easilly, when called with a screensaver_set_mode(normal), I'm guessing. Umm... All this is not really well anchored in reality yet, but... comments are welcome. What do Søren and Kazutaka think? Anyone else? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 17:25:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19048 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 17:25:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19043 for ; Wed, 4 Nov 1998 17:25:22 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id RAA03094; Wed, 4 Nov 1998 17:24:51 -0800 (PST) Message-Id: <199811050124.RAA03094@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo Cc: seggers@semyam.dinoco.de (Stefan Eggers), bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: How sync() gets called every 30 seconds? In-Reply-To: Your message of "Wed, 04 Nov 1998 16:54:54 +0100." <199811041554.QAA19119@labinfo.iet.unipi.it> X-Url: http://www.isi.edu/~faber Date: Wed, 04 Nov 1998 17:24:51 -0800 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Luigi Rizzo wrote: >speaking of this... is this [update's sync freq.] parametrized ? On a >laptop, i wonder if syncing every 30s while doing ordinary activities >(e.g. editing) defeats completely the disk auto-shutdown routines. The man page from 2.2.7-RELEASE says: DESCRIPTION The update kernel process helps protect the integrity of disk volumes by flushing volatile cached filesystem data to disk. This is done at thirty second intervals by default. The time period may be changed by using sysctl(8) to modify the kern.update variable. So, it looks like it is. I haven't tried it. YMMV. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNkD+YYb4eisfQ5rpAQHbDAQAg7yqokDQsEywFKAd+w263+Iqe8mC8vzB OoLJUNE4d3izY7rK4yHGMggzPtoG3pCXs2iInmvquTl+Xy17pXfaEwY9kimEcOn/ 1ZN35nN5SMpFGnRe39bgnF0KHjiap6nGh81xjh5lR/YQyTCuRgqI9quh7178yEwa +hfbH/YEFDY= =POyg -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 17:55:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23079 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 17:55:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23070 for ; Wed, 4 Nov 1998 17:55:22 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA06130; Thu, 5 Nov 1998 12:24:54 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA06879; Thu, 5 Nov 1998 12:24:54 +1030 (CST) Message-ID: <19981105122453.B784@freebie.lemis.com> Date: Thu, 5 Nov 1998 12:24:53 +1030 From: Greg Lehey To: Etienne de Bruin , Hackers FreeBSD Subject: Re: waiting in device driver References: <199811041416.PAA04355@borg.kryptokom.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811041416.PAA04355@borg.kryptokom.de>; from Etienne de Bruin on Wed, Nov 04, 1998 at 03:16:24PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 4 November 1998 at 15:16:24 +0100, Etienne de Bruin wrote: > which is the best way to wait for the DMA routines of a card to complete? > should one go in a while loop and test a flag (which gets set by the > interrupt handler once completed) or should i go for the tsleep option? Please don't copy -questions on this kind of question. -hackers is the appropriate forum. How long are you expecting to wait? If you're transferring from external storage such as disk or tape, tsleep() is your only option, but you can only use it from the top half of a driver. If you're talking to an electronic device which can reasonably be expected to respond in a few (< 10) microseconds, you might get away with a loop, but you'd have to limit it to a certain number of iterations and give up if it didn't happen in that time: otherwise you could cause hangs. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 19:16:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05390 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 19:16:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05383 for ; Wed, 4 Nov 1998 19:16:47 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA06544; Thu, 5 Nov 1998 13:46:35 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA16143; Thu, 5 Nov 1998 13:46:34 +1030 (CST) Message-ID: <19981105134634.N784@freebie.lemis.com> Date: Thu, 5 Nov 1998 13:46:34 +1030 From: Greg Lehey To: Terry Lambert , Reinier Bezuidenhout Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Malloc in the kernel References: <199811041747.SAA05132@borg.kryptokom.de> <199811041835.LAA09570@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811041835.LAA09570@usr07.primenet.com>; from Terry Lambert on Wed, Nov 04, 1998 at 06:35:12PM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 4 November 1998 at 18:35:12 +0000, Terry Lambert wrote: >> If I want to malloc really large space in the kernel, say from >> 2k up to 1M or maybe more .... wat parameter should 'n >> give to malloc ?? >> >> malloc(1000, ????, M_WAITOK); >> >> ? M_DEVBUF >> >> if it is possible :) > > It depends on what you intend to use the memory for. > > Ideally, you would be prepared to take a page fault, and would > allocate pageable memory backed by swap so that you didn't > exhaust the physical memory in the system. > > In general, the kernel is better at deciding what memory it needs > when it needs it than a kernel code author. You either trust > the locality of reference model upon which VM systems are based, > or you don't. Assuming that fits his needs, what's the answer? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 19:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06072 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 19:21:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05904 for ; Wed, 4 Nov 1998 19:21:36 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA04278; Wed, 4 Nov 1998 19:21:25 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma004274; Wed Nov 4 19:21:02 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA07965; Wed, 4 Nov 1998 19:21:02 -0800 (PST) From: Archie Cobbs Message-Id: <199811050321.TAA07965@bubba.whistle.com> Subject: Re: scanf in the kernel? In-Reply-To: <199810302106.NAA02040@dingo.cdrom.com> from Mike Smith at "Oct 30, 98 01:06:10 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 4 Nov 1998 19:21:01 -0800 (PST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > Seems like the kernel was missing memmove(), memcpy(), and/or memset() > > at some point. I like using these better than bcopy()/bzero() because > > they are more ANSI and portable... > > I think there'd be some BSD traditionalist sentiment here. But you can > fake them up easily enough, so if there's a compelling need this could > be done, yes. Not memset() .. I think the other way around is better.. bzero() and bcmp() should be defined in terms of the ANSI functions for backward compatibility.. :-) > > And what about snprintf()? Would that be hard to add to the existing > > printf() functionality? The kernel is definitely one place you > > don't want to overflow string buffers... > > I don't know. Want to take a quick look and tell us? Turns out it's quite easy.. patch below. Also filed as a feature request: kern/8577. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Index: kern/subr_prf.c =================================================================== RCS file: /cvs/freebsd/src/sys/kern/subr_prf.c,v retrieving revision 1.50 diff -u -r1.50 subr_prf.c --- subr_prf.c 1998/09/06 06:25:04 1.50 +++ subr_prf.c 1998/11/05 03:10:12 @@ -68,6 +68,8 @@ struct putchar_arg {int flags; struct tty *tty; }; static void putchar __P((int ch, void *arg)); static char *ksprintn __P((u_long num, int base, int *len)); +static void snprintf_func __P((int ch, void *arg)); +struct snprintf_arg { char *buf; size_t remain; }; static int consintr = 1; /* Ok to handle console interrupts? */ static int msgbufmapped; /* Set when safe to use msgbuf */ @@ -326,6 +328,47 @@ retval = kvprintf(cfmt, NULL, (void *)buf, 10, ap); buf[retval] = '\0'; return retval; +} + +/* + * Scaled down version of snprintf(3). + */ +int +snprintf(char *buf, size_t max, const char *cfmt, ...) +{ + int retval; + va_list ap; + + va_start(ap, cfmt); + retval = vsnprintf(buf, max, cfmt, ap); + va_end(ap); + return retval; +} + +/* + * Scaled down version of vsnprintf(3). + */ +int +vsnprintf(char *buf, size_t size, const char *cfmt, va_list ap) +{ + struct snprintf_arg info = { buf, size }; + int retval; + + retval = kvprintf(cfmt, snprintf_func, &info, 10, ap); + if (info.remain >= 1) + *info.buf++ = '\0'; + return retval; +} + +static void +snprintf_func(int ch, void *arg) +{ + struct snprintf_arg *const info = (struct snprintf_arg *) arg; + + if (info->remain >= 2) { + *info->buf++ = ch; + info->remain--; + } } /* Index: sys/systm.h =================================================================== RCS file: /cvs/freebsd/src/sys/sys/systm.h,v retrieving revision 1.78 diff -u -r1.78 systm.h --- systm.h 1998/10/30 05:41:15 1.78 +++ systm.h 1998/11/05 03:10:13 @@ -108,6 +108,8 @@ void logwakeup __P((void)); int printf __P((const char *, ...)) __printflike(1, 2); int sprintf __P((char *buf, const char *, ...)) __printflike(2, 3); +int snprintf __P((char *, size_t, const char *, ...)) __printflike(3, 4); +int vsnprintf __P((char *, size_t, const char *, _BSD_VA_LIST_)) __printflike(3, 0); void uprintf __P((const char *, ...)) __printflike(1, 2); void vprintf __P((const char *, _BSD_VA_LIST_)) __printflike(1, 0); int vsprintf __P((char *buf, const char *, _BSD_VA_LIST_)) __printflike(2, 0); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 20:52:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15269 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 20:52:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from banshee.cs.uow.edu.au (banshee.cs.uow.edu.au [130.130.188.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15251 for ; Wed, 4 Nov 1998 20:52:10 -0800 (PST) (envelope-from ncb05@banshee.cs.uow.edu.au) Received: (from ncb05@localhost) by banshee.cs.uow.edu.au (8.9.1a/8.9.1) id PAA04055; Thu, 5 Nov 1998 15:51:57 +1100 (EST) Date: Thu, 5 Nov 1998 15:51:57 +1100 (EST) From: Nicholas Charles Brawn X-Sender: ncb05@banshee.cs.uow.edu.au To: freebsd-hackers@FreeBSD.ORG Subject: NDINIT probs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In execve() i'm attempting an operation similar to the following: struct nameidata *ndp; NDINIT(ndp, LOOKUP, NOCACHE, UIO_USERSPACE, p->p_comm, p->p_pptr); error = namei(ndp) ... I keep getting an error each time i call namei(). Anyone able to hazard a guess (or know) what I'm doing wrong? Cheers, Nick -- Email: ncb05@uow.edu.au - http://rabble.uow.edu.au/~nick Key fingerprint = DE 30 33 D3 16 91 C8 8D A7 F8 70 03 B7 77 1A 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 20:56:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15575 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 20:56:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15569 for ; Wed, 4 Nov 1998 20:56:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA04156; Wed, 4 Nov 1998 20:54:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811050454.UAA04156@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nicholas Charles Brawn cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NDINIT probs In-reply-to: Your message of "Thu, 05 Nov 1998 15:51:57 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Nov 1998 20:54:59 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In execve() i'm attempting an operation similar to the following: > > struct nameidata *ndp; > NDINIT(ndp, LOOKUP, NOCACHE, UIO_USERSPACE, p->p_comm, p->p_pptr); > error = namei(ndp) > ... > > I keep getting an error each time i call namei(). Anyone able to hazard > a guess (or know) what I'm doing wrong? Not telling us what the error is? Not checking back through namei() to find out where the error comes from? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 21:34:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18088 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 21:34:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18069 for ; Wed, 4 Nov 1998 21:34:24 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id AAA19223; Thu, 5 Nov 1998 00:34:11 -0500 (EST) (envelope-from luoqi) Date: Thu, 5 Nov 1998 00:34:11 -0500 (EST) From: Luoqi Chen Message-Id: <199811050534.AAA19223@lor.watermarkgroup.com> To: freebsd-hackers@FreeBSD.ORG, ncb05@uow.edu.au Subject: Re: NDINIT probs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In execve() i'm attempting an operation similar to the following: > > struct nameidata *ndp; > NDINIT(ndp, LOOKUP, NOCACHE, UIO_USERSPACE, p->p_comm, p->p_pptr); ^^^^^^^^^^^^^ ^^^^^^^^^ p->p_comm is in kernel space, use UIO_SYSSPACE instead. > error = namei(ndp) > ... > > I keep getting an error each time i call namei(). Anyone able to hazard > a guess (or know) what I'm doing wrong? > > Cheers, > Nick > > -- > Email: ncb05@uow.edu.au - http://rabble.uow.edu.au/~nick > Key fingerprint = DE 30 33 D3 16 91 C8 8D A7 F8 70 03 B7 77 1A 2A > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 21:55:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19691 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 21:55:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from banshee.cs.uow.edu.au (banshee.cs.uow.edu.au [130.130.188.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19683 for ; Wed, 4 Nov 1998 21:55:48 -0800 (PST) (envelope-from ncb05@banshee.cs.uow.edu.au) Received: (from ncb05@localhost) by banshee.cs.uow.edu.au (8.9.1a/8.9.1) id QAA15310; Thu, 5 Nov 1998 16:55:11 +1100 (EST) Date: Thu, 5 Nov 1998 16:55:11 +1100 (EST) From: Nicholas Charles Brawn X-Sender: ncb05@banshee.cs.uow.edu.au To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NDINIT probs In-Reply-To: <199811050454.UAA04156@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Nov 1998, Mike Smith wrote: : Not telling us what the error is? : : Not checking back through namei() to find out where the error comes : from? At the time of writing I hadn't thought to log the error as I thought it was primarily a syntax error on my part. I'll do it again and see what gets returned. Nick -- Email: ncb05@uow.edu.au - http://rabble.uow.edu.au/~nick Key fingerprint = DE 30 33 D3 16 91 C8 8D A7 F8 70 03 B7 77 1A 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 22:00:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19979 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 22:00:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from banshee.cs.uow.edu.au (banshee.cs.uow.edu.au [130.130.188.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19971 for ; Wed, 4 Nov 1998 22:00:01 -0800 (PST) (envelope-from ncb05@banshee.cs.uow.edu.au) Received: (from ncb05@localhost) by banshee.cs.uow.edu.au (8.9.1a/8.9.1) id QAA15447; Thu, 5 Nov 1998 16:56:08 +1100 (EST) Date: Thu, 5 Nov 1998 16:56:08 +1100 (EST) From: Nicholas Charles Brawn X-Sender: ncb05@banshee.cs.uow.edu.au To: Luoqi Chen cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NDINIT probs In-Reply-To: <199811050534.AAA19223@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 5 Nov 1998, Luoqi Chen wrote: : > In execve() i'm attempting an operation similar to the following: : > : > struct nameidata *ndp; : > NDINIT(ndp, LOOKUP, NOCACHE, UIO_USERSPACE, p->p_comm, p->p_pptr); : ^^^^^^^^^^^^^ ^^^^^^^^^ : p->p_comm is in kernel space, use UIO_SYSSPACE instead. Thanks. I'll try that and see if it works. Nick -- Email: ncb05@uow.edu.au - http://rabble.uow.edu.au/~nick Key fingerprint = DE 30 33 D3 16 91 C8 8D A7 F8 70 03 B7 77 1A 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 4 22:01:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20112 for freebsd-hackers-outgoing; Wed, 4 Nov 1998 22:01:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20107 for ; Wed, 4 Nov 1998 22:01:47 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA25805 for ; Thu, 5 Nov 1998 16:31:35 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 05 Nov 1998 16:31:34 +1030 (CST) From: "Daniel O'Connor" To: freebsd-hackers@FreeBSD.ORG Subject: Mysterious delays in processes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We have a tcl script which runs a C program and passes it various parameters and expects an ACK/NACK response from it, and if it doesn't get it it complains. We are having a problem that the C program is getting paused for several seconds in apparently random places. Does anyone have any idea what could be causing the problem? I realise the description is kind of sparse :) Its happening on 2.2.7 machines with the CAM patch applied.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 00:31:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04565 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 00:31:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles186.castles.com [208.214.165.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04544; Thu, 5 Nov 1998 00:31:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA00972; Thu, 5 Nov 1998 00:30:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811050830.AAA00972@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Etienne de Bruin cc: freebsd-hackers@FreeBSD.ORG (Hackers FreeBSD), questions@FreeBSD.ORG Subject: Re: interrupt handler discrepancy In-reply-to: Your message of "Wed, 04 Nov 1998 14:11:36 +0100." <199811041311.OAA04022@borg.kryptokom.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 00:30:26 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i install my interrupt handler using pci_map_int(). > > when using ioctl call to my pci device driver and issuing an interrupt, > the interupt handler gets > called - no problem. my crypt device driver gets called from user space > in this case. > > but when using my crypt card together with two network interfaces, when > i issue an interrupt, my _intr function does not get called for some > reason. my crypt device driver gets called from within the kernel in this > case. > > all i can think is that for some reasons the network cards do splxxx() > to such an extent that my interupt handler never gets a chance .. is this > possible? No. It's possible that your test is not seeing that your interrrupt is being called, but shared interrupts are known to work (albeit inefficiently). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 00:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04587 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 00:31:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04567 for ; Thu, 5 Nov 1998 00:31:12 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA15625; Thu, 5 Nov 1998 09:30:45 +0100 (MET) Date: Thu, 5 Nov 1998 09:30:43 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Reinier Bezuidenhout cc: FreeBSD hackers mailing list Subject: Re: Malloc in the kernel In-Reply-To: <199811041747.SAA05132@borg.kryptokom.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG DEFINE_MALLOC(M_MYMEM, "My mem", "My Memory (large)") (grep for it in the kernel sources, see also sys/malloc.h) and use that name. Nick > If I want to malloc really large space in the kernel, say from > 2k up to 1M or maybe more .... wat parameter should 'n > give to malloc ?? > > malloc(1000, ????, M_WAITOK); > > ? M_DEVBUF > > if it is possible :) > > Thanx > Reinier > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 00:59:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07935 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 00:59:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles186.castles.com [208.214.165.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07910 for ; Thu, 5 Nov 1998 00:59:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA01153; Thu, 5 Nov 1998 00:57:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811050857.AAA01153@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: peter@netplex.com.au, hackers@FreeBSD.ORG Subject: Re: MMAP and sync writes (Re: sync writes with softupdates enabled) In-reply-to: Your message of "Wed, 04 Nov 1998 21:05:16 +1100." <98Nov4.210449est.40336@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 00:57:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any followthrough on this one? Particularly, any test results? > Peter Wemm wrote: > >> Note that there is a similar bug in 2.2.x. The fix is similar, but > >> needs some thought since there appears to be a problem with the > >> parameters to vm_object_page_clean(). In particular, `syncio' is > >> defined as boolean_t, as passed as the `waitfor' argument to > >> VOP_FSYNC() - which is MNT_ASYNC or MNT_SYNC elsewhere. I haven't > >> had the time to work out the correct definitions. > > > >Use TRUE and FALSE instead of OBJPC_SYNC and 0. > > I don't think it's that simple. The following is from 2.2.7-RELEASE: > > Looking at vm_object_page_clean(), all the existing calls use TRUE or > FALSE (or 1 or 0, which is equivalent, if less clear). This matches > the definition 'boolean_t syncio'. > > Within vm_object_page_clean(), syncio is only used as: > VOP_FSYNC(vp, NULL, syncio, curproc); > > The problem is that everywhere else, VOP_FSYNC() is called with the > third parameter as one of the following: > a) MNT_WAIT or MNT_NOWAIT explicitly specified. > b) (struct vop_fsync_args).a_waitfor > c) the 2nd argument of {fstype}_sync, invoked via VFS_SYNC() and > explicitly defined as MNT_WAIT or MNT_NOWAIT in > > a_waitfor is only assigned from VOP_FSYNC() and is compared against > MNT_WAIT/MNT_NOWAIT everywhere except: > ffs_inode.c:ffs_update() > if (ap->a_waitfor && (ap->a_vp->v_mount->mnt_flag & MNT_ASYNC) == 0) > return (bwrite(bp)); > > lfs_inode.c:lfs_update() > error = (ap->a_waitfor & LFS_SYNC ? lfs_vflush(vp) : 0); > if(ap->a_waitfor & LFS_SYNC && vp->v_dirtyblkhd.lh_first != NULL) > > VFS_SYNC() is invoked with the second parameter as one of the following: > a) MNT_WAIT or MNT_NOWAIT explicitly specified. > b) 1 in lfs_vfsops.c:lfs_unmount() > > Based on the above, I believe the 4th argument to vm_object_page_clean() > should really be an int and all calls should be updated to pass > MNT_WAIT or MNT_NOWAIT. > > These discrepancies would be far more obvious if more of the kernel > magic numbers were enum's instead of #defines - the compiler would > have some hope of pointing out the inconsistencies. > > Peter > -- > Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au > Alcatel Australia Limited > 41 Mandible St Phone: +61 2 9690 5019 > ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 02:34:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19625 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 02:34:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19620 for ; Thu, 5 Nov 1998 02:34:27 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id CAA10726 for hackers@FreeBSD.ORG; Thu, 5 Nov 1998 02:34:18 -0800 (PST) (envelope-from obrien) Message-ID: <19981105023418.A5837@nuxi.com> Date: Thu, 5 Nov 1998 02:34:18 -0800 From: "David O'Brien" To: Hackers Mailing List Subject: Re: Memory leak location tool? Reply-To: obrien@NUXI.com References: <19981030141624.A1244@thought.org> <86u30lms4a.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <86u30lms4a.fsf@detlev.UUCP>; from Joel Ray Holveck on Fri, Oct 30, 1998 at 07:34:29PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the > following: Closely related is also ElectricFence. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 11:17:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16710 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 11:17:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16695 for ; Thu, 5 Nov 1998 11:17:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA04119 for ; Thu, 5 Nov 1998 11:16:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811051916.LAA04119@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: ncurses update? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 11:16:23 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Coming out of a discussion on the -alpha list, I was contacted about this. We're still at 1.8.6. What's the justification for not upgrading? From: dickey@clark.net Date: Thu, 5 Nov 1998 08:12:42 -0500 (EST) To: mike@smith.net.au Subject: http://x5.dejanews.com/getdoc.xp?AN=408607429&CONTEXT=910271281.396886 sounds like someone's confused the terminfo setf/setb for setaf/setab. This is in my faq: The current version of ncurses is 4.2 There's an faq at http://www.clark.net/pub/dickey/ncurses/ncurses.faq.html (report bugs, but the red/blue interchange was fixed more than a year ago). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 12:15:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25021 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 12:15:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25016 for ; Thu, 5 Nov 1998 12:15:08 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id OAA17671; Thu, 5 Nov 1998 14:14:34 -0600 (CST) Date: Thu, 5 Nov 1998 14:14:33 -0600 From: Dan Nelson To: Mike Smith , hackers@FreeBSD.ORG Subject: Re: ncurses update? Message-ID: <19981105141433.A17448@emsphone.com> References: <199811051916.LAA04119@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199811051916.LAA04119@dingo.cdrom.com>; from "Mike Smith" on Thu Nov 5 11:16:23 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 05), Mike Smith said: > Coming out of a discussion on the -alpha list, I was contacted about > this. We're still at 1.8.6. What's the justification for not > upgrading? The new ncurseses rely heavily on terminfo; to get good termcap emulation, you need to configure with --enable-termcap --enable-getcap --disable-overwrite. And even then it does an internal termcap->info translation on the entry. I tried to maintain a set of patches that would rip all the terminfo stuff out of ncurses, but I gave up; ncurses kept changing too fast for me to keep up :) And the cap->info translation time is negligible anyway, even on a 486. But apart from that it works fine. I've been running with ncurses 4.2 for a long time with no problems. > From: dickey@clark.net > To: mike@smith.net.au > > sounds like someone's confused the terminfo setf/setb for > setaf/setab. This is in my faq: I believe screen has the same problem; I remember having to fix it every time I recompile. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 13:03:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01446 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 13:03:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01428; Thu, 5 Nov 1998 13:03:22 -0800 (PST) (envelope-from ziggy@wopr.inetu.net) Received: from localhost (ziggy@localhost) by wopr.inetu.net (8.8.8/8.8.5) with SMTP id QAA06849; Thu, 5 Nov 1998 16:03:03 -0500 (EST) Date: Thu, 5 Nov 1998 16:03:02 -0500 (EST) From: Ryan Ziegler To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG, advocacy@FreeBSD.ORG Subject: Re: Documentation upgrade: where are the other humans? In-Reply-To: <199811041850.LAA10454@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG lets move this to advocacy, On Wed, 4 Nov 1998, Terry Lambert wrote: > > When not getting paid, programmers tend to code what they find > > interesting. We can say the same thing for writers when writing. I would > > say technical documentation is not the most exciting literary form, nor > > are the arguments for kmem_free() the most exciting subject matter. > > > > What we need are technical writers who feel a severe allegiance to > > FreeBSD. > > Or people who get off on techinical writing, or a professor with > an allegiance to FreeBSD in charge of a Technical Writing class. > > I have to say that there exist people who actually enjoy doing > things that the rest of us would find about as enjoyable as > home dentistry (those of you with capped teeth, imagine removing > your caps with an awl). > > I have a sister who happens to enjoy double-column bookkeeping. > It takes all kinds... > > > I also think that it's very likely that someone who had to take > a technical writing class for their CS/CIS/MIS/BIS degree would > have classmates who were English Majors or whatever, also looking > for writing projects, and that it would be a good idea to encourage > them suggesting FreeBSD documentation to their classmates as a > potential "project fodder gold mine". > > I know that if I were to adjunct teach a technical writing class, > I'd be please as punch if I could find a never-ending supply of > projects, all in the same general problem space; it'd make it a > hell of a lot easier to grade on a curve. Its more of a question of how many people who really enjoy home dentistry exist. Not many, simply isn't glamorous enough. What we need to do is to paint the technical writer as some sort of a hero or rogue. Give him a catchy name. "The dockers, a brand new breed of technical writers, infiltrating open source archives and documenting everything they see. They stop at nothing to see the cvs repositories of the world bloating up with inline documentation." Get an article on CNet and we're off. Approaching professors of technical writing classes doesn't seem like a bad idea, but those students have no allegiance to freebsd. We would easily wind up with inferior documentation (you can argue if thats better than no documentation at all). Maybe we could set up a synergy with the professor. The prof refers his students to us, they do what we want, and if we accept their work they get A's, otherwise, F's. > > > > > Maybe it's just that the majority of people are too busy sitting > > > on their butts hacking code in cave-like computer labs to talk > > > to people in other departments on campus? > > > > You're not suggesting that we're a tad clannish, are you? :) > > Well, this *is* a "free software" project, not a "free product" > project... it's kind of self-limiting in its involvement of > people not that interested in producing software. > > The Linux Documentation project has that whole "Young Communist" > thing going for it... I am still suprised to see that the microsoft vs good-software division hasn't erased the their-free-os vs our-free-os division. I also would think that with all the talk of OSS nowadays, people would be eager to latch onto the 'its not just linux and apache, its everyone' idea. Maybe they have, I don't know. Has freebsd tried to jump in the pool yet? Maybe, also, I make too many assumptions -Ryan > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 13:56:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07894 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 13:56:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07854 for ; Thu, 5 Nov 1998 13:56:19 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id QAA01002 for hackers@freebsd.org; Thu, 5 Nov 1998 16:56:18 -0500 (EST) (envelope-from lee) Message-ID: <19981105165613.A955@tidalwave.net> Date: Thu, 5 Nov 1998 16:56:13 -0500 From: Lee Cremeans To: hackers@FreeBSD.ORG Subject: Coprocessor board--which I/O method should I use? Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm writing a device driver for a board we're de3veloping at work that does encryption and compression in hardware. This board is going to be used in embedded applications (it's a PCI board), like VPNs and firewalls, so it'll be handling a good amount of data. For something like this, what would be the best way to do I/O from userland to the card? I'm thinking character would do, but I'd appreciate other opinions, and also being told if I'm off-base. Also, I'd need to know which interrupt level (net, bio, tty, etc.) this thing should be in. PS: this card is just a processor board, it is not a network protocol controller. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 15:39:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20227 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 15:39:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20222 for ; Thu, 5 Nov 1998 15:39:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00845; Thu, 5 Nov 1998 15:38:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811052338.PAA00845@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? In-reply-to: Your message of "Thu, 05 Nov 1998 16:56:13 EST." <19981105165613.A955@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 15:38:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm writing a device driver for a board we're de3veloping at work that does > encryption and compression in hardware. This board is going to be used in > embedded applications (it's a PCI board), like VPNs and firewalls, so it'll > be handling a good amount of data. For something like this, what would be > the best way to do I/O from userland to the card? I'm thinking character > would do, but I'd appreciate other opinions, and also being told if I'm > off-base. Also, I'd need to know which interrupt level (net, bio, tty, etc.) > this thing should be in. Will the card only be accessed by a single process at one time? If so, and if it uses memory-mapped I/O, I would consider having the device driver allow memory-mapping the I/O region into the user process space. If you combined that with an interrupt handler that poked the process (eg. with a signal or using a callin/semaphore) you'd avoid multiple copies and gain performance. Alternatively, appearing as a character device would be the way to go. You face some interesting problems if the board supports multiple simultaneous streams, in that you'll need to devise a technique for multiplexing your I/O. > PS: this card is just a processor board, it is not a network protocol > controller. That doesn't mean that you couldn't make it look like a loopback interface and route stuff through it, though I doubt it'd be the easiest way to go. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 17:17:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00252 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 17:17:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00238 for ; Thu, 5 Nov 1998 17:17:50 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id UAA01614; Thu, 5 Nov 1998 20:17:33 -0500 (EST) (envelope-from lee) Message-ID: <19981105201733.B1450@tidalwave.net> Date: Thu, 5 Nov 1998 20:17:33 -0500 From: Lee Cremeans To: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? Reply-To: lcremean@tidalwave.net References: <19981105165613.A955@tidalwave.net> <199811052338.PAA00845@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811052338.PAA00845@dingo.cdrom.com>; from Mike Smith on Thu, Nov 05, 1998 at 03:38:41PM -0800 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 05, 1998 at 03:38:41PM -0800, Mike Smith wrote: > > I'm writing a device driver for a board we're de3veloping at work that does > > encryption and compression in hardware. This board is going to be used in > > embedded applications (it's a PCI board), like VPNs and firewalls, so it'll > > be handling a good amount of data. For something like this, what would be > > the best way to do I/O from userland to the card? I'm thinking character > > would do, but I'd appreciate other opinions, and also being told if I'm > > off-base. Also, I'd need to know which interrupt level (net, bio, tty, etc.) > > this thing should be in. > > Will the card only be accessed by a single process at one time? It should be. Most firewall programs I've seen are monolithic. > If so, and if it uses memory-mapped I/O, I would consider having the > device driver allow memory-mapping the I/O region into the user process > space. If you combined that with an interrupt handler that poked the > process (eg. with a signal or using a callin/semaphore) you'd avoid > multiple copies and gain performance. Ah...but this chip is interesting. It's a Hi/fn 7751 (www.hifn.com for the data sheet, it's in PDF), and it uses IP-like headers to get commands from the host--you could technically stream them in with data. Thing is, the chip has 4 DMA channels: one for command headers, one for source (raw) data, one for destination (processed) data, and one for "result" structures. TO top it off it does scatter-gather DMA, meaning that mapping the buffers to user space would be interesting (since, unlike a network card, this thing doesn't have any common buffer memory on the card or in the chip). So, I guess my question is how to get the packets down to the chip in an efficient fashion. I keep thinking a struct with the necessary pointers in it would do...the driver could lock down the pages (is this necessary? My mind is polluted with NT driver programming horrors :( ), then vtophys them to make the lists, and send that on to the card. > Alternatively, appearing as a character device would be the way to go. > You face some interesting problems if the board supports multiple > simultaneous streams, in that you'll need to devise a technique for > multiplexing your I/O. It does; the chip has different "contexts" for each stream going through it, which it stores in dedicated RAM on the board. However, these requests can be packetized fairly easily, I'd say; the firewall/VPN app would do the serialization/prioritizing (it'd more than likely be the only app on the machine), and the driver would handle moving the data around. > > PS: this card is just a processor board, it is not a network protocol > > controller. > > That doesn't mean that you couldn't make it look like a loopback > interface and route stuff through it, though I doubt it'd be the > easiest way to go. Right; this would also hamper some of the interesting features of the card, such as being able to use different encryption keys for each packet. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 17:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03220 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 17:57:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03215 for ; Thu, 5 Nov 1998 17:57:54 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id JAA08921; Fri, 6 Nov 1998 09:57:14 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199811060157.JAA08921@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: ncurses update? In-reply-to: Your message of "Thu, 05 Nov 1998 11:16:23 PST." <199811051916.LAA04119@dingo.cdrom.com> Date: Fri, 06 Nov 1998 09:57:13 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Coming out of a discussion on the -alpha list, I was contacted about > this. We're still at 1.8.6. What's the justification for not > upgrading? I've got a bmaked version running on one of my systems and it has been in that state for quite some time. I find very few problems with it as a result.. One thing I was very much tempted to do was to grab the OpenBSD termcap reader that generates the terminfo style tables that ncurses can use directly. The beauty of that is that the result is both libtermcap and libncurses compatable. The other nice thing it does (I think) is support a terminfo.db file rather than thousands of tiny binary files. So, you can have a text file (just like termcap) and do a cap_mkdb on it for fast lookups. The ncurses version of the termcap reader is pretty rotten (IMHO). It had some 'getcap' compatability code added for 4.4BSD compatability, but then they built in a castrated version of getcap that didn't support .db files etc. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 18:00:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03471 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 18:00:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03466 for ; Thu, 5 Nov 1998 18:00:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01574; Thu, 5 Nov 1998 17:58:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811060158.RAA01574@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: ncurses update? In-reply-to: Your message of "Fri, 06 Nov 1998 09:57:13 +0800." <199811060157.JAA08921@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 17:58:44 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > Coming out of a discussion on the -alpha list, I was contacted about > > this. We're still at 1.8.6. What's the justification for not > > upgrading? > > I've got a bmaked version running on one of my systems and it has been in > that state for quite some time. > > I find very few problems with it as a result.. One thing I was very much > tempted to do was to grab the OpenBSD termcap reader that generates the > terminfo style tables that ncurses can use directly. The beauty of that > is that the result is both libtermcap and libncurses compatable. The > other nice thing it does (I think) is support a terminfo.db file rather > than thousands of tiny binary files. So, you can have a text file (just > like termcap) and do a cap_mkdb on it for fast lookups. > > The ncurses version of the termcap reader is pretty rotten (IMHO). It > had some 'getcap' compatability code added for 4.4BSD compatability, but > then they built in a castrated version of getcap that didn't support .db > files etc. Ok. Can we assume this is in your queue, or should we find an eager go-getter to look after it? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 22:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20863 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 22:00:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20858 for ; Thu, 5 Nov 1998 22:00:34 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA17262; Thu, 5 Nov 1998 22:00:19 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA28928; Thu, 5 Nov 1998 22:00:18 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA16417; Thu, 5 Nov 1998 22:00:16 -0800 (PST) From: Don Lewis Message-Id: <199811060600.WAA16417@salsa.gv.tsc.tdk.com> Date: Thu, 5 Nov 1998 22:00:16 -0800 In-Reply-To: Luoqi Chen "Re: question about getsid()" (Oct 24, 2:44am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Luoqi Chen , Don.Lewis@tsc.tdk.com, hackers@FreeBSD.ORG, jau@jau.tmt.tele.fi Subject: Re: question about getsid() Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 24, 2:44am, Luoqi Chen wrote: } Subject: Re: question about getsid() } > getsid() needs to verify s_leader is not NULL before dereferencing it, } > but what should getsid() return if there is no session leader? } > } If the session leader is gone, the session losts the ability to acquire } a controlling terminal, which is the sole purpose of its existence. } This session should be disbanded, and member process groups join session 0. I can see three possible implementations. The first two implementations are literally what you describe. In the first, all the process groups need to be visited and any that reference this session need have their pg_session pointer changed to point to session0, and the reference counts updated. This could be expensive if there are a lot of process groups. In the second implementation, all of the process groups that belong to a session would be linked together and hung off the session structure. When the session leader exits, it would only be necessary to traverse this short list. This is more expensive in terms of memory consumption, but it would be possible to eliminate the session reference count. Another disadvantage would be the expense of maintaining the session0 process group list, since this list could be quite long. The simple but hackish thing to do would be to change getsid() to return session0.s_leader->p_pid if p->p_pgrp->pg_session->s_leader is NULL, and reclaim the abandoned session when all the process groups that reference it are gone. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 5 23:05:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25976 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 23:05:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles159.castles.com [208.214.165.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25968 for ; Thu, 5 Nov 1998 23:05:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA00536; Thu, 5 Nov 1998 23:04:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811060704.XAA00536@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? In-reply-to: Your message of "Thu, 05 Nov 1998 20:17:33 EST." <19981105201733.B1450@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 23:04:00 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Nov 05, 1998 at 03:38:41PM -0800, Mike Smith wrote: > > > I'm writing a device driver for a board we're de3veloping at work that does > > > encryption and compression in hardware. This board is going to be used in > > > embedded applications (it's a PCI board), like VPNs and firewalls, so it'll > > > be handling a good amount of data. For something like this, what would be > > > the best way to do I/O from userland to the card? I'm thinking character > > > would do, but I'd appreciate other opinions, and also being told if I'm > > > off-base. Also, I'd need to know which interrupt level (net, bio, tty, etc.) > > > this thing should be in. > > > > Will the card only be accessed by a single process at one time? > > It should be. Most firewall programs I've seen are monolithic. That's not a good spec to be writing to. Get an answer. 8) > > If so, and if it uses memory-mapped I/O, I would consider having the > > device driver allow memory-mapping the I/O region into the user process > > space. If you combined that with an interrupt handler that poked the > > process (eg. with a signal or using a callin/semaphore) you'd avoid > > multiple copies and gain performance. > > Ah...but this chip is interesting. It's a Hi/fn 7751 (www.hifn.com for the > data sheet, it's in PDF), and it uses IP-like headers to get commands from > the host--you could technically stream them in with data. Thing is, the chip > has 4 DMA channels: one for command headers, one for source (raw) data, one > for destination (processed) data, and one for "result" structures. TO top it > off it does scatter-gather DMA, meaning that mapping the buffers to user > space would be interesting (since, unlike a network card, this thing doesn't > have any common buffer memory on the card or in the chip). > > So, I guess my question is how to get the packets down to the chip in an > efficient fashion. I keep thinking a struct with the necessary pointers in > it would do...the driver could lock down the pages (is this necessary? My > mind is polluted with NT driver programming horrors :( ), then vtophys them > to make the lists, and send that on to the card. Yick. You really don't want to have to deal with that. You should be OK just using uiomove to pull stuff in from user space to a local pool of buffers. If the card does scatter-gather and supports multiple outstanding commands, you should be able to keep its pipe full all the time. > > Alternatively, appearing as a character device would be the way to go. > > You face some interesting problems if the board supports multiple > > simultaneous streams, in that you'll need to devise a technique for > > multiplexing your I/O. > > It does; the chip has different "contexts" for each stream going through it, > which it stores in dedicated RAM on the board. However, these requests can > be packetized fairly easily, I'd say; the firewall/VPN app would do the > serialization/prioritizing (it'd more than likely be the only app on the > machine), and the driver would handle moving the data > around. How much context RAM does it have? Can you page to/from the context memory? If you're doing the mux/demux in the driver and you only have one consumer, you will probably have to wrap the read/write data with a header structure to identify the logcal channel it's on. The only alternative is always having more device nodes than that you have connections. > > > PS: this card is just a processor board, it is not a network protocol > > > controller. > > > > That doesn't mean that you couldn't make it look like a loopback > > interface and route stuff through it, though I doubt it'd be the > > easiest way to go. > > Right; this would also hamper some of the interesting features of the card, > such as being able to use different encryption keys for each packet. Not at all; you'd just leverage the private address space off the virtual interface to present an arbitrary number of virtual loopback interfaces, each forming part of the "pipe" for each connection. Probably too much of a headgame though. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 05:28:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29776 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 05:28:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29771 for ; Fri, 6 Nov 1998 05:28:51 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id IAA03012; Fri, 6 Nov 1998 08:28:36 -0500 (EST) (envelope-from lee) Message-ID: <19981106082835.A2926@tidalwave.net> Date: Fri, 6 Nov 1998 08:28:35 -0500 From: Lee Cremeans To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? Reply-To: lcremean@tidalwave.net References: <19981105201733.B1450@tidalwave.net> <199811060704.XAA00536@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811060704.XAA00536@dingo.cdrom.com>; from Mike Smith on Thu, Nov 05, 1998 at 11:04:00PM -0800 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 05, 1998 at 11:04:00PM -0800, Mike Smith wrote: > > > If so, and if it uses memory-mapped I/O, I would consider having the > > > device driver allow memory-mapping the I/O region into the user process > > > space. If you combined that with an interrupt handler that poked the > > > process (eg. with a signal or using a callin/semaphore) you'd avoid > > > multiple copies and gain performance. > > > > Ah...but this chip is interesting. It's a Hi/fn 7751 (www.hifn.com for the > > data sheet, it's in PDF), and it uses IP-like headers to get commands from > > the host--you could technically stream them in with data. Thing is, the chip > > has 4 DMA channels: one for command headers, one for source (raw) data, one > > for destination (processed) data, and one for "result" structures. TO top it > > off it does scatter-gather DMA, meaning that mapping the buffers to user > > space would be interesting (since, unlike a network card, this thing doesn't > > have any common buffer memory on the card or in the chip). > > > > So, I guess my question is how to get the packets down to the chip in an > > efficient fashion. I keep thinking a struct with the necessary pointers in > > it would do...the driver could lock down the pages (is this necessary? My > > mind is polluted with NT driver programming horrors :( ), then vtophys them > > to make the lists, and send that on to the card. > > Yick. You really don't want to have to deal with that. You should be > OK just using uiomove to pull stuff in from user space to a local pool > of buffers. If the card does scatter-gather and supports multiple > outstanding commands, you should be able to keep its pipe full all the > time. All righty...are there any good examples of a card that does this? (And the method I mentioned is basically what NT makes you do. It's extremely 0dd...I really should have tried writing for BSD first.) I have been looking at wpaul's if_tl.c code, and it's been helpful, but since I'm writing for something that's not a NIC, and I don't want my head to swim in the loopback idea, I've been avoiding using mbuf I/O. > > > Alternatively, appearing as a character device would be the way to go. > > > You face some interesting problems if the board supports multiple > > > simultaneous streams, in that you'll need to devise a technique for > > > multiplexing your I/O. > > > > It does; the chip has different "contexts" for each stream going through it, > > which it stores in dedicated RAM on the board. However, these requests can > > be packetized fairly easily, I'd say; the firewall/VPN app would do the > > serialization/prioritizing (it'd more than likely be the only app on the > > machine), and the driver would handle moving the data > > around. > > How much context RAM does it have? Can you page to/from the context > memory? If you're doing the mux/demux in the driver and you only have > one consumer, you will probably have to wrap the read/write data with a > header structure to identify the logcal channel it's on. The only > alternative is always having more device nodes than that you have > connections. You can send commands to read and write the contexts through the DMA, but you can't map it into PCI address space if that's what you're asking. Also, Hi/fn recommends locking the CRAM and letting the chip manage it, since context is intermediary data (like a glorified carry register), not actual commands or data. As for contexts, the command header has the context in it, and I figure if you keep the pointers together, you'll be OK. The card can have up to 2MB context RAM. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 05:30:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29897 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 05:30:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29892 for ; Fri, 6 Nov 1998 05:30:20 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id IAA03023; Fri, 6 Nov 1998 08:30:18 -0500 (EST) (envelope-from lee) Message-ID: <19981106083018.B2926@tidalwave.net> Date: Fri, 6 Nov 1998 08:30:18 -0500 From: Lee Cremeans To: "Ron G. Minnich" Cc: hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? Reply-To: lcremean@tidalwave.net References: <199811052338.PAA00845@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Ron G. Minnich on Fri, Nov 06, 1998 at 02:32:51AM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 06, 1998 at 02:32:51AM -0500, Ron G. Minnich wrote: > > > I'm writing a device driver for a board we're de3veloping at work that does > > > encryption and compression in hardware. This board is going to be used in > > > embedded applications (it's a PCI board), like VPNs and firewalls, so it'll > > > be handling a good amount of data. For something like this, what would be > > > the best way to do I/O from userland to the card? I'm thinking character > > > would do, but I'd appreciate other opinions, and also being told if I'm > > > off-base. Also, I'd need to know which interrupt level (net, bio, tty, etc.) > > > this thing should be in. > > If you want to handle lots of data over pci you're not going to do it via > userland read/writes. PCI reads from the host run about 56 Mbits/sec. So > the question is what data rates are you after? > ron The chip itself can handle 27 MBytes/s in single DES, 10 Mbytes/s in triple DES. THere's a data sheet for it if you want to see it; go look at www.hifn.com, it's the 7751. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 06:15:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03520 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 06:15:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jau.tmt.tele.fi (jau.tmt.tele.fi [194.252.70.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03515 for ; Fri, 6 Nov 1998 06:15:08 -0800 (PST) (envelope-from jau@jau.tmt.tele.fi) Received: (from jau@localhost) by jau.tmt.tele.fi (8.9.1/8.9.1/JAU-2.2) id QAA02132; Fri, 6 Nov 1998 16:14:04 +0200 (EET) From: "Jukka A. Ukkonen" Message-Id: <199811061414.QAA02132@jau.tmt.tele.fi> Subject: Re: question about getsid() To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Fri, 6 Nov 1998 16:14:03 +0200 (EET) Cc: luoqi@watermarkgroup.com, Don.Lewis@tsc.tdk.com, hackers@FreeBSD.ORG In-Reply-To: <199811060600.WAA16417@salsa.gv.tsc.tdk.com> from "Don Lewis" at Nov 5, 98 10:00:16 pm Latin-Date: Vineri VI Novembrie a.d. MCMXCVIII Organization: Internet Services R&D / Sonera Ltd. Finland Phone: +358-2040-4025 (office) / +358-400-606671 (mobile) Content-Conversion: prohibited X-Mailer: ELM [version 2.4 PL25+pgp] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Don Lewis: > > On Oct 24, 2:44am, Luoqi Chen wrote: > } Subject: Re: question about getsid() > > } > getsid() needs to verify s_leader is not NULL before dereferencing it, > } > but what should getsid() return if there is no session leader? > } > > } If the session leader is gone, the session looses the ability to acquire > } a controlling terminal, which is the sole purpose of its existence. > } This session should be disbanded, and member process groups join session 0. > > I can see three possible implementations. The first two implementations > are literally what you describe. > > In the first, all the process groups need to be visited and any that > reference this session need have their pg_session pointer changed to > point to session0, and the reference counts updated. This could be > expensive if there are a lot of process groups. This would be all too costly in the sense of CPU time. > In the second implementation, all of the process groups that belong to > a session would be linked together and hung off the session structure. > When the session leader exits, it would only be necessary to traverse > this short list. This is more expensive in terms of memory consumption, > but it would be possible to eliminate the session reference count. > Another disadvantage would be the expense of maintaining the session0 > process group list, since this list could be quite long. Also this alternative would take a lot of unnecessary work that can be avoided. And as you said, the memory is also a resource which should be saved if possible. So, I do not think this is either the way to go. > The simple but hackish thing to do would be to change getsid() to > return session0.s_leader->p_pid if p->p_pgrp->pg_session->s_leader > is NULL, and reclaim the abandoned session when all the process groups > that reference it are gone. Basically this is the ideal thing, because the system does no extra fiddling with anything when it is not absolutely necessary. I really do not remember whether POSIX actually requires the system to let the processes in a session to know that their original session leader is gone by getsid() returning 0, but I take it that you have checked this. I tried to seek a document where this rather odd behavior has been defined, but I have not found anything containing a reference to such behavior. All of the definitions of getsid() I have been able to find have been virtually equal to http://www.opengroup.org/onlinepubs/7908799/xsh/getsid.html So, before deciding upon implementation I would really like to find all the facts first. If you have a document where the odd getsid() behavior has been defined, please, please, quote the text, or point me to the paper where it is stated. As I said already earlier, it might be sometimes preferable to let the notion of session double also as an indication of processes being related in addition to only limiting allocation of a new ctty. If the POSIX rules really require an indication of the session leader being gone as a 0 return value from getsid(), I do not understand what end does this serve. As long as ctty allocation is considered any process should be quite content knowing whether it is a process leader or not. If the POSIX intention has been only to let the caller to know it cannot allocate a ctty, a test (pid != getsid(pid)) would have sufficed just fine. Otherwise returning the original session ID would carry much more information. Cheers, // jau .--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -. / Jukka A. Ukkonen, Internet Services R&D / Sonera Ltd. /__ M.Sc. (sw-eng & cs) (Phone) +358-2040-4025 / Internet: Jukka.Ukkonen@sonera.fi (Fax) +358-2040-64724 / Internet: jau@iki.fi (Mobile) +358-400-606671 v Internet: ukkonen@nic.funet.fi (Home&Fax) +358-9-6215280 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 06:42:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06414 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 06:42:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA06398 for ; Fri, 6 Nov 1998 06:41:40 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA28889; Fri, 6 Nov 1998 09:41:13 -0500 Date: Fri, 6 Nov 1998 09:41:12 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: lcremean@tidalwave.net cc: hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? In-Reply-To: <19981106083018.B2926@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Nov 1998, Lee Cremeans wrote: > The chip itself can handle 27 MBytes/s in single DES, 10 Mbytes/s in triple > DES. THere's a data sheet for it if you want to see it; go look at > www.hifn.com, it's the 7751. Right so what I'm saying is this: PII and other Intel-based motherboards can only do PCI reads at 7 Mbytes/second. Intel bridges don't support burst mode reads from the processor to PCI, even in cacheable space. So, if you want to get that bandwidth from the board to main memory you're going to have to have the board do PCI writes in DMA mode. This sort of thing slightly complicates user-mode access. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 08:19:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18326 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 08:19:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18320 for ; Fri, 6 Nov 1998 08:19:18 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id LAA03379; Fri, 6 Nov 1998 11:19:05 -0500 (EST) (envelope-from lee) Message-ID: <19981106111905.A3375@tidalwave.net> Date: Fri, 6 Nov 1998 11:19:05 -0500 From: Lee Cremeans To: "Ron G. Minnich" , lcremean@tidalwave.net Cc: hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? Reply-To: lcremean@tidalwave.net References: <19981106083018.B2926@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Ron G. Minnich on Fri, Nov 06, 1998 at 09:41:12AM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 06, 1998 at 09:41:12AM -0500, Ron G. Minnich wrote: > > On Fri, 6 Nov 1998, Lee Cremeans wrote: > > The chip itself can handle 27 MBytes/s in single DES, 10 Mbytes/s in triple > > DES. THere's a data sheet for it if you want to see it; go look at > > www.hifn.com, it's the 7751. > > Right so what I'm saying is this: PII and other Intel-based motherboards > can only do PCI reads at 7 Mbytes/second. Intel bridges don't support > burst mode reads from the processor to PCI, even in cacheable space. So, > if you want to get that bandwidth from the board to main memory you're > going to have to have the board do PCI writes in DMA mode. This sort of > thing slightly complicates user-mode access. Exactly; in fact, DMA mode is the only one supported for actual work on this board. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 09:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03928 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 09:54:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03923 for ; Fri, 6 Nov 1998 09:54:39 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id MAA23003; Fri, 6 Nov 1998 12:54:31 -0500 (EST) (envelope-from lee) Message-ID: <19981106125431.A22944@tidalwave.net> Date: Fri, 6 Nov 1998 12:54:31 -0500 From: Lee Cremeans To: mike@smith.net.au, hackers@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? Reply-To: lcremean@tidalwave.net References: <19981105201733.B1450@tidalwave.net> <199811060704.XAA00536@dingo.cdrom.com> <19981106082835.A2926@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981106082835.A2926@tidalwave.net>; from Lee Cremeans on Fri, Nov 06, 1998 at 08:28:35AM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 06, 1998 at 08:28:35AM -0500, Lee Cremeans wrote: > commands or data. As for contexts, the command header has the context in > it, and I figure if you keep the pointers together, you'll be OK. The card > can have up to 2MB context RAM. > Um, I screwed this up and didn't realise it...what I mean is that the Hi/fn can keep track of contexts itself 9sort of), and each context gets an index number (the data sheet calls it the "session number"). You include this number in the command header, and it will DTRT. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 11:45:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19343 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 11:45:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19314 for ; Fri, 6 Nov 1998 11:45:51 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id OAA25951 for ; Fri, 6 Nov 1998 14:45:32 -0500 (EST) Date: Fri, 6 Nov 1998 14:45:31 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Questions about DEVFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After reading the file /miscfs/devfs/README and some postings related to DEVFS, I am still confused with it. The back plane is said to be a tree of back nodes. How many nodes are created in this back plane? How can we know the hierarchy of the tree in order to create it? How can the back plane serve as a blueprint of multiple front planes? I hope someone will give me a general idea about DEVFS so that I can go over the source code easily. Any help is appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 12:00:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22048 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 12:00:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22041 for ; Fri, 6 Nov 1998 12:00:10 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id MAA03204 for ; Fri, 6 Nov 1998 12:00:37 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: hackers@FreeBSD.ORG Reply-To: chat@FreeBSD.ORG Followups-To: chat@freebsd.org Really-Long-Threads-Which-Come-Out-Of-This-Should-Definitely-Go-To: chat@freebsd.org Subject: "Eek" Date: Fri, 06 Nov 1998 12:00:37 -0800 Message-ID: <3200.910382437@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://dd.sh/perlfs/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 12:19:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25875 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 12:19:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25863; Fri, 6 Nov 1998 12:19:45 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (cam [10.0.0.50]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id WAA21270; Fri, 6 Nov 1998 22:18:22 +0200 Message-ID: <36435979.892DFA6D@Shevchenko.Kiev.UA> Date: Fri, 06 Nov 1998 22:18:02 +0200 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: chat@FreeBSD.ORG CC: hackers@FreeBSD.ORG Subject: Re: "Eek" References: <3200.910382437@time.cdrom.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > http://dd.sh/perlfs/ > IMHO, Linux-ism > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- @= //RSSH mailto:Ruslan@Shevchenko.Kiev.UA CORBA in Ukraine & ex-USSR: http://www.corbadev.kiev.ua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 12:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27796 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 12:33:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27789 for ; Fri, 6 Nov 1998 12:33:54 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.164]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA9A; Fri, 6 Nov 1998 21:33:41 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 06 Nov 1998 21:37:43 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: zhihuizhang Subject: RE: Questions about DEVFS Cc: hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Nov-98 zhihuizhang wrote: > > After reading the file /miscfs/devfs/README and some postings related to > DEVFS, I am still confused with it. All that I know is that DEVFS doesn't need entries in /dev except /dev itself and simply creates devices at boot-up. HTH, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 12:46:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29381 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 12:46:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29376 for ; Fri, 6 Nov 1998 12:46:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00773; Fri, 6 Nov 1998 12:44:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811062044.MAA00773@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Coprocessor board--which I/O method should I use? In-reply-to: Your message of "Fri, 06 Nov 1998 08:28:35 EST." <19981106082835.A2926@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Nov 1998 12:44:31 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yick. You really don't want to have to deal with that. You should be > > OK just using uiomove to pull stuff in from user space to a local pool > > of buffers. If the card does scatter-gather and supports multiple > > outstanding commands, you should be able to keep its pipe full all the > > time. > > All righty...are there any good examples of a card that does this? (And the > method I mentioned is basically what NT makes you do. It's extremely 0dd...I > really should have tried writing for BSD first.) Euww. Wiring user pages is OK *if* your VM system is fast enough, but it leaves you open to *serious* abuse. > I have been looking at > wpaul's if_tl.c code, and it's been helpful, but since I'm writing for > something that's not a NIC, and I don't want my head to swim in the loopback > idea, I've been avoiding using mbuf I/O. The ideas are still basically applicable; your *write routine will take writes and copy them into internal buffers; you will want to make some policy decisions about buffer sizes, write atomicity, etc. You'll want to allocate these buffers at startup time, and probably store the physical address of the buffer in the buffer control structure. The internal buffers then get fed to the processor via the interrupt handler, and completed buffers are put on the 'done' queue ready for reading. > > How much context RAM does it have? Can you page to/from the context > > memory? If you're doing the mux/demux in the driver and you only have > > one consumer, you will probably have to wrap the read/write data with a > > header structure to identify the logcal channel it's on. The only > > alternative is always having more device nodes than that you have > > connections. > > You can send commands to read and write the contexts through the DMA, but > you can't map it into PCI address space if that's what you're asking. No. The issue is simply that unless you want to limit the total number of simultaneous connections you support to the capabilities of the device, you'll need to be able to page contexts in and out. > Also, > Hi/fn recommends locking the CRAM and letting the chip manage it, since > context is intermediary data (like a glorified carry register), not actual > commands or data. As for contexts, the command header has the context in > it, and I figure if you keep the pointers together, you'll be OK. The card > can have up to 2MB context RAM. How big is a context? Do you have any idea whether you'll be limited here? At any rate, adding context paging will be reasonably simple at a later stage it seems. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 13:29:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05290 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 13:29:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05284 for ; Fri, 6 Nov 1998 13:29:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01139 for ; Fri, 6 Nov 1998 13:28:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811062128.NAA01139@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Reiserfs? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Nov 1998 13:28:20 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone watching this one? The summary paper looks pretty interesting; it'd be a good project for someone wanting to learn the VFS interface... http://www.idiom.com/~beverly/reiserfs.html -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 13:40:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06594 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 13:40:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06587 for ; Fri, 6 Nov 1998 13:40:15 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.164]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA11BC; Fri, 6 Nov 1998 22:40:00 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811062128.NAA01139@dingo.cdrom.com> Date: Fri, 06 Nov 1998 22:44:03 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: RE: Reiserfs? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Nov-98 Mike Smith wrote: > > Anyone watching this one? The summary paper looks pretty interesting; > it'd be a good project for someone wanting to learn the VFS interface... Thanks for the pointer Mike... Looks interesting... Better than Jordan's PerlFS URL anyways *chuckles* --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 14:15:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11153 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 14:15:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11146; Fri, 6 Nov 1998 14:15:02 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id RAA22508; Fri, 6 Nov 1998 17:14:53 -0500 (EST) Date: Fri, 6 Nov 1998 17:14:52 -0500 (EST) To: chat@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: Re: "Eek" In-Reply-To: <3200.910382437@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Nov 1998, Jordan K. Hubbard wrote: > http://dd.sh/perlfs/ Great... when will FreeBSD implement this? ;-P Later, -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 14:21:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11731 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 14:21:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11722; Fri, 6 Nov 1998 14:21:07 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id XAA11699; Fri, 6 Nov 1998 23:14:57 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199811062214.XAA11699@ocean.campus.luth.se> Subject: Re: "Eek" In-Reply-To: <36435979.892DFA6D@Shevchenko.Kiev.UA> from Ruslan Shevchenko at "Nov 6, 98 10:18:02 pm" To: rssh@grad.kiev.ua Date: Fri, 6 Nov 1998 23:14:57 +0100 (CET) Cc: chat@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Ruslan Shevchenko: > Jordan K. Hubbard wrote: > > http://dd.sh/perlfs/ > IMHO, Linux-ism IMO: "Maybe, but so what? That's WAY COOOOOL!" it's not a good idea to scrap all the filesystems and redo them in perl, or anything... but as an extension it can only bring good. It IS a rather neat idea... If we could make a similar thing that had the same API, we could share code with them too. And yes... it's less efficient, but then again... You don't always care, do you? I mean... if it gets to be a generic interface (version are written for all BSDs too, etc) then we might find a lot of obscure filesystems implmented like that... which might allow us to support reading/write such filsystems to people that need it, without having to do anything. And these people will be MUCH happier that they can read/write that file they needed to/from their obscure filesystem at half the speed then not at all. I wonder how much work it would be... How do they integrate perl with the kernel?? That could get ugly :) *starts diggint for details* /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 14:26:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12916 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 14:26:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12908; Fri, 6 Nov 1998 14:26:39 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA20098; Fri, 6 Nov 1998 23:26:23 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 6 Nov 1998 23:26:22 +0100 (MET) Mime-Version: 1.0 To: mike@seidata.com Cc: chat@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: "Eek" References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 06 Nov 1998 23:26:21 +0100 In-Reply-To: mike@seidata.com's message of "Fri, 6 Nov 1998 17:14:52 -0500 (EST)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA12910 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mike@seidata.com writes: > On Fri, 6 Nov 1998, Jordan K. Hubbard wrote: > > http://dd.sh/perlfs/ > Great... when will FreeBSD implement this? ;-P Never, I hope. There is a proverb about hammers and nails which has often been invoked for Perl; it is particularly pertinent to this situation. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 14:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15505 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 14:49:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15500; Fri, 6 Nov 1998 14:49:03 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4025.ime.net [209.90.195.35]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id RAA18785; Fri, 6 Nov 1998 17:48:07 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981106174527.00b45a70@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 06 Nov 1998 17:46:04 -0500 To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ), mike@seidata.com From: Drew Baxter Subject: Re: "Eek" Cc: chat@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA15501 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:26 PM 11/6/98 +0100, Dag-Erling C. Smørgrav wrote: >mike@seidata.com writes: >> On Fri, 6 Nov 1998, Jordan K. Hubbard wrote: >> > http://dd.sh/perlfs/ >> Great... when will FreeBSD implement this? ;-P > >Never, I hope. There is a proverb about hammers and nails which has >often been invoked for Perl; it is particularly pertinent to this >situation. > >DES >-- >Dag-Erling Smørgrav - dag-erli@ifi.uio.no > Yknow, this looks pretty flaky.. Maybe SUPPORT should be added, but I wouldn't rely on it for a damned thing myself. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 14:50:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15849 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 14:50:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15831; Fri, 6 Nov 1998 14:50:23 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id QAA28014; Fri, 6 Nov 1998 16:49:42 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma028012; Fri, 6 Nov 98 16:49:33 -0600 Received: from spawn.nectar.com (localhost.nectar.com [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id QAA11821; Fri, 6 Nov 1998 16:49:33 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199811062249.QAA11821@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199811062214.XAA11699@ocean.campus.luth.se> References: <199811062214.XAA11699@ocean.campus.luth.se> Subject: Re: "Eek" To: Mikael Karpberg cc: rssh@grad.kiev.ua, chat@FreeBSD.ORG, hackers@FreeBSD.ORG Date: Fri, 06 Nov 1998 16:49:33 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I think everyone would be better served by shfs, a kernel interface for implementing filesystems using the Bourne shell. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 6 November 1998 at 23:14, Mikael Karpberg wrote: > According to Ruslan Shevchenko: > > Jordan K. Hubbard wrote: > > > http://dd.sh/perlfs/ > > IMHO, Linux-ism > > IMO: "Maybe, but so what? That's WAY COOOOOL!" > it's not a good idea to scrap all the filesystems and redo them in perl, > or anything... but as an extension it can only bring good. [snip] -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNkN8/TeRhT8JRySpAQEAhwQAmpIcwdiae+HVXbEtI4Lifd+0ZV8Z1M4S Quivq56AUH+HWu2pUWCvq03jhYXg0uLUpo4kS8eBw4SS4HfXE8mbS8Xfafvfm63x 8hN6jBfUqzb9W/JmdgBN+VYHWHSbqyeb1Rqt61mrAGup2FDACjFMaK66U6onZtri 2IeJPUN/5EE= =5bVQ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 15:05:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17868 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 15:05:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from squirrel.tgsoft.com (cx20270-a.pwy1.sdca.home.com [24.0.169.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA17849 for ; Fri, 6 Nov 1998 15:05:33 -0800 (PST) (envelope-from thompson@tgsoft.com) Received: (qmail 17828 invoked by uid 128); 6 Nov 1998 23:05:20 -0000 Date: 6 Nov 1998 23:05:20 -0000 Message-ID: <19981106230520.17827.qmail@squirrel.tgsoft.com> From: mark thompson To: freebsd-hackers@FreeBSD.ORG Subject: From NTK... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is from ntknow, which probably is widely read by the members of hackers, but IMHO it is an idea that should be widely disseminated. It is just about the most, uhm, *interesting* idea I have seen in a long while... >> TRACKING << making good use of the things that we find You know how everything in UNIX is supposed to be a file? You know Perl lets you do everything you'd ever want to do? You know that means, logically, you can return UNIX to its pure, pre-Fall state, where everything *is* a file - anything you want? So you could, say, chdir to "http://www.yahoo.com/", then chdir to all the links on that page? And you know that there's only one person insane enough to thus let you write your own filing system - in Perl? Yes, from the people who brought you the Turing Machine using only dd and sh, we roundly announce: http://dd.sh/perlfs/ - next: X-Windows servers using trained cellular automata -- It may be a pipe to you, but it's a socket to me. -- dmr on an imaginary episode of Laugh in -mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 16:06:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27159 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 16:06:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27142; Fri, 6 Nov 1998 16:06:14 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA01561; Sat, 7 Nov 1998 10:35:59 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA00882; Sat, 7 Nov 1998 10:35:53 +1030 (CST) Message-ID: <19981107103553.J499@freebie.lemis.com> Date: Sat, 7 Nov 1998 10:35:53 +1030 From: Greg Lehey To: Mohit Aron Cc: FreeBSD Hackers Subject: Re: VM internals References: <199811062201.QAA15340@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811062201.QAA15340@cs.rice.edu>; from Mohit Aron on Fri, Nov 06, 1998 at 04:01:36PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 6 November 1998 at 16:01:36 -0600, Mohit Aron wrote: > Hi, > it seems that FreeBSD has added new features to the VM implementation > of 4.4BSD. Is there any place I can get to know about these features (short > of reading the actual code). I'm particulary interested in knowing about > the VM cache and its interactions with other caches in the kernel like the > Filesystem cache and the buffer cache. Thanks, This is a question more suited to -hackers, so I've followed up there. The short answer is "no real documentation is available". The slightly longer one is "so get what's available and make real documentation out of it" :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 16:49:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01855 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 16:49:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01850; Fri, 6 Nov 1998 16:49:48 -0800 (PST) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id TAA23710; Fri, 6 Nov 1998 19:49:22 -0500 (EST) Date: Fri, 6 Nov 1998 19:49:21 -0500 (EST) To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" cc: chat@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: "Eek" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id QAA01851 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote: > > Great... when will FreeBSD implement this? ;-P > > Never, I hope. There is a proverb about hammers and nails which has > often been invoked for Perl; it is particularly pertinent to this > situation. Ahh, inflection is lost in the cyber-translation yet again. The ';-P' implies, 'tongue in cheek'. ;) Later, -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 17:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04978 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 17:29:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from set.scient.com (set.scient.com [208.202.109.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA04922; Fri, 6 Nov 1998 17:29:41 -0800 (PST) (envelope-from enkhyl@scient.com) Received: by set.scient.com; (5.65v4.0/1.3/10May95) id AA10283; Fri, 6 Nov 1998 17:29:08 -0800 Received: from somewhere by smtpxd Date: Fri, 6 Nov 1998 17:28:30 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: enkhyl@hayseed.net To: Mikael Karpberg Cc: rssh@grad.kiev.ua, chat@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: "Eek" In-Reply-To: <199811062214.XAA11699@ocean.campus.luth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It might be useful for prototyping of filesystems, which is what I use perl for a lot of times (prototyping in general, that is :-) On Fri, 6 Nov 1998, Mikael Karpberg wrote: > According to Ruslan Shevchenko: > > Jordan K. Hubbard wrote: > > > http://dd.sh/perlfs/ > > IMHO, Linux-ism > > IMO: "Maybe, but so what? That's WAY COOOOOL!" > it's not a good idea to scrap all the filesystems and redo them in perl, > or anything... but as an extension it can only bring good. > > It IS a rather neat idea... If we could make a similar thing that had the > same API, we could share code with them too. And yes... it's less efficient, > but then again... You don't always care, do you? I mean... if it gets to be > a generic interface (version are written for all BSDs too, etc) then we > might find a lot of obscure filesystems implmented like that... which > might allow us to support reading/write such filsystems to people that > need it, without having to do anything. And these people will be MUCH > happier that they can read/write that file they needed to/from their > obscure filesystem at half the speed then not at all. > > I wonder how much work it would be... How do they integrate perl with > the kernel?? That could get ugly :) > > *starts diggint for details* -- Christopher Nielsen Scient: The eBusiness Systems Innovator cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 6 23:03:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03606 for freebsd-hackers-outgoing; Fri, 6 Nov 1998 23:03:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.147.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03601 for ; Fri, 6 Nov 1998 23:03:20 -0800 (PST) (envelope-from howardjp@dragon.ham.muohio.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.8.5/8.8.5) with SMTP id CAA02501; Sat, 7 Nov 1998 02:02:40 -0500 Date: Sat, 7 Nov 1998 02:02:40 -0500 (EST) From: Jamie Howard To: mark thompson cc: freebsd-hackers@FreeBSD.ORG Subject: Re: From NTK... In-Reply-To: <19981106230520.17827.qmail@squirrel.tgsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6 Nov 1998, mark thompson wrote: > - next: X-Windows servers using trained cellular automata This would be cool, I once wrote a calculator (only addition) using Christopher Langton's Vants. I doubt I have the source code anymore though. :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 01:39:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14131 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 01:39:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tiger1.nownuri.net (tiger1.nownuri.net [203.238.129.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14122 for ; Sat, 7 Nov 1998 01:39:40 -0800 (PST) (envelope-from ildos@nownuri.net) Received: (from k3@localhost) by tiger1.nownuri.net (8.9.0/H/8.9.0) id SAA15829; Sat, 7 Nov 1998 18:38:56 +0900 (KST) Date: Sat, 7 Nov 1998 18:38:56 +0900 (KST) From: ÀÌÀϵµ Message-Id: <199811070938.SAA15829@tiger1.nownuri.net> To: freebsd-hackers@FreeBSD.ORG Subject: Device Driver MIME-Version: 1.0 Content-Type: text/plain; charset=EUC-KR Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My major field of interest is network. Now I am interested to IEEE 1394 and internetworing in home. I hope to make IEEE 1394 device driver for FreeBSD. But it is difficult for me to understand FreeBSD architecture and requirement. Although I find relate information, I don't have it. If you help me, Please give information for making. Also, do you know who help me? If you know, inform me. Then very very thank you. I would appreciate any additional information you could send me about making device driver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 02:15:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17597 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 02:15:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from henoch.cc.fh-lippe.de (henoch.cc.fh-lippe.de [193.16.112.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17592 for ; Sat, 7 Nov 1998 02:15:14 -0800 (PST) (envelope-from lkoeller@cc.fh-lippe.de) Received: from spock.cc.fh-lippe.de([193.16.118.120]) (8214 bytes) by henoch.cc.fh-lippe.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 7 Nov 1998 11:14:56 +0100 (MET) (Smail-3.2.0.101 1997-Dec-17 #3 built 1998-Feb-3) Received: from odie.lippe.de by spock.cc.fh-lippe.de with smtp (Smail3.1.29.1 #2) id m0zc5OM-00070XC; Sat, 7 Nov 98 11:14 MET Received: from odie.lippe.de (localhost [127.0.0.1]) by odie.lippe.de (8.9.1/8.8.8) with ESMTP id LAA03040; Sat, 7 Nov 1998 11:14:34 +0100 (CET) (envelope-from lkoeller@odie.lippe.de) Message-Id: <199811071014.LAA03040@odie.lippe.de> X-Mailer: exmh version 2.0.2 2/24/98 From: Lars =?iso-8859-1?Q?K=F6ller?= To: Thierry.Herbelot@alcatel.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: Still freeze with 3.0-RELEASE, PLEASE give me any suggestions!! In-reply-to: Thierry.Herbelot's message of Thu, 05 Nov 1998 09:38:53 +0100. X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ Hum ... > > > Well, I did not read your mail carefully enough ... > > I've reinstalled my home box with 3.0-Release and cvsupped it recently, > but I don't have problems with the sound (or do I ? I'm still struggling > to hear a .wav recording made under Win'95 ... but I don't have time to > investigate this fully). > > could you summarize the problems you have (and more precisely the exact > combination of drivers which crash your machine) ? Shure! I add the working kernel config in the attachement, and the addition of the sound config below, which leads to the instability. All the other stuff works well, also the sound works well most of the time, but suddenly the machine is frozen! I spoke to the OSS team, and they mention, that there are some problems with a kernel routine allocating kernel memory .... >> From: 4Front Technologies >> This is a known problem.....we have found a major bug with FreeBSD 3.0 and >> 2.2.7 for that matter and have notified the kernel group....thus far we haven't >> heard anything. >> THe problem seems to be in a kernel function call vm_page_alloc_contig() which >> allocates kernel memory and for some reason it's not doing the right thing. OSS >> requires this and every now and then we are given some bogus memory address by >> the kernel and that's where it crashes. >> Do stay tuned. >> best regards >> Dev Mazumdar I dont know if it is the same problem with the old voxware driver? But the OSS driver shows some similar problems also under 2.2.7 and 3.0. Only an older version 3.8s runns stable under 2.2.7! Here are the lines of my kernel config which brings the instability into the kernel. # # Audio drivers: `snd', `sb', `pas', `gus', `pca' # controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device awe0 at isa? port 0x620 Any ideas? Thanks and regards Lars -- E-Mail: | Lars Koeller Lars.Koeller@Uni-Bielefeld.DE | UNIX Sysadmin lkoeller@cc.fh-lippe.de | Computing Center PGP-key: | University of Bielefeld http://www.nic.surfnet.nl/pgp/pks-toplev.html | Germany ----------- FreeBSD, what else? ---- http://www.freebsd.org ------------- --==_Exmh_-14575155040 Content-Type: text/plain ; name="TEST"; charset=us-ascii Content-Description: TEST Content-Disposition: attachment; filename="TEST" # # ODIE kernel config file # machine "i386" cpu "I586_CPU" cpu "I686_CPU" # aka Pentium Pro(tm) ident TEST maxusers 32 config kernel root on da1 options SMP #Smmetric Multiprocessor Kernel options APIC_IO #Smmetric (APIC) I/O # Lets always enable the kernel debugger for SMP. options DDB options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options MAXCONS=8 #Number of max. allowed virt. consoles options QUOTA #enable disk quotas options SYSVSHM #System V shared memory support options SYSVSEM #System V Semophore support options SYSVMSG #System V Message support options UCONSOLE #Allow ordinary users to take the #console - this is useful for X. options XSERVER #include code for XFree86 options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #kernel tracing # # ISA devices # controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # # PCI devices # controller pci0 options SCSI_DELAY=15000 # Be pessimistic about Joe SCSI device # Adaptec 2940[U/UW] SCSI Adapter controller ahc0 controller ahc1 # Devices connected device ch0 device da0 device sa0 device cd0 device pass0 # The syntax for wiring down devices is: # AH2940 U controller scbus0 at ahc0 # Seagate ST15150N disk da0 at scbus0 target 0 disk da1 at scbus0 target 1 # Seagate Python 28388, DDS2 tape sa0 at scbus0 target 3 # PIONEER CD-ROM DR-U12X auf ID 4 device cd0 at scbus? # Adic Autochanger mit HP DAT, DDS2 device ch0 at scbus0 target 5 tape sa1 at scbus0 target 6 # AH 2940 UW controller scbus1 at ahc1 # Seagate ST32171W disk da2 at scbus1 target 8 disk da3 at scbus1 target 9 # ps2 mouse device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options SC_HISTORY_SIZE=512 # number of history buffer lines device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr # sio1 (dcf-77) # serial console options BREAK_TO_DEBUGGER # a BREAK on a comconsole goes to DDB options CONSPEED=19200 #default speed for serial console (default 9600) device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr pseudo-device loop pseudo-device ether pseudo-device ccd 4 pseudo-device bpfilter 4 pseudo-device pty 128 pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver) # note that the ``options'' and ``device'' lines must BOTH be defined ! # Teles S0/16.3 options "TEL_S0_16_3" device isic0 at isa? port 0xd80 net irq 10 flags 0x04 vector isicintr # i4b passive cards D channel handling # Q.921 pseudo-device "i4bq921" # Q.931 pseudo-device "i4bq931" # common passive and active layer 4 # layer 4 pseudo-device "i4b" # userland driver to do ISDN tracing (for passive cards oly) pseudo-device "i4btrc" 4 # userland driver to control the whole thing pseudo-device "i4bctl" # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # userland driver for telephony pseudo-device "i4btel" 2 # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 pseudo-device sppp 4 --==_Exmh_-14575155040-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 02:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19112 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 02:33:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19107 for ; Sat, 7 Nov 1998 02:33:23 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.59.248]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4ECC; Sat, 7 Nov 1998 11:33:10 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811070938.SAA15829@tiger1.nownuri.net> Date: Sat, 07 Nov 1998 11:37:06 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: =?us-ascii?Q?=C0=CC=C0=CF=B5=B5?= Subject: RE: Device Driver Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Nov-98 ÀÌÀϵµ wrote: > I would appreciate any additional > information you could send me about making device driver. www.freebsd.org > tutorials > How to Write Device Drivers for FreeBSD... Have fun =) --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 07:31:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10853 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 07:31:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10843 for ; Sat, 7 Nov 1998 07:30:55 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id PAA18406; Sat, 7 Nov 1998 15:29:29 GMT (envelope-from nik) Message-ID: <19981107152928.28834@nothing-going-on.org> Date: Sat, 7 Nov 1998 15:29:28 +0000 From: Nik Clayton To: hackers@FreeBSD.ORG Subject: text mode screen grabber? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone got (or have pointers to useful code) a screen grabber for syscons? Ideally (and given an 80x25 screen) I'm looking for something that would write a 4000 byte file of { character code, colour } tuples. I want to do this so I can put screenshots in the Handbook. I think I can 1. Take a dump of a screen from sysinstall (i.e., run sysinstall on VT1, run the screen dump program on VT2) 2. Read this dump and produce an HTML table 'screenshot' (see ) 3. Read this dump and produce a GIF file. This way I get screenshots suitable for people with and without graphic browsers/printers, and the process is relatively easy to automate. If I was doing this in DOS, I'd just set a pointer to 0xb80000000 and write the next 4000 bytes. I figure I can do this (as a root process) by opening /dev/kmem. But virtual terminals will presumably screw this up. I've had a look at the syscons code, and some of the screen savers, but nothing's leaping out at me saying "Here, this is where the screen buffer is. . .". N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 07:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11931 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 07:49:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA11926 for ; Sat, 7 Nov 1998 07:49:23 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 28656 invoked from network); 7 Nov 1998 15:48:50 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 7 Nov 1998 15:48:50 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id JAA08451; Sat, 7 Nov 1998 09:46:46 -0600 Date: Sat, 7 Nov 1998 09:46:46 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199811071546.JAA08451@bonkers.taronga.com> To: hackers@FreeBSD.ORG Newsgroups: taronga.freebsd.hackers Subject: Re: text mode screen grabber? References: <19981107152928.28834@nothing-going-on.org> Organization: none Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981107152928.28834@nothing-going-on.org>, Nik Clayton wrote: >This way I get screenshots suitable for people with and without graphic >browsers/printers, and the process is relatively easy to automate. Why don't you use "screen"? It'd be easier to modify "screen" to save attributes than to modify a driver, wouldn't it? The only thing you wouldn't be able to save is boot-time stuff, and dmesg should give you that. -- This is The Reverend Peter da Silva's Boring Sig File - there are no references to Wolves, Kibo, Discordianism, or The Church of the Subgenius in this document "The GCOS GERTS interface is so bad that a description here is inappropriate. Anyone seeking to use this interface should seek divine guidance." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 07:54:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12192 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 07:54:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12187 for ; Sat, 7 Nov 1998 07:54:39 -0800 (PST) (envelope-from vanmaren@fast.cs.utah.edu) Received: from fast.cs.utah.edu (fast.cs.utah.edu [155.99.212.1]) by wrath.cs.utah.edu (8.8.8/8.8.8) with SMTP id IAA27112 for ; Sat, 7 Nov 1998 08:54:27 -0700 (MST) Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf) id IAA11756; Sat, 7 Nov 1998 08:54:27 -0700 Date: Sat, 7 Nov 1998 08:54:27 -0700 From: vanmaren@fast.cs.utah.edu (Kevin Van Maren) Message-Id: <199811071554.IAA11756@fast.cs.utah.edu> To: hackers@FreeBSD.ORG Subject: reading crashdumps in 3.0-ELF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone been able to read a crashdump in 3.0-ELF? I'm experiencing the same behavior as in PR gnu/8425 (Even the same problems with a 2.2.X gdb). Do I just need to find/build a 3.0-aout GDB? Thanks, Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 09:59:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21335 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 09:59:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21323 for ; Sat, 7 Nov 1998 09:59:22 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22120; Sat, 7 Nov 1998 09:59:02 -0800 (PST) (envelope-from jdp) Message-Id: <199811071759.JAA22120@austin.polstra.com> To: vanmaren@fast.cs.utah.edu Subject: Re: reading crashdumps in 3.0-ELF In-Reply-To: <199811071554.IAA11756@fast.cs.utah.edu> References: <199811071554.IAA11756@fast.cs.utah.edu> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Sat, 07 Nov 1998 09:59:02 -0800 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811071554.IAA11756@fast.cs.utah.edu>, Kevin Van Maren wrote: > Has anyone been able to read a crashdump in 3.0-ELF? > I'm experiencing the same behavior as in PR gnu/8425 > (Even the same problems with a 2.2.X gdb). Do I just > need to find/build a 3.0-aout GDB? Yes, it's awkward, but that's what you need to do in the current state of the world. cd /usr/src/gnu/usr.bin/gdb make clean cleandepend env OBJFORMAT=aout make obj depend env OBJFORMAT=aout make all install clean cleandepend If your -current is recent enough, the new gdb will be installed into /usr/libexec/aout. You can then run it with "gdb -aout ...". Your ELF gdb will also still be available. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 10:18:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23097 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 10:18:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from limbo.rtfm.net (limbo.rtfm.net [207.198.222.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23092; Sat, 7 Nov 1998 10:18:03 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.9.1/8.9.1) id NAA20079; Sat, 7 Nov 1998 13:13:26 -0500 (EST) (envelope-from nathan) Message-ID: <19981107131325.A20032@rtfm.net> Date: Sat, 7 Nov 1998 13:13:25 -0500 From: Nathan Dorfman To: Amancio Hasty Jr , advocacy@FreeBSD.ORG, imp@village.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ariel Faigon: The Holloween Document (fwd) References: <199811032201.OAA13297@netcom14.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811032201.OAA13297@netcom14.netcom.com>; from Amancio Hasty Jr on Tue, Nov 03, 1998 at 02:01:40PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 03, 1998 at 02:01:40PM -0800, Amancio Hasty Jr wrote: > The e-mail made it to today's San Jose Mercury NewsPaper in the business > section. The news article claims that the e-mail was confirmed by > Microsoft to be authenticate --- not sure who to believe Microsoft or > the Linux camp 8) > > Cheers, > Amancio > http://www.microsoft.com/ntserver/highlights/editorletter.asp -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 10:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26489 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 10:48:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sand.global.net.uk (sand.global.net.uk [194.126.82.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26484 for ; Sat, 7 Nov 1998 10:48:13 -0800 (PST) (envelope-from peter@aspltd.globalnet.co.uk) Received: from p39s07a01.client.global.net.uk ([195.147.135.58] helo=hal) by sand.global.net.uk with smtp (Exim 2.05 #1) id 0zcDOx-0002ID-00 for freebsd-hackers@FreeBSD.ORG; Sat, 7 Nov 1998 18:47:59 +0000 Message-ID: <3644954C.4D8F@aspltd.globalnet.co.uk> Date: Sat, 07 Nov 1998 18:45:32 +0000 From: Peter Pendlebury Reply-To: peter@alliedsoftware.co.uk Organization: ASP Ltd. X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir or Madam, Could you please add me to your mailing list? Thanks in advance, Peter Pendlebury ASP Ltd, Stockport UK. Email: peter@alliedsoftware.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 10:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27931 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 10:59:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27926 for ; Sat, 7 Nov 1998 10:59:26 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id OAA20095; Sat, 7 Nov 1998 14:02:00 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Sat, 7 Nov 1998 14:02:00 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: peter@alliedsoftware.co.uk cc: freebsd-hackers@FreeBSD.ORG Subject: Re: subscribe In-Reply-To: <3644954C.4D8F@aspltd.globalnet.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG funny how we tell people how to get off the list, but not on... what about people that see these messages on an archive :) anyhow, peter, send mail to majordomo@freebsd.org with the only thing in the message: subscribe freebsd-hackers Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Sat, 7 Nov 1998, Peter Pendlebury wrote: > Dear Sir or Madam, > > Could you please add me to your mailing list? > > Thanks in advance, > Peter Pendlebury > ASP Ltd, Stockport UK. > Email: peter@alliedsoftware.co.uk > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 11:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02106 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 11:37:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02100 for ; Sat, 7 Nov 1998 11:37:16 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-38.camalott.com [208.229.74.38]) by mail.camalott.com (8.8.7/8.8.7) with ESMTP id NAA07525; Sat, 7 Nov 1998 13:37:15 -0600 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA03054; Sat, 7 Nov 1998 13:36:42 -0600 (CST) (envelope-from joelh) To: obrien@NUXI.com Cc: Hackers Mailing List Subject: Re: Memory leak location tool? References: <19981030141624.A1244@thought.org> <86u30lms4a.fsf@detlev.UUCP> <19981105023418.A5837@nuxi.com> From: Joel Ray Holveck Date: 07 Nov 1998 13:36:38 -0600 In-Reply-To: "David O'Brien"'s message of "Thu, 5 Nov 1998 02:34:18 -0800" Message-ID: <86ww57qoqh.fsf@detlev.UUCP> Lines: 14 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the >> following: > Closely related is also ElectricFence. Correct me if I'm wrong, but EF doesn't detect leaks, does it? Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 11:52:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03711 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 11:52:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lodge.guildinternational.com (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03702 for ; Sat, 7 Nov 1998 11:52:21 -0800 (PST) (envelope-from davidc@acns.ab.ca) Received: from acns.ab.ca (dslc00912.adsl.telusplanet.net [209.115.158.150]) by lodge.guildinternational.com (8.9.1/8.9.1) with ESMTP id MAA05972 for ; Sat, 7 Nov 1998 12:40:44 -0700 (MST) Message-ID: <3644A494.C40D3C8F@acns.ab.ca> Date: Sat, 07 Nov 1998 12:50:44 -0700 From: Chad David Organization: ACNS Inc. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #299 References: <199811062019.MAA25886@hub.freebsd.org> <36449AA9.102BBB11@acns.ab.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 5 Nov 1998 16:03:02 -0500 (EST) > From: Ryan Ziegler > Subject: Re: Documentation upgrade: where are the other humans? > > lets move this to advocacy, Before this thread dies here (I don't subscribe to advocacy) I would like to volunteer. Over the past few months I can't count the times I have wished for better documentation (LKM -> KLD would be nice). Just when I finish writing something someone changes the interface, or the library is upgraded. It's not as bad as Linux, but is was a little depressing to joyfully congratulate myself for getting my first LKM device driver to work, only to read five minutes later in Jordan's 3.0 announcement that LKM was dead. > > > On Wed, 4 Nov 1998, Terry Lambert wrote: > > > > When not getting paid, programmers tend to code what they find > > > interesting. We can say the same thing for writers when writing. I would > > > say technical documentation is not the most exciting literary form, nor > > > are the arguments for kmem_free() the most exciting subject matter. > I find the arguments for kmem_free() to be very exciting. A programmer is only as good as the functions he can call. The idea that you can just learn the language and find the functions as you need them doesn't work very well if there are no docs for the functions you want or docs at least describing the implementation. If there were a man page for kmem_free() and any related calls it seems unlikely the discussion would have made it here. > > > > > > What we need are technical writers who feel a severe allegiance to > > > FreeBSD. > > > > Or people who get off on techinical writing, or a professor with > > an allegiance to FreeBSD in charge of a Technical Writing class. > > > > I have to say that there exist people who actually enjoy doing > > things that the rest of us would find about as enjoyable as > > home dentistry (those of you with capped teeth, imagine removing > > your caps with an awl). > > > > I have a sister who happens to enjoy double-column bookkeeping. > > It takes all kinds... > > > > > > I also think that it's very likely that someone who had to take > > a technical writing class for their CS/CIS/MIS/BIS degree would > > have classmates who were English Majors or whatever, also looking > > for writing projects, and that it would be a good idea to encourage > > them suggesting FreeBSD documentation to their classmates as a > > potential "project fodder gold mine". > > > > I know that if I were to adjunct teach a technical writing class, > > I'd be please as punch if I could find a never-ending supply of > > projects, all in the same general problem space; it'd make it a > > hell of a lot easier to grade on a curve. > > Its more of a question of how many people who really enjoy home > dentistry exist. Not many, simply isn't glamorous enough. What we need to > do is to paint the technical writer as some sort of a hero or rogue. Give > him a catchy name. "The dockers, a brand new breed of technical writers, > infiltrating open source archives and documenting everything they see. > They stop at nothing to see the cvs repositories of the world bloating up > with inline documentation." Get an article on CNet and we're off. > > Approaching professors of technical writing classes doesn't seem like a > bad idea, but those students have no allegiance to freebsd. We would > easily wind up with inferior documentation (you can argue if thats better > than no documentation at all). > Maybe we could set up a synergy with the professor. The prof refers his > students to us, they do what we want, and if we accept their work they get > A's, otherwise, F's. Point me at what needs to be documented. I am only one person, but one person can make a huge difference to something like documentation over a year. > > > > > > > > > > Maybe it's just that the majority of people are too busy sitting > > > > on their butts hacking code in cave-like computer labs to talk > > > > to people in other departments on campus? > > > > > > You're not suggesting that we're a tad clannish, are you? :) > > > > Well, this *is* a "free software" project, not a "free product" > > project... it's kind of self-limiting in its involvement of > > people not that interested in producing software. > > > > The Linux Documentation project has that whole "Young Communist" > > thing going for it... Young Communist? "Coders of the world unite! You have nothing to lose but the inability to figure out where the hell kmem_free() is actually declared without resorting to find . -exec grep -l kmem_free {} \;!" If you think about it OSS is largely a communist idea. "From each according to his abilities, to each according to his needs". As long as you can keep money out of the picture it will continue to work. Watch out Linux. I digress. > > I am still suprised to see that the microsoft vs good-software division > hasn't erased the their-free-os vs our-free-os division. I also would > think that with all the talk of OSS nowadays, people would be eager to > latch onto the 'its not just linux and apache, its everyone' idea. Maybe > they have, I don't know. Has freebsd tried to jump in the pool yet? Maybe, > also, I make too many assumptions > > - -Ryan > > > Terry Lambert > > terry@lambert.org > > --- > > Any opinions in this posting are my own and not those of my present > > or previous employers. > > I apologize if this is not the place to volunteer, but I find that if you want to be heard this is the best place to talk. I also figured that it is at least as valid as the smoke signals and genetics threads :-). Chad David davidc@acns.ab.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 11:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04328 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 11:58:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04323 for ; Sat, 7 Nov 1998 11:58:43 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id LAA12572; Sat, 7 Nov 1998 11:59:10 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Chad David cc: hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #299 In-reply-to: Your message of "Sat, 07 Nov 1998 12:50:44 MST." <3644A494.C40D3C8F@acns.ab.ca> Date: Sat, 07 Nov 1998 11:59:10 -0800 Message-ID: <12568.910468750@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > like to volunteer. Over the past few months I can't count the times I > have wished for better documentation (LKM -> KLD would be nice). > Just when I finish writing something someone changes the interface, Yes, well, technical docs of this nature are definitely a job which requires that someone actively keep it up to date or it becomes rapidly worthless. Nik Clayton has just taken over as the new Documentation Project Manager (yea Nik!) and perhaps this is something he'd be willing to give you some bootstrapping assistance with. His early docs on coming to grips with SGML are already quite good and I imagine that the Docbook DTD could be used (or enhanced) to do programmer's API documentation just as well as the Handbook. > depressing to joyfully congratulate myself for getting my first LKM > device driver to work, only to read five minutes later in Jordan's 3.0 > announcement that LKM was dead. Sorry about that.. . Is it at least some consolation that what it's getting replaced with is a whole lot better? :) > Point me at what needs to be documented. I am only one person, but /usr/src/sys :-) > one person can make a huge difference to something like documentation > over a year. Indeed! I say go for it, by all means. FreeBSD certainly lacks for programmer's guides and that's a real shame. We could do better. Follow-ups to doc please, thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 12:18:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06154 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 12:18:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles356.castles.com [208.214.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06149 for ; Sat, 7 Nov 1998 12:17:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA05947; Sat, 7 Nov 1998 12:17:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811072017.MAA05947@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: " " cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Device Driver In-reply-to: Your message of "Sat, 07 Nov 1998 18:38:56 +0900." <199811070938.SAA15829@tiger1.nownuri.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 07 Nov 1998 12:17:02 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA06150 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Firstly, welcome! We've been looking for someone interested in this for a while now. You will best understand FreeBSD's architecture by looking at the source code. We are currently adopting a new modular bus architecture, which will make writing your driver much easier. For an example of new the bus design, see the iicbus code in /sys/dev/iicbus. The author of this code, Nicholas Souchu (nsouch@freebsd.org) should be able to answer your questions, and Doug Rabson (dfr@freebsd.org) is the architect of the new design, and will be able to help you further. Please study the source code a little, and ask questions as you go. It would also help to know which 1394 hardware you planned to support. > My major field of interest is network. Now I am interested > to IEEE 1394 and internetworing in home. > > I hope to make IEEE 1394 device driver for FreeBSD. > But it is difficult for me to understand FreeBSD architecture > and requirement. > Although I find relate information, I don't have it. > If you help me, Please give information for making. > > Also, do you know who help me? If you know, inform me. > Then very very thank you. > > I would appreciate any additional > information you could send me about making device driver. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 12:18:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06400 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 12:18:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06395 for ; Sat, 7 Nov 1998 12:18:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id MAA08930; Sat, 7 Nov 1998 12:18:02 -0800 (PST) (envelope-from obrien) Message-ID: <19981107121802.F13487@nuxi.com> Date: Sat, 7 Nov 1998 12:18:02 -0800 From: "David O'Brien" To: Joel Ray Holveck Cc: Hackers Mailing List Subject: Re: Memory leak location tool? Reply-To: obrien@NUXI.com References: <19981030141624.A1244@thought.org> <86u30lms4a.fsf@detlev.UUCP> <19981105023418.A5837@nuxi.com> <86ww57qoqh.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <86ww57qoqh.fsf@detlev.UUCP>; from Joel Ray Holveck on Sat, Nov 07, 1998 at 01:36:38PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Closely related is also ElectricFence. > > Correct me if I'm wrong, but EF doesn't detect leaks, does it? Nope. But like I said closely. :-) It helps with the reverse problem, more free()'s than malloc()'s or accessing memory that has been free()ed. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 13:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13023 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 13:42:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13018 for ; Sat, 7 Nov 1998 13:42:19 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id VAA08548; Sat, 7 Nov 1998 21:12:09 GMT (envelope-from nik) Message-ID: <19981107211208.12650@nothing-going-on.org> Date: Sat, 7 Nov 1998 21:12:08 +0000 From: Nik Clayton To: hackers@FreeBSD.ORG Subject: TeX problems; Doc. Proj. needs you! Reply-To: nik@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ multi-posted, because of x-post limits, to -hackers, -advocacy, -newbies, and -doc. -hackers, because we might have some hackers who know TeX, but wouldn't think of reading -doc because they don't think they can write. -advocacy, for similar reasons -newbies, for similar reasons (some of the folks in there are new to FreeBSD, but not knew to Unix and/or Unix apps) -doc, because it's Doc. Proj. related. Also posted to comp.unix.bsd.freebsd.misc. Reply-To set back to me, nik@freebsd.org ] Calling all TeX hackers, your Documentation Project needs you. The Handbook has been converted to DocBook. This process is (bar some merging from current content) complete. One of the last hurdles is getting PostScript and PDF versions of the Handbook generated. When that's done, we can retire the LinuxDoc version (and start working on the FAQ, and other tutorials). I don't know TeX, and I don't have reference materials handy. There's also a bunch of other Doc. Proj. related stuff that I can do to help bring others up to speed. So I need your help. Briefly, this is how the Handbook is now arranged; * The DocBook Handbook is in the doc/en/handbook subdirectory of the CVS tree. There's a Makefile in there, which should work, as long as you've installed ports/textproc/docproj -- this is a meta-port which will pull in all the others. * The Handbook is processed by an application called Jade. Jade produces a .tex file. * This .tex file then needs to be used, in conjunction with some macros, called JadeTeX, to produce a DVI file. The JadeTeX macros also have a PDF variant. JadeTex needs teTeX v0.9. In theory, that's all the pieces that are needed. I can sort of get things to work. But there are problems, and I don't know how to fix them. This where I've got to so far; * Download and install textproc/docproj from the ports system. This will give you Jade, the DTDs for the Doc. Proj. (don't worry, you don't need to know what they are). * Download and install print/teTeX-beta from the ports system (you want a version which identifies itself as 0.9-YYMMDD). It's large, ~30MB of required distfiles. * Configure TeX with /usr/local/bin/texconfig. - Rebuild the ls-R database - Change the hyphenation table. Uncomment the British entry (and keep a stiff upper lip as you do so). - Set an xdvi default papertype - Set a dvips default papertype - In the fonts menu, add global write permissions * Fetch the JadeTeX macro package from a CTAN repository, such as You want the contents of that directory and all the subdirectories, so somewhere that supports on the fly tarring of directories is useful. The RCS string in jadetex.dtx should be 2.3 or higher. * Install it. It comes with a Makefile, but it's got problems; 1. The line tex -ini "&hugelatex" jadetex.ini doesn't work, there is no &hugelatex. I used &latex. 2. It references dsssl.def and isoents.tex. I don't know where they come from. 3. Building pdfjadetex doesn't work, due to problems with hyperref. Ignoring those problems, I can get it to install using the Makefile. * Checkout a copy of /doc/en/handbook/ from the CVS repository. You'll also need /doc/en/sgml checked out (and in the same relative position in the filesystem). Run make handbook.tex and wait for it to generate a ~5MB .tex file. If the "handbook.tex" target doesn't exist, it means I haven't committed the Makefile yet. Instead, you can run the following /usr/local/bin/jade -c ../../sgml/catalog \ -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ -c /usr/local/share/sgml/docbook/3.0/catalog \ -c /usr/local/share/sgml/jade/catalog \ -d /usr/local/share/sgml/docbook/dsssl/modular/print/docbook.dsl \ -t tex handbook.sgml * Bump up your TeX limits, since the Handbook's size pushes TeX fairly hard. In particular, you want these settings hash_extra = 60000 pool_size = 1000000 max_strings = 70000 in /usr/local/share/texmf/web2c/texmf.cnf (adjust the path depending on your $PREFIX setting). * Run tex "&jadetex" handbook.tex You will see errors go by, but it will eventually generate handbook.dvi. The generated file has some problems, in particular, most of the ISO entities (>, ö, and so on) are still in that form, and haven't been translated. Also, the table of contents doesn't have the page numbers correct. You should also be able to do tex "&pdfjadetex" handbook.tex to get the PDF version. I can't do this because of the hyperref problems I outline above. If you can get this working, *and* come up with a jadetex port, I'll be very grateful. If you can get this working, and can give me detailed instructions so that I can write a jadetex port, I'll still be pretty grateful :-) Many thanks to anyone who can help with this. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 13:42:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13223 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 13:42:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13180; Sat, 7 Nov 1998 13:42:53 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id VAA11901; Sat, 7 Nov 1998 21:39:33 GMT (envelope-from nik) Message-ID: <19981107213933.43220@nothing-going-on.org> Date: Sat, 7 Nov 1998 21:39:33 +0000 From: Nik Clayton To: "Jordan K. Hubbard" , Chad David , hackers@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Documentation (was Re: freebsd-hackers-digest V4 #299) Reply-To: doc@FreeBSD.ORG References: <3644A494.C40D3C8F@acns.ab.ca> <12568.910468750@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <12568.910468750@time.cdrom.com>; from Jordan K. Hubbard on Sat, Nov 07, 1998 at 11:59:10AM -0800 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ x-posted to hackers, where it started, and doc, where it should continue. Reply-to set to doc] On Sat, Nov 07, 1998 at 11:59:10AM -0800, Jordan K. Hubbard wrote: > Yes, well, technical docs of this nature are definitely a job which > requires that someone actively keep it up to date or it becomes > rapidly worthless. I know nothing about it, but what are people's thoughts on using some sort of 'literate' programming system (is that the right term?) in FreeBSD. After a day spent playing with TeX, the Web2c system is obviously the nearest example. Or maybe there's a C equivalent to JavaDoc? As I say, I know nothing about these things, I'm just throwing it out as a discussion point. > Nik Clayton has just taken over as the new > Documentation Project Manager (yea Nik!) and perhaps this is something > he'd be willing to give you some bootstrapping assistance with. Certainly. Ask and ye shall receive and all that. The -doc mailing list is the general place to ask these sorts of questions (as Jordan has indicated). Take a look at for my half-completed draft of a primer for contributors to the FreeBSD documentation effort. I'm trying to get a critical mass of documents together so that the learning curve is sufficiently shallow for most people that they can just get stuck in documenting, rather than spending time fighting with the toolchain. > His > early docs on coming to grips with SGML are already quite good and I > imagine that the Docbook DTD could be used (or enhanced) to do > programmer's API documentation just as well as the Handbook. Absolutely. DocBook is designed for exactly that sort of technical documentation. In fact, Someone on -doc recently made the suggestion that we shift the manual pages from *roff format to DocBook. That's possibly a touch too controversial at the moment, but might not be beyond the bounds of possiblity for the medium term future. In fact, it might be worth doing that within the Doc. Project, treating them as another translation (similar to the Japanese translation) of the manual pages? See the (short) thread in -doc starting with a message from Christine McKinty, , subject is "FreeBSD manpages in SGML?", messageID is <199811061532.QAA26783@odin.France.Sun.COM>. > > depressing to joyfully congratulate myself for getting my first LKM > > device driver to work, only to read five minutes later in Jordan's 3.0 > > announcement that LKM was dead. > > Sorry about that.. . Is it at least some consolation that what it's > getting replaced with is a whole lot better? :) It's also still useful. There are a lot of 2.2.x systems out there for which it will be useful. And it can be added to a growing corpus of sample documentation to point people to and say "Steal ideas from this." :-) > > Point me at what needs to be documented. I am only one person, but > > /usr/src/sys :-) And pick a part of that, particularly if you're already familiar with it. Better still, work out who's responsible for it (say, syscons, maintained by Soren) and work with them. Ideally, you don't want them making large changes without first working with you to make sure it stays documented. This is one of my concerns with the Handbook at the moment. For example, the section on how FreeBSD boots is getting more and more out of date as -current progresses, and I don't know if anyone's stuck their hand up to document it. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 15:04:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20234 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 15:04:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20200; Sat, 7 Nov 1998 15:04:16 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id AAA04413; Sun, 8 Nov 1998 00:03:17 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 8 Nov 1998 00:03:16 +0100 (MET) Mime-Version: 1.0 To: doc@FreeBSD.ORG Cc: "Jordan K. Hubbard" , Chad David , hackers@FreeBSD.ORG Subject: Re: Documentation (was Re: freebsd-hackers-digest V4 #299) References: <3644A494.C40D3C8F@acns.ab.ca> <12568.910468750@time.cdrom.com> <19981107213933.43220@nothing-going-on.org> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 08 Nov 1998 00:03:16 +0100 In-Reply-To: Nik Clayton's message of "Sat, 7 Nov 1998 21:39:33 +0000" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA20205 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton writes: > Or maybe there's a C equivalent to JavaDoc? I'm sure any halfway competent Perl hacker could write one in a few hours. I've done similar stuff for a project I worked on this summer. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 15:26:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21823 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 15:26:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21818; Sat, 7 Nov 1998 15:26:35 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (cam [10.0.0.50]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id BAA25226; Sun, 8 Nov 1998 01:25:04 +0200 Message-ID: <3644D6B7.C10CBF9E@Shevchenko.Kiev.UA> Date: Sun, 08 Nov 1998 01:24:39 +0200 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: "Dag-Erling C. Smørgrav" CC: doc@FreeBSD.ORG, "Jordan K. Hubbard" , Chad David , hackers@FreeBSD.ORG Subject: Re: Documentation (was Re: freebsd-hackers-digest V4 #299) References: <3644A494.C40D3C8F@acns.ab.ca> <12568.910468750@time.cdrom.com> <19981107213933.43220@nothing-going-on.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling C. Smørgrav wrote: > > Nik Clayton ?nik@nothing-going-on.demon.co.uk? writes: > ? Or maybe there's a C equivalent to JavaDoc? > > I'm sure any halfway competent Perl hacker could write one in a few > hours. I've done similar stuff for a project I worked on this summer. > This problem can be very simple or very huge, depend from what you want to receive. for very simple friend of javadoc you can look at my sdoc. http://cam.grad.kiev.ua/~rssh/sdoc/ Now I need *really* C++ documentation generator and think about creating gcc backend. > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- @= //RSSH mailto:Ruslan@Shevchenko.Kiev.UA CORBA in Ukraine & ex-USSR: http://www.corbadev.kiev.ua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 22:03:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05021 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 22:03:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hotmail.com (f239.hotmail.com [207.82.251.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA05002 for ; Sat, 7 Nov 1998 22:03:38 -0800 (PST) (envelope-from beavix@hotmail.com) Received: (qmail 1628 invoked by uid 0); 8 Nov 1998 06:03:18 -0000 Message-ID: <19981108060318.1627.qmail@hotmail.com> Received: from 203.33.252.180 by www.hotmail.com with HTTP; Sat, 07 Nov 1998 22:03:18 PST X-Originating-IP: [203.33.252.180] From: "the beavix" To: current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Serial port oddnesses in -CURRENT MIME-Version: 1.0 Content-Type: text/plain Date: Sat, 07 Nov 1998 22:03:18 PST Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I've got an Intel PR440FX dual-PPro motherboard, and am having some problems regarding serial ports in -CURRENT (which I built 3 days ago). Nov 8 13:53:34 ether /kernel: sio1: 1 more silo overflow (total 121) That's the 121st message I've got so far, and pppd has only been running for <10 minutes. I think I might have traced the problem, here's a quick snippet from dmesg: sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A Now what puzzles me if that any serial port should complain, it should be sio0, not sio1. What is similarly strange is that sio1 is not being used, it's been disabled in the BIOS. All I am running is an external Banksia 56k modem (connecting at 33k6), which hangs off of sio0 on the board. For one reason or another, BIOS won't let me set sio0 to use COM1 (even though I have a PS/2 mouse), so I'm stuck with COM2 for sio0. sio1 has been set to disabled in the BIOS, and there's nothing hanging off of the connector. Here I am puzzled. You can't use an external modem on a serial port if it's disabled, so why am I getting sio1 errors when the modem is using sio0? I've tried disabling sio0 and using sio1 from the BIOS, but this hasn't worked either. sio1 can take COM2 if sio0 is disabled; and when I try this, cu just sits there with "Connected" but doesn't take input. The modem doesn't seem to respond. Any ideas? Info would be greatly appreciated! -- beav. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 7 22:27:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07631 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 22:27:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07626; Sat, 7 Nov 1998 22:27:08 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id WAA09353; Sat, 7 Nov 1998 22:26:59 -0800 (PST) Message-ID: <19981107222659.L25743@Alameda.net> Date: Sat, 7 Nov 1998 22:26:59 -0800 From: Ulf Zimmermann To: the beavix , current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Serial port oddnesses in -CURRENT Reply-To: ulf@Alameda.net References: <19981108060318.1627.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981108060318.1627.qmail@hotmail.com>; from the beavix on Sat, Nov 07, 1998 at 10:03:18PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an Intel DK440LX motherboard, there if I disable the serial ports, they get seen, but don't work when I try to use them. On Sat, Nov 07, 1998 at 10:03:18PM -0800, the beavix wrote: > Hi guys, > > I've got an Intel PR440FX dual-PPro motherboard, and am having some > problems regarding serial ports in -CURRENT (which I built 3 days ago). > > Nov 8 13:53:34 ether /kernel: sio1: 1 more silo overflow (total 121) > > That's the 121st message I've got so far, and pppd has only been running > for <10 minutes. I think I might have traced the problem, here's a quick > snippet from dmesg: > > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 8250 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > > Now what puzzles me if that any serial port should complain, it should > be sio0, not sio1. What is similarly strange is that sio1 is not being > used, it's been disabled in the BIOS. > > All I am running is an external Banksia 56k modem (connecting at 33k6), > which hangs off of sio0 on the board. For one reason or another, BIOS > won't let me set sio0 to use COM1 (even though I have a PS/2 mouse), so > I'm stuck with COM2 for sio0. sio1 has been set to disabled in the BIOS, > and there's nothing hanging off of the connector. > > Here I am puzzled. You can't use an external modem on a serial port if > it's disabled, so why am I getting sio1 errors when the modem is using > sio0? > > I've tried disabling sio0 and using sio1 from the BIOS, but this hasn't > worked either. sio1 can take COM2 if sio0 is disabled; and when I try > this, cu just sits there with "Connected" but doesn't take input. The > modem doesn't seem to respond. > > Any ideas? Info would be greatly appreciated! > > -- > > beav. > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message