problem whit kld and write(2) ...
Hi :) I'm coding an kld for fbsd 4.x for using encrypted file (such sfs/cfs/tcfs) whis some difference ... but I've got a problem, when I redir the system call write, I must change his 2nd argument ( int fd, const void *buf, int nbyte) buf point to buffer whit data to copy, I cannot change it because is declared as const. I've used my new buffer big nbyte byte, but when i call original write syscall they return EFAULT (Bad Address) because my pointer isn't from user space memory related with the process that calling write... I'm follow the function on write, from: sys_generic.c: unmodified: line 290 of 972 [29%] it call getfp for fill struct *file, and after dofilewrite, static func: sys_generic.c: unmodified: line 329 of 972 [33%] the error is generated as return value from fo_write, at line 363, I've search fo_write, I've find it on /usr/src/sys/sys/file.h on struct file, fo_write is function pointer, on file.h, at line 156, fo_write call fo_write ... but it don't generate a loop, and return EFAULT ... anyone has some ideas ? bye and thanks, vecna :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
get tun0's ip from my program
I want to get tun0's two ip addresses. and add ipfw rules to system at my program. How can I do it?is there a function? or have document describe it. someone please tell me! thank you! oscar [EMAIL PROTECTED] ~~~ ¡°200¼ÒÁ¬ËøÍøÕ¾£¬ÈÃÑÛ¾¦³¢³¢ÏÊ¡± http://www.chinese.com ~~~ 163µç×ÓÓʾ֣¬¸øÄú¸üÍêÃÀEmail·þÎñ£¡ http://www.163.net ~~~ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: get tun0's ip from my program
On Mon, Dec 04, 2000 at 08:12:50PM +0800, [EMAIL PROTECTED] wrote: I want to get tun0's two ip addresses. and add ipfw rules to system at my program. How can I do it?is there a function? or have document describe it. someone please tell me! thank you! See the tun(4) manpage, it describes the tun interface. It refers to 'the usual network-interface ioctl(2)s, such as SIOCSIFADDR and SIOCSIFNETMAS'. I think in this case you need something like SIOCGIFADDR. As usual when talking about network interfaces, my recommendation would be 'see the ifconfig(8) source, ifconfig usually knows how to do its job'. Hope that helps. G'luck, Peter -- If this sentence didn't exist, somebody would have invented it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: call for testers: nsswitch + dynamic linking
hi, there! On Wed, 25 Oct 2000, Jacques A. Vidrine wrote: nsswitch extends the C library so that arbitrary sources may be consulted by database routines such as getpwent, gethostbyname, and so on. This implementation was based on NetBSD's implementation. I have enhanced it to make the interfaces thread safe, and to provide support for dynamically loaded nsswitch modules. Patches for 4-STABLE and 5-CURRENT are at: http://www.nectar.com/freebsd/nsswitch. Also available there are patches for PADL.COM's nss_ldap so that it may be used with FreeBSD. Incidentally this also adds reentrant versions of common routines such as getpwnam_r. Note that routines that eventually call the resolver are only as thread safe as the resolver -- i.e. not really. bind 8 has nearly-thread-safe libresolv (only res_debug.c functions are not thread-safe) and this with your NSS patches will give us thread-safe (at least IPv4) resolver. any plans to merge libresolv from bind 8? btw when do you plan to MFC NSS stuff? thanks, /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: res_ functions thread safe?
Alfred Perlstein [EMAIL PROTECTED] writes: This is useless for a commercial product for obvious reasons. I'm looking for something freely available. Perhaps ftp://athena-dist.mit.edu/pub/ATHENA/ares/ares-1.1.0.tar.gz is useful? It comes with an MIT-style license. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
New 4.2 complaint.
I just upgraded our main server to 4.2 I would like to know why nslookup is complaining about being deprecated and may be removed from future releases. (why someone would remove it) Are you guys on crack? nslookup is still tought as part of basic TCP/IP troubleshooting technique, and I think your message about having it removed is wrong, and would take away from FreeBSD's user friendlyness. Why would you take away a tool that's installed on almost every TCP/IP application? I'm no Guru, but I use nslookup about 2000 times a day, and it pisses me off to see that it may be missing from future releases. My 2 cents. Chuck Rock To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New 4.2 complaint.
On Mon, Dec 04, 2000 at 10:16:29AM -0600, Chuck Rock wrote: I just upgraded our main server to 4.2 I would like to know why nslookup is complaining about being deprecated and may be removed from future releases. (why someone would remove it) On my laptop using RELENG_4 a few days after 4.2-RELEASE: jedgar@darkstar:~$ uname -a FreeBSD darkstar.rcinfo.net 4.2-STABLE FreeBSD 4.2-STABLE #2: Wed Nov 29 14:00:28 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/DARKSTAR i386 jedgar@darkstar:~$ nslookup freefall.freebsd.org Server: gatekeeper.rcinfo.net Address: 10.0.0.1 Name:freefall.freebsd.org Address: 216.136.204.21 jedgar@darkstar:~$ Can you please show the warning you are receiving? -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New 4.2 complaint.
On Mon, 4 Dec 2000, Chuck Rock wrote: I'm no Guru, but I use nslookup about 2000 times a day, and it pisses me off to see that it may be missing from future releases. My 2 cents. Chuck Rock Learn to use dig, it's much more useful for debugging purposes. That being said, I doubt nslookup would actually be removed anytime soon, so don't get your feathers all ruffled. Mike "Silby" Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New 4.2 complaint.
On Mon, 4 Dec 2000 10:16:29 -0600
"Chuck Rock" [EMAIL PROTECTED] said:
carock I just upgraded our main server to 4.2
carock I would like to know why nslookup is complaining about being deprecated and
carock may be removed from future releases. (why someone would remove it)
I guess you are using BIND9 version of nslookup. It's not a FreeBSD
shipped version.
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
RE: New 4.2 complaint.
Sorry, I found out it's from BIND 9.0.1 Apparently they install their own nslookup command, and it must be first in my path statement before FreeBSD's Their command is in /usr/local/bin/nslookup and FreeBSD's is in /usr/sbin/nslookup My path statement in the .cshrc file has all my bin path's listed before sbin path's. Sorry for the blowup :-) Chuck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Faulhaber Sent: Monday, December 04, 2000 10:24 AM To: Chuck Rock Cc: FreeBSD Hackers Subject: Re: New 4.2 complaint. On Mon, Dec 04, 2000 at 10:16:29AM -0600, Chuck Rock wrote: I just upgraded our main server to 4.2 I would like to know why nslookup is complaining about being deprecated and may be removed from future releases. (why someone would remove it) On my laptop using RELENG_4 a few days after 4.2-RELEASE: jedgar@darkstar:~$ uname -a FreeBSD darkstar.rcinfo.net 4.2-STABLE FreeBSD 4.2-STABLE #2: Wed Nov 29 14:00:28 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/DARKSTAR i386 jedgar@darkstar:~$ nslookup freefall.freebsd.org Server: gatekeeper.rcinfo.net Address: 10.0.0.1 Name:freefall.freebsd.org Address: 216.136.204.21 jedgar@darkstar:~$ Can you please show the warning you are receiving? -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/lib/libc/sys mmap.2
On Sun, Dec 03, 2000 at 12:17:36PM -0800, Matt Dillon wrote: dillon 2000/12/03 12:17:36 PST Modified files: lib/libc/sys mmap.2 Log: Add warning on file-fragmentation issues related to MAP_NOSYNC I've got a (hopefully) quick question about this warning. If I'm using mmap to create shared memory segments and I don't care about the contents of the file after the run does this fragmentation hurt me? I'm asking because I've got code that uses up to 1.3GB of mmaped storage. The mmaped storage may be larger then physical memory at this point, but the portion I actually use should fit in RAM. Thanks, Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: natd bug
I had the same thing until I removed rule 200 in rc.firewall (using open)
#${fwcmd} add 200 deny all from any to 127.0.0.0/8
Now it works, but I feel a bit less secure, but I don't have anything of
great importance on the box.
One thing I noticed in common, is we're both running Etherlink III's.
(although mine is isa and yours is PCI) I have a friend that a pair of fxp's,
and I tried his rc.firewall, that works fine for him, but doesn't for me.
-Charlie
dmesg is as follows.
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Fri Sep 8 10:09:47 GMT 2000
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MIDGARD
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 463911525 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (463.91-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x660 Stepping = 0
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
real memory = 134217728 (131072K bytes)
avail memory = 127090688 (124112K bytes)
Preloaded elf kernel "kernel.ko" at 0xc0364000.
Preloaded elf module "linux.ko" at 0xc03640a0.
Preloaded elf module "usb.ko" at 0xc0364140.
Preloaded elf module "ugen.ko" at 0xc03641dc.
Preloaded elf module "ums.ko" at 0xc0364278.
Preloaded elf module "randomdev.ko" at 0xc0364314.
Preloaded elf module "linprocfs.ko" at 0xc03643b8.
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: Matrox MGA G400 AGP graphics accelerator at 0.0 irq 11
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 15 at device
7.2 on pci0
usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ugen0: BELKIN UPS, rev 1.10/0.06, addr 2
ums0: Logitech USB Mouse, rev 1.10/6.10, addr 3, iclass 3/1
ums0: 4 buttons and Z dir.
intpm0: Intel 82371AB Power management controller port 0x5000-0x500f irq 9 at device
7.3 on pci0
intpm0: I/O mapped 5000
intpm0: intr IRQ 9 enabled revision 0
smbus0: System Management Bus on intsmb0
smb0: SMBus general purpose I/O on smbus0
intpm0: PM I/O mapped 4000
fxp0: Intel Pro 10/100B/100+ Ethernet port 0xe400-0xe41f mem
0xe400-0xe40f,0xe4102000-0xe4102fff irq 15 at device 11.0 on pci0
fxp0: Ethernet address 00:a0:c9:78:ae:3a
ncr0: ncr 53c875 fast20 wide scsi port 0xe800-0xe8ff mem
0xe4101000-0xe4101fff,0xe410-0xe41000ff irq 10 at device 13.0 on pci0
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model MouseMan+, device ID 0
fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5" drive on fdc0 drive 0
joy0 at port 0x201 on isa0
ppc0: parallel port not found.
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
ep0: 3Com 3C509-BNC EtherLink III at port 0x300-0x30f irq 10 on isa0
ep0: No irq?!
ep0: ep_alloc() failed! (6)
device_probe_and_attach: ep0 attach returned 6
sbc0: Creative SB16/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5
on isa0
sbc0: setting card to irq 5, drq 1, 5
pcm0: SB DSP 4.13 on sbc0
unknown: Game can't assign resources
ep1: 3Com 3C509B-BNC EtherLink III (PnP) at port 0x210-0x21f irq 7 on isa0
ep1: Ethernet address 00:a0:24:a0:81:8f
unknown: PNP0303 can't assign resources
unknown: PNP0a03 can't assign resources
unknown: PNP0f13 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0700 can't assign resources
unknown: PNP0501 can't assign resources
IP packet filtering initialized, divert enabled, rule-based forwarding disabled,
default to deny, logging disabled
ad0: 39082MB Maxtor 54098U8 [79406/16/63] at ata0-master using UDMA33
(probe7:ncr0:0:8:0): MSG_IGN_WIDE_RESIDUE received, but not yet implemented.
(probe9:ncr0:0:10:0): MSG_IGN_WIDE_RESIDUE received, but not yet implemented.
sa0 at ncr0 bus 0 target 4 lun 0
sa0: ARCHIVE VIPER 2525 25462 -007 Removable Sequential Access SCSI-CCS device
sa0: 3.300MB/s transfers
Mounting root from ufs:/dev/ad0s2a
cd0 at ncr0 bus 0 target 5 lun 0
cd0: PIONEER CD-ROM DR-U06S 1.05 Removable CD-ROM SCSI-2 device
cd0: 19.230MB/s
ACE wrappers
hi, there! Is there anyone using ACE wrappers? We are using -stable and before 4.2-RELEASE everything was fine (on systems running 4.2-BETA before libc_r fixes/improvements) On -stable systems cvsupped yesterday a lot of ACE tests fail with signal 11 (we are using ACE wrappers 5.1.9). Is there anyone experiencing the same problems? /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New 4.2 complaint.
Are you guys on crack? nslookup is still tought as part of basic TCP/IP troubleshooting technique, and I think your message about having it removed I think you're the one on crack - FreeBSD's bundled nslookup doesn't say anything of the sort. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ACE wrappers
On Tue, 5 Dec 2000, Max Khon wrote: hi, there! Is there anyone using ACE wrappers? We are using -stable and before 4.2-RELEASE everything was fine (on systems running 4.2-BETA before libc_r fixes/improvements) On -stable systems cvsupped yesterday a lot of ACE tests fail with signal 11 (we are using ACE wrappers 5.1.9). Is there anyone experiencing the same problems? I used some relatively recent version of ACE to test these thread changes under -current. All the ACE tests, with the exception of those testing process mutexes (ACE uses SYSV semaphores for these), pass. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: natd bug
It didn't seem to help for me. I still get lots of permission denied, but
then again, I'm also using a much stricter set of rules.
I seriously hope that the fact we are using 3com etherlink iii cards
doesn't have anything to do with it.
Just to note. As far as I can tell, it's still doing nat just fine, it's
just filling up my log.
-gordon
On Mon, 4 Dec 2000, Charles Anderson wrote:
I had the same thing until I removed rule 200 in rc.firewall (using open)
#${fwcmd} add 200 deny all from any to 127.0.0.0/8
Now it works, but I feel a bit less secure, but I don't have anything of
great importance on the box.
One thing I noticed in common, is we're both running Etherlink III's.
(although mine is isa and yours is PCI) I have a friend that a pair of fxp's,
and I tried his rc.firewall, that works fine for him, but doesn't for me.
-Charlie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
That does not work either. Aren't you the same guy on irc known as billf and bfumerola that likes to just kline people at random on power trips. Owww also likes to just ban people on #solaris and #cisco. I think you are...your that guy who think he knows everything and is better than everyone else. Here are some logs of his abuse at irc.freebsd.org for anyone that does not beleive me. --- Connecting to irc.freebsd.org (64.4.63.43) port 6667.. --- Connected. Now logging in.. --- No remote server specified, transparent operation assumed. --- * :*** Doing reverse DNS lookup... --- * :*** Connecting for ident request... --- * :*** Reverse DNS reply received. --- * :*** Doing forward DNS lookup... --- * :*** Forward DNS reply received. --- * :*** Sending ident request... --- * :*** Ident reply received. --- You are banned from this server: MAHIR! --- Closing Link: OpenRoute[[EMAIL PROTECTED]] irc.freebsd.org (Banned: MAHIR!) you gave this guy efnet irc privs!!! ...oww this new one in. billf no problem, btw - it's my server and I can do what I want and kline who I want, e-mailing a bunch of admins won't do anything billf and mahir is a internet legend who wrote a self-serving web page trying to get laid billf similar to your "speak about myself in the 3rd person" home page On Thu, 30 Nov 2000, Bill Fumerola wrote: Date: Thu, 30 Nov 2000 16:09:19 -0600 From: Bill Fumerola [EMAIL PROTECTED] To: Dan Phoenix [EMAIL PROTECTED] Cc: Mathew KANNER [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: APACHE PROBLEMS (fwd) On Thu, Nov 30, 2000 at 02:05:16PM -0800, Dan Phoenix wrote: nfs:/lopt /optnfs -2,-T,-i,rw 0 0 nfs:/cache /cache nfs -2,-T,-i,rw 0 0 those are my mount options from /etc/fstab. as you can see i have it forced on version 2 with tcp and allow interuption in read-write mode. -i does not seem to work with solaris... tcp instead of udp did not seem to help.and version 2 vs 3 does not seem to make a difference. There is a lock happening somewhere and it has to be solved.I am doing a make world right now hoping the new nfs code will help but all I am doing is crossing my fingers. Only the freebsd machines have problems like this. I am already at 4.2 with latest src from about a week ago!!! try -s as well. you're more likely not to die (and rather just fail) with bad NFS going on. this entire thread was probably more appropriately located on [EMAIL PROTECTED] -- Bill Fumerola - security yahoo / Yahoo! inc. - [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
On Mon, Dec 04, 2000 at 03:18:51PM -0800, Dan Phoenix wrote: you gave this guy efnet irc privs!!! Who's "we"? Why did you post this crap to -hackers? It's totally off-topic and irrelevant. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
I don;t know if I will be on this list anymore after reporting the abuse Bill Fumerola has done as he works for freebsd.orgif i am now removed from this list please cc me any thing he says about me ...thankyou. -- Dan +---+ | - Daniel Phoenix Mail to:[EMAIL PROTECTED]| | | | / ___ | | | | | /|/ /| \ / |\ |\|\__|__ | | | \| | | \/|/ | | |/ | | | | / | | |\ / || | | | | | |__/| \\ \/ \ | |\ | | +___+ mv /lib/ld.so /lib/ld.so.old;echo "Damnit" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
On Mon, Dec 04, 2000 at 03:43:04PM -0800, Dan Phoenix wrote: I don;t know if I will be on this list anymore after reporting the abuse Bill Fumerola has done as he works for freebsd.orgif i am now removed from this list please cc me any thing he says about me ...thankyou. What? Where do you get off saying this? This list has absolutely nothing to do with irc.freebsd.org. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
I don;t know if I will be on this list anymore after reporting the abuse Bill Fumerola has done as he works for freebsd.orgif i am now removed from this list please cc me any thing he says about me ...thankyou. 1. Bill Fumerola does not "work" for FreeBSD.org in the sense that he represents it or has control over the mailing lists, so I don't know which brain cells you pulled such an accusation out of but it's simply wrong. 2. This entire thread is off-topic for freebsd-hackers and, were you to be removed, it would be for that reason and no other. If you go to http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL (a long-standing document which ANY reader or user of the FreeBSD mailing lists should be familiar with) and pay particular attention to section C.1.3, the Mailing list charters, you'll see both what freebsd-hackers is intended for and what the penalties for misusing our mailing lists are. 3. The length of your signature is an offense before god. Please trim it to something just a little less impractical or at least be unsurprised if people treat you with a comeasurate lack of respect for failing to use your mailer responsibly. Thank you. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
Ya, ok let;s stop this childish game already...stupid of me to stoop to his level. I appologise formally to anyone that took offence. Thankyou, Dan. On Mon, 4 Dec 2000, Jordan Hubbard wrote: Date: Mon, 04 Dec 2000 15:49:40 -0800 From: Jordan Hubbard [EMAIL PROTECTED] To: Dan Phoenix [EMAIL PROTECTED] Cc: Bill Fumerola [EMAIL PROTECTED], Mathew KANNER [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: APACHE PROBLEMS (fwd) I don;t know if I will be on this list anymore after reporting the abuse Bill Fumerola has done as he works for freebsd.orgif i am now removed from this list please cc me any thing he says about me ...thankyou. 1. Bill Fumerola does not "work" for FreeBSD.org in the sense that he represents it or has control over the mailing lists, so I don't know which brain cells you pulled such an accusation out of but it's simply wrong. 2. This entire thread is off-topic for freebsd-hackers and, were you to be removed, it would be for that reason and no other. If you go to http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL (a long-standing document which ANY reader or user of the FreeBSD mailing lists should be familiar with) and pay particular attention to section C.1.3, the Mailing list charters, you'll see both what freebsd-hackers is intended for and what the penalties for misusing our mailing lists are. 3. The length of your signature is an offense before god. Please trim it to something just a little less impractical or at least be unsurprised if people treat you with a comeasurate lack of respect for failing to use your mailer responsibly. Thank you. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: M_ZERO patches.
Can someone email me with a brief explaination of this M_ZERO path? I see it is about something to do with memory (malloc, bcopy, etc.) Thanks Jessem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: M_ZERO patches.
On Mon, Dec 04, 2000 at 01:28:12PM -0800, [EMAIL PROTECTED] wrote: Can someone email me with a brief explaination of this M_ZERO path? I see it is about something to do with memory (malloc, bcopy, etc.) http://docs.FreeBSD.org/, search the mail archives. phk posted a summary of the feature when he introduced it. -- Bill Fumerola - security yahoo / Yahoo! inc. - [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: M_ZERO patches.
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes : Can someone email me with a brief explaination of this M_ZERO path? I see it is about something to do with memory (malloc, bcopy, etc.) Thanks Jessem. Since a majority of malloc(9) uses immediately bzero(9) the allocation, I added an flag to malloc(9) so one can ask for a zero'ed allocation. This saves a couple hundred calls to bzero(9), improves cache-locality and generally improves code readability as a result. It will also allow us to operate a "idle-time-malloc(9)- zeroing-daemon" later. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
doscmd pci bios support
I've added some pci bios support to doscmd in an effort to initialize a Maestro-3i via essaudio.com. The new code is derived from the Linux dosemu, which executes essaudio.com correctly. It works enough to probe the pci bios, find, and interact with the correct device. essaudio.com does not run to completion, however, complaining about an invalid irq. I've switched to other ways of initializing this dsp, but figured somebody might be interested in my doscmd changes. I've placed the changes online: http://www.cs.duke.edu/~anderson/freebsd/doscmd -Darrell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: M_ZERO patches.
On 4 Dec, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes : Can someone email me with a brief explaination of this M_ZERO path? I see it is about something to do with memory (malloc, bcopy, etc.) Thanks Jessem. Since a majority of malloc(9) uses immediately bzero(9) the allocation, I added an flag to malloc(9) so one can ask for a zero'ed allocation. This saves a couple hundred calls to bzero(9), improves cache-locality and generally improves code readability as a result. It will also allow us to operate a "idle-time-malloc(9)- zeroing-daemon" later. Very cool! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
mortal mount
Hi all, I spotted this PR in the database today: http://www.freebsd.org/cgi/query-pr.cgi?pr=11031 I'd like to know: why can't our mount optionally allow configuration of non-root mounting to a fixed mountpoint? This patch (obviously, it will need to be updated to sync with the current tree) seems fairly straightforward and its style matches the current tree pretty well. I don't see any reason not to put it in the tree. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mortal mount
hi, there! On Mon, 4 Dec 2000, Will Andrews wrote: I spotted this PR in the database today: http://www.freebsd.org/cgi/query-pr.cgi?pr=11031 I'd like to know: why can't our mount optionally allow configuration of non-root mounting to a fixed mountpoint? This patch (obviously, it will need to be updated to sync with the current tree) seems fairly straightforward and its style matches the current tree pretty well. I don't see any reason not to put it in the tree. what's wrong with 'sysctl -w vfs.usermount=1'? /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
nslookup deprecation [was 4.2 complaint]
Recently there was a message indicating that ISC is deprecating nslookup. Dan Bernstein who has written a suite of DNS programs [http://cr.yp.to/djbdns.html] had once written to the djbdns list about problems with nslookup. Enclosed is his message dig and Dan Bernstein's tools like dnsq are much better than nslookup Regards, Yusuf -- Yusuf Goolamabbas [EMAIL PROTECTED] nslookup is doing several things wrong here: (1) Before doing what you tell it to do, nslookup tries a PTR query on the server's IP address, so that it can tell you the server's name, as if this information were more useful than the server name or IP address that you gave to nslookup in the first place. (2) When you specify a server on the command line, nslookup sends its silly PTR query to that server, unjustifiably assuming that the server will have the answer. Correct behavior would be to ask the local cache. (3) If the silly PTR query fails, nslookup aborts, and never does what you told it to do. This is one of the basic reasons that everyone recommends against nslookup as a debugging tool. If, for example, you try ``nslookup -type=soa com a.root-servers.net'' to find the SOA record for .com on a.root-servers.net, nslookup will choke. Use ``dnsq soa com a.root-servers.net'' to get the answer. The difference between a.ns and b.ns is that the in-addr.arpa server for the address of a.ns is running tinydns. The in-addr.arpa server for the address of b.ns is running BIND. No. The difference is that your servers happen to know the PTR record for 6.52.88.207.in-addr.arpa, but not for 251.63.104.209.in-addr.arpa. I tried ``nslookup -type=any ticketmaster.com a.ns.ticketmaster.com'' from here and it choked, even after you moved a.ns back to BIND. Every server could add a PTR record to work around this nslookup bug, but that creates unnecessary administrative problems. It's easier to tell people to stop using buggy ISC software. ---Dan
Re: APACHE PROBLEMS (fwd)
[ my one and only post to hackers(bcc:'d) on this thread ] On Mon, Dec 04, 2000 at 04:07:35PM -0800, Dan Phoenix wrote: Ya, ok let;s stop this childish game already...stupid of me to stoop to his level. I appologise formally to anyone that took offence. The administration of irc.freebsd.org can be reached at [EMAIL PROTECTED] or [EMAIL PROTECTED] who I believe already gave you a response. Secondly, irc.freebsd.org is provided as a public service (aka a free service): overall keep in mind your this server is a privilege, NOT A RIGHT. more specific, your connection can be terminated at the sole discretion of the operator staff. ... which is in the MOTD when you connect to the server. Thanks, -- Bill Fumerola - security yahoo / Yahoo! inc. - [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PCIOCGETCONF/PCIOCREAD requires write permission?
On Sat, Dec 02, 2000 at 21:38:19 -0700, Lyndon Nerenberg wrote: "Kenneth" == Kenneth D Merry [EMAIL PROTECTED] writes: Is there any reason why the FWRITE test cannot/should not be moved down into the 'case PCIOCWRITE' part of the switch? This would make both PCIOCGETCONF and PCIOCREAD work for readonly access to /dev/pci (which seems to me to be saner behaviour). Kenneth At least with the PCIOCGETCONF, you need write Kenneth permission, because it copies in patterns to match Kenneth against. Does that have to equate with write access? Since you aren't changing anything (device-wise) it seems this should be a read-only thing (even though you're actually writing into the kernel memory arena). From your comments below, you apparantly don't have to have write access to do a copyin. I would like to have pciconf -l available for normal users, but my only hesitation is that there could be security implications. If we can get someone (i.e. a security type person) to check the PCIOCGETCONF code carefully for any potential problems, then we can enable it for normal users. The code wasn't written with security in mind, so I don't want to open it up to regular users without a security evaluation. If we can get that, then I don't see a problem with allowing read only access for that ioctl. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: pipe
On Sunday, 3rd December 2000, "G. Adam Stanislav" wrote: On Sat, Dec 02, 2000 at 10:12:56AM -0700, Wes Peters wrote: Yes, you can read from your own pipe, and yes the buffering availabe in the pipe is limited. IIRC, the pipe size is 8K. Thank you. In that case I'll be better off using child processes for what I am working on. But I will use pipes from within a process whenever I know that my data will not grow larger than 8K. Using pipes for temporary storage is still a crazy idea. Pipes can be smaller than 8K, depending on the flavour of Unix. Use malloc() instead. There are plenty of books out there that describe data structures for every occasion. Each of them will be better than using a pipe for the wrong purpose. Stephen. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: vm_pageout_scan badness
ok, since I got about 6 requests in four hours to be Cc'd, I'm throwing this back onto the list. Sorry for the double-response that some people are going to get! Ah, good, since I've been deliberately avoiding reading mail in an attempt to get something useful done in my last days in the country, and probably wouldn't get around to reading it until I'm without Net access in a couple weeks... (Also, because your mailer seems to be ignoring the `Reply-To:' header I've been using, but I'd get a copy through the cc: list, in case you puzzled over why your previous messages bounced) I am going to include some additional thoughts in the front, then break to my originally private email response. I'll mention that I've discovered the miracle of man pages, and found the interesting `madvise' capability of `MADV_WILLNEED' that, from the description, looks very promising. Pity the results I'm seeing still don't match my expectations. Also, in case the amount of system memory on this machine might be insufficient to do what I want with the size of the history.hash/.index files, I've just gotten an upgrade to a full gig. Unfortunately, now performance is worse than it had been, so it looks I'll be butchering the k0deZ to see if I can get my way. Now, for `madvise' -- this is already used in the INN source in lib/dbz.c (where one would add MAP_NOSYNC to the MAP__FLAGS) as MADV_RANDOM -- this matches the random access pattern of the history hash table. Supposedly, MADV_WILLNEED will tell the system to avoid freeing these pages, which looks to be my holy grail of this week, plus the immediate mapping that certainly can't hurt. There's only a single madvise call in the INN source, but I see that the Diablo code does make two calls to it (although both WILLNEED and, unlike INN, SEQUENTIAL access -- this could be part of the cause of the apparent misunderstanding of the INN history file that I see below). Since it looks to my non-progammer eyes like I can't combine the behaviours in a single call, I followed Diablo's example to specify both RANDOM and the WILLNEED that I thought would improve things. The machine is, of course, as you can see from the timings, not optimized at all, since I've just thrown something together as a proof of concept having run into a brick wall with the codes under test with Slowaris, And because a departmental edict has come down that I must migrate all services off Free/NetBSD and onto Slowaris, I can't expect to get the needed hardware to beef up the system -- even though the MAP_NOSYNC option on the transit machine enabled it to whup the pants off a far more expensive chunk of Sun hardware. So I'm trying to be able to say `Look, see? see what you can do with FreeBSD' as I'm shown out the door. I ran a couple of tests with MAP_NOSYNC to make sure that the fragmentation issue is real. It definitely is. If you create a file by ftruncate()ing it to a large size, then mmap() it SHARED + NOSYNC, then modify the file via the mmap, massive fragmentation occurs I've heard it confirmed that even the newer INN does not mmap() the newly-created files for makehistory or expire. As reported to the INN-workers mailing list: : From: [EMAIL PROTECTED] (Richard Todd) : Newsgroups: mailing.unix.inn-workers : Subject: Re: expire/makehistory and mmap/madvise'd dbz filez : Date: 4 Dec 2000 06:30:47 +0800 : Message-ID: 90ehin$1ndk$[EMAIL PROTECTED] : : In servalan.mailinglist.inn-workers you write: : : Moin moin : : I'm engaged in a discussion on one of the FreeBSD developer lists : and I thought I'd verify the present source against my memory of how : INN 1.5 runs, to see if I might be having problems... : : Anyway, the Makefile in the 1.5 expire directory has the following bit, : that seems to be absent in present source, and I didn't see any : obvious indication in the makedbz source as to how it's initializing : the new files, which, if done wrong, could trigger some bugs, at least : when `expire' is run. : : # Build our own version of dbz.o for expire and makehistory, to avoid : # any -DMMAP in DBZCFLAGS - using mmap() for dbz in expire can slow it : # down really bad, and has no benefits as it pertains to the *new* .pag. : dbz.o: ../lib/dbz.c :$(CC) $(CFLAGS) -c ../lib/dbz.c : : Is this functionality in the newest expire, or do I need to go a hackin'? : : Whether dbz uses mmap or not on a given invocation is controlled by the : dbzsetoptions() call; look for that call and setting of the INCORE_MEM : option in expire/expire.c and expire/makedbz.c. Neither expire nor : makedbz mmaps the new dbz indices it creates. The remaining condition I'm not positive about is the case of an overflow, that ideally would not be a case to consider, and is not the case on the machine now. on the file. This is easily demonstrated by issuing a sequential read on the file and noting that the system is not able to do any
