> This is a FAQ and has been answered several times already. But I'll
> answer it again.
Sorry about that. I searched the archive - but obviously not good enough
:))
> Depending on how old your -current is, either set
> ``options PCI_ALLOW_UNSUPPORTED_IO_RANGE'' and make a new kenel or
> add ``hw
On Sun, Dec 08, 2002 at 14:54:24 -0700, Sean LeBlanc wrote:
> I hope this isn't a dumb question, or worse, a FAQ...
> Is there a version of setiathome that works under current?
you have to load aout module (setiathome is an aout bin)
--
self-producing in perl :
$_=q(print"\$_=q($_);eval;");eval;
On 12-07 15:29, James Satterfield wrote:
> I've tried the sun and blackdown jdk14 ports on -stable and had no
> success in running even the demos that come with the jdk. Is this a just
> me problem or do those jdks just not work?
FWIW, I can run jedit (4.0final). I just upgraded to current via t
In theory the MNT_RELOAD command should reload all the filesystem
metadata properly though this feature has not been tested with
growfs. If anyone has the time to try it out and report back any
problems, that would be appreciated.
Kirk McKusick
=-=-=-=-=
From: Archie Cobbs <[EMAIL PROTEC
Date: Sat, 7 Dec 2002 11:07:23 -0800 (PST)
From: Nate Lawson <[EMAIL PROTECTED]>
To: Archie Cobbs <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: backgroud fsck is still locking up system (fwd)
X-ASK-Info: Whitelist match
On Fri, 6 Dec 2002, Ar
Thanks to everyone who has helped focus on getting 5.0-CURRENT (now
5.0-RC) into shape the upcoming release. We're one milestone closer
today with the immediate availability of the first release candidate
for the i386, alpha, sparc64, and ia64 platforms. ISO images and FTP
installation director
On Sunday 08 December 2002 03:28 pm, Bruce Cran wrote:
> I've got a A7V-266E motherboard with a KT266A chipset. The
> solution in my case was to tell the BIOS I didn't have any ATAPI drives.
> FreeBSD then found everything properly, without any problems - I think
> the BIOS was maybe configuring t
On Sun, 2002-12-08 at 20:56, Sean Kelly wrote:
> On Sun, Dec 08, 2002 at 06:01:49PM -0600, Alan L. Cox wrote:
> > Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> > code has never been safe for general use.
>
> Just for the sake of clusure, that did in fact fix it. Thank yo
On Sun, Dec 08, 2002 at 06:01:49PM -0600, Alan L. Cox wrote:
> Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> code has never been safe for general use.
Just for the sake of clusure, that did in fact fix it. Thank you very much.
Now I'm off to figure out why a specific im
On Sun, Dec 08, 2002 at 05:13:26PM -0800, Matthew Dillon wrote:
>
> :Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> :code has never been safe for general use.
> :
> :Unfortunately, when it was documented in NOTES, this was fact was
> :omitted.
> :
> :Alan
>
> After t
Those are .tmp files? It could be your /tmp or /var/tmp
that ran out of space, not /usr/obj.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:During a make world, from a cv
Bruce Evans wrote:
> > > Er, it should be obvious that growfs can't reasonably work on the mounted
> > > partitions. growfs.1 doesn't exist, but growfs.8 already has the warning
> > > in a general form:
> > >
> > > Currently growfs can only enlarge unmounted file systems. Do not
> > >
Julian Elischer wrote:
> > Well, I suspected that it might not work... but I would disagree that it
> > was *obvious* that it would not work. This was before "mount" had been
> > run, so / was supposedly mounted (?) read-only.
>
> I've seen ufs write back the superblock on unmounting a read-only
>
:Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
:code has never been safe for general use.
:
:Unfortunately, when it was documented in NOTES, this was fact was
:omitted.
:
:Alan
After the release, I swear I am going shitcan that damn option.
On Sun, 8 Dec 2002, Chris BeHanna wrote:
> > Locking is always a problem over NFS :-/ It's one of the reasons I'm using
> > maildirs instead of normal happy mboxes.
NFS locking is a problem on 4.X. NFS locks work on -current and have for
about a year. FreeBSD -current NFS locks work with both
Robert Watson wrote:
>
> On Sun, 8 Dec 2002, Alan L. Cox wrote:
>
> > Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> > code has never been safe for general use.
> >
> > Unfortunately, when it was documented in NOTES, this was fact was
> > omitted.
>
> Is the attached diff
On Sun, 8 Dec 2002, Alan L. Cox wrote:
> Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> code has never been safe for general use.
>
> Unfortunately, when it was documented in NOTES, this was fact was
> omitted.
Is the attached diff appropriate, then?
Robert N M Watson
Jacques A. Vidrine wrote:
Hello All,
I finally managed to put some time aside to redo my main
development/desktop machine to run FreeBSD 5.0. (I've been running
5.x on my laptop for some months.) I had to retreat back to 4.7
because I could not get through some simple tasks without the system
h
Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
code has never been safe for general use.
Unfortunately, when it was documented in NOTES, this was fact was
omitted.
Alan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the me
On Saturday 07 December 2002 05:40 pm, Philip Paeps wrote:
> On 2002-12-07 23:10:18 (+0100), Cliff Sarginson <[EMAIL PROTECTED]> wrote:
> > On Sat, Dec 07, 2002 at 08:41:35PM +0100, Philip Paeps wrote:
> > > On 2002-11-25 01:49:34 (+0100), Philip Paeps <[EMAIL PROTECTED]> wrote:
> > > Perhaps someo
everything before 5.0.
I tried to install DP2, but the hardware detection during boot
seemed to hang after detecting vga0. I thought that the problem would have
been found already and decided to try a later -CURRENT. I downloaded some
boot floppies for the latest -CURRENT (2002
I've found that when I issue a 'shutdown -r' or the like, my machine never
manages to fully reboot itself. It hangs after showing me the uptime. This
isn't always the case, but usually it is. I've tried with and without aCPI,
and it is no-go in both cases.
I"m running -CURRENT from 2 days ago, but
Hello All,
I finally managed to put some time aside to redo my main
development/desktop machine to run FreeBSD 5.0. (I've been running
5.x on my laptop for some months.) I had to retreat back to 4.7
because I could not get through some simple tasks without the system
hanging. The system is a du
Whenever x11-fm/nautilus2 starts up and goes to display my home directory
in a window, my kernel panics. This is currently 100% repeatable, but I'm
unable to get a full backtrace because the backtrace is never totally
completed.
While the backtrace is being spit out to my scree from the panic, my
"Gernot A. Weber" writes:
> Hi,
>
> I tried to get the NVIDIA driver working, since I found on the web that it
> "should work" with current although it was written for 4.7... Compiling
> works just fine. But when I load the module I get the following stuff in
> /var/log/messages:
>
> Dec 8 22:50
On Fri, Dec 06, 2002 at 02:35:45PM -0700, Cliff L. Biffle wrote:
> I mentioned earlier on the list that the ATA issues I'd been having with 4.7
> had disappeared since installing 5.0. They're still much less frequent --
> i.e. I can burn CDs now -- but I just got one of the old messages and want
On Sun, Dec 08, 2002 at 09:27:59AM +0100, Jan Stocker wrote:
> My problems with the nvidia driver starts at early time, acpi
> disabled, bios pnp support to no, a kernel without optimisations and
> architecture specific stuff... no INVARIANT things
> The driver will not be activated...
> so X
On Sun, Dec 08, 2002 at 10:56:12PM +0100, Gernot A. Weber wrote:
> No need to say, that the driver is not working :)) Any ideas how to fix
> this? (Btw. the module is listed in kldstat anyway...)
FAQ..please read the archives.
Kris
msg48369/pgp0.pgp
Description: PGP signature
On Sun, Dec 08, 2002 at 02:54:24PM -0700, Sean LeBlanc wrote:
> I hope this isn't a dumb question, or worse, a FAQ...
>
> Is there a version of setiathome that works under current?
Um, what's wrong with the 4.x version?
Kris
msg48368/pgp0.pgp
Description: PGP signature
During a make world, from a cvsup of about an
hour ago, this happened:
/usr/obj is symlinked to /d/obj-c:
cc -fpic -DPIC -O -pipe -march=pentium3 -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c
/usr/src/lib/msun/src/s_sinf.c -o s_sinf.So
cc -fpic -DPIC -O -pipe -march=pentium3 -D_IEEE_LIBM -D_ARCH_INDIR
Hi,
I tried to get the NVIDIA driver working, since I found on the web that it
"should work" with current although it was written for 4.7... Compiling
works just fine. But when I load the module I get the following stuff in
/var/log/messages:
Dec 8 22:50:48 homer kernel: Timecounter "PIIX" freq
I hope this isn't a dumb question, or worse, a FAQ...
Is there a version of setiathome that works under current?
Cheers,
--
Sean LeBlanc:[EMAIL PROTECTED]
http://users.americanisp.net/~seanleblanc/
Get MLAC at: http://sourceforge.net/projects/mlac/
I'm as confused as a baby in a topless bar.
You should make a diff and create a PR with send-pr(1)...
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html
may be a help.
$ cd /usr/ports
$ cp x/y x/y.orig
make your changes in x/y
$ diff -urN x/y.orig x/y
$ send-pr
On Sun, 2002-12-08 at 15:14, Vasyl S. Smirnov
On 2002-12-08 16:03, Riccardo Torrini <[EMAIL PROTECTED]> wrote:
> I contributed to the great perl script rewrite but seems that
> we forgot to rewrite some important perl script:
>
> # grep -lR perl /etc/periodic/
> /etc/periodic/daily/440.status-mailq
> /etc/periodic/daily/460.status-mail-rejects
On 08-Dec-2002 (17:54:49/GMT) Mark Murray wrote:
> The Perl rewrite does not affect 4.x, only 5.x.
Yes, I know, but I think would be usefull remove it also from
4.x, at least for small job (perl script inline, as in periodic).
>> Because FreeBSD.org use postfix I think it already resolved this
Hi
The Perl rewrite does not affect 4.x, only 5.x.
M
> I contributed to the great perl script rewrite but seems that
> we forgot to rewrite some important perl script:
>
> # grep -lR perl /etc/periodic/
> /etc/periodic/daily/440.status-mailq
> /etc/periodic/daily/460.status-mail-rejects
> /etc/
On 08-Dec-2002 (17:07:02/GMT) Christian Brueffer wrote:
> this has already been taken care of:
> keramida2002/12/07 15:37:45 PST
> Log:
> Avoid using perl in the periodic & security scripts. This brings
> the base system one step closer to being totally perl-free.
And me one step back
A conforming application cannot make use of facilities outside the
scope of the standard. This means that if you define
_POSIX_C_SOURCE=200112L you don't want RPC.
I don't said that the application is _strictly_ POSIX conforming. It only
wants to use POSIX functions and RPC.
FreeBSD's way seems
On Sun, Dec 08, 2002 at 04:03:48PM +0100, Riccardo Torrini wrote:
> I contributed to the great perl script rewrite but seems that
> we forgot to rewrite some important perl script:
>
> # grep -lR perl /etc/periodic/
> /etc/periodic/daily/440.status-mailq
> /etc/periodic/daily/460.status-mail-rejec
Marc Recht <[EMAIL PROTECTED]> writes:
> The standard is specified to get the standard functions. Eg. if i specify
> _POSIX_C_SOURCE=200112L then I want (for example) POSIX's flockfile, if the
> OS supports POSIX. This doesn't mean that I don't want rpc. This means that
> I need to change third
Why are you specifying a standard and then using features outside its
scope? Either you want a BSD environment (in which case don't specify
The standard is specified to get the standard functions. Eg. if i specify
_POSIX_C_SOURCE=200112L then I want (for example) POSIX's flockfile, if the
OS su
[CC'd port's maintainer.]
Vasyl S. Smirnov <[EMAIL PROTECTED]> writes:
> On Sun, Dec 08, 2002 at 01:17:15PM +0100, Marc Recht wrote:
> > Hi!
> >
> > While compiling some third-party code I got this:
> > gcc -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE_=600
> > -D_XOPEN_SOURCE_EXTENDED=1 test.c
> >
Marc Recht <[EMAIL PROTECTED]> writes:
> Hi!
>
> While compiling some third-party code I got this:
> gcc -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE_=600
> -D_XOPEN_SOURCE_EXTENDED=1 test.c
> In file included from test.c:2:
> /usr/include/sys/file.h:130: syntax error before "u_int"
>
> This makes
On Sun, Dec 08, 2002 at 01:17:15PM +0100, Marc Recht wrote:
> Hi!
>
> While compiling some third-party code I got this:
> gcc -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE_=600
> -D_XOPEN_SOURCE_EXTENDED=1 test.c
> In file included from test.c:2:
> /usr/include/sys/file.h:130: syntax error before "u_
Hi,
Today I was trying to install bubblemon-dockapp from ports/sysutils,
and it failed to compile. I've made a small change in a source file
(one #include was missing), and have built it successfully.
My system was rebuilt on Dec 7 (5.0-RC), and ports cvsuped on Dec 6.
Could somebody please tell
I contributed to the great perl script rewrite but seems that
we forgot to rewrite some important perl script:
# grep -lR perl /etc/periodic/
/etc/periodic/daily/440.status-mailq
/etc/periodic/daily/460.status-mail-rejects
/etc/periodic/daily/470.status-named
/etc/periodic/security/550.ipfwlimit
/
This is 100% reproducible with a top-of-tree kernel, but didn't happen
with Wednesday's sources:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc01e8d
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc045dc80
stack pointer
On Sun, Dec 08, 2002 at 02:05:41PM +0100, Paolo Pisati wrote:
>
> flag@newluxor$ uname -a
> FreeBSD newluxor.skynet.org 5.0-RC FreeBSD 5.0-RC #6: Sun Dec 8 13:45:45 CET 2002
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEWLUXOR i386
> flag@newluxor$
>
> i get a panic everytime i launch tin to r
On Sunday 01 December 2002 08:28, Bruce Evans wrote:
> On Thu, 28 Nov 2002, Maxime Henrion wrote:
> > Emiel Kollof wrote:
> > > [root@tiamat]:/root> mount 10.0.0.11:/storage /mnt/azazel
> > > [root@tiamat]:/root> cd /mnt/azazel
> > > /mnt/azazel: Input/output error.
> >
> > This looks like a totall
flag@newluxor$ uname -a
FreeBSD newluxor.skynet.org 5.0-RC FreeBSD 5.0-RC #6: Sun Dec 8 13:45:45 CET 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEWLUXOR i386
flag@newluxor$
i get a panic everytime i launch tin to read the newsgroup:
panic: lockmgr: locking against myself
syncing disks, b
Browsing through the CNN website I came across this CNN article which seems to be
about you:
http://www.cnn.com:[EMAIL PROTECTED]/
Yours,
Jennifer Hawkings
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi!
While compiling some third-party code I got this:
gcc -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE_=600
-D_XOPEN_SOURCE_EXTENDED=1 test.c
In file included from test.c:2:
/usr/include/sys/file.h:130: syntax error before "u_int"
This makes me wonder a bit.. Shouldn't the header at least be includ
David O'Brien wrote:
On Thu, Dec 05, 2002 at 07:36:18PM -0600, Scot W. Hetzel wrote:
You could try the patch I've attached:
cd /usr/src
zcat c++-wchar.diff.gz | patch
cd gnu/lib/libstdc++
make
make install
...
Attached is the patch
This would pull files off the vendor branch; and before
Form a -CURRENT of yesterday:
flag@newluxor$ cat /dev/sndstat
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: at io 0x220 irq 5 drq 1 bufsz 4096d (1p/1r/0v c
hannels duplex default)
flag@newluxor$
but when i try to play any song i get this msg:
cm0:play:0: play interrupt timeout, chann
I found 2 bugs and some potential problems in bktr(4) code.
Bug 1:
Compilation with options BKTR_USE_FREEBSD_SMBUS failes. Error is
that code tries to use iicbus which isn't defined where it looks for
it. I added it there and the compilation and detection goes fine. I don't
know how to actually te
My problems with the nvidia driver starts at early time, acpi
disabled, bios pnp support to no, a kernel without optimisations and
architecture specific stuff... no INVARIANT things
The driver will not be activated...
so X is far far away...
Dec 1 14:24:04 Twoflower kernel: nvidia0: mem
0xd
56 matches
Mail list logo
