On Sat, Aug 11, 2001 at 01:04:07PM -0700, John Polstra wrote:
>
> I have no argument about the keyboard probes. I just want to add
> that in the case of the Belkin OmniView, it should be noted that
> Belkin shipped a bunch of them with a couple of EPROM chips swapped
> accidentally. There's a p
In article <[EMAIL PROTECTED]>,
Jason Evans <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 11, 2001 at 01:04:07PM -0700, John Polstra wrote:
> >
> > I just want to add that in the case of the Belkin OmniView, it
> > should be noted that Belkin shipped a bunch of them with a couple
> > of EPROM chips s
On Sun, Aug 12, 2001 at 02:35:22PM -0700, John Polstra wrote:
>
> Maybe they swapped the labels on the chips too. :-)
Well, it apparently doesn't fry anything to have the chips reversed, so
maybe I should try swapping them just to make sure. =)
Jason
To Unsubscribe: send mail to [EMAIL PROTECT
On Sun, 12 Aug 2001 10:16:47 -0600, Nate Williams wrote:
>> > > :Finally, most keyboard/mouse/monitor switches don't work with
>> > > :FreeBSD;
>> >
>> > This is actually not true. I'd doubt that you've even tried many of them.
>>
>> Boy, you are on one about me...
>>
>> I have tried 5 switch
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. Everything must
be kept in it's ORIGINA
On Sat, Aug 11, 2001 at 05:16:28PM +0930, Daniel O'Connor wrote:
> I recently had a chance to buildworld on new -stable and -current
> machines with similar spec'd HW..
> The -current build was _slow_ ->
> 10756.71 real 2026.00 user 7814.64 sys
> vs -stable ->
> 2332.03 real
On Sat, Aug 11, 2001 at 05:16:28PM +0930, Daniel O'Connor wrote:
> I recently had a chance to buildworld on new -stable and -current machines with
> similar spec'd HW..
> The -current build was _slow_ ->
> 10756.71 real 2026.00 user 7814.64 sys
> vs -stable ->
> 2332.03 real
On Sun, Aug 12, 2001 at 08:38:56PM +0200, Bernd Walter wrote:
> Yes the sun packages installs into /bin:
> ticso@cicely22> uname -a
> SunOS cicely22 5.8 Generic_108528-01 sun4m sparc SUNW,SPARCclassic
> ticso@cicely22> which bash
> /bin/bash
> ticso@cicely22> file /bin/bash
> /bin/bash: ELF 3
> > # Bash has a license which precludes its inclusion as part
> > # of the base system.
> >
> > [Not that I favor more shells on the root file system, but anyway:]
> > What about gcc and grep? Does the license differ or are these not regarded
> > being part of the base system?
>
> We would get
On Sun, 12 Aug 2001, Julian Elischer wrote:
...
> my guess is that you are
Lets see...
Attached is a first shot to get /compat/linux/usr/bin/ipcs -s working.
I extended sem.h for SEM_STAT and gave it a special handling
in __semctl() to accept a index number.
Please review and commmit if accep
> I've seen the 'have to be on the machine while booting' behavior
> using a Belkin Omniview Pro switch, which oddly, wasn't a problem
> with their OmniCube switch, at least not with my machines. Windows
> had as much, or more problems with not having the console on the
> booting machine as fbsd t
As a preface to this whole thing, I find it higly amusing that you are
sending this mail from a Linux box. Of course, for that matter, so am I.
(I'm planning on changing that soon.)
On Sun, 12 Aug 2001, Jim Bryant wrote:
> I said I'd drop it, but apparently there are people that don't
> understa
> 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 a design def
On 12-Aug-01 Joe Kelsey wrote:
> Thank you very much for the clear and cogent explanation of your
> philosophy of the psm code. Could I suggest that you copy the
> aforementioned e-mail directly into the psm.c file for everyone to see
> in posterity?
>
> Also, I have a fundamental problem with
On 12-Aug-01 Terry Lambert wrote:
> Mike Smith wrote:
>>
>> > :Finally, most keyboard/mouse/monitor switches don't work with
>> > :FreeBSD;
>>
>> This is actually not true. I'd doubt that you've even tried many of them.
*sigh*
It seems no one has investigated why we probe keyboards at all.
On 12-Aug-01 Terry Lambert wrote:
> The FreeBSD keyboard detection is another matter; FreeBSD
> will assume that there is no keyboard, and try to "helpfully"
> drop you into serial console mode. Some of this _used_ to
> be mitigated by checking for the "extended keyboard bit" in
> the "keyboard
On Sun, Aug 12, 2001 at 04:54:08PM -0700, Gordon Tetlow wrote:
> > FreeBSD is getting military contracts now. We need to think ahead to
> > the needs of a whole new class of admin and user, and they are in
> > highly restrictive environments that preclude `mv /usr/local/bin/*sh
> > /bin`.
>
> An
On 13-Aug-01 John Baldwin wrote:
> runtime interface (IMO). I realize the user side of the attributes is up for
> debate, but working on solving this problem is much more problem than
> complaining that people aren't giving you the free gift you want.
s/problem/productive/2
--
John Baldwin <
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) should be used for those
Built new sources yesterday and now I'm getting the following when i su:
pam_rootok: pam_sm_authenticate: Refused; not superuser
My etc files are current and it doesn't affect login, but I thought I would
pass it along.
Beech
--
Micro$oft: "Where can we make you go today?"
---
Gordon Tetlow wrote:
> As a preface to this whole thing, I find it higly amusing that you are
> sending this mail from a Linux box. Of course, for that matter, so am I.
> (I'm planning on changing that soon.)
Excuse me?
FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #18: Fri Aug 10 16
Yeah, I've been seeing that also with recent -CURRENT. /etc is in sync
with /usr/src/etc. Doesn't seem to prevent normal functioning, but isn't
encouraging. Looks like rootok needs to not whine when not running as
root?
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAI
Warner Losh writes:
> 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,
[This email contains coarse language due to the absurdity of the thread
level we're in. My apologies to those offended. Also, my apologies to
the author of the original mail. You have triggered very sensitive areas
of my mind. :)]
[This probably belongs to -chat, -flame (we should create that one
In message <[EMAIL PROTECTED]> Joe Kelsey writes:
: Warner Losh writes:
: > 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 thi
On Monday 13 August 2001 3:08 am, The Anarcat wrote:
> [This email contains coarse language due to the absurdity of the thread
> level we're in. My apologies to those offended. Also, my apologies to
> the author of the original mail. You have triggered very sensitive areas
> of my mind. :)]
Swea
OK, so we have beaten the psm and keyboard code to death. The entire
point that I have been trying to make in this discussion is that it is
imperative to document design decisions somewhere that is likely to
survive changes in maintainer.
I have been working as an administrator and programmer fo
On Sun, 12 Aug 2001, Warner Losh wrote:
> A word about tone. If you were to get as in my face about, say,
> pccard, as you about the psm driver, I'd certainly be ill inclined to
> provide you with what you want.
>
> Good Tone:
> Say Warner, why do you bother turning off the power after
>
Warner Losh writes:
> Good Tone:
> Say Warner, why do you bother turning off the power after
> you suspend a socket. Shouldn't the power routines take care
> of that? Is there something subtle that's going on? Maybe a
> comment is in order?
>
> Bad Tone:
> Plea
On Sun, Aug 12, 2001 at 07:51:05PM -0700, Joe Kelsey wrote:
> OK, so we have beaten the psm and keyboard code to death. The entire
> point that I have been trying to make in this discussion is that it is
> imperative to document design decisions somewhere that is likely to
> survive changes in ma
Not to be a pain, but can you wrap lines at a more standard 74 columns as
opposed to whatever you are currently wrapping them at? Thanks.
On Sun, 12 Aug 2001, Jim Bryant wrote:
> Gordon Tetlow wrote:
>
> > As a preface to this whole thing, I find it higly amusing that you are
> > sending this ma
On Sun, 12 Aug 2001, Steve Kargl wrote:
> On Sun, Aug 12, 2001 at 04:54:08PM -0700, Gordon Tetlow wrote:
> > > FreeBSD is getting military contracts now. We need to think ahead to
> > > the needs of a whole new class of admin and user, and they are in
> > > highly restrictive environments that p
On Sun, Aug 12, 2001 at 09:20:59PM -0700, Gordon Tetlow wrote:
> After seeing that grep is a GNU tool, I'm almost tempted to try writing a
> BSD-style grep for the fun/exercise of it.
Rather than do that, continue the development of
/usr/ports/textproc/freegrep, which was started for exactly the
On Sun, Aug 12, 2001 at 08:15:15PM -0500, Jim Bryant wrote:
> 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.
Sigh. If an admin cannot handle /bin/sh long enough to get /usr mounted,
they have n
On Sun, Aug 12, 2001 at 09:20:37PM -0700, Gordon Tetlow wrote:
> After seeing that grep is a GNU tool, I'm almost tempted to try writing a
> BSD-style grep for the fun/exercise of it.
lizzy:/usr/ports/textproc/freegrep# cat pkg-descr
This is an implementation of grep(1) intended as a replacemen
On Sun, Aug 12, 2001 at 10:08:40PM -0400, The Anarcat wrote:
> And FreeBSD is the *vendor*? I don't think so. At least I don't hope so.
Actually we *are*. Seen those ISO's up on ftp.freebsd.org??
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Sat, Aug 11, 2001 at 05:25:42PM -0700, Terry Lambert wrote:
> It's like trying to find something in hierachically organized
> "GNU info" documentation: redundancy is useful, and try to
> find "__PRETTY_FUNCTION__" in the "gcc" documentation, when
> you need to read the man page carefully to fin
On Sat, 11 Aug 2001, Terry Lambert wrote:
> Finally, most keyboard/mouse/monitor switches don't work with
> FreeBSD; for example, the Belkin console extender that uses the
> ethernet cable doesn't work at all (it's the best one out there),
I'm using a Cybex KVM-over-CAT5 extender with a cheap 4-
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.
JB>
JB> If it's not in the ba
> 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 b
40 matches
Mail list logo
