Re: mremap help ? or no support for FreeBSD ? so do what ?
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000512 21:54] wrote: > I know that this was discussed in the past but I can't find out what to > do ? > > In Linux if I have to resize a mmap 'ed object I can just use mremap > but in FreeBSD if, I want to resize it what do I do ? > > I have tried writing past where I know the end is and it kinda works ? > but why ? > > Is their a better solution besides just writing to the file and then > calling msync ? > > Is their new plans to make a mremap call for FreeBSD 4.x ? no. > > Or am I just sh%t out of luck ? Possibly, but if you describe what you are trying to accomplish there may be some advice available. Your misuse of msync makes me think that a rethinking of what you are trying to accomplish may be a good idea. Please explain what makes you need mremap which is not portable to any version of unix. I'm assuming you want your app to work on Solaris and other commercial systems. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD Port: xosview-1.7.3
On Thu, May 11, 2000 at 10:52:04PM -0700, Doug Barton wrote: > Arun Sharma wrote: > > See the patches I mailed to freebsd-hackers late last year. You need to > > patch both the kernel and the userland. I'm a little disappointed at > > the lack of response. I just assumed that no one is interested - but > > the question keeps coming up on the lists. > > You'd get better results if you put it all together in a PR. > I just submitted a PR. Talking about PRs, I see more than 1000 open PRs on the kernel alone: http://www.FreeBSD.org/cgi/query-pr-summary.cgi?category=kern&severity=&priority=&class=&state=open&sort=none&text=&responsible=&multitext=&originator= This includes a request for change regarding dynamic sysctls I submitted back in Feb. I understand that FreeBSD is an entirely voluntary project, So people can't be blamed for having so many open PRs. But common sense tells me that this is not good. I'll shut up now. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Funny Network Transit Delays
> the other end is set to full. I wouldn't trust any "Auto" settings until > it can be assured that it doesn't hurt. Agreed -- from experience with a couple of HP Procurve 2424M switches and various 100Mb cards, the "Auto" setting is less than reliable... My Netgear FA310TX(?) and Intel EtherExpress 100B cards all get detected correctly, but most of the other ones can be a little flaky with auto-detect... If you can't control the switch settings (most unmanaged switches), you'll have to play with the ifconfig flags to get the net card and the switch to agree on what protocol they're using. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kernel panics at boot, how to specify dump device?
This is an easy problem to solve. Drop into ddb, and do a "show disk/device", e.g.: ddb> show disk/ad0s1b dev_t = 0xf000b444 This will return to you the dev_t for it. Take this value, and call setdumpdev(dev_t value): ddb> call setdumpdev(0xf000b444) The setdumpdev() call should return 0 for success. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Funny Network Transit Delays
Are you sure the duplex settings are correct on all nics? If they are on coax or a hub, it should be set to half duplex. If you are connected to a switch or a crossover cable, you may use full duplex on the nic only if the other end is set to full. I wouldn't trust any "Auto" settings until it can be assured that it doesn't hurt. On Fri, 12 May 2000, Yann Ramin wrote: >-BEGIN PGP SIGNED MESSAGE- > >Hi there. I have an interesting problem (figured it out myself) but I'm >wondering why it is occuring. > >I have a setup with Two FreeBSD machines (3.2 and 4.0 RELEASE), a Windows >machine, and a NetBSD machine. The NetBSD machine has three 3Com 3C509/B NICs >(ISA) and acts as a router to three subnets, one per machine. When I FTP >something from the 4.0 to the 3.2 box, performance sucks. And not that the >NetBSD machine is too slow, it seems neither the 4.0 or 3.2 is using the >network like it should. Looking at the hub, I'm getting a pattern like this: > >Activity(3 secs) -- Pause (4 secs) -- Activity (2 secs) -- Pause (1 sec) -- >Activity (7 secs) -- Pause (7 secs) > >and on for a total throughput of 80KB/s. The same occurs from Windows to the >4.0 box with Samba. I tried installing FreeBSD on the router, with no luck. >The only solution I could come up with was to: > >sysctl -w net.inet.tcp.sendspace=2900 >sysctl -w net.inet.tcp.recvspace=2900 > >This brings performance up to about 400KB/s, which is "ok" because of the extra >latency of the router. I have another similar situation with two 4.0 boxes and >iMacs running on two Cisco Catalyst 2924XL switches. If I use a plain >vanilla 10Base hub I get a cool 620KB/s. Does anyone have any idea what is >causing this? > >Yann > >-- > > >Yann Ramin [EMAIL PROTECTED] >Atrus Trivalie Productions www.atrustrivalie.eu.org > irm.it.montereyhigh.com >Monterey High IT www.montereyhigh.com >ICQ46805627 >AIModdatrus >Marina, CA > >"All cats die. Socrates is dead. Therefore Socrates is a cat." > - The Logician > > # fortune >"To be responsive at this time, though I will simply say, and therefore >this is a repeat of what I said previously, that which I am unable to >offer in response is based on information available to make no such >statement." > > > >-BEGIN PGP SIGNATURE- >Version: PGPfreeware 5.0i for non-commercial use >MessageID: FUGyzVH4vQLKyp0A67Qx1eOXvDr2V38A > >iQA/AwUBORzT6jEK6loGD1TnEQK9/QCg5+2Jaxj+BzYd0JkHCPoYMRgLsVoAnjp3 >8t3n4rO9Oyr+R086nXwG5Asb >=/RT8 >-END PGP SIGNATURE- > > >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
mremap help ? or no support for FreeBSD ? so do what ?
I know that this was discussed in the past but I can't find out what to do ? In Linux if I have to resize a mmap 'ed object I can just use mremap but in FreeBSD if, I want to resize it what do I do ? I have tried writing past where I know the end is and it kinda works ? but why ? Is their a better solution besides just writing to the file and then calling msync ? Is their new plans to make a mremap call for FreeBSD 4.x ? Or am I just sh%t out of luck ? thank you in advance nathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Funny Network Transit Delays
-BEGIN PGP SIGNED MESSAGE- Hi there. I have an interesting problem (figured it out myself) but I'm wondering why it is occuring. I have a setup with Two FreeBSD machines (3.2 and 4.0 RELEASE), a Windows machine, and a NetBSD machine. The NetBSD machine has three 3Com 3C509/B NICs (ISA) and acts as a router to three subnets, one per machine. When I FTP something from the 4.0 to the 3.2 box, performance sucks. And not that the NetBSD machine is too slow, it seems neither the 4.0 or 3.2 is using the network like it should. Looking at the hub, I'm getting a pattern like this: Activity(3 secs) -- Pause (4 secs) -- Activity (2 secs) -- Pause (1 sec) -- Activity (7 secs) -- Pause (7 secs) and on for a total throughput of 80KB/s. The same occurs from Windows to the 4.0 box with Samba. I tried installing FreeBSD on the router, with no luck. The only solution I could come up with was to: sysctl -w net.inet.tcp.sendspace=2900 sysctl -w net.inet.tcp.recvspace=2900 This brings performance up to about 400KB/s, which is "ok" because of the extra latency of the router. I have another similar situation with two 4.0 boxes and iMacs running on two Cisco Catalyst 2924XL switches. If I use a plain vanilla 10Base hub I get a cool 620KB/s. Does anyone have any idea what is causing this? Yann -- Yann Ramin [EMAIL PROTECTED] Atrus Trivalie Productions www.atrustrivalie.eu.org irm.it.montereyhigh.com Monterey High ITwww.montereyhigh.com ICQ 46805627 AIM oddatrus Marina, CA "All cats die. Socrates is dead. Therefore Socrates is a cat." - The Logician # fortune "To be responsive at this time, though I will simply say, and therefore this is a repeat of what I said previously, that which I am unable to offer in response is based on information available to make no such statement." -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use MessageID: FUGyzVH4vQLKyp0A67Qx1eOXvDr2V38A iQA/AwUBORzT6jEK6loGD1TnEQK9/QCg5+2Jaxj+BzYd0JkHCPoYMRgLsVoAnjp3 8t3n4rO9Oyr+R086nXwG5Asb =/RT8 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why this works?
This is a silly question, but, Is there anyway to do read/write on the same file without the kernel lock? Thanks! On Fri, 12 May 2000, Alfred Perlstein wrote: > * Sergey Babkin <[EMAIL PROTECTED]> [000512 15:23] wrote: > > Alfred Perlstein wrote: > > > > > > * Ville-Pertti Keinonen <[EMAIL PROTECTED]> [000511 22:49] wrote: > > > > > > > > [EMAIL PROTECTED] (FengYue) writes: > > > > > > > > > loop. Now, the third program reads 4K of data from /tmp/pagetest > > > > > and exit if the 4K data does not contain all 'A's nor 'Z's. 3 programs > > > > > run concurrently on the same machine (3.4). No lock in the code whatsoever, > > > > > > > > Not quite. If FreeBSD didn't perform locking, operations affecting > > > > single filesystem blocks would probably be atomic (as long as the > > > > userland buffer is in memory). > > > > > > > > However, FreeBSD does perform locking in read(2) and write(2) for > > > > local files, so your third program should never fail and exit. > > > > > > > > Note that the system call interface does not guarantee reads or writes > > > > to be atomic, this just happens to be how it is implemented at the > > > > moment. > > > > > > Afaik several Unix standards mandate this behavior, Linux doesn't > > > follow this standard though. > > > > Sounds like one more of these subtle weirdnesses in Linux that > > annoy me so much :-( > > This weirdness is intentional, it's a shortcut for speed taken at > the expense of real unix compatibility. > > > Solaris seems to be another example a system with not quite atomic > > writes. The writes themselves seem to be atomic but in append mode the > > positioning at the end of file is not atomic with writes. So when > > appending to a log file from multiple sources the messages tend to > > overlap (be written at the same position). > > That's why I use FreeBSD, it works. :) > > -- > -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] > "I have the heart of a child; I keep it in a jar on my desk." > > > 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
Strange behaviour of mtree(8)?
[posted to -questions several days ago, but still no response] It always seems to me that `mtree -c | mtree` should output nothing (because it compares current directory with itself). But recently I noticed very strange thing: andrew@sign> ls -la total 4 drwxr-xr-x 2 andrew wheel 512 4 May 19:48 . drwxr-xr-x 46 andrew wheel 2560 4 May 19:47 .. lrwxr-xr-x 1 andrew wheel 1 4 May 19:47 a -> . lrwxr-xr-x 1 andrew wheel 1 4 May 19:48 b -> . andrew@sign> mtree -c | mtree extra: b missing: ./a/b andrew@sign> mtree -c | mtree -U extra: b missing: ./a/b (directory not created: File exists) In another similar sitation: andrew@sign> ls -lR total 2 drwxr-xr-x 2 andrew wheel 512 4 May 20:02 1 drwxr-xr-x 2 andrew wheel 512 4 May 20:03 2 ./1: total 0 lrwxr-xr-x 1 andrew wheel 1 4 May 20:02 a -> . lrwxr-xr-x 1 andrew wheel 1 4 May 20:02 b -> . ./2: total 0 lrwxr-xr-x 1 andrew wheel 1 4 May 20:03 a -> . lrwxr-xr-x 1 andrew wheel 1 4 May 20:03 b -> . andrew@sign> mtree -c | mtree extra: 1/b extra: 2 missing: ./1/a/b missing: ./1/a/2 missing: ./1/a/2/a missing: ./1/a/2/a/b andrew@sign> mtree -c | mtree -U extra: 1/b extra: 2 missing: ./1/a/b (directory not created: File exists) missing: ./1/a/2 (created) missing: ./1/a/2/a (created) missing: ./1/a/2/a/b (created) andrew@sign> Guys! What happens? I'll greatly appreciate any input from you! -- Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why this works?
* Sergey Babkin <[EMAIL PROTECTED]> [000512 15:23] wrote: > Alfred Perlstein wrote: > > > > * Ville-Pertti Keinonen <[EMAIL PROTECTED]> [000511 22:49] wrote: > > > > > > [EMAIL PROTECTED] (FengYue) writes: > > > > > > > loop. Now, the third program reads 4K of data from /tmp/pagetest > > > > and exit if the 4K data does not contain all 'A's nor 'Z's. 3 programs > > > > run concurrently on the same machine (3.4). No lock in the code whatsoever, > > > > > > Not quite. If FreeBSD didn't perform locking, operations affecting > > > single filesystem blocks would probably be atomic (as long as the > > > userland buffer is in memory). > > > > > > However, FreeBSD does perform locking in read(2) and write(2) for > > > local files, so your third program should never fail and exit. > > > > > > Note that the system call interface does not guarantee reads or writes > > > to be atomic, this just happens to be how it is implemented at the > > > moment. > > > > Afaik several Unix standards mandate this behavior, Linux doesn't > > follow this standard though. > > Sounds like one more of these subtle weirdnesses in Linux that > annoy me so much :-( This weirdness is intentional, it's a shortcut for speed taken at the expense of real unix compatibility. > Solaris seems to be another example a system with not quite atomic > writes. The writes themselves seem to be atomic but in append mode the > positioning at the end of file is not atomic with writes. So when > appending to a log file from multiple sources the messages tend to > overlap (be written at the same position). That's why I use FreeBSD, it works. :) -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BROKEN_KEYBOARD_RESET
In message <[EMAIL PROTECTED]> Kazutaka YOKOTA writes: : >Speaking of AT keyboard controllers, does anybody know if the new : >legacy free PCs have this port available for compatibility reasons? : : I guess it depends on the level of compatiblity the BIOS offers I'm not sure how the BIOS would impact this. The reset is done by wrinting stuff to the keyboard controller port. I'm curious if there's A-20 compat as well as reset, but no actual keyboard controller. Or if it is completely gone. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why this works?
Alfred Perlstein wrote: > > * Ville-Pertti Keinonen <[EMAIL PROTECTED]> [000511 22:49] wrote: > > > > [EMAIL PROTECTED] (FengYue) writes: > > > > > loop. Now, the third program reads 4K of data from /tmp/pagetest > > > and exit if the 4K data does not contain all 'A's nor 'Z's. 3 programs > > > run concurrently on the same machine (3.4). No lock in the code whatsoever, > > > > Not quite. If FreeBSD didn't perform locking, operations affecting > > single filesystem blocks would probably be atomic (as long as the > > userland buffer is in memory). > > > > However, FreeBSD does perform locking in read(2) and write(2) for > > local files, so your third program should never fail and exit. > > > > Note that the system call interface does not guarantee reads or writes > > to be atomic, this just happens to be how it is implemented at the > > moment. > > Afaik several Unix standards mandate this behavior, Linux doesn't > follow this standard though. Sounds like one more of these subtle weirdnesses in Linux that annoy me so much :-( Solaris seems to be another example a system with not quite atomic writes. The writes themselves seem to be atomic but in append mode the positioning at the end of file is not atomic with writes. So when appending to a log file from multiple sources the messages tend to overlap (be written at the same position). -SB To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BROKEN_KEYBOARD_RESET
>In message <[EMAIL PROTECTED]> >"Chris D. Faulhaber" writes: >: Since this has been brought up, any reason that BROKEN_KEYBOARD_RESET is >: not a recognized option (see kern/12927)? > >Likely fell through the cracks when Eivind made everything an option. >If it didn't, then someone likely broke it later on. vm_machdep.c >should include opt_.h for this, but doesn't. > >Speaking of AT keyboard controllers, does anybody know if the new >legacy free PCs have this port available for compatibility reasons? I guess it depends on the level of compatiblity the BIOS offers Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
make question
I am having difficulties to implement the following rule in BSD make: to produce file foobar.o, then start from foobar.adb if it exists, foobar.ads otherwise. I want this to be compatible with both BSD and GNU make. I tried: .SUFFIXES: .adb .ads .lo .adb.lo: .ads.lo: but make prefers the .ads.lo rule instead of the .adb.lo, despites the order in the .SUFFIXES. Using "make -d s" to trace dependencies and rules, I get: SuffFindDeps (broca-exceptions.lo) trying broca-exceptions.S...not there trying broca-exceptions.adb...got it using existing source broca-exceptions.ads applying .ads -> .lo to "broca-exceptions.lo" broca-exceptions.adb has been found and should have been used, but this "using existing source" message (coming after!) bugs me. The wrong rule is then being selected. Any hint of where it can come from? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
mailing list?
How can I begin getting mailings from this list? Regards, Daniel Killingsworth, MCP IS Desktop Support Specialist SCA Hygiene Products 610-499-3406 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rexec as root
In message <[EMAIL PROTECTED]> Nick Sayer writes: : Warner Losh wrote: : : > [...] In the absense of this : > test, machines in a yp netowrk would be extremely vulnerable to root : > uid penetration when an intruder can hack the yp database, or spoof : > replies. : : Ok. How about adding an rexecd command line flag to disable : that test (with suitable warnings in the man page)? I'd be all for a "make this insanely insecure protocol even more insecure because security doesn't matter to my setup" flag. So long as it isn't default :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rexec as root
Warner Losh wrote: > [...] In the absense of this > test, machines in a yp netowrk would be extremely vulnerable to root > uid penetration when an intruder can hack the yp database, or spoof > replies. Ok. How about adding an rexecd command line flag to disable that test (with suitable warnings in the man page)? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BROKEN_KEYBOARD_RESET
In message <[EMAIL PROTECTED]> "Chris D. Faulhaber" writes: : Since this has been brought up, any reason that BROKEN_KEYBOARD_RESET is : not a recognized option (see kern/12927)? Likely fell through the cracks when Eivind made everything an option. If it didn't, then someone likely broke it later on. vm_machdep.c should include opt_.h for this, but doesn't. Speaking of AT keyboard controllers, does anybody know if the new legacy free PCs have this port available for compatibility reasons? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
In message <[EMAIL PROTECTED]> "Aleksandr A.Babaylov" writes: : > This is one reason I have TMPDIR set to "." when I'm running as me. : ...and lose a lot of files to delete... My sources are cvs controlled, and a cvs update -n tells me what to delete when gcc doesn't do it for me. And when I'm not running -pipe :-). : I propose create (or use old) subdirectory in /tmp on startup : and use this subdirectory for set TMPDIR : See PR bin/18275 I'll have to take a look a tthis, but my plate is very full these days. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rexec as root
In message <[EMAIL PROTECTED]> Nick Sayer writes: : I put it to everyone that the first and third checks are equivalent and : redundant. They are not redundant. They provide a little (although not much) extra security for those sites that have had a root account added by intruders which the admin know nothing of. In the absense of this test, machines in a yp netowrk would be extremely vulnerable to root uid penetration when an intruder can hack the yp database, or spoof replies. OK, so that's a weak wall for a weak protocol, but I'm pretty sure why the extra check for uid 0 is in there. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BROKEN_KEYBOARD_RESET
On Fri, 12 May 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> FreeBSD MAIL writes: > : Is this the kernel setting to dislable ctrl-alt-delete from resetting > : a systtem? If so it seems to be broken in 4.0-RELEASE. > : is there another way of doing this? remaping keyboard perhaps? > : > : # BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to > : # reset the CPU for reboot. This is needed on some systems with broken > : # keyboard controllers. > > No. The hot key squence CAD will reboot the system. Or rather it > will cause the init process to get a signal that causes it to reboot > the system. > > BROKEN_KEYBOARD_RESET does something different. In the IBM PC and > newer compatible machines, the keyboard controller part is connected > to a lot of different things, including the reset line to the CPU. > Generally one can get a fairly clean reset of the CPU by telling the > keyboard controller micro controller to reset the CPU with a nice > pulse downt he reset line. Some keyboard controllers didn't think > this was important enough to get right, so they don't implement this > proplerly. These controllers are generally on the 386 and 486 class > of machines and some pentium laptops (exceptions to the rule exist) > where the keyboard controller was still a 8042 microcontroller > programmed to talk to the keyboard. > Since this has been brought up, any reason that BROKEN_KEYBOARD_RESET is not a recognized option (see kern/12927)? - 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: Double buffered cp(1)
Warner Losh writes: > In message <[EMAIL PROTECTED]> Kris >Kennaway writes: > : (incidentally, another reason to use -pipe is that the above filenames are > : predictable and probably handled insecurely so that another user can cause > : any of your files to be overwritten when you compile something. This is > : on my list of things to fix). > > This is one reason I have TMPDIR set to "." when I'm running as me. ...and lose a lot of files to delete... I propose create (or use old) subdirectory in /tmp on startup and use this subdirectory for set TMPDIR See PR bin/18275 -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BROKEN_KEYBOARD_RESET
In message <[EMAIL PROTECTED]> FreeBSD MAIL writes: : Is this the kernel setting to dislable ctrl-alt-delete from resetting : a systtem? If so it seems to be broken in 4.0-RELEASE. : is there another way of doing this? remaping keyboard perhaps? : : # BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to : # reset the CPU for reboot. This is needed on some systems with broken : # keyboard controllers. No. The hot key squence CAD will reboot the system. Or rather it will cause the init process to get a signal that causes it to reboot the system. BROKEN_KEYBOARD_RESET does something different. In the IBM PC and newer compatible machines, the keyboard controller part is connected to a lot of different things, including the reset line to the CPU. Generally one can get a fairly clean reset of the CPU by telling the keyboard controller micro controller to reset the CPU with a nice pulse downt he reset line. Some keyboard controllers didn't think this was important enough to get right, so they don't implement this proplerly. These controllers are generally on the 386 and 486 class of machines and some pentium laptops (exceptions to the rule exist) where the keyboard controller was still a 8042 microcontroller programmed to talk to the keyboard. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kernel panics at boot, how to specify dump device?
On Fri, 12 May 2000, Greg Lehey wrote: > On Thursday, 11 May 2000 at 13:03:59 -0700, Brian O'Shea wrote: > > > On Thu, May 11, 2000 at 12:20:38PM -0700, Marco Molteni wrote: > > > > > I have a 4-STABLE kernel that panics at boot. How do I force the kernel > > > to core dump? [..] > > From the LINT kernel config file: > > > > config kernel root on wd0 dumps on wd0 > > That's not there in 4.0. I believe most of this was vandalized some > time late last year. Yes, I remember having seen it in the past. > I've been running in to this problem too. Hehe, I've seen your emails on the subject in the archive ;-) > I'm planning to add an option to ddb where you can specify the dump > device at the time where you want to take the dump. Looks like a good idea. > Marco, where exactly is it panicing? Do you have ddb in the kernel? Yes, I have ddb in the kernel, although I am not good at it (I prefer symbolic debuggers ;-). It is panicing in the initialization of the routing tables, probably because I am playing with them :-) Anyway, reading the email archives I found a suggestion by bde (I think) who said: who needs a core dump, if you can use remote gdb? Well, since I have two machines, I found that remote gdb is the way to go :-) Thanks Marco -- Marco Molteni "rough consensus and running code" SRI International, System Design Laboratory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
In message <[EMAIL PROTECTED]> Kris Kennaway writes: : (incidentally, another reason to use -pipe is that the above filenames are : predictable and probably handled insecurely so that another user can cause : any of your files to be overwritten when you compile something. This is : on my list of things to fix). This is one reason I have TMPDIR set to "." when I'm running as me. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
more still breaks world
buildworld still breaks in more (cvsup from around 12:30 EDT)... however it only breaks if you have obj directories: virtual-voodoo# make obj /usr/obj/source/src/usr.bin/more created for /source/src/usr.bin/more virtual-voodoo# make depend sed -e 's/\\//g' -e 's/\"/\\\"/g' -e 's/$/\\n\\/' < /source/src/usr.bin/mor e/default.morerc >> defrc.h rm -f .depend mkdep -f .depend -a-I/source/src/usr.bin/more -I/usr/obj/source/src/usr.bin/ more -DTERMIOS /source/src/usr.bin/more/ch.c /source/src/usr.bin/more/command.c /source/src/usr.bin/more/help.c /source/src/usr.bin/more/input.c /source/src/us r.bin/more/line.c /source/src/usr.bin/more/linenum.c /source/src/usr.bin/more/ma cro.c main.c /source/src/usr.bin/more/ncommand.c /source/src/usr.bin/more/option .c /source/src/usr.bin/more/os.c /source/src/usr.bin/more/output.c /source/src/u sr.bin/more/position.c /source/src/usr.bin/more/prim.c /source/src/usr.bin/more/ screen.c /source/src/usr.bin/more/signal.c /source/src/usr.bin/more/tags.c /sour ce/src/usr.bin/more/ttyin.c cc: main.c: No such file or directory mkdep: compile failed *** Error code 1 Notice how 'main.c' above doesn't have a path? Without the obj directory the path isn't required since your building in /usr/src.. -Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Dual ethernet tl on Compaq Server (fwd)
I sent this in yesterday but got no info back. Any ideas? I am getting the following error after I upgraded from 3.4 -stable to 4.0 -stable cvsuped as of a few days ago. I am getting the following error: tl0: got an invalid interrupt! tl1: got an invalid interrupt! Network services seem ok, but it is throwing this error constantly. It is a cvsup of 4.0 -stable as of a few days ago. The hardware is a compaq 1850r server with the embedded tl nic and a tl addon card. Any help would be appreciated. Thanks Chris --- Christopher T. Griffiths Quansoo Group Inc. [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rexec as root
>What you say is correct, but personally I think deprecated really should >mean deprecated. There are better alternatives to rexec (ssh - open or >otherwise) and they ought to be pushed. FreeBSD provides tools for people, we don't enforce our policy on them. I think the proposed change makes sense. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rexec as root
On Fri, 12 May 2000, Nick Sayer wrote: > I would like to gather some opinions in regards to _very slightly_ > backing off > on rexec's security. Don't do it? > rexec makes the following checks... [ uid==0, password blank, uname in /etc/ftpusers ] > I put it to everyone that the first and third checks are equivalent and What you say is correct, but personally I think deprecated really should mean deprecated. There are better alternatives to rexec (ssh - open or otherwise) and they ought to be pushed. If admins _really_ want this functionality, patching the source isn't so much of a hardship. But it makes the path f least resistance the installation of a better alternative :-) jan -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 [EMAIL PROTECTED] Spreadsheet through network. Oh yeah. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
rexec as root
I would like to gather some opinions in regards to _very slightly_ backing off on rexec's security. rexec makes the following checks, and refuses to allow usage if any are true: uid == 0 password is blank user is in /etc/ftpusers I put it to everyone that the first and third checks are equivalent and redundant. Moreover, since the first check can be done by the third check (and is at install time by default) without recompiling rexecd, removing the first check results in no real loss of security, while slightly increasing flexibility for those who have some need for it. Yes, the r commands are deprecated. But they are still there, and I am all for allowing the administrator to decide to override defaults rather than forcing them to alter the source and recompile it. Comments? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re:BROKEN_KEYBOARD_RESET
Sorry for the stupid quiestion. I figured it out from LINT that is the options SC_DISABLE_REBOOT # disable reboot key sequence Thanks Richard Puga [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BROKEN_KEYBOARD_RESET
The option you're looking for is: options SC_DISABLE_REBOOT BROKEN_KEYBOARD_RESET is used for something else. :) Cheers, Marc On Fri, May 12, 2000 at 04:29:40AM -1000, FreeBSD MAIL wrote: > Is this the kernel setting to dislable ctrl-alt-delete from resetting > a systtem? If so it seems to be broken in 4.0-RELEASE. > is there another way of doing this? remaping keyboard perhaps? > > > # BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to > # reset the CPU for reboot. This is needed on some systems with broken > # keyboard controllers. > > Thanks in advance > > Richard Puga > [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
BROKEN_KEYBOARD_RESET
Is this the kernel setting to dislable ctrl-alt-delete from resetting a systtem? If so it seems to be broken in 4.0-RELEASE. is there another way of doing this? remaping keyboard perhaps? # BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to # reset the CPU for reboot. This is needed on some systems with broken # keyboard controllers. Thanks in advance Richard Puga [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Kris Kennaway writes: > On Fri, 12 May 2000, Koster, K.J. wrote: > > > Unless this has been changed from 3.4 to 4.0, gcc defaults to /var/tmp. I > > never understood why, and the gcc manual page claims that it's /tmp (I > > think). MFS users, synchronize your TMPDIR variables ... now. :-) > > It did. > > Compiling a simple test program just now shows: > > + -rw--- 1 root wheel0 May 12 00:16 /tmp/ccl22910.i > + -rw--- 1 root wheel0 May 12 00:16 /tmp/ccc22910.s > + -rw--- 1 root wheel0 May 12 00:16 /tmp/ccP22910.o > - -rw--- 1 root wheel0 May 12 00:16 /tmp/ccl22910.i > - -rw--- 1 root wheel0 May 12 00:16 /tmp/ccc22910.s > - -rw--- 1 root wheel0 May 12 00:16 /tmp/ccP22910.o > > (incidentally, another reason to use -pipe is that the above filenames are > predictable and probably handled insecurely so that another user can cause > any of your files to be overwritten when you compile something. This is > on my list of things to fix). Just use own subdirectory in /tmp with some anticrackers manoevres. see PR bin/18275 and http://www.links.ru/FreeBSD/mkinittmpdir/ which do this work. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: newbusified rp driver
On Thu, 11 May 2000 06:55:48 -0700 (PDT), Chris Ptacek <[EMAIL PROTECTED]> said: Chris> I am currently working on a program to download the microcode into Chris> the RocketModem2 cards. One thing I noticed is that the RocketPort Chris> driver defaults the cards to 8 lines, I put in a small fix and since Chris> you were already updating it I though you might want to include it. They used to call sReadAiopNumChan() to count the number of channels on an aiop. Maybe we can revert to it for an unknown PCI ID, but sReadAiopNumChan() seems to freeze my box every now and then during configuration. Chris> In the sPCIInitController function in the switch(VendorDevice) I Chris> added RP_DEVICE_ID_6M and RP_DEVICE_ID_4M 0x000C and 0x000D Chris> respectivly, and added the defines to the rpreg.h file. Note this Chris> really on means the correct number of lines will be reported, but Chris> I think it is really the only change needed. Thanks, the updated patch is now at the same URI as the one announced in my first mail. Actually, I have tested my driver with only one PCI card. The ISA part of the driver is not tested. -- Seigo Tanimura <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Double buffered cp(1)
Kris Kennaway wrote: > > On Mon, 24 Apr 2000, Kent Stewart wrote: > > > This is what I see on a buildworld with 4.0-Stable > > > > Modified /etc/make.conf and commented out CFLAGS= -Os -pipe > > 3707.4u 799.6s 1:35:52.46 78.3% 1374+1477k 56974+173232io 2337pf+0w > > 3693.9u 800.5s 1:29:45.73 83.4% 1375+1477k 55201+173224io 2160pf+0w > > Modified /etc/make.conf and added CFLAGS= -pipe > > 3559.2u 807.2s 1:28:00.05 82.6% 1608+1286k 56499+174033io 2516pf+0w > > This is an old message, but what you're seeing here is that if CFLAGS is > not overridden, it is set by sys.mk to "-O -pipe" > > Setting CFLAGS explicitly to "-pipe" is faster because it does no > optimization, "-Os -pipe" would be slower because it does more. Leaving > out -pipe would be slower still, because the compiler does data passing > using temporary files in /tmp instead of via a pipe. Part of this you had to go back about 15-20 messages. There were some comments about options that would speed the system up. I then ran both styles of buildworlds on kernels built with the -Os to see if my buildworld times changed. It wasn't significant. A long about this same time I ran some tests with using this for IBM DCAS drive current setup. da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Previously, the tagged queueing was turned off. I have run a number of tests with 4.0-Stable and enabling tagged queueing on this drive didn't slow the disk down. It really didn't speed it up to speak of either. Kent > > Kris > > > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: ipfw and verbose mode (solved)
At 12/05/00, you wrote: >On Fri, 12 May 2000, Gianmarco Giovannelli wrote: > > > I am missing these kind of logging which I require with the "log" keyword: > >Check your syslog.conf settings - ipfw didn't change the logging behaviour >with 4.0, AFAIK. Find it ! Thanks it logs everything in /var/log/security now... Thanks again for your input. Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why this works?
* Ville-Pertti Keinonen <[EMAIL PROTECTED]> [000511 22:49] wrote: > > [EMAIL PROTECTED] (FengYue) writes: > > > I've 3 small programs. First one writes 4K of data contains 'A's into a > > file /tmp/pagetest and then lseek() to the begin of the file. > > Second one writes 4K of 'Z' into the same file /tmp/pagetest and > > then lseek() to the begin of the file. They both do that in a tight > > loop. Now, the third program reads 4K of data from /tmp/pagetest > > and exit if the 4K data does not contain all 'A's nor 'Z's. 3 programs > > run concurrently on the same machine (3.4). No lock in the code whatsoever, > > and all 3 programs use pure write() and read(). I thought the third > > program would exit pretty quickly since the data in the file may contain > > mixed of 'A's and 'Z's, but it has been running for hours and nothing > > happened. Could someone kindly explain this? I was told that this is > > because the pagesize is 4096 in the kernel, so that read()/write() 4K of > > data will not get context switched until the call is compeleted. > > Is that right? > > Not quite. If FreeBSD didn't perform locking, operations affecting > single filesystem blocks would probably be atomic (as long as the > userland buffer is in memory). > > However, FreeBSD does perform locking in read(2) and write(2) for > local files, so your third program should never fail and exit. > > Note that the system call interface does not guarantee reads or writes > to be atomic, this just happens to be how it is implemented at the > moment. Afaik several Unix standards mandate this behavior, Linux doesn't follow this standard though. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: ipfw and verbose mode
On Fri, 12 May 2000, Gianmarco Giovannelli wrote: > I am missing these kind of logging which I require with the "log" keyword: Check your syslog.conf settings - ipfw didn't change the logging behaviour with 4.0, AFAIK. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Double buffered cp(1)
On Fri, 12 May 2000, Koster, K.J. wrote: > Unless this has been changed from 3.4 to 4.0, gcc defaults to /var/tmp. I > never understood why, and the gcc manual page claims that it's /tmp (I > think). MFS users, synchronize your TMPDIR variables ... now. :-) It did. Compiling a simple test program just now shows: + -rw--- 1 root wheel0 May 12 00:16 /tmp/ccl22910.i + -rw--- 1 root wheel0 May 12 00:16 /tmp/ccc22910.s + -rw--- 1 root wheel0 May 12 00:16 /tmp/ccP22910.o - -rw--- 1 root wheel0 May 12 00:16 /tmp/ccl22910.i - -rw--- 1 root wheel0 May 12 00:16 /tmp/ccc22910.s - -rw--- 1 root wheel0 May 12 00:16 /tmp/ccP22910.o (incidentally, another reason to use -pipe is that the above filenames are predictable and probably handled insecurely so that another user can cause any of your files to be overwritten when you compile something. This is on my list of things to fix). Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: ipfw and verbose mode
At 11/05/00, Conrad Sabatier wrote: >On 12-May-00 Gianmarco Giovannelli wrote: > > > > The problem is that ipfw, even if working, don't log me on > > the screen or in /var/log/messages the rules that are triggered > > (with the log keyword) like: > > > > ipfw -q add 1 deny log ip from any to any > >I don't suppose it could be that you're using the "quiet" flag (-q)? >:-) No, I think the -q flag is used i.e. to disable output when the rules is set, not to disable the logging facilities. I am missing these kind of logging which I require with the "log" keyword: [3.4-stable] May 9 20:14:34 freebsd /kernel: ipfw: 1 Deny ICMP:3.13 195.22.192.30 192.168.0.124 in via tun0 May 9 20:14:46 freebsd /kernel: ipfw: 1 Deny ICMP:3.13 195.22.192.30 192.168.0.124 in via tun0 May 9 20:17:59 freebsd /kernel: ipfw: 1 Deny ICMP:8.0 194.119.192.34 194.243.20.91 in via tun0 In 4.0-STABLE these kind of logging doesn't happen anymore, even if I set in the kernel options IPFIREWALL options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity (I repeat because I fw the message in -hackers mailing list) and even if ipfw logs the reached counter [4.0-stable] May 10 19:58:41 freebsd /kernel: ipfw: limit 100 reached on entry 1 and my ipfw var are ok (I presume): sysctl -a [...] net.inet.ip.fw.enable: 1 net.inet.ip.fw.one_pass: 1 net.inet.ip.fw.debug: 1 net.inet.ip.fw.verbose: 1 net.inet.ip.fw.verbose_limit: 100 net.inet.ip.fw.dyn_buckets: 256 net.inet.ip.fw.curr_dyn_buckets: 256 net.inet.ip.fw.dyn_count: 0 net.inet.ip.fw.dyn_max: 1000 net.inet.ip.fw.dyn_ack_lifetime: 300 net.inet.ip.fw.dyn_syn_lifetime: 20 net.inet.ip.fw.dyn_fin_lifetime: 20 net.inet.ip.fw.dyn_rst_lifetime: 5 net.inet.ip.fw.dyn_short_lifetime: 5 [...] Thanks to everyone for attention... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Double buffered cp(1)
> > Leaving out -pipe would be slower still, because the > compiler does data passing using temporary files in /tmp > instead of via a pipe. > Unless this has been changed from 3.4 to 4.0, gcc defaults to /var/tmp. I never understood why, and the gcc manual page claims that it's /tmp (I think). MFS users, synchronize your TMPDIR variables ... now. :-) Kees Jan == You are only young once, but you can stay immature all your life To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
