On Mon, 17 May 1999 09:58:10 +0100, Doug Rabson wrote:
> I don't think LINT in current mentions the new debug flag.
Are you talking about this:
# The `makeoptions' parameter allows variables to be passed to the
# generated Makefile in the build area. DEBUG happens to be magic.
[...]
#makeopti
On Tuesday, 18 May 1999 at 9:00:49 +0200, Sheldon Hearn wrote:
>
>
> On Mon, 17 May 1999 09:58:10 +0100, Doug Rabson wrote:
>
>> I don't think LINT in current mentions the new debug flag.
>
> Are you talking about this:
>
> # The `makeoptions' parameter allows variables to be passed to the
> # gen
On Tue, 18 May 1999 16:34:55 +0930, Greg Lehey wrote:
> In fact, there's also a 0x80, which you need to set (along with 0x10,
> it appears) to run remote debugging. I'm guessing a bit at this,
> since I haven't had time to look at the code, but 0x90 works for me.
This is something new since ab
Hi hackers,
I'm pleased to participate in such cool project. Is anybody kind
enough to tell me how to run this program while the FreeBSD box is
idle?
Thanks in advance,
--
Kazukiyo Ueda
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the me
* David E. Cross
| I dug through the archives and found peopel with similiar problems to
| what I am experiencing, but I didn't find any answers that have worked
| for me. Here are the problem I am having:
|
[..]
I've experienced this problem too, and have found a solution:
(Should have posted
* sth...@nethelp.no
| > 1: The built-in SCSI ROM is v2.01, there was mention of BIOS 1008 including
| >2.11. I applied the 1008 flash and I am still v2.01 (I don't know if
| >this matters at all)
| At least for the P2B-S, you need 1008B, not 1008. The file I got from
I haven't tested 1.0
On Tue, 18 May 1999, Greg Lehey wrote:
> In fact, there's also a 0x80, which you need to set (along with 0x10,
> it appears) to run remote debugging. I'm guessing a bit at this,
> since I haven't had time to look at the code, but 0x90 works for me.
> Doug?
I used to use 0x50 but now 0x80 works f
My experience is that most modern (and many older) PC NIC's are
able to change their MAC address. The question really is, how
should I do this from within FreeBSD.
Is there a standard entry into the drivers to do this?
If you are wondering why I want to do this, I am looking at hot
standby and
On Tuesday, 18 May 1999 at 9:17:03 +0200, Sheldon Hearn wrote:
>
> On Tue, 18 May 1999 16:34:55 +0930, Greg Lehey wrote:
>> In fact, there's also a 0x80, which you need to set (along with 0x10,
>> it appears) to run remote debugging. I'm guessing a bit at this,
>> since I haven't had time to look
cro...@cs.rpi.edu (David E. Cross) writes:
> One of our users way able to reliably crash an NFS server 3 times today.
> I have since copied his program and have reliably crashed a seperate and
> unloaded machine with the exact same panic, "lockmgr: locking against
> myself". I check the recent DG
On Tue, 18 May 1999, Ueda, Kazukiyo wrote:
> I'm pleased to participate in such cool project. Is anybody kind
> enough to tell me how to run this program while the FreeBSD box is
> idle?
Install the astro/setiathome port. One thing I've been meaning to look at
though is that it seems to run it a
Hi,
At 16:48 18/05/99 +0900, Ueda, Kazukiyo wrote:
>I'm pleased to participate in such cool project. Is anybody kind
>enough to tell me how to run this program while the FreeBSD box is
>idle?
man nice
--
Bob Bishop +44 118 977 4017
r...@gid.co.uk fax +44 118 989 4254 (
speaking of Ensoniq...
Is anyone working on ES1371 drivers?
--
Steve Rubin - s...@tch.org - http://www.tch.org/~ser/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
At 02:36 -0700 05/18/99, Steve Rubin wrote:
> Is anyone working on ES1371 drivers?
Yes. I'm working on ES1371 drivers with SB PCI128.
--
KEK, High Energy Accelerator Research Organization
Shin-ichi YOSHIMOTO
To Unsubscribe: send mail to m
Marc Slemko wrote:
>
> In any case, it makes sense, and is a reasonable alternative.
> Unfortunately it isn't portable, but that's life.
And linux /proc is portable?
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org
"If at first you don't succeed, sky
On 18-May-99 Shin-ichi YOSHIMOTO wrote:
> > Is anyone working on ES1371 drivers?
> Yes. I'm working on ES1371 drivers with SB PCI128.
Hmm.. I have access to an SB Ensoniq Audio PCI which has the ES1371 on it. I can
test patches etc. The machine is running 3.2-BETA.
---
Daniel O'Connor software
On Mon, 17 May 1999, Marc Slemko wrote:
> The reasoning: reading from kernel data structures without any locking has
> obvious race conditions.
[...]
> This is why netstat will often bail out in the middle with kvm errors on a
> busy machine with lots of TCP connections, especially if you slow
At 19:31 +0930 05/18/99, Daniel O'Connor wrote:
> Hmm.. I have access to an SB Ensoniq Audio PCI which has the ES1371 on it.
I also tried an Ensoniq Audio PCI with the ES1371 at first. But this card
did not work. Then I tried a CREATIVE SB PCI128 which has the CREATIVE 5507
on it. It was working f
>The premise: libkvm is fatally flawed by design, and fixing it is not an
>easy proposition.
>
>The reasoning: reading from kernel data structures without any locking has
>obvious race conditions.
>
>This is why any identd that uses libkvm sucks and gets into loops all the
>time, etc.
>
>This is
Last night I switched from 3.1-STABLE to 4.0-CURRENT. Everything
went great except for one spot.
I have two ethernet cards in this machine. Both use the 'ed'
driver. One is PCI the other is ISA.
In the 3.1 machine I had a line in the config that said:
device ed0 at isa? port 0x280 net irq 10 io
On Tue, 18 May 1999, Kazutaka YOKOTA wrote:
> > I think you just nailed the problem here. It requires a prohibitive
> >amount of effort to support modex video modes given the return. What I am
> >thinking about is removing the 320x240 mode (since it is impossibly
> >difficult to deal with)...no o
(Already posted to freebsd-net)
I'm currently doing a FreeBSD installation from network, a bit like
jumpstart.
So,I need to find a freeware to netboot a freebsd kernel with 3c905B
Ken Yap from the etherboot site, told me about a special etherboot that
freebsd people had done to make etherboot boo
>I'm currently doing a FreeBSD installation from network, a bit like
>jumpstart.
>So,I need to find a freeware to netboot a freebsd kernel with 3c905B
>Ken Yap from the etherboot site, told me about a special etherboot that
>freebsd people had done to make etherboot boot freebsd kernel.
>A comple
On Tue, 18 May 1999, Soren Schmidt wrote:
> It seems Kelly Yancey wrote:
> >
> > I admit that they are less common than say 320x240 mode x...but they are
> > linear and don't require any hacking to support from applications which
> > would use graphics modes (unlike the unchained "modex" modes)
>> > > I'm not really sure what practical use there is for using graphics modes
> > >to render text (and hence why character cell sizes for graphics modes
What if FreeBSD ends up supporting mips or sparc? These machines don't
have anything like VGA text modes, and PROM consoles suck.
> > >that
Kris Kennaway wrote:
> On Tue, 18 May 1999, Ueda, Kazukiyo wrote:
>
>> I'm pleased to participate in such cool project. Is anybody kind
>> enough to tell me how to run this program while the FreeBSD box is
>> idle?
>
> Install the astro/setiathome port.
Make sure you have the newest version of
Last night switched from 3.1 to 4.0. Smooth transition. The only
error I've seen is one of my ethernet cards is no longer detected.
In the previous kernel (3.1-STABLE) I had the following config
line:
device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000
When the system booted it would detect
>
> However, this applies to the functionality wherever it is implemented.
> Moving the formatting to the kernel does not change anything.
It "changes" thinks in that it unnecessarily bloats the kernel.
> If you are concerned about the time that it takes to do hostname lookups,
> that time is no
Steven Ames wrote:
>
> Under the 4.0 kernel the PCI card is given ed0 and a message
> is displayed saying ed0 already in use giving next number.
> The isa card is _NEVER_ probed. I don't even get a message
> saying it was probed and not found.
>
> I've tried disabling the pnp controller in the ke
#define quoting(Stefan Bethke)
// Kris Kennaway wrote:
// > On Tue, 18 May 1999, Ueda, Kazukiyo wrote:
// > One thing I've been meaning to look at though is that it seems to run it
// > at niceness 1, which isn't exactly friendly to the other consumers of
// > CPU. You should be able to tweak it e
David Greenman wrote:
>
>Generally we've been moving towards using sysctl for reading kernel data.
> procfs/kernfs is usually the wrong tool for the job in most cases (my
> subjective opinion of course).
And afterwards, if someone really wants it, you could reimplement
procfs using sysctl, ta
Stefan Bethke wrote:
>
> Make sure you have the newest version of the port (for setiathome-1.1).
> Pre-1.1 version don't work anymore. Unfortunatly, the release of 1.1 came
> too late for the 3.2 CDs. Even more unfortunate is the fact that all
> versions (including 1.1) try to send mail by invoki
On Tue, 18 May 1999, Mike Smith wrote:
> >
> > However, this applies to the functionality wherever it is implemented.
> > Moving the formatting to the kernel does not change anything.
>
> It "changes" things in that it unnecessarily bloats the kernel.
I agree. My reference was in relation to the
> Wes Peters wrote:
>
> Steven Ames wrote:
> >
> > Under the 4.0 kernel the PCI card is given ed0 and a message
> > is displayed saying ed0 already in use giving next number.
> > The isa card is _NEVER_ probed. I don't even get a message
> > saying it was probed and not found.
> >
> > I've tried
In the last episode (May 18), Wes Peters said:
> Stefan Bethke wrote:
> > Would you suggest a different default nice level, then, and what
> > should it be?
>
> RTP_PRIO_IDLE of course. See rtprio(2).
>
> > One can easily modifiy ${PREFIX}/etc/rc.d/setiathome.sh to run it
> > -with nice 100, and
On Tue, 18 May 1999, Richard Wackerbarth wrote:
> On Mon, 17 May 1999, Marc Slemko wrote:
>
> > The reasoning: reading from kernel data structures without any locking has
> > obvious race conditions.
> [...]
>
> > This is why netstat will often bail out in the middle with kvm errors on a
> > b
On Tue, 18 May 1999, Greg Lehey wrote:
>
> Kirk committed some stuff a week or two ago. And yes, IIRC it was to
> allow the same serial port to be used for both purposes.
Actually it's to allow DIFFERENT serial ports to be used..
>
> Greg
>
To Unsubscribe: send mail to majord...@freebsd
> It breaks because compat22 is installing _everything_ in
> /usr/lib/compat/aout. We've reproduced this locally - compat22 is
> hosed.
Will fix this. I followed the lead of the "unoffical" compat22 which was
built from libs on Hub.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
> It breaks because compat22 is installing _everything_ in
> /usr/lib/compat/aout. We've reproduced this locally - compat22 is
> hosed.
I *knew* this was going to bite us in the ass. I brought it up at E-day
time... and was ignored.
Some body please decide where bits should live. *IF* you up
On Mon, 17 May 1999 23:40:03 +0200
Andreas Braukmann wrote:
> ... and the Connectix Virtual PC is available for FreeBSD?
No, it's a MacOS program.
> that's for sure, ... from a theoretically point of view at least.
> But I suppose, that the virtual machine approach would lead to more
> pe
Could you guys please give yer own opinions on that?
I will compile some of the better arguments and resend them to the Posix
revision list...
-FW: <990518120639.zm1...@tamarix.rdg.opengroup.org>-
Date: Tue, 18 May 1999 13:06:40 +0100
From: Andrew Josey
To: austin-gr...@opengroup.org
Sub
Dan Nelson wrote:
>
> Problem is that idprio isn't safe. I used to idprio the rc5client, but
> within a day or do the machine would lock up. Rc5client would get a
> lock on the root of the filesystem at idprio, and if there was another
> process running at 100% CPU, rc5client would never get a c
:Dan Nelson wrote:
:>
:> Problem is that idprio isn't safe. I used to idprio the rc5client, but
:> within a day or do the machine would lock up. Rc5client would get a
:> lock on the root of the filesystem at idprio, and if there was another
:> process running at 100% CPU, rc5client would never
Wow. I don't think that should ever happen but at this point I'll
try a lot of things :)
Tried it. didn't work.
really, isn't there a way to enable more verbose probing so that
it says 'ed0 not found at 0x280' or some such?
> When I upgraded, my ed0 became ep0 you might want to try that...
David O'Brien wrote:
> > It breaks because compat22 is installing _everything_ in
> > /usr/lib/compat/aout. We've reproduced this locally - compat22 is
> > hosed.
>
> I *knew* this was going to bite us in the ass. I brought it up at E-day
> time... and was ignored.
"I hear what you say - I ju
> > NOW if you look at the compat2{0,1} bits we shipped with 3.2, they
> > install into /usr/lib/compat/. Thus we have no consistancy. So compat22
> > is no more broken than ``make aout-to-elf''.
>
> I think you are abusing compat22 by adding the aout (legacy) stuff.
> Why not just build a legac
David O'Brien wrote:
> > > NOW if you look at the compat2{0,1} bits we shipped with 3.2, they
> > > install into /usr/lib/compat/. Thus we have no consistancy. So compat22
> > > is no more broken than ``make aout-to-elf''.
> >
> > I think you are abusing compat22 by adding the aout (legacy) stuf
Hi,
On Tue, May 18, 1999 at 12:17:48PM -0500, Dan Nelson wrote:
> Problem is that idprio isn't safe. I used to idprio the rc5client, but
> within a day or do the machine would lock up.
oops. That's new for me.
I'm running the 'rc5client' on various machines (2.2.6-stable, 2.2.8-stable,
3.1-stab
[ crossposted to -ports, please follow up to -hackers ]
s...@freebsd.org wrote:
> - Added support for SMP systems to etc/rc.d/setiathome.sh
> - Added etc/setiathome.conf with options to set the nice level, the max.
> number of processes to run, the working directory, and the the user id
>
On 18-May-99 Shin-ichi YOSHIMOTO wrote:
> > Hmm.. I have access to an SB Ensoniq Audio PCI which has the ES1371 on it.
> I also tried an Ensoniq Audio PCI with the ES1371 at first. But this card
> did not work. Then I tried a CREATIVE SB PCI128 which has the CREATIVE 5507
> on it. It was workin
*sigh* No suprise here. As 90% of these things are this was yet
another Dumb User Error. I had a base address conflict that kept
the card from being probed.
Thanks for everyone's help. As always FreeBSD is working just
great!
-Steve
To Unsubscrib
On Wed, 19 May 1999, Stefan Bethke wrote:
>
> I've left out idprio(8) for now.
>
> If someone could point me to a man page explaining the use of kern.quantum,
> and when it might be useful to fiddle with that knob, I'll happily add that
> reference to the setiathome man page.
In 3.2 kern.quant
Trimble is selling a gps kit that can be used to create a Stratum 1
GPS referenced NTP server.
Qty 1 cost is $995
Qty 10 cost is $525
Are there 9 other people interested out there ? I'd like to try & put
together a group purchase.
Joe
Joe McGuckin
ViaNet Communications
994 San Antonio Ro
:Trimble is selling a gps kit that can be used to create a Stratum 1
:GPS referenced NTP server.
:
:Qty 1 cost is $995
:Qty 10 cost is $525
:
:Are there 9 other people interested out there ? I'd like to try & put
:together a group purchase.
:
:Joe
:
:Joe McGuckin
I am not particularly impre
Dennis writes:
> What is required to get an assembly listing of the crashpoint when
> analyzing a crash dump?
Program received signal SIGSEGV, Segmentation fault.
0x80483c4 in main () at xx.c:8
(gdb) x/10i main
0x80483b4 : pushl %ebp
0x80483b5 : movl %esp,%ebp
0x80483b7 :
On Tue, May 18, 1999 at 11:02:38PM -0700, Matthew Dillon wrote:
> I am not particularly impressed with Trimble equipment. I
> think you can probably find something better if you are
> really interested in it. Also, A Qty 1 cost of $1K is
> pretty high for a GPS these days.
It'
56 matches
Mail list logo
