Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jon Ribbens
"Daniel C. Sobral" [EMAIL PROTECTED] wrote: I can add it to the list of reasons I don't use it then I guess ;-). Whatever. The operating system you use also does it. How terribly tedious. Cheers Jon -- \/ Jon Ribbens / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED]

Setting up a firewall with dynamic IPs

1999-07-13 Thread Stephen Hocking-Senior Programmer PGS Tensor Perth
I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external interface. I don't know ahead of time what IP address is going to be allocated to me before I dial up. Would it be possible to specify an interface

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
You're browsing with netscape and It hits about 32megs in size, you click on a multimedia object and netscape execs a helper app. If the system has real vfork(2) like NetBSD, this is not problem. you also have to consider a program wishing to make sparse use of its address space, without

Re: bin/12578: `` subshell taints PWD

1999-07-13 Thread Niall Smart
Sheldon Hearn wrote: On Mon, 12 Jul 1999 18:37:13 GMT, Niall Smart wrote: The patch appended seems to fix this, I'd like someone familiar with sh to review it though, since this may be symptomatic of a general problem with command substitution. As I understand your patch, you're

Re: a BSD identd

1999-07-13 Thread Niall Smart
"Brian F. Feldman" wrote: On Mon, 12 Jul 1999, Sheldon Hearn wrote: On Sun, 11 Jul 1999 12:47:30 MST, Doug wrote: Finally, Brian might want to search the bugtraq archives before he commits anything. There have been quite a few identd related discussions, and it would be

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Kris Kennaway
On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external interface. I don't know ahead of time what IP address is going to be

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Keith Stevenson
On Tue, Jul 13, 1999 at 10:16:32PM +0930, Kris Kennaway wrote: On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Jon Hamilton
In message Pine.OSF.4.10.9907132210380.2013-10@bragg, Kris Kennaway wrote : } On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote } : } } I was checking out the firewall setup in /etc/rc.firewall, and noticed } that the simple example relied on a fixed IP

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Brian F. Feldman
On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external interface. I don't know ahead of time what IP address is going to be

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
On Tue, 13 Jul 1999 10:11:14 -0400 (EDT), "Brian F. Feldman" [EMAIL PROTECTED] said: you also have to consider a program wishing to make sparse use of its address space, without overcommit it becomes impossible. SVR4 has MAP_NORESERVE option for mmap(2) for this. So, default

Re: Why 'dd' does not seek over 'char' devs (specifically raw diskpartitions).

1999-07-13 Thread Brian F. Feldman
On Tue, 13 Jul 1999, Luigi Rizzo wrote: Hi, i have a question. Why 'dd' does not seek over 'char' devs (specifically raw disk partitions). Not all character devices support seeking. So, we work with the LCD... Sorry, I don't like this either. It would be better, maybe, just to fix character

