Doug Barton wrote:
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
Hmm, that was an unfortunate side effect.
Heh, well, stuff happens. I think your idea of opening swap exclusive is
probably a good one, but it will require some gymnastics to accomodate
it. One thing that'd really help is an option
In message <[EMAIL PROTECTED]>, Doug Barton writes:
>On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
>
>> Hmm, that was an unfortunate side effect.
>
>Heh, well, stuff happens. I think your idea of opening swap exclusive is
>probably a good one, but it will require some gymnastics to accomodate
>it.
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
> Hmm, that was an unfortunate side effect.
Heh, well, stuff happens. I think your idea of opening swap exclusive is
probably a good one, but it will require some gymnastics to accomodate
it. One thing that'd really help is an option to savecore that t
On Sep 1, 2003, at 6:36 PM, Nicole wrote:
*SIGH*
No what I want is NO serial console. DO NOT FOR ANY REASON turn
off/not resp
ond to the keyboard port
-Dh means both keyboard and serial console... what's the problem? And
please
stop shouting.
Dave
Nicole
On 01-Sep-03 Unnamed Admini
*SIGH*
No what I want is NO serial console. DO NOT FOR ANY REASON turn off/not resp
ond to the keyboard port
Nicole
On 01-Sep-03 Unnamed Administration sources reported Scott Long said :
> Aaron Wohl wrote:
>> My notes on getting a serial console at 115200
>>
>> -must be com1
>> -com1 mu
It seems Petri Helenius wrote:
> ATAng does not seem to detect my RAID set, while ATAold boots it
> fine, first boot -v with ATAng kernel and then ATAold.
>
> Any ideas if raid configs should be compatible between them? Should
> make sense that they are so people upgrading don't get burned...
Do
It seems Petri Helenius wrote:
>
> I also noticed that earlier ATAng spits out these messages; (cut&pasting boot -v
> is a little tedious, but I can copy it all if it helps)
>
> The err=0x01 caught my eye.
Err=0x01 is actually "OK Im' there" signal from an ATA device :)
What I need to know is i
Aaron Wohl wrote:
My notes on getting a serial console at 115200
-must be com1
-com1 must be at port 0x3F8 irq 4
-in bios set the port and irq as above
-in bios set serial redirection to com1
-in bios set baud rate 115200
-in bios set RTS/CTS flow control
-edit (or create) /etc/make.conf to add th
On Mon, 1 Sep 2003, Scott Long wrote:
> Device flags are not specified in the kernel config anymore unless you
> try really, really hard. /etc/device.hints is the correct place to
> adjust this flag.
Yeah, I was looking at the kernel config on the wrong box. This flag did
used to be in GENERIC,
I have a file .fsck_snapshot in /usr (of 7 GB ?!)
-r 1 root wheel 7220781056 Aug 22 18:08 .fsck_snapshot
I hope I can delete it without consequences (after chmod'ing it
of course :-)
--
Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
__
My notes on getting a serial console at 115200
-must be com1
-com1 must be at port 0x3F8 irq 4
-in bios set the port and irq as above
-in bios set serial redirection to com1
-in bios set baud rate 115200
-in bios set RTS/CTS flow control
-edit (or create) /etc/make.conf to add these lines:
BOOT_CO
On 01-Sep-03 Unnamed Administration sources reported Scott Long said :
> Scott M. Likens wrote:
>> I have a question related to FreeBSD Serial console,
>>
>> I am aware you can use -Dh for both internal and serial, but is it
>> possible to see the 'kernel' "boot" messages sent on both the serial
On Sun, Aug 31, 2003 at 10:10:49PM -0700, David O'Brien wrote:
> On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
> > > > I might be missing an obvious, but I just don't see a reason
> > > > why we should use relative linking here: we should just link
> > > > to where we really insta
On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
>
> Now it looks like this:
>
> install -C -o root -g wheel -m 444 libalias.a /foo/usr/lib
> install -s -o root -g wheel -m 444 libalias.so.4 /foo/lib
> ln -fs libalias.so.4 /foo/lib/libalias.so
> ln -fs /lib/libalias.so.4 /fo
Scott M. Likens wrote:
I have a question related to FreeBSD Serial console,
I am aware you can use -Dh for both internal and serial, but is it
possible to see the 'kernel' "boot" messages sent on both the serial and
the console?
It was a question that was asked to me by a client, and after
researc
BTW - I do thank you Marc for your advice. I know you were trying to assist.
It just drives me crazy when important things get broken and people act like..
What the big deal. I don't need it why should you?
I still have not solved the going to comsonsole mode if there is no keyboard
detecte
On 01-Sep-03 Unnamed Administration sources reported Marc G. Fournier said :
>
>
> On Mon, 1 Sep 2003, Nicole wrote:
>
>>
>> So are you saying it Will work in single user mode perhaps? (drives in use)
>>
>> or are you saying gee we have this nice new version that if you need to
>> modify any
On Sep 1, 2003, at 2:47 PM, Scott M. Likens wrote:
I have a question related to FreeBSD Serial console,
I am aware you can use -Dh for both internal and serial, but is it
possible to see the 'kernel' "boot" messages sent on both the serial
and
the console?
If your BIOS supports serial port redir
Hi.
I noticed that network collition increase, in log of 7/26.
Such still a state continues.
What became like this owing to?
5.1-CURRENT-20030720 (daily run 7/26):
Network interface status:
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
dc01500 00:90:cc:
Daniel O'Connor wrote:
> On Monday 01 September 2003 08:41, Mark Kettenis wrote:
> >I asked this on -hackers a little while ago but no response. I'm
> > curious if anyone has made an attempt to port these Winmodem drivers.
> >http://www.linuxant.com/drivers/
> >
> > I did look into it, but
Doug Barton wrote:
> On Mon, 1 Sep 2003, Terry Lambert wrote:
> > > I attached a verbose dmesg, just in case someone wants to take a look.
> >
> > | ACPI: DSDT was overridden.
> > | -0424: *** Error: UtAllocate: Could not allocate size 50204453
> > | ACPI-0428: *** Error: Could not allo
"M. Warner Losh" wrote:
> In message: <[EMAIL PROTECTED]>
> Doug Barton <[EMAIL PROTECTED]> writes:
> : I posted one approach to this today... touch a file right before you
> : start installworld, then consider anything not newer than that file a
> : candidate for disposal. There is cur
In message: <[EMAIL PROTECTED]>
Doug Barton <[EMAIL PROTECTED]> writes:
: On Mon, 1 Sep 2003, M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > Doug Barton <[EMAIL PROTECTED]> writes:
: > : On Mon, 1 Sep 2003, M. Warner Losh wrote:
: > : > My tool is initially ju
Pawel Jakub Dawidek wrote:
> On Mon, Sep 01, 2003 at 12:48:41AM -0600, Kenneth D. Merry wrote:
> +> - I tried just holding a mutex all the time, but obviously you can't
> +>malloc while holding a mutex (except Giant), and the sysctl code does a
> +>number of mallocs. (The original cause o
On Mon, 1 Sep 2003, Ian Freislich wrote:
> Hi
>
> Any idea why '-C' is hard coded for bsd.lib.mk and bsd.own.mk? I
> thought that the make.conf variable was there to allow or disallow
> this. The following comes from bsd.lib.mk:
I'd also like to see this option be a knob, preferably defaulting
On Mon, 1 Sep 2003, Terry Lambert wrote:
> Doug Barton wrote:
> > > I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl
> >
> > Thanks for the suggestion... I tried that one, but got the same error
> > about not enough memory to load the override file.
> >
> > I attached a verbos
Doug Barton wrote:
> > I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl
>
> Thanks for the suggestion... I tried that one, but got the same error
> about not enough memory to load the override file.
>
> I attached a verbose dmesg, just in case someone wants to take a look.
|
I am using -CURRENT cvsup'd August 29 and having some problems with a
3com 3c575B PC Card. I am running on a Dell Latitude C600 and -CURRENT
has, for the most part, worked perfectly for me.
The problem is that the 3Com card is no longer getting activated. The
system sees when the card is plugged
I have a question related to FreeBSD Serial console,
I am aware you can use -Dh for both internal and serial, but is it
possible to see the 'kernel' "boot" messages sent on both the serial and
the console?
It was a question that was asked to me by a client, and after
researching it more, it seems
On Mon, 1 Sep 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Doug Barton <[EMAIL PROTECTED]> writes:
> : On Mon, 1 Sep 2003, M. Warner Losh wrote:
> :
> : > My tool is initially just a 'delete these files' tool, but now that I
> : > think about it, it wouldn't be hard
So are you saying it Will work in single user mode perhaps? (drives in use)
or are you saying gee we have this nice new version that if you need to modify
any disk slice you did after an install your screwed into going back to caveman
tools (which I admit I have NO IDEA how to use and I bet ma
In message <[EMAIL PROTECTED]>, Nicole writes:
>
> Is anyone going to be fixing the sysinstall problem of not being able to
>re-slice a drive? For those who are not technical whizes this IS a big problem.
>We do still care about them right?
If you are talking about using sysinstall to modify d
Is anyone going to be fixing the sysinstall problem of not being able to
re-slice a drive? For those who are not technical whizes this IS a big problem.
We do still care about them right?
Nicole
|\ __ /| (`\
| o_o |__ ) )
On Mon, 1 Sep 2003, Lefteris Chatzibarbas wrote:
> I have a problem with kernels, built the last couple of days, where
> during shutdown syncer is "giving up" on buffers. During the next boot
> all filesystems are checked because of improper dismount. Here follow
> the exact messages I get:
>
>
David O'Brien wrote:
On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote:
|-+---+-+|
| | | | Productionable |
| | | | support fo
On Monday 01 September 2003 09:17 am, ODHIAMBO Washington wrote:
> * Steve Kargl <[EMAIL PROTECTED]> [20030901 18:36]:
wrote:
> > On Mon, Sep 01, 2003 at 05:00:44PM +0300, ODHIAMBO Washington wrote:
> > > Now after cvsupping afresh, I have failed to buildworld
> > &g
Hello,
I have a problem with kernels, built the last couple of days, where
during shutdown syncer is "giving up" on buffers. During the next boot
all filesystems are checked because of improper dismount. Here follow
the exact messages I get:
Waiting (max 60 seconds) for system process `vnlru
David O'Brien wrote:
On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote:
|-+---+-+|
| | | | Productionable |
| | | | support fo
On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote:
> |-+---+-+|
> | | | | Productionable |
> | | | | support for the|
>
On Mon, Sep 01, 2003 at 09:31:29AM -0700, David O'Brien wrote:
> On Mon, Sep 01, 2003 at 09:44:24AM +0300, Ruslan Ermilov wrote:
> > On Sun, Aug 31, 2003 at 10:10:49PM -0700, David O'Brien wrote:
> > > On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
> > > > > > I might be missing an
On Mon, Sep 01, 2003 at 09:44:24AM +0300, Ruslan Ermilov wrote:
> On Sun, Aug 31, 2003 at 10:10:49PM -0700, David O'Brien wrote:
> > On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
> > > > > I might be missing an obvious, but I just don't see a reason
> > > > > why we should use rel
In message: <[EMAIL PROTECTED]>
Ian Freislich <[EMAIL PROTECTED]> writes:
: "M. Warner Losh" wrote:
: > Don't build pcic with newcard. It is broken, doesn't work and isn't
: > supported. I have a rewrite in my p4 tree that I'm slugging through,
: > but pcic is likely to coninue to not
In message: <[EMAIL PROTECTED]>
Doug Barton <[EMAIL PROTECTED]> writes:
: On Mon, 1 Sep 2003, Ruslan Ermilov wrote:
:
: > > I posted one approach to this today... touch a file right before you
: > > start installworld, then consider anything not newer than that file a
: > > candidate f
In message: <[EMAIL PROTECTED]>
Doug Barton <[EMAIL PROTECTED]> writes:
: On Mon, 1 Sep 2003, M. Warner Losh wrote:
:
: > My tool is initially just a 'delete these files' tool, but now that I
: > think about it, it wouldn't be hard to say also 'create these
: > symlinks'. The hard par
* Steve Kargl <[EMAIL PROTECTED]> [20030901 18:36]: wrote:
> On Mon, Sep 01, 2003 at 05:00:44PM +0300, ODHIAMBO Washington wrote:
> >
> > Now after cvsupping afresh, I have failed to buildworld completely,
> > even doing cvsup N times again. Buildworld always fails wit
Hi.
On Thu, 28 Aug 2003 21:57:24 -0700 (PDT)
Nate Lawson <[EMAIL PROTECTED]> wrote:
> With today's ATAng, I can suspend my laptop but when I resume, the system
> hangs. I'll try to get the exact dmesg with a serial console since
> syscons gets screwed up by resuming (this is normal behavior). I
>I upgraded, and now my DVDROM (ata1-slave) is working again, but
>my Plextor 8/4/32A CDRW (ata1-master) still won't probe >correctly.
>
>atacontrol list appears to send out the same message as before.
>
>dmesg & atacontrol list output attached.
>
>Andrew Lankford
Crap, I attached the wrong file (
I have a wi0 (Linksys WPC11 V3) card that is usually in the pcmcia slot of
my
laptop, but occasionally I need to pull it to use the built in nic.
Is dhclient supposed to be killed on remove?
Is dhclient supposed to be restarted on insert?
Both of these are NOT happening on my box.
-CURRENT fro
[ On Monday, September 1, Scot W. Hetzel wrote: ]
> From: "John Reynolds" <[EMAIL PROTECTED]>
> I
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1203173+1206388+/usr/local/www/db/text/2003/freebsd-questions/20030622.freebsd-questions
> You would need to add the following to /etc/devfs.rules:
>
> [
>I've gone over the probe code once again.
I upgraded, and now my DVDROM (ata1-slave) is working again, but
my Plextor 8/4/32A CDRW (ata1-master) still won't probe correctly.
atacontrol list appears to send out the same message as before.
dmesg & atacontrol list output attached.
Andrew Lankford
From: "John Reynolds" <[EMAIL PROTECTED]>
> Hi all, in debugging /dev/usb* and /dev/ugen* permissions problems so that
I
> could access my digital camera as a mere-mortal user, I came across this
> posting to -questions:
>
>
http://www.freebsd.org/cgi/getmsg.cgi?fetch=1203173+1206388+/usr/local/www
After making world as of August 30 i am seeing weird disk access when i boot
up the little yellow LED that shows disk access is constantly lit there is
no way of turning it off and i dont see/know a way to see ehats making it do
what it does fstat,lsof dont seem to find anything its a bit anoyin
Hi
Any idea why '-C' is hard coded for bsd.lib.mk and bsd.own.mk? I
thought that the make.conf variable was there to allow or disallow
this. The following comes from bsd.lib.mk:
.if defined(LIB) && !empty(LIB) && !defined(NOINSTALLLIB)
${INSTALL} -C -o ${LIBOWN} -g ${LIBGRP} -m ${LIBMOD
"M. Warner Losh" wrote:
> Don't build pcic with newcard. It is broken, doesn't work and isn't
> supported. I have a rewrite in my p4 tree that I'm slugging through,
> but pcic is likely to coninue to not compile until that's committed.
Will that eventually fix support for the following (dmesg fr
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Op
Hello gurus,
I have a dead system! No service will start at all, but if I can get
over this buildworld failure, then maybe I can compile a new kernel
and get my services running. It's not a production box, but a test
box. The problem started this way:
I cvsup-ped, make buildworld, then kind of I
Matt wrote:
Soren Schmidt wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
Mine is working perfectly now (see below).
Soren Schmidt wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
Mine is working perfectly now (see below). With atapicam a
On Fri, 22 Aug 2003, 19:49+0400, Maxim Konovalov wrote:
> On Fri, 22 Aug 2003, 10:39-0400, Craig Rodrigues wrote:
>
> > On Fri, Aug 22, 2003 at 09:00:32AM +0400, Maxim Konovalov wrote:
> > > On Sun, 17 Aug 2003, 17:21-0400, Craig Rodrigues wrote:
> > >
> > > > Hi,
> > > >
> > > > With GEOM in plac
Alastair G. Hogge wrote:
On Monday, 01 September 2003 02:24, Steve Kargl wrote:
On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote:
Hello list,
For the past couple of weeks I've been tyring to keep my system up to
date with cvsup. However, when ever I run a buildworld I get proble
On Monday, 01 September 2003 02:24, Steve Kargl wrote:
> On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote:
> > Hello list,
> >
> > For the past couple of weeks I've been tyring to keep my system up to
> > date with cvsup. However, when ever I run a buildworld I get problems
> > wit
Check out the header comments in the recently created
/etc/defaults/devfs.rules and the new rc.conf variable
devfs_system_ruleset. In your case below, you'd probably need an
/etc/devfs.rules like:
# Create local ruleset
[local_ruleset=10]
add path 'ugen*' mode 664
And then you'd add the fo
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
___
[EMAIL PROTECTED] mailing list
On Mon, Sep 01, 2003 at 12:48:41AM -0600, Kenneth D. Merry wrote:
+> - I tried just holding a mutex all the time, but obviously you can't
+>malloc while holding a mutex (except Giant), and the sysctl code does a
+>number of mallocs. (The original cause of this problem -- M_WAITOK
+>ma
On Sun, 31 Aug 2003 15:02:21 -0700 (PDT)
Doug Barton <[EMAIL PROTECTED]> wrote:
> There was a discussion of this recently, and the conclusion was more or
> less that doing this in an automated fashion is frought with danger,
> since you don't know for sure what else besides system components the
>
On Mon, 1 Sep 2003, Ruslan Ermilov wrote:
> > I posted one approach to this today... touch a file right before you
> > start installworld, then consider anything not newer than that file a
> > candidate for disposal. There is currently something weird going on in
> > /usr/lib though... a lot of th
On Mon, Sep 01, 2003 at 01:58:52AM -0700, Doug Barton wrote:
> On Mon, 1 Sep 2003, M. Warner Losh wrote:
>
> > My tool is initially just a 'delete these files' tool, but now that I
> > think about it, it wouldn't be hard to say also 'create these
> > symlinks'. The hard part here is generating th
I am currently trying to upgrade from 5.1-RELEASE to current on my Sony VAIO
laptop, model number GRX-570. On first boot of CURRENT kernel a panic occurs
right after inphy:
Fatal trap 12: page fault while in kernel mode
Fault virtual address= 0xdeadc0de
Fault code=
Oeps I've put the old one up...
Now ik have the new one. I don't load the VESA modules, it seems these
are loaded before acpi code is replaced?
Robert
On Mon, Sep 01, 2003 at 01:49:42AM -0700, Doug Barton wrote:
> On Mon, 1 Sep 2003, Robert [unknown-8bit] Blacquire wrote:
>
> > I don't seem to
In message <[EMAIL PROTECTED]>, "Kenneth D. Merry" writes:
>In particular, I went through some interesting permutations in
>taskqueue_kthread() to make things work right:
>
> - I tried holding Giant when calling tsleep, but it complained that I
> didn't own Giant.
I have had a similar issue a c
On Mon, 1 Sep 2003, M. Warner Losh wrote:
> My tool is initially just a 'delete these files' tool, but now that I
> think about it, it wouldn't be hard to say also 'create these
> symlinks'. The hard part here is generating the 'obsolete' lists.
I posted one approach to this today... touch a fil
On Mon, 1 Sep 2003, Robert [unknown-8bit] Blacquière wrote:
> I don't seem to have these problems. I use xbattbar without problem.
Argh. How recent is your -current? I compile regularly, and I was up to
date as of this afternoon.
> I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsd
On Mon, Sep 01, 2003 at 01:22:49AM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> : On Mon, Sep 01, 2003 at 08:58:19AM +0200, Christoph P. Kukulies wrote:
> : > On Mon, Sep 01, 2003 at 09:44:24AM +0300, Ruslan Ermilov wrote:
On Sun, Aug 31, 2003 at 04:57:57PM +0200, Soren Schmidt wrote:
> It seems Jan Srzednicki wrote:
> > ad0: 19546MB [39714/16/63] at ata0-master UDMA66
> > ad1: 39093MB [79428/16/63] at ata0-slave UDMA66
> > ata1-slave: FAILURE - ATA_IDENTIFY status=51
> > error=4
> > acd0: CDROM at ata1-master UDM
In message: <[EMAIL PROTECTED]>
Scott Long <[EMAIL PROTECTED]> writes:
: >> Clarify the numbering of some of the build stages.
: > How about if we get rid of the numbering here completely?
: I like the numbering since it can give me an idea of progress at a
: quick glance without havin
Ruslan Ermilov wrote:
On Sun, Aug 31, 2003 at 11:43:25PM -0700, Scott Long wrote:
scottl 2003/08/31 23:43:25 PDT
FreeBSD src repository
Modified files:
.Makefile.inc1
Log:
Clarify the numbering of some of the build stages.
Revision ChangesPath
1.389
In message: <[EMAIL PROTECTED]>
Ruslan Ermilov <[EMAIL PROTECTED]> writes:
: On Mon, Sep 01, 2003 at 08:58:19AM +0200, Christoph P. Kukulies wrote:
: > On Mon, Sep 01, 2003 at 09:44:24AM +0300, Ruslan Ermilov wrote:
: > > I think that Gordon took a safe path with creating compatibility
On Mon, Sep 01, 2003 at 08:58:19AM +0200, Christoph P. Kukulies wrote:
> On Mon, Sep 01, 2003 at 09:44:24AM +0300, Ruslan Ermilov wrote:
> > I think that Gordon took a safe path with creating compatibility symlinks.
> > Besides, creating compatibility symlinks has a nicety of removing your
> > stal
On Sun, Aug 31, 2003 at 11:43:25PM -0700, Scott Long wrote:
> scottl 2003/08/31 23:43:25 PDT
>
> FreeBSD src repository
>
> Modified files:
> .Makefile.inc1
> Log:
> Clarify the numbering of some of the build stages.
>
> Revision ChangesPath
> 1.3
On Mon, Sep 01, 2003 at 02:23:18 +0200, Pawel Jakub Dawidek wrote:
> On Mon, Sep 01, 2003 at 02:13:45AM +0200, Pawel Jakub Dawidek wrote:
> +> I was getting same panics while I was working on GEOM Gate.
> +> After many hours of debugging I've tracked this down - I've initialized
> +> a mutex, but I
On Mon, Sep 01, 2003 at 09:44:24AM +0300, Ruslan Ermilov wrote:
> I think that Gordon took a safe path with creating compatibility symlinks.
> Besides, creating compatibility symlinks has a nicety of removing your
> stale symlinks in /usr/lib.
I always asked myself whether there is a tool or some
On Sun, Aug 31, 2003 at 12:52:47 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Kenneth D. Merry" writes:
>
> >Anyway, I got some debugging output, and I've attached dmesg output. Let
> >me know whether anything in there looks suspicious or points to a possible
> >problem.
>
On Sun, Aug 31, 2003 at 10:10:49PM -0700, David O'Brien wrote:
> On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
> > > > I might be missing an obvious, but I just don't see a reason
> > > > why we should use relative linking here: we should just link
> > > > to where we really insta
On Mon, 1 Sep 2003, [iso-8859-1] RMH wrote:
> Oh yes, user threading doesn't support multiple CPUs... Thanks for
> pointing me.
>
> Both libkse and libthr work with that code snippet, but Viewperf
> when linked against any of them locks my machine pretty deadly.
> With Linuxthreads it just segf
On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
> > > I might be missing an obvious, but I just don't see a reason
> > > why we should use relative linking here: we should just link
> > > to where we really install. With the attached patch, I get:
...
> +.if ${LIBDIR} != ${SHLIBDIR
On Sun, Aug 31, 2003 at 08:31:49PM +0200, Alexander Leidinger wrote:
> shouldn't we add something like
> ---snip---
> for i in /lib/lib*.so.*; do
> lib=$(basename $i)
> [ -f /usr/lib/$lib ] && chflags noschg /usr/lib/$lib && rm /usr/lib/$lib
> done
> ---snip---
> into UPDATING or append
I don't seem to have these problems. I use xbattbar without problem.
I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl
On Sun, Aug 31, 2003 at 07:50:03PM -0700, Doug Barton wrote:
> I got interested in this recently because I inherited one of these
> laptops from work.
>
>
In the last episode (Sep 01), RMH said:
> Oh yes, user threading doesn't support multiple CPUs... Thanks for
> pointing me.
>
> Both libkse and libthr work with that code snippet, but Viewperf
> when linked against any of them locks my machine pretty deadly.
> With Linuxthreads it just segfaults ;
In message: <[EMAIL PROTECTED]>
"Martin Jessa" <[EMAIL PROTECTED]> writes:
: Sources fetched an hour ago.
: Running make in /usr/src/sys/i386/compile/MYKERNEL :
:
:
: cc -c -O -pipe -march=i486 -Wall -Wredundant-decls -Wnested-externs
: -Wstrict-prototypes -Wmissing-prototypes -Wpoin
Oh yes, user threading doesn't support multiple CPUs... Thanks for
pointing me.
Both libkse and libthr work with that code snippet, but Viewperf
when linked against any of them locks my machine pretty deadly.
With Linuxthreads it just segfaults ;)
---
Regards,
Rhett
Dan Nelson wrote:
>
> In th
I got interested in this recently because I inherited one of these
laptops from work.
On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote:
> Which version of the N610C BIOS are you using? (F.14 is the latest on
> the hp.com website.) I know that the _OSI("Windows 2001") bug will be
> fixed in
Hi all, in debugging /dev/usb* and /dev/ugen* permissions problems so that I
could access my digital camera as a mere-mortal user, I came across this
posting to -questions:
http://www.freebsd.org/cgi/getmsg.cgi?fetch=1203173+1206388+/usr/local/www/db/text/2003/freebsd-questions/20030622.freebsd
In the last episode (Sep 01), RMH said:
> Hello gentlemen,
>
> I seem to have threading problems with 5.1-RELEASE. Every time I run
> a multithreaded application (linked against libc_r) on a SMP system,
> I get only 1 CPU loaded at any moment given. I tried different
Correct. libc_r is a userlan
On Monday 01 September 2003 08:41, Mark Kettenis wrote:
>Date: Sun, 31 Aug 2003 15:02:36 -0700 (PDT)
>From: Nate Lawson <[EMAIL PROTECTED]>
>
>I asked this on -hackers a little while ago but no response. I'm
> curious if anyone has made an attempt to port these Winmodem drivers.
>h
On Mon, 1 Sep 2003 03:13:31 +0100 (BST)
RMH <[EMAIL PROTECTED]> wrote:
> # gcc -O2 -fomit-frame-pointer -march=i686 -o smp smp.c -pthread
> # ./smp
> 4Gb per pass mode
> INTEGER | WRITING 8 Kb block: 1351 Mb/s
> res0: 674
> res1: 677
> # gcc -O2 -fomit-frame-pointer -march=i686 -o smp2 smp.c -
Hi.
Great, now it compiles cleanly.
Thanks Doug.
> On Mon, 1 Sep 2003, Martin Jessa wrote:
>
>> Sources fetched an hour ago.
>> Running make in /usr/src/sys/i386/compile/MYKERNEL :
>
> Remove device pcic from your kernel config. My understanding is that
> it's broken anyway, so you're not losi
With a relatively current CURRENT on an MSI 875P-Neo (MS-6758)
motherboard, I see the following spurious about "ACPI-1287..." messages,
but this does not seem to affect the system boot or anything else.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
Hello gentlemen,
I seem to have threading problems with 5.1-RELEASE. Every time I run
a multithreaded application (linked against libc_r) on a SMP system,
I get only 1 CPU loaded at any moment given. I tried different
software, including Viewperf, but results remain the same. When linked
against L
On Mon, 1 Sep 2003, Martin Jessa wrote:
> Sources fetched an hour ago.
> Running make in /usr/src/sys/i386/compile/MYKERNEL :
Remove device pcic from your kernel config. My understanding is that
it's broken anyway, so you're not losing anything by removing it.
HTH,
Doug
--
This .signatur
Sources fetched an hour ago.
Running make in /usr/src/sys/i386/compile/MYKERNEL :
cc -c -O -pipe -march=i486 -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../..
-I../..
1 - 100 of 103 matches
Mail list logo
