> Okay, can you be specific about what you mean by
> "There was a time that we were very lax".
If there was a change of server identity, then we did not necessarily
announce what the new identity was in a way that people could trust.
These days, a member of the Security Officer team sends out an
> The current work in progress is available at :
> http://people.freebsd.org/~murray/
> Any feedback would be greatly appreciated.
>
> Thanks,
>
> - Murray
Okay, I read your page and printed it out, and went over it a few times. A
couple of things bothered me, but for the most par
> Jeremiah Gowdy wrote:
> >
> > > Trouble is there is no consistency in the rulings.
> >
> > United States Code Title 17 Chapter 12 Section 1201 Subsection (f)
> >
> > My basic interpretation of this is, if you legally own a copy of the
> > software (firmware is software), you can legally reverse
On Wed, 27 Dec 2000, "Renaud Waldura" <[EMAIL PROTECTED]> wrote:
> I've got that FreeBSD gateway in a corner at my house, it works fine & dandy
> but the constant noise (whirring fans, hard drives) gets on my nerves.
> What solutions have people explored to quiet down a computer system? (actual
> At 05:14 PM 12/19/2000, you wrote:
> >On Tue, Dec 19, 2000 at 12:25:43PM -0500, Dennis wrote:
> > >Am I a thief because my company provides value added solutions without
> > >source to our enhancements on a freebsd platform? If you are insulted that
> > >other people are using your work without
Okay Wes, This is your original message.
You state:
"This is exactly the sort of problem we need to solve..."
In the context of this message I must assume that since
the subject is SSH, then you are referring to SSH.
If not, there is nothing in the message that would
lead me to believe o
On 26 Dec, Mike Smith wrote:
>> If it is FUD as you claim, then the call should be made
>> by the SO. This would seem to be prudent policy.
>
> Jesse, Kris *is* the Security Officer.
>
> Now, please let this thread die.
>
Mike,
You and I don't often agree, but this time is worth noting.
I
On 27 Dec 2000, at 19:17, [EMAIL PROTECTED] wrote:
> > the constant noise (whirring fans, hard drives) gets on my
> > nerves.
>
> My screen, keyboard and mouse are on 12 metre extension cables.
> The computer itself (with 3 more fans installed after a heat problem)
> is 2 floors down, under the
> the constant noise (whirring fans, hard drives) gets on my
> nerves.
My screen, keyboard and mouse are on 12 metre extension cables.
The computer itself (with 3 more fans installed after a heat problem)
is 2 floors down, under the stairs. I can't hear those fans :-)
-- TJ
To Unsubscribe: s
On 25 Dec, David O'Brien wrote:
> On Mon, Dec 25, 2000 at 06:34:09PM -0800, Mike Smith wrote:
>> No, in several particulars. "The FreeBSD Project" doesn't change the SSH
>> keys on the FreeBSD.org machines.
>
> Not changed for change sake, but failure to do anything to preserve them.
>
>
>
On 26 Dec, Mark Murray wrote:
>> Which original keys are you talking about?
>
> SSH public server keys. (Sometimes called "server identities").
>
>> Are you saying that the original SSH Public Keys for the servers
>> were always sent in the clear, without PGP signature or anything?
>
> David
On 26 Dec, Wes Peters wrote:
> [EMAIL PROTECTED] wrote:
>>
>> On 25 Dec, David O'Brien wrote:
>> > On Fri, Dec 22, 2000 at 11:28:07PM -0800, Kris Kennaway wrote:
>> >> Incorrect..the problems with SSH come down to flaws in the human
>> >> operator who ignore the warnings SSH gives them, and tel
I came up with a very similar solution independently (although I chose a
"reserved" partition number). You may also wish to (I did) patch boot0 for
the cosmetic fix. It is possible to rescue a 165'd [ATX] series thinkpad
by booting an install floppy without an installed HD and hot-inserting the
H
On 27 Dec 2000, at 11:25, Jack Rusher wrote:
> > At present the files are created through procmail like this:
> >
> > |/usr/bin/perl $HOME/process_cvs_mail.pl > ~/msgs/$FILE
>
> ...this fragment tells me that you are in control of the process of
> creating these files.
That is correct.
> Th
On 27 Dec 2000, at 19:56, Peter Pentchev wrote:
> On Wed, Dec 27, 2000 at 09:16:34AM -0800, Alfred Perlstein wrote:
> > * Dan Langille <[EMAIL PROTECTED]> [001226 23:50] wrote:
> > >
> > > My idea is to have a daemon, or something resembling one, sitting on
> > > the box watching the directory.
Tekrar sizlere mail atabilmek gercekten güzel
Sitemiz hemen hemen hergün muntazam olarak yenilenmektedir.
Sitemize girdiðinizde göreceðiniz en büyük yenilik
site tasarýmýmýzýn tamaen deðiþtiðidir. Gerçekten çok güzel olduðuna inandýðýmýz bir
tasarýmla karþýnýzdayýz.
Kendi serverýmýza turkçe ve y
On 27 Dec 2000, at 12:53, Peter Pentchev wrote:
> Something like..
> | /usr/bin/perl $HOME/process.pl > ~/msgs/$FILE.tmp && \
> mv ~/msgs/$FILE.tmp ~/msgs/$FILE.cvs
Thanks for that. It's helped me solve a procmail problem I was having.
The files were 600 instead of 640, so I did this:
|/us
On Wed, Dec 27, 2000 at 11:44:34AM -0500, Dennis wrote:
>>Then again, I may decide not to do it: My latest port submission has been
>>sitting in the GNATS database for months, so why bother submitting more
>>when nobody cares anyway?
>
>Welcome to the Animal Farm THIS was my point about the Fr
On Dec 27, Renaud Waldura wrote:
> I've got that FreeBSD gateway in a corner at my house, it works fine & dandy
> but the constant noise (whirring fans, hard drives) gets on my nerves.
>
> What solutions have people explored to quiet down a computer system? (actual
> experience will be preferred
In message <463.977951088@critter>, Poul-Henning Kamp writes:
>
>>I've also run in a production machine where the edict was there shall
>>be no fans with big honkin heat sinks (like 9inch long 2inch high fins
>>running the length of the unit). But that was a fairly custom design
>>and would likel
>I've also run in a production machine where the edict was there shall
>be no fans with big honkin heat sinks (like 9inch long 2inch high fins
>running the length of the unit). But that was a fairly custom design
>and would likely be too expensive for the normal user (we also had to
>underclock
In message <005801c07037$47ae6ea0$[EMAIL PROTECTED]> "Renaud Waldura" writes:
: I've got that FreeBSD gateway in a corner at my house, it works fine & dandy
: but the constant noise (whirring fans, hard drives) gets on my nerves.
:
: What solutions have people explored to quiet down a computer sy
In message <[EMAIL PROTECTED]> Andreas Brodmann writes:
: The pccardd is running. Does anyone know what it could be
: or what I have to do to get any output from pccardd (even
: if it was just saying "i don't know the card you inserted").
Interesting. You should at least get a card inserted mess
>> What solutions have people explored to quiet down a computer
>> system? (actual
>> experience will be preferred over wild speculations).
I ran a totally noiseless Xterm for about a 18 months:
A P5/133 with the CPU fan running on 7V (12V - 5V = 7V)
which made it rotate fast e
I know your pain. At home I have a good sized collection of hardware and the
noise level in my office was getting unbearably high. I used to have the mp3
player (xmms) turned up loud enough that I couldn't hear the doorbell ring.
I had been drooling over the G4 cube just because they're silent and
On Wed, 27 Dec 2000, someone on freebsd-hackers wrote:
> > They dont want your stinking binary contributions. Get used to it.
>
> Not suprisingly you're both wrong. Many binary-only ports exist
> in the FreeBSD ports tree.
World is not black and white.
There are binary ports (for example netsc
I was about to write up a group of suggestions that include the notion
that you could use kqueue to watch the directory's vnode, you could use
Erez's stackable file system code to pass all file creates through a
filter, use lpd's spooling mechanism to treat the incoming directory
like a print q
On Wed, Dec 27, 2000 at 11:44:34AM -0500, Dennis wrote:
> At 05:14 PM 12/19/2000, you wrote:
> >On Tue, Dec 19, 2000 at 12:25:43PM -0500, Dennis wrote:
> > >Am I a thief because my company provides value added solutions without
> > >source to our enhancements on a freebsd platform? If you are insu
I've got that FreeBSD gateway in a corner at my house, it works fine & dandy
but the constant noise (whirring fans, hard drives) gets on my nerves.
What solutions have people explored to quiet down a computer system? (actual
experience will be preferred over wild speculations). I'm already aware
On Wed, Dec 27, 2000 at 09:16:34AM -0800, Alfred Perlstein wrote:
> * Dan Langille <[EMAIL PROTECTED]> [001226 23:50] wrote:
> >
> > My idea is to have a daemon, or something resembling one, sitting on
> > the box watching the directory. When a new file appears, it starts a perl
> > script. T
* Dan Langille <[EMAIL PROTECTED]> [001226 23:50] wrote:
>
> My idea is to have a daemon, or something resembling one, sitting on
> the box watching the directory. When a new file appears, it starts a perl
> script. This perl script is beyound the scope of my question, but it
> processes al
At 05:14 PM 12/19/2000, you wrote:
>On Tue, Dec 19, 2000 at 12:25:43PM -0500, Dennis wrote:
> >Am I a thief because my company provides value added solutions without
> >source to our enhancements on a freebsd platform? If you are insulted that
> >other people are using your work without paying for
At 01:16 PM 12/19/2000, John Baldwin wrote:
> >>We have a saying in Denmark, which I'm sure exist in as many forms
> >>as there are languages in the world:
> >>
> >>"A thief belive everybody steals."
> >>
> >>Dennis, considering the recorded history of your arguments in our
> >>mailing list a
Dear All,
What you'd really want is some kind of message queueing system for this kind
of work. What message queueing systems are (non-commercially) available on
UNIX systems?
Kees Jan
You are only young once,
but you can stay immatur
> > > unlock the file
> > >
> > > The cleaner you mentioned: run it every 15 minutes, compare the
> > > date/time on the lockfile, if more than 15 minutes old, grab the PID,
> > > and kill the job, remove the lock.
> >
> > Correct.
Actually, you can make it a lot better:
If the lockfile exi
In message <[EMAIL PROTECTED]>, "M
atthew C. Forman" $B$5$s$$$o$/(B:
>
>First, sorry this is a bit long; I probably should have split it up, but
>when I get going... Y'Know...
>
>I've done some work on a driver for the SMBus functions of the AMD 756
>chip found on K7-based motherboards, based on
Just a comment on this...
I used to work for a pretty big Unix OS vendor in the operating systems
development group. 90% of the bug fixes I applied were never found by
the QA group (otherwise they would have been fixed long before I ever
worked there :-). Where they really found problems were c
>
> First, sorry this is a bit long; I probably should have split it up, but
> when I get going... Y'Know...
Size is not a problem.
> My newbus efforts are not going too well; specifically I'm having a hard
> time with bus_alloc_resource, which refuses to allocate any I/O space for
> me. I've t
First, sorry this is a bit long; I probably should have split it up, but
when I get going... Y'Know...
I've done some work on a driver for the SMBus functions of the AMD 756
chip found on K7-based motherboards, based on alpm.c from -CURRENT. This
works nicely on my system (Gigabyte GA7IXE-4 with
On Wed, Dec 27, 2000 at 01:18:28PM +0200, Peter Pentchev wrote:
[snip..]
> closedir(D);
> foreach $fname (@files) {
> next if (($fname eq ".") || ($fname eq ".."));
> # more filename vailidity checks go here
^ validity
On Wed, Dec 27, 2000 at 11:09:40AM +, Mike Bristow wrote:
> On Wed, Dec 27, 2000 at 12:53:37PM +0200, Peter Pentchev wrote:
> > Btw, anybody reading this discussion - I tried the attached script with
> > #!/usr/bin/perl -wT, and Perl died on the unlink() - "unsafe dependency".
> > What gives?
On Wed, Dec 27, 2000 at 12:53:37PM +0200, Peter Pentchev wrote:
> Btw, anybody reading this discussion - I tried the attached script with
> #!/usr/bin/perl -wT, and Perl died on the unlink() - "unsafe dependency".
> What gives?
$ man perldiag
[snip]
Insecure dependency in %s
(F)
On 27 Dec 2000, at 10:11, Mark Murray wrote:
> > Any ideas on how to do this? Any suggestions on the process?
>
> Simple lock (like flock(3)) in the perl script. Lock some ${FILE},
> and if you can't get the lock, die. The file should contain the PID
> of the process that holds the lock, so tha
On Wed, Dec 27, 2000 at 11:17:47PM +1300, Dan Langille wrote:
> On 27 Dec 2000, at 12:11, Peter Pentchev wrote:
>
> > I would do that (and have done it in several projects) using opendir()
> > and readdir(). Open the directory, read entry by entry, when you find
> > a file you want, process it a
> On 27 Dec 2000, at 10:11, Mark Murray wrote:
> >
> > [use flock(2)]
>
> But what part of the solution does flock solve?
It solves the problem of finding out whether the Perl script is
already running, but as I understood the original posting, this isn't
what you were asking. See below.
> I'
On 27 Dec 2000, at 12:11, Peter Pentchev wrote:
> I would do that (and have done it in several projects) using opendir()
> and readdir(). Open the directory, read entry by entry, when you find
> a file you want, process it and unlink() it. Get to the end of the dir,
> sleep, repeat.
Thanks for
On Wed, Dec 27, 2000 at 08:49:51PM +1300, Dan Langille wrote:
> FreshPorts2 will have a new processing strategy for incoming
> messages. Each message will be in a separate file in a predetermined
> directory. As each file arrives, it is processed by a perl script. I want
> only one instance o
On Tue, Dec 26, 2000 at 07:45:36AM -0800, [EMAIL PROTECTED] wrote:
>
> If I read what you are saying, and please correct me if I'm wrong,
> you are saying "the original keys were never .".
> Which original keys are you talking about?
> Are you saying that the original SSH Public Keys for the
On 27 Dec 2000, at 10:11, Mark Murray wrote:
> > Any ideas on how to do this? Any suggestions on the process?
>
> Simple lock (like flock(3)) in the perl script. Lock some ${FILE},
> and if you can't get the lock, die. The file should contain the PID
> of the process that holds the lock, so tha
> Any ideas on how to do this? Any suggestions on the process?
Simple lock (like flock(3)) in the perl script. Lock some ${FILE},
and if you can't get the lock, die. The file should contain the PID
of the process that holds the lock, so that a cleanerd can kill
stuck processes, or so that the lo
50 matches
Mail list logo
