I said I'd drop it, but apparently there are people that don't
understand the dinosaur mentality of certain organizations such as
DOD, DISA/DECC, OSD, DARPA, USA, USN, USAF, and USMC.
If it's not in the base setup, on a production box, you can't use it.
*Huh* This policy must have been
On Sun, Aug 12, 2001 at 10:29:53AM -0400, Daniel Eischen wrote:
sigprocmask() behaves the same as pthread_sigmask(). pthread_sigmask()
needs to obtain the current thread. In obtaining the current thread,
the threads library must be initialized. In initializing the threads
library malloc()
Jason Evans wrote:
I had the same problems, and took my KVM switch apart, expecting to find
the chips reversed. They were in fact installed correctly, so at least in
my case, the problem exists regardless. If I'm careful to have the KVM
switch on the same channel as a booting machine, and
Nate Williams wrote:
Umm, Terry. There was no 'free' tar. Back in the 386BSD days, when we
were looking for a free tar, I contacted Andy Tanenbaum (of Minix) and
got permission to use it, since we didn't have one. However, it was
voted down as being 'too simple', so we opted for the GNU
The Anarcat wrote:
[Foul-mouthed anti-gummint drivel deleted]
Actually, it is up to us to resolve this. I don't think you understand how
DOD operates. The vendor makes the changes, not DOD. Not the admin.
And FreeBSD is the *vendor*? I don't think so. At least I don't hope so.
If I'm
Steve O'Hara-Smith wrote:
On Sun, 12 Aug 2001 17:04:01 -0500
Jim Bryant [EMAIL PROTECTED] wrote:
JB I said I'd drop it, but apparently there are people that don't understand the
dinosaur mentality of certain organizations such as
JB DOD, DISA/DECC, OSD, DARPA, USA, USN, USAF, and USMC.
Mike Smith wrote:
Here is the _precise_ problem with older firmware:
The Belkin KVM switch uses the on-off-on or off-on-off
of this LED to signal a port change character is coming next,
and times out the port change request only after a little
while.
Ah, so the problem is actually
John Baldwin wrote:
1) Implement probing/detection for PS/2 keyboards post-boot. You can hack
this by having the atkbd0 driver always attach to IRQ 1, but not create and
export a kbd0 syscons keyboard driver until it gets an interrupt event from
the keyboard.
This would be pretty easy.
2)
John Baldwin wrote:
My suggestion for a probe in this case would be to set up
a different handler for the reset signal, and then ask the
keyboard to send the reset signal. If it does, then there
is a keyboard present.
Yeah, and resetting the controller works fine on machines that
Warner Losh wrote:
In message [EMAIL PROTECTED] Joe Kelsey writes:
: I also second Terry's comment about 0x800. There is no reason to add
: yet more driver flags in order to do the right thing. The do the
: right thing case should always be default and a flag (sysctl variable,
: etc)
Joe Kelsey wrote:
[ ... 0x8000 ... ]
Again, all I am asking is for someone to explain why they make a design
decision. The comment in the psm.c file about a hack is extremely
unhelpful. Why did the coder think it was a hack solution? What were
the pros and cons that went into that
Gordon Tetlow wrote:
This is such a great example of how tone can come across poorly in a text
medium. I doubt (hope) that Joe didn't mean to come across as that. But
tone in email is so often inferred based on the readers own moods, that
phrasing email becomes much more important so as to
Chris Dillon wrote:
Occasionally I'll have mouse sync problems when I switch between
FreeBSD and NT when the NT box has had difference mice (wheel vs.
non-wheel MS mice, apparently) used on it via the dual-user KVM
switch. NT seems to handle that case fairly well by resetting the
PS/2 port
Cahnges made between Friday morning and today may have broken make release.
I just got the following error:
/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/
cvs/cvs/../../../../contrib/cvs/diff -DHAVE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DE
NCRYPTION-c
After importing a new cvs (located at src/gnu/usr.bin/cvs),
src/gnu/usr.bin/Makefile was modified not to compile cvs, since cvs is
temporary broken for bulid.
However, there is yet another makefile which builds cvs also --
src/kerberosIV/Makefile. Since this file is left unchanged, we cannot
With source moved back to /usr/src, this hasn't yet reproduced.
On Thu, 9 Aug 2001, David O'Brien wrote:
On Thu, Aug 09, 2001 at 09:02:50AM -0700, Matthew Jacob wrote:
I put a fresh clean source tree off not in /usr/src- it seems to die on the
alpha in binutils. Anyone seen this?
Can
On Sat, Aug 11, 2001 at 11:51:18AM -0700, Terry Lambert wrote:
[...]
If this is really a goal, then you should redesign the
process and not put more and more tools into the build tools
category to work around these problems.
Take a look at sysinstall/Makefile to have a better idea
On Fri, Aug 10, 2001 at 11:54:27AM -0700, John Baldwin wrote:
On 10-Aug-01 Ruslan Ermilov wrote:
On Fri, Aug 10, 2001 at 10:04:01AM -0700, Mark Peek wrote:
At 7:14 PM +0300 8/10/01, Ruslan Ermilov wrote:
On Fri, Aug 10, 2001 at 08:38:21AM -0700, Mark Peek wrote:
At 5:37 PM +0300
On 13-Aug-01 Ruslan Ermilov wrote:
On Fri, Aug 10, 2001 at 11:54:27AM -0700, John Baldwin wrote:
On 10-Aug-01 Ruslan Ermilov wrote:
On Fri, Aug 10, 2001 at 10:04:01AM -0700, Mark Peek wrote:
At 7:14 PM +0300 8/10/01, Ruslan Ermilov wrote:
On Fri, Aug 10, 2001 at 08:38:21AM -0700, Mark
On 13-Aug-01 Terry Lambert wrote:
John Baldwin wrote:
More ideally, the FreeBSD box would detect whether or not
the video card had been disabled, and use _that_ to decide
whether or not to use a keyboard. It would become the job
of the video driver -- be it a regular driver, or be it
OK already. I am sick and tired of this documentation discussion and it
appears that it is too hot of a topic for this list.
However, I have one last comment to make. TWO people have written to me
and said that the reason THEY write documentation in their day jobs is
that they get PAID for it.
On 11-Aug-01 Alexander Langer wrote:
Hi!
Under high network load together with high ata disk i/o, I can
easily reprocude this trap. I think it happens when a fork() is done
(I always got it when starting new programs...).
E. I used to get this on my test SMP alpha machine a lot with
On Mon, Aug 13, 2001 at 04:13:52AM -0500, Jim Bryant wrote:
from what i've read here, not many undrestand the actual mindset of the
military when it comes to computing.
the closest would be the guy who mentioned that since ports are on the
CD's that they should be acceptable, this is
DOD/DFAS, as well as DOD/DISA.
I find it amazing that the CIA has a more lax policy than DFAS and DISA.
David O'Brien wrote:
On Mon, Aug 13, 2001 at 04:13:52AM -0500, Jim Bryant wrote:
from what i've read here, not many undrestand the actual mindset of the
military when it comes to
On Mon, Aug 13, 2001 at 07:23:26PM -0500, Jim Bryant wrote:
DOD/DFAS, as well as DOD/DISA.
I find it amazing that the CIA has a more lax policy than DFAS and DISA.
The only person I've ever talked to from the CIA was in charge of network
security to some degree, and according to him they
Joseph Mallett wrote:
On Mon, Aug 13, 2001 at 07:23:26PM -0500, Jim Bryant wrote:
DOD/DFAS, as well as DOD/DISA.
I find it amazing that the CIA has a more lax policy than DFAS and DISA.
The only person I've ever talked to from the CIA was in charge of network
security to some degree,
On Mon, Aug 13, 2001 at 06:01:55PM -0400, Garrett Wollman wrote:
On Mon, 13 Aug 2001 14:57:54 -0700, David O'Brien [EMAIL PROTECTED] said:
I should have mentioned this.
/tmp is on /, which is UFS, mounted noatime and with softupdates enabled.
Plenty of freespace:/dev/da0s1a 1.3G 843M
On Mon, Aug 13, 2001 at 11:23:12AM -0700, Joe Kelsey wrote:
TWO people have written to me and said that the reason THEY write
documentation in their day jobs is that they get PAID for it. So,
excuse me! I guess real programmers only write documentation when they
are PAID!
Yes!
Obviously,
Some of us try documant our stuff so that others can use it
and because we feel that it's better to do something right
than shoddily.
On Mon, 13 Aug 2001, David O'Brien wrote:
On Mon, Aug 13, 2001 at 11:23:12AM -0700, Joe Kelsey wrote:
TWO people have written to me and said that the reason
On Fri, Aug 10, 2001 at 08:23:00PM +0300, Ruslan Ermilov wrote:
Your solution does not work. You're creating binary files in HOST
format during the build phase and expecting things such as alignment
and endianness to be the same as the TARGET format. Unless the tools
are built to
Hello?? Those that have committed to /sys in the past 1.5mo, awake?
I am continuing to suffer thru what appears to be inode deadlocks where
the resulting race-to-the-root soon locks everything up solid. Tried to
figure out how to reproduce it on demand. All I can characterize is the
file
I should have mentioned this.
/tmp is on /, which is UFS, mounted noatime and with softupdates enabled.
Plenty of freespace:/dev/da0s1a 1.3G 843M 361M 70% /
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, 10 Aug 2001 23:06:49 -0400
David Hill [EMAIL PROTECTED] wrote:
Hello -
Here is my patch to make write.c work when WARNS=2. I also did some code
cleanup
1. Constify
2. Changed a strncpy to strlcpy
3. Changed (S_IWRITE 3) to S_IWGRP
4. Cleaned up 2
33 matches
Mail list logo