Re: Why 'dd' does not seek over 'char' devs (specifically raw disk

1999-07-13 Thread Luigi Rizzo
Hi, i have a question. Why 'dd' does not seek over 'char' devs (specifically raw disk partitions). Not all character devices support seeking. So, we work with the LCD... Sorry, I don't like this either. It would be better, maybe, just to fix character devices. couldn't we first try

Which device should I make with this error?

1999-07-13 Thread eT
During a make release for 3.2-RELEASE I get the following error: Making the regular boot floppy. Compressing doc files... sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/m fsfd 8000 minimum2 vnconfig: open: Device not configured *** Error code 1 Stop. *** Error

Re: Which device should I make with this error?

1999-07-13 Thread Chris D. Faulhaber
On Tue, 13 Jul 1999, eT wrote: During a make release for 3.2-RELEASE I get the following error: Making the regular boot floppy. Compressing doc files... sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/m fsfd 8000 minimum2 vnconfig: open: Device not

Re: Which device should I make with this error?

1999-07-13 Thread David G. Andersen
Lo and Behold, eT said: During a make release for 3.2-RELEASE I get the following error: vnconfig: open: Device not configured *** Error code 1 What does this mean and how do I fix it? It means you don't have any vnode devices configured in your kernel. What, you ask, is a vnode disk

Re: bin/12578: `` subshell taints PWD

1999-07-13 Thread Oliver Fromme
Niall Smart wrote in list.freebsd-hackers: As I understand it most builtins will not spawn a new shell when they are used in command substitution: niall% echo `echo $$` $$ 20354 20354 niall% Actually, that example doesn't prove anything. :-) $ echo `echo $$` $$ 8376 8376 $ echo

Re: bin/12578: `` subshell taints PWD

1999-07-13 Thread Sheldon Hearn
On Tue, 13 Jul 1999 18:13:42 +0200, Oliver Fromme wrote: Command substitution certainly has to spawn a subshell, even for built-in commands, because otherwise you could modify parent shell variables within command substitutions. But isn't that exactly what's happening here, where PWD is

Re: Why 'dd' does not seek over 'char' devs (specifically raw disk

1999-07-13 Thread John Polstra
In article [EMAIL PROTECTED], Brian F. Feldman [EMAIL PROTECTED] wrote: On Tue, 13 Jul 1999, Luigi Rizzo wrote: couldn't we first try lseek and only do the reads on char devs where the lseek fails ? lseek() won't usually fail unless it's something like EBADF. It merely sets the current

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 10:11:14 -0400 (EDT) "Brian F. Feldman" [EMAIL PROTECTED] wrote: SVR4 has MAP_NORESERVE option for mmap(2) for this. So, default behaivour don't have to be overcommitment. Isn't that just like mmap()ing then mlock()ing the range? That would keep it in core.

RE: more amd hangs: in _start()

1999-07-13 Thread Doug
On Tue, 13 Jul 1999, Ladavac Marino wrote: I don't know if your diagnosis was in jest, Yes it was, but thank you for asking. :) I should have known better than to attempt subtle humor at the end of a long, tiring day. Doug -- On account of being a democracy and run by the

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
This topic has been rehashed a thousand times. What it comes down to is that if you want to disallow overcommit, you have to multiply the amount of swap space in the system relative to current levels in order to get the same performance limits as you had before. If you

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 11:13:49 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: SysV was totally and utterly broken in regards to swap allocation. The only major operating system that used it as a base was IRIX and SGI found out very quickly that pre-reserving swap is a

Re: bin/12578: `` subshell taints PWD

1999-07-13 Thread Doug
On Tue, 13 Jul 1999, Oliver Fromme wrote: But isn't that exactly what's happening here, where PWD is being tainted by the commands evaluated within the substitution? Yes, I'd call that a bug which should be fixed. The manpage clearly says: "The shell expands the command

Re: 3.2-STABLE not stable but panicy?

1999-07-13 Thread Wilko Bulte
As Mike Smith wrote ... This is typically symptomatic of poor CPU cooling; all of a sudden you Well, it wasn't the cooler, that was just fine. The CPU was quite cool (it has a big, good heatsink fan) are running the CPU at full power 100% of the time, rather than sitting in an HLT

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread David Malone
On Tue, Jul 13, 1999 at 02:47:20PM -0400, Brian F. Feldman wrote: But I have a valid point: can we do something better than posting a SIGKILL to the largest process? I think AIX sends all running processes a magic signal (SIGDANGER?) which indicates that the system is short of resources, and

Re: Why 'dd' does not seek over 'char' devs (specifically raw disk

1999-07-13 Thread Brian F. Feldman
On Tue, 13 Jul 1999, John Polstra wrote: In article [EMAIL PROTECTED], Brian F. Feldman [EMAIL PROTECTED] wrote: On Tue, 13 Jul 1999, Luigi Rizzo wrote: couldn't we first try lseek and only do the reads on char devs where the lseek fails ? lseek() won't usually fail unless it's

Re: a BSD identd

1999-07-13 Thread Ian Dowse
In message [EMAIL PROTECTED], "Bria n F. Feldman" writes: On 13 Jul 1999, Ville-Pertti Keinonen wrote: [EMAIL PROTECTED] (Brian F. Feldman) writes: It's "out with the bad, in with the good." Pidentd code is pretty terrible . The only security concerns with my code were wrt FAKEID, and

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Jacob
We could have the ability to mark processes as being more or less preferable as kill candidates. I'm not sure I really care anymore, though... there is so much disk space available now that it is fairly difficult to run the system out of swap space. I don't think I've

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Brian F. Feldman
On Tue, 13 Jul 1999, Matthew Dillon wrote: :But I have a valid point: can we do something better than posting a SIGKILL :to the largest process? : : Brian Fundakowski Feldman _ __ ___ ___ ___ ___ : [EMAIL PROTECTED] _ __ ___ | _ ) __| \ We could

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread R. Matthew Emerson
"Brian F. Feldman" [EMAIL PROTECTED] writes: But I have a valid point: can we do something better than posting a SIGKILL to the largest process? If I remember correctly, AIX sends a signal to all processes asking them to free up memory. (Processes ignore this signal by default.) If nobody

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Chris G. Demetriou
[cc list trimmed because it was getting ... insane, and it's not like this is a critical point. It's just beating up a topic which has been beaten up by many others.] Matthew Dillon [EMAIL PROTECTED] writes: Thus it makes little sense to try to disallow overcommit. It gains you

Re: a BSD identd

1999-07-13 Thread John Polstra
In article [EMAIL PROTECTED], Ian Dowse [EMAIL PROTECTED] wrote: Why not actually store the fake ID in a symbolic link? That way you just do a readlink(), which would be safer, neater and faster than reading a file. A user can set up a fake ID with something like: ln -s

Anybody tried one of these VXA tape drives with FreeBSD?

1999-07-13 Thread Jaye Mathisen
Look fairly robust: http://vxatape.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
:How hard would it be to add a sysctl variable that controlled whether or not :the system would overcommit memory? : :-Archie : :___ :Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Archie,

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 11:59:25 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: We could have the ability to mark processes as being more or less preferable as kill candidates. I'm not sure I really care anymore, though... there is so much disk space available now that it

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
: :On Tue, 13 Jul 1999 11:59:25 -0700 (PDT) : Matthew Dillon [EMAIL PROTECTED] wrote: : : We could have the ability to mark processes as being more or less : preferable as kill candidates. I'm not sure I really care anymore, : though... there is so much disk space available now

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
: : On Tue, 13 Jul 1999 11:13:49 -0700 (PDT), : Matthew Dillon [EMAIL PROTECTED] said: : : Doh! Even solaris doesn't overcommit - you think it actually : reserves data blocks for its file-backed swap? Bzzt! It uses : an overcommit model too. : :Unlike 4.4BSD derived VM,

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
On Tue, 13 Jul 1999 14:16:54 -0700 (PDT), Matthew Dillon [EMAIL PROTECTED] said: Unlike 4.4BSD derived VM, Solaris VM has a way to reserve backing store. Secondly, for such a server to fail to run is just as bad as if the system were to run out of swap. IRIX has a

Re: more amd hangs: problem really in syslog?

1999-07-13 Thread Matthew Dillon
: : So I started thinking that maybe the problem was actually in :syslog (or amd's interface to it). So I disabled the following two options :in my amd.conf file: : :log_file = syslog:local7 :log_options =all : : And lo and behold, it worked like a charm. I

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 14:14:52 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: If you don't have the disk necessary for a standard overcommit model to work, you definitely do not have the disk necessary for a non-overcommit model to work. You obviously didn't pay

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
: ram and 512MB of swap (4MB of swap in use), but the kernel reports over : 3 GB of VM assigned to processes. That's a fairly lightly loaded machine. : :What you say is generally true; however, the problem is that *you* :are making implicit assumptions about what applications *I* might

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 14:16:54 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: ... and it doesn't mean squat. What, the absolutely critical server that you are trying to run decides to exit because it can't guarentee sufficient backing store? First of all, this situation

Re: more amd hangs: problem really in syslog?

1999-07-13 Thread Mike Smith
After pounding on this some more with today's -current (prior to the MNT_ASYNC flag change) I got a lot more lockups that looked like this: On Mon, 12 Jul 1999, Doug wrote: Ok, got another hang in "siobi" state (this time after it successfully completed the script). Here is

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 14:27:54 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: You are assuming that the situation actually occurs. In real life, it will not occur unless the critical server is running away with memory. I have never, ever run one of BEST's servers

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
On Tue, 13 Jul 1999 14:27:54 -0700 (PDT), Matthew Dillon [EMAIL PROTECTED] said: That's wrong. On such systems, critical server has a chance to save it's data to filesystem. On 4.4BSD derived systems, it cannot be guaranteed. You are assuming that the situation actually

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 14:31:38 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: :- I might be creating a very limited embedded system with just a few : small processes that are all written to *handle* out of memory situations. Really? Then setting resource limits from within

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Chris G. Demetriou
Matthew Dillon [EMAIL PROTECTED] writes: If you don't have the disk necessary for a standard overcommit model to work, you definitely do not have the disk necessary for a non-overcommit model to work. I'd _really_ like to know how you figure this. textdatabss dec

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
: :On Tue, 13 Jul 1999 14:27:54 -0700 (PDT) : Matthew Dillon [EMAIL PROTECTED] wrote: : : You are assuming that the situation actually occurs. In real life, : it will not occur unless the critical server is running away with : memory. : : I have never, ever run one of

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
On Tue, 13 Jul 1999 14:53:43 -0700 (PDT), Matthew Dillon [EMAIL PROTECTED] said: If you are talking about a user intentionally attempting to run a system out of swap, it is fairly easy to do whether the system uses an overcommit model or not. The user has any number of

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 14:56:52 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: Jason, I am using real life situations to demonstrate my point. You are perfectly welcome to use your own REAL-LIFE situations to demonstrate yours. It is the real-life application that

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
: a system out of swap, it is fairly easy to do whether the system : uses an overcommit model or not. The user has any number of : ways of blowing the server up too - for example, by making : thousands of connections to it or running many huge queries in : parallel. : :If

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
:Jason Thorpe wrote: : : On Tue, 13 Jul 1999 14:14:52 -0700 (PDT) : Matthew Dillon [EMAIL PROTECTED] wrote: : : If you don't have the disk necessary for a standard overcommit model to : work, you definitely do not have the disk necessary for a non-overcommit : model to work.

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Neil A. Carson
On Tue, 13 Jul 1999, Matthew Dillon wrote: This is an excellent example of a solution. Another example would be to implement your own memory management subsystem... that is, your own shared library which keeps track of memory allocations on a global basis. I could do one in

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 15:37:26 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: When you write embedded systems like these, you do not run any general purpose binaries at all. You run fully custom binaries and you take control of the memory management yourself. Heh,

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
:On Tue, 13 Jul 1999 15:12:14 -0700 (PDT) : Matthew Dillon [EMAIL PROTECTED] wrote: : : The text size of a program is irrelevant, because swap is never : allocated for it. The data and BSS are only relevant when they : are modified. : :Bzzt. BSS is relevant when accessed (at

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
On Tue, 13 Jul 1999 15:29:37 -0700 (PDT), Matthew Dillon [EMAIL PROTECTED] said: In the same manner any truely critical system server must handle the resource management itself to deal with all sorts of problem situations, including memory. You do not need to build any

Re: more amd hangs: problem really in syslog?

1999-07-13 Thread Doug
On Tue, 13 Jul 1999, Matthew Dillon wrote: : : So I started thinking that maybe the problem was actually in :syslog (or amd's interface to it). So I disabled the following two options :in my amd.conf file: : :log_file = syslog:local7 :log_options =all : :

Re: more amd hangs: problem really in syslog?

1999-07-13 Thread Doug
On Tue, 13 Jul 1999, Mike Smith wrote: After pounding on this some more with today's -current (prior to the MNT_ASYNC flag change) I got a lot more lockups that looked like this: On Mon, 12 Jul 1999, Doug wrote: Ok, got another hang in "siobi" state (this time after it

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Archie Cobbs
Matthew Dillon writes: : ram and 512MB of swap (4MB of swap in use), but the kernel reports over : 3 GB of VM assigned to processes. That's a fairly lightly loaded machine. : :What you say is generally true; however, the problem is that *you* :are making implicit assumptions about what

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Mike Smith
So, Matt, I understand that you think that the folks who are want to turn off overcommit are looking to hang themselves, but how much does it cost to sell them the rope? The issue here is that "turning off overcommit" isn't just a switch. There are a lot of other things that you're likely

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 16:16:07 -0700 Mike Smith [EMAIL PROTECTED] wrote: Matt's point, which he's not making by virtue of talking too much, is that you can't make a "no overcommit" system behave like an "overcommit" system, and most people are used to the sort of things that the latter

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 16:24:53 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: I'm sure the feeling is mutual. More to the point, I really seriously doubt that any of the core developers would consider this idea either because it's been rejected in the past and, so far,

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
:(Mike Smith [EMAIL PROTECTED]) :Matt's point, which he's not making by virtue of talking too much, is :that you can't make a "no overcommit" system behave like an "overcommit" :system, and most people are used to the sort of things that the latter :makes practical. Heh heh.

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
:On Tue, 13 Jul 1999 16:24:53 -0700 (PDT) : Matthew Dillon [EMAIL PROTECTED] wrote: : : I'm sure the feeling is mutual. More to the point, I really seriously : doubt that any of the core developers would consider this idea either : because it's been rejected in the past and, so

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 16:29:50 -0700 Mike Smith [EMAIL PROTECTED] wrote: You can make the "overcommit or not overcommit" option a switch, but the consumers of the system (may) need to change their behaviour as well. I never said they wouldn't have to. -- Jason R. Thorpe [EMAIL

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Mike Smith
On Tue, 13 Jul 1999 16:29:50 -0700 Mike Smith [EMAIL PROTECTED] wrote: You can make the "overcommit or not overcommit" option a switch, but the consumers of the system (may) need to change their behaviour as well. I never said they wouldn't have to. "Making it just a switch"

Re: a BSD identd

1999-07-13 Thread Kevin Day
Doug wrote: John Polstra wrote: Are you sure? If you simply don't run an identd, the queries will get an instant connection refused error. That's even faster than sending back a bogus response. Many daemons that request ident, and almost all IRC daemons that I'm aware of

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread David Greenman
: :Well, all I can say is: : : I'm sure glad you don't have any influence over the code : base I run. : :-- Jason R. Thorpe [EMAIL PROTECTED] I'm sure the feeling is mutual. More to the point, I really seriously doubt that any of the core developers would consider

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread John-Mark Gurney
Matthew Dillon scribbled this message on Jul 13: FreeBSD's swap subsystem has a basic limitation of 4 swap areas. This is due to the design of the interleaving algorithms. Increasing this number is simple, but it results in phenominally more kernel memory getting wired.

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-13 Thread Jason Thorpe
On Tue, 13 Jul 1999 16:56:26 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: You have to consider the probability of an event occuring, not just the possibility that the event might occur. If the probability is one in a million years, then it is not something you need

Re: a BSD identd

1999-07-13 Thread Sheldon Hearn
On Mon, 12 Jul 1999 15:12:49 -0400, "Brian F. Feldman" wrote: It's "out with the bad, in with the good." Pidentd code is pretty terrible. Hi Brian, I let your comment above go at the time that you said it and I waited for Kevin Day to substantiate similar claims. Kevin very kindly took the

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-13 Thread Matthew Dillon
: :On Tue, 13 Jul 1999 16:56:26 -0700 (PDT) : Matthew Dillon [EMAIL PROTECTED] wrote: : : You have to consider the probability of an event occuring, not just : the possibility that the event might occur. If the probability is : one in a million years, then it is not something

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Ted Faber
-BEGIN PGP SIGNED MESSAGE- Matthew Dillon wrote: I said: :So, Matt, I understand that you think that the folks who are want to :turn off overcommit are looking to hang themselves, but how much does :it cost to sell them the rope? I'm guessing that a simple implementation would be

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
:Hm. It's misunderstanding. : :I don't agree with you about the following point. :Thus, the situation might happen. : :Give me a shell and I can crash any machine. If you are assuming :hostile users, you cannot assume that your magic overcommit protection :will save your server.

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
On Tue, 13 Jul 1999 17:25:21 -0700 (PDT), Matthew Dillon [EMAIL PROTECTED] said: With today's modern high capacity disk drives, a properly configured multi-user system will have enough swap that running it out is difficult to say the least. That's wrong. Please remember

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Matthew Dillon
: On Tue, 13 Jul 1999 17:25:21 -0700 (PDT), : Matthew Dillon [EMAIL PROTECTED] said: : : With today's modern high capacity disk drives, a properly configured : multi-user system will have enough swap that running it out is difficult : to say the least. : :That's wrong. :Please

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
On Tue, 13 Jul 1999 17:53:10 -0700 (PDT), Matthew Dillon [EMAIL PROTECTED] said: You keep on saying that users can run the system out of swap easily, and I've tried to point out to you that it isn't quite as easy as you believe (and I've used a real-life example to

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Stephen Hocking-Senior Programmer PGS Tensor Perth
Thanks for every one's help - I now have it working nicely. It's amazing what you discover when RTFMing. Oddly enough, running nmap with the Christmas tree scan (after I've allowed only smtp ssh to be connected to) gives the following - # ./nmap -v -v -sX foo Starting nmap V. 2.12 by Fyodor

Re: Reading CIS from kernel?

1999-07-13 Thread David O'Brien
The Xircom ethernet driver needs to read/write PCCARD attribute memory from its probe routine, in order to identify the type of card and to beat ... then making crdread() and crdwrite() (in /sys/pccard/pccard.c) non-static and calling them directly from the driver code would be an easy

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-13 Thread Matthew Dillon
: : Has your simulation ever been kicked by the kernel due to lack of : swap space? : :I already said so. Please at least pretend to read what I wrote :before replying. : :There is a big difference here between a piddling web server and a :1000-hour simulation. If the web server goes

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-13 Thread David Greenman
The point is, the OS should have provided *some* mechanism to insure that the long-running process wasn't affected. It didn't. That's a clear failure of the OS to provide a reasonable environment for this type of computing. Whether this should be solved by switching to a no-overcommit policy,

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-13 Thread Matthew Dillon
: I've long felt that the best solution to problems like this is a per-user :swap space quota. This gives admins a knob to manage the allocation of swap :space while still allowing overcommit. The downside is that it doesn't provide :a graceful way for a program to recover from it's

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-13 Thread John Baldwin
On 14-Jul-99 Jason Thorpe wrote: On Tue, 13 Jul 1999 16:56:26 -0700 (PDT) Matthew Dillon [EMAIL PROTECTED] wrote: You have to consider the probability of an event occuring, not just the possibility that the event might occur. If the probability is one in a million

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Brian F. Feldman
On Tue, 13 Jul 1999, Matthew Dillon wrote: There are other ways. For example, even if a user account is resource limited, root processes (such as sendmail, popper, identd, and so forth) are not. Attacks against these servers generally result in very high loads and sometimes

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread David Brownlee
On Tue, 13 Jul 1999, Matthew Dillon wrote: Jason, I am using real life situations to demonstrate my point. You are perfectly welcome to use your own REAL-LIFE situations to demonstrate yours. It is the real-life application that matters, not a worst-case nightmare theory.

Re: a BSD identd

1999-07-13 Thread Ville-Pertti Keinonen
gr...@freebsd.org (Brian F. Feldman) writes: It's out with the bad, in with the good. Pidentd code is pretty terrible. The only security concerns with my code were wrt FAKEID, and those were mostly fixed (mostly meaning that a symlink _may_ be opened, but it won't be read.) If anyone wants

Boot messages on console in 3.2

1999-07-13 Thread Reinier Bezuidenhout
Hi ... I'm trying to get a 3.2-STABLE to boot via the serial console. I can get the boot: rompt and loader to display to the serial console, but after the 9 second delay it continues to boot but no output is generated to the screen (device probes etc.). After the boot has completed, the login

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jon Ribbens
Daniel C. Sobral d...@newsguy.com wrote: I can add it to the list of reasons I don't use it then I guess ;-). Whatever. The operating system you use also does it. How terribly tedious. Cheers Jon -- \/ Jon Ribbens / j...@oaktree.co.uk To Unsubscribe: send mail to majord...@freebsd.org

Setting up a firewall with dynamic IPs

1999-07-13 Thread Stephen Hocking-Senior Programmer PGS Tensor Perth
I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external interface. I don't know ahead of time what IP address is going to be allocated to me before I dial up. Would it be possible to specify an interface (tun0)

Re: Boot messages on console in 3.2

1999-07-13 Thread Kazutaka YOKOTA
I'm trying to get a 3.2-STABLE to boot via the serial console. I can get the boot: rompt and loader to display to the serial console, but after the 9 second delay it continues to boot but no output is generated to the screen (device probes etc.). After the boot has completed, the login prompt

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Jon Ribbens
Alfred Perlstein bri...@rush.net wrote: You're browsing with netscape and It hits about 32megs in size, you click on a multimedia object and netscape execs a helper app. vfork() you also have to consider a program wishing to make sparse use of its address space, without overcommit it becomes

Re: Replacement for grep(1) (part 2)

1999-07-13 Thread Noriyuki Soda
You're browsing with netscape and It hits about 32megs in size, you click on a multimedia object and netscape execs a helper app. If the system has real vfork(2) like NetBSD, this is not problem. you also have to consider a program wishing to make sparse use of its address space, without

Re: bin/12578: `` subshell taints PWD

1999-07-13 Thread Niall Smart
Sheldon Hearn wrote: On Mon, 12 Jul 1999 18:37:13 GMT, Niall Smart wrote: The patch appended seems to fix this, I'd like someone familiar with sh to review it though, since this may be symptomatic of a general problem with command substitution. As I understand your patch, you're

Re: a BSD identd

1999-07-13 Thread Niall Smart
Brian F. Feldman wrote: On Mon, 12 Jul 1999, Sheldon Hearn wrote: On Sun, 11 Jul 1999 12:47:30 MST, Doug wrote: Finally, Brian might want to search the bugtraq archives before he commits anything. There have been quite a few identd related discussions, and it would be points

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Kris Kennaway
On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external interface. I don't know ahead of time what IP address is going to be

Why 'dd' does not seek over 'char' devs (specifically raw disk partitions).

1999-07-13 Thread Luigi Rizzo
Hi, i have a question. Why 'dd' does not seek over 'char' devs (specifically raw disk partitions). My point is, when a disk develops problems, sometimes it is possible to recover nearby sectors e.g. using dd, and seeking to the right block. However running dd over the char device (rwd*) takes

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Keith Stevenson
On Tue, Jul 13, 1999 at 10:16:32PM +0930, Kris Kennaway wrote: On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Jon Hamilton
In message pine.osf.4.10.9907132210380.2013-100...@bragg, Kris Kennaway wrote : } On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote } : } } I was checking out the firewall setup in /etc/rc.firewall, and noticed } that the simple example relied on a fixed IP address

Re: a BSD identd

1999-07-13 Thread Brian F. Feldman
On 13 Jul 1999, Ville-Pertti Keinonen wrote: gr...@freebsd.org (Brian F. Feldman) writes: It's out with the bad, in with the good. Pidentd code is pretty terrible. The only security concerns with my code were wrt FAKEID, and those were mostly fixed (mostly meaning that a symlink _may_

Re: Setting up a firewall with dynamic IPs

1999-07-13 Thread Brian F. Feldman
On Tue, 13 Jul 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: I was checking out the firewall setup in /etc/rc.firewall, and noticed that the simple example relied on a fixed IP address for the external interface. I don't know ahead of time what IP address is going to be

  1   2   3   >