T Kellers wrote:
...and subsequent kernel build/install with device pcm, not only
didn't I have any pcm line in my dmesg, but I didn't have any snd_maestro3.ko
entries in /boot/kernel...
That's pretty weird. Do you have any other snd_* modules in /boot/kernel?
You don't have NO_MODULES in /etc
To all of you who celebrate Thanksgiving today, I wish you a happy one!
And speaking of turkeys, does anyone know how Microsoft handles the
performance issues associated with dynamic linking? Do they do
anything special, or just ignore the whole thing?
Brooks Davis answered:
walt asked:
What does 'buildworld' give us that the new kernel might need?
The correct toolchain including the compiler and config(8).
Okay, thanks, that helps.
Just thinking out loud about worst-case examples for people who
do routinely use 'make world&#x
Kevin Oberman wrote:
...Because changes are applied that will allow smooth upgrades
when the kernel is built after the new system is built, but before it is
installed, "make world" is increasingly unlikely to work...
The recent statfs changes demonstrated why the 'makeworld' > 'makekernel'
sequenc
Terry Lambert wrote:
"Robert M.Zigweid" wrote:
I'll admit to being mostly a lurker here, but isn't the point of /sbin
to be statically linked. That's what the 's' stands for?
Second question. This seems to imply that /sbin and /bin both have to
have the same behavior? I have no problem with /bi
I found that the new statfs changes cause nautilus to crash on startup.
The fix is to recompile/reinstall devel/gnomevfs2.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAI
I got this nonsensical error from sed while trying to update python:
/usr/bin/sed -i.bak -e 's,/usr/doc/python-docs-,/usr/local/share/doc/python,g'
/usr/ports/lang/python/work/Python-2.3.2/Lib/pydoc.py
sed: /usr/ports/lang/python/work/Python-2.3.2/Lib/pydoc.py: No such file or directory
But the
I'm trying to compile mozilla thunderbird on -current and the
configure program stops with this error:
checking whether C++ compiler has -pedantic long long bug... yes
configure: error: Your compiler appears to have a known bug where
long long is miscompiled when using -pedantic.
Reconfigure using
Harald Schmalzbauer wrote:
--Boundary-02=_Nn+R/bAN6Fk+pt3
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline
Hi all,
I can confirm something is wrongwith pcm.
I have no sound output with todays ker
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
The previous kernel compiled on July 22 worked fine
and I've made no changes to the kernel configuration.
I'm using the standard GENERIC.hints fil
walt wrote:
> sio0: configured irq 4 not in bitmap of probed irqs 0
> sio0: port may not be enabled
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
>
I changed the Plug-n-Play BIOS setting and now it works
normally again.
I also changed the ACPI-aware-OS
Karel J. Bosschaart wrote:
Hi,
After googling and searching in the mailing list archive I still can't
figure out how to make device nodes in -current when devfs doesn't do this
automatically. I have an external USB-drive (external 3.5" case with leftover
1.6 GB HD) from which I want to mount /d
Is this the expected output for an unexpected input?:
$ who /etc
. May 9 03:09 (? )
netconfig?? Jan 10 11:57 ()
ices Oct 23 13:41 (hosts)
bSep 8 18:48 (gnats)
Jan 10 11:31 (?<)
e
Poul-Henning Kamp wrote:
I have uploaded a proof of concept patch:
http://phk.freebsd.dk/patch/fd_dev.patch
...And with this code enabled, it is possible to go from userland to
device driver without touching Giant underway.
I'm sorry, I can't parse that last sentence. Could you explain in
25
Juan Rodriguez Hervella wrote:
Hello:
I've got a PCI-NVidia Riva TNT 64 video card at home,
and I've tried to compile the drivers but it doesn't work,
and after changing the source to let the compilation progress,
when the module is loaded I've received a "kernel panic".
Im using FreeBSD-5.1 with
cc -O -pipe -mcpu=pentiumpro -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -std=gnu99 -c
i387_e_acos.S -o i387_e_acos.o
{standard input}: Assembler messages:
{standard input}:19: Error: junk `(__ieee754_acos)' after expression
{standard input}:19: Error: junk `(__ieee754_acos)' after expression
*** Error
cc1: warnings being treated as errors
/usr/src/sys/i386/linux/linux_sysvec.c: In function `linux_elf_modevent':
/usr/src/sys/i386/linux/linux_sysvec.c:928: warning: implicit declaration of function
`linux_mib_destroy'
___
[EMAIL PROTECTED] mailing list
h
CARTER Anthony wrote:
Xfree requires wrapper but seems to break GDM for user logins. Is this
normal, and can I force un-install wrapper without breaking anything?
Excuse me, I'm a bonehead. You don't need to uninstall wrapper, just
change this symbolic link:
/usr/X11R6/bin/X@ -> Xwrapper-4
to thi
CARTER Anthony wrote:
Hi,
I updated XFree86 this morning after a cvsup using portupgrade -r...did
all packages for XFree86 (Server, libraries etc. etc.)
I now have a problem with GDM...
I can log in as root using the GDM, but if I log in as another user, it
pops a message up about my session not
Dag-Erling Smørgrav wrote:
walt <[EMAIL PROTECTED]> writes:
... Looking thru sys/geom I don't see any
such ifdefs in your code, so I still don't know why the
recent geom bug was hidden by INVARIANTS.
On the contrary, there is a lot on INVARIANTS-specific code in GEOM:
[EMAIL
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, walt writes:
If inclusion of INVARIANTS serves to disguise bugs in
the kernel, I wonder if kernel committers should be
using this option routinely?
Please check into our current reality :-)
Hm. How do I parse that sentence? If y
If inclusion of INVARIANTS serves to disguise bugs in
the kernel, I wonder if kernel committers should be
using this option routinely?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Bryan Liesner wrote:
On Sun, 16 Mar 2003, Poul-Henning Kamp wrote:
One thing I'd like you to try is to remove any trace of USB from your
systems. USB does some ugly VOP_REVOKES which I am not happy about, and
I would like to exclude them from the list of suspects.
You can remove USB from your
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, walt writes:
I've been unable to boot any kernel I've built since about March 11
and I've narrowed it down to the GEOM_MBR option.
With GEOM_MBR I get a kernel page fault error when trying to
mount the root filesystem a
So far today this file has been updated four times and it still
won't compile. Can this be debugged off-line before being committed?
I'm trying to debug another problem and I haven't been able to work
on it all day because of this problem.
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
I've been unable to boot any kernel I've built since about March 11
and I've narrowed it down to the GEOM_MBR option.
With GEOM_MBR I get a kernel page fault error when trying to
mount the root filesystem at boot time.
ad0: 76319MB [155061/16/63] at ata0-master UDMA100
ad1: 76319MB [155061/16/63]
CARTER Anthony wrote:
Hi lads and lassies,
I just tried to do a build world that failed, so I tried re-running it
and it told me directory not empty (/usr/obj/usr/src/i386*)...Funny,
even though the first thing it does is an rm -rf of that directory...
So I tried to do it manually (of course as ro
04:00 GMT Mar 12:
Just cvsup'd and rebuilt with same result as 12 hours ago --
I see a kernel panic "page fault while in kernel mode" just
after attempting to mount the root filesystem.
The kernel from yesterday works fine and when I reboot the
filesystems come up clean, so the new kernel nevers w
After cvsup/rebuild today at about 14:00GMT I now get a
'page fault while in kernel mode' just after the system
tries to mount the rootfs.
Yesterday's kernel still works fine, and the filesystem
came up clean, so I guess the new kernel didn't get far
enough to write anything to disk.
To Unsubscribe
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, walt writes:
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
Yes, fixed n
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Because of the repeated breakage of the proprietary nVidia driver
in -CURRENT I've been trying out the native XFree86 'nv' driver
with some puzzling results. Maybe one of the nVidia whiz-kids
in this group can explain:
I reboot the machine, then start the X server. The X server
immediately aborts
Andre Guibert de Bruet wrote:
If you really need to use your workstation, you can try the open source nv
XFree86 driver. It's not as fast as the nVidia detonator driver and it's
not accelerated, but you can at least use X11 at a reasonable resolution
and color depth.
It works well enough for my pu
Michael Hostbaek wrote:
--ncSAzJYg3Aa9+CRW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi,
I cvsup'ed my source this morning, and after a successfull 'make
buildworld' I launch 'make buildkernel KERNCONF=3DGENERIC' - shortly af
My mini 'disaster' of earlier today was caused by the nvidia kernel
module being autoloaded at boot, which causes an immediate kernel panic.
The newest kernel seems fine until I try to load the module manually,
at which time I still get the kernel panic even after re-compiling
the module.
Maxime, i
Andre Guibert de Bruet wrote:
On Mon, 3 Mar 2003, walt wrote:
After cvsup'ing just now I cannot reboot -CURRENT either with the new
kernel or the old kernel.
The new kernel panics instantly on boot, and the old kernel halts
with multiple messages about ACPI, so I'm stuck with an
After cvsup'ing just now I cannot reboot -CURRENT either with the new
kernel or the old kernel.
The new kernel panics instantly on boot, and the old kernel halts
with multiple messages about ACPI, so I'm stuck with an unbootable
machine.
What is the command to disable acpi at the boot prompt? I tr
Matt Smith wrote:
What does your Drive Layout look like? Is your W2k partition FAT32?
Has it always been the first partition on the drive, or did you move it,
using something like partition magic? Is freeBSD in the extended
partition?
-Matt
On Tue, 2003-02-25 at 11:58, Andrew Boothman wrote:
Qu
Maxime Henrion wrote:
--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Hi all,
Recent interface changes made the nVidia driver unbuildable on -CURRENT.
The attached patch should make it work as it used to. Please let me
know if it doesn't.
Yes! [Big kis
Just finished a cvsup and rebuild of world/kernel and now my
X server refuses to start:
(EE) NVIDIA(0): Failed to initialize the NVdriver kernel module!
The proprietary nvidia.ko module from nVidia still loads normally
with no error messages during system boot.
There is also a warning about a 'pos
David Wolfskill wrote:
Date: Mon, 24 Feb 2003 07:39:08 -0800
From: walt <[EMAIL PROTECTED]>
After this morning's cvsup I now get a 'syncing disks...giving up
on three buffers' error message when shutting down the system and
the filesystem doesn't get properly dismounted
Jan Stocker wrote:
Jan Stocker wrote:
Before blaming me, i know it is not supported for 5.x or -current, but i
think some of us have that stuff already running on -current.
I've been in hospital for many weeks and now i updated my system (late
November) to the currents current. After adding the mi
After this morning's cvsup I now get a 'syncing disks...giving up
on three buffers' error message when shutting down the system and
the filesystem doesn't get properly dismounted.
For the last four days I could never shut the system down cleanly
because of the nVidia driver problem causing a kernel
walt wrote:
Jan Stocker wrote:
Before blaming me, i know it is not supported for 5.x or -current, but i
think some of us have that stuff already running on -current.
I've been in hospital for many weeks and now i updated my system (late
November) to the currents current. After adding the mi
Jan Stocker wrote:
Before blaming me, i know it is not supported for 5.x or -current, but i
think some of us have that stuff already running on -current.
I've been in hospital for many weeks and now i updated my system (late
November) to the currents current. After adding the missing include, i
suc
Terry Lambert wrote:
walt wrote:
This problem started about Feb 19 and continues thru today's updates.
Everything seems to work great until I shut down the X server
at which time I get a fatal 'page fault while in kernel mode.'
I have two -CURRENT machines at the moment and only t
This problem started about Feb 19 and continues thru today's updates.
Everything seems to work great until I shut down the X server
at which time I get a fatal 'page fault while in kernel mode.'
I have two -CURRENT machines at the moment and only the one
with the nVidia driver (and kernel module)
Hiten Pandya wrote:
On Fri, Feb 07, 2003 at 07:49:54PM -0800, walt wrote the words in effect of:
Hiten Pandya wrote:
Hi gang.
Recently removing the NO_GEOM option from my kernel; I noticed that my
dos extended slices dev entries disappeared under a GEOM kernel...
I've been using ext
Hiten Pandya wrote:
Hi gang.
Recently removing the NO_GEOM option from my kernel; I noticed that my
dos extended slices dev entries disappeared under a GEOM kernel...
I've been using extended slices on both -stable and -current for
quite a while without any problems, both with and without GEOM.
Soeren Schmidt wrote:
Just reply to this message with the output from pciconf -l and you
have helped me sort out the myriads of SiS chipsets out there.
~# pciconf -l
chip0@pci0:0:0: class=0x06 card=0x chip=0x55911039 rev=0x02 hdr=0x00
atapci0@pci0:0:1: class=0x010180 card=0x5
Steve Kargl wrote:
On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
Is there any reason, on newer motherboards, to need the MAXMEM option?
I don't know. I've always used MAXMEM. Guess it's
time to remove it from my kernel config file.
FWIW, I've been using FBSD -stable and -cu
Poul-Henning Kamp wrote:
This is the final call for users using NODEVFS and NO_GEOM options!
I marvel at my own temerity. I normally would never presume to speak
for Bruce Evans but I haven't seen a post from him for many days. I
think he would probably object to eliminating NO_GEOM based on h
cc1: warnings being treated as errors
/usr/src/sys/kern/sysv_msg.c: In function `msgsnd':
/usr/src/sys/kern/sysv_msg.c:775: warning: cast discards qualifiers from pointer target type
/usr/src/sys/kern/sysv_msg.c:818: warning: cast discards qualifiers from pointer target type
*** Error code 1
To
walt wrote:
Damien U wrote:
Hello,
I will firstly say that although I am not experienced with freeBSD, I have been using Linux for some time. I obtained the first ISO in the set for FreeBSD 5.0-RELEASE last saturday, here are the problems I have been experiencing whilst attempting to install
Damien U wrote:
Hello,
I will firstly say that although I am not experienced with freeBSD, I have been using Linux for some time. I obtained the first ISO in the set for FreeBSD 5.0-RELEASE last saturday, here are the problems I have been experiencing whilst attempting to install it.
2) Cannot
Where can I find the definitions for the AJ, aj, HR<, etc. that
are being discussed in the 'performance' thread?
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sheldon Hearn wrote:
Hi folks,
Could someone with an up-to-date -CURRENT (as of anything since
Wednesday last week) and OpenOffice let me know whether OpenOffice's
swriter works?
Mine definitely works okay, but I recompiled mine on Jan 14 just after
Martin applied some patches. You may get bet
While trying to debug a linux sound driver on my new ASUS A7V8X
mobo I changed the Plug-n-Play OS setting from 'no' to 'yes'
in the BIOS.
When I rebooted the machine back into FreeBSD I got watchdog
timer error messages from the Broadcom (bge) ethernet driver
and the network was unreachable in spi
[EMAIL PROTECTED] wrote:
Julian Elischer writes:
I think that one of the things we need to do is declare a new flag in
disklabel that declares that the disklabel has been converted to use
relative offsets...
Better plan: Abandon BSD labels before disks outgrow them.
To be replaced bywh
Sean Kelly wrote:
--UlVJffcvxoiEqYs2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Jan 12, 2003 at 12:49:46PM +0100, [EMAIL PROTECTED] wrote:
There is an erratum on "disklabel -B" for 5.0-RELEASE.
So how the hell d
cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c
/usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o
/usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
/usr/src/lib/libkvm/kvm_proc.c:376: structure has no member named `ke_pctcpu'
To Unsubscribe: send mail to [EMAIL PROTECTED]
David Holm wrote:
Hi,
it's getting boring seeing all the nvidia posts but I'm so darn close to
having it working here...
May I ask what you've done to get as far as you have? I have their
driver working okay on -STABLE but of course it won't even compile
on -CURRENT and I don't know enough to
[EMAIL PROTECTED] wrote:
In message <[EMAIL PROTECTED]>, walt writes:
>VOP_STRATEGY on VCHR
>: 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags
(VV_OBJBUF),
>Sorry, need DDB option to print backtrace
>
>That feels like an error message (so
After updating world and kernel this evening I saw this message fly by
during the reboot:
Mounting root from ufs:/dev/ad0s3a
VOP_STRATEGY on VCHR
: 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF),
Sorry, need DDB option to print backtrace
That feels like
I've installed RC2 on my new ASUS A7V8X/AthlonXP and the
whole thing went very well except for building XFree.
X does compile with no complaints but when I attempt to
run it I get unresolved symbol errors and then a coredump.
I'm not asking for a fix here, really, so I won't bother
you with debug
Willem Jan Withagen wrote:
Hi,
I'm trying to edit my disklabels to create some swap on just all of them,
however when I try to do so, I get:
---
files# disklabel -w -B ad4s1 auto
disklabel: ioctl DIOCSDINFO: open partition would move or shrink
---
This is in single user
Martin Hasenbein wrote:
Hoi,
I've tried to upgrade to -current a few minutes ago.
Before upgrading I had FreeBSD 4.7-RELEASE-p2
After a "make buildworld / make buildkernel /make installkernel"
and erbooting, I still have FreeBSD 4.7-RELEASE-p2
Sounds like you are rebooting with the old kernel
Aleksander Rozman - Andy wrote:
Hi !
I am back at developing some stuff for FreeBSD, but I am again getting
"warnings are treated as errors" problem and it seems that -DNO_WERROR
doesn't work anymore. Is there a solution for this? I use gcc (Prerelease
3.1). Must I recompile world again?
I don
[EMAIL PROTECTED] wrote:
In message <[EMAIL PROTECTED]>, Craig Rodrigues writes:
>Hi,
>
>I just did a cvsup and rebuilt my kernel, and now my kernel
>panics upon bootup. I don't have a serial console, so I wrote
>down the error messages that I saw:
>
>I saw this one in the middle of some GEOM d
walt wrote:
I built world+kernel about an hour ago ( Dec 17 about 23:00 UTC)
and the kernel hangs in the middle of printing phk's GEOM diagnostics:
I noticed some GEOM-related commits in today's cvsup, but unfortunately
they didn't solve this problem. The kernel still hangs
I built world+kernel about an hour ago ( Dec 17 about 23:00 UTC)
and the kernel hangs in the middle of printing phk's GEOM diagnostics:
ad0: 76319MB [155061/16/63] at ata0-master UDMA100
ad2: 42934MB [87233/16/63] at ata1-master UDMA66
acd0: CD-RW at ata1-slave PIO4
MBREXT Slice 15 on ad0s4:
Matthew Dillon wrote:
:
:Matt Dillon wrote:
:> Thanks to my dear friend Warner Losh. I've decided to leave FreeBSD and
:> flame in another project. Maybe I could join OpenBSD, the seem to share
:> my views on how to deal with other people
Sorry, Matt, but if you don't see the humor in this
[EMAIL PROTECTED] wrote:
Because few if any 80386 computers have the ram it takes to run sysinstall.
Was sysinstall around when 386 was new? Just curious what's changed since
then to make it bigger.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bod
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
Poul-Henning Kamp wrote:
From the next branch on -current, it is my intent to not install
BSD labels anymore, but switch to GPT instead, (possibly encapsulated
in an BSD MBR slice for legacy systems).
Do you mean this GPT:
http://www.microsoft.com/hwdev/tech/storage/GPT_FAQ.asp
or are you s
I noticed David Xu's changes to libpthread this morning, so I did
a "make libraries" and noticed with surprise that libpthread.so.5
was still dated Sep 16.
I then did 'cd /usr/src/lib' and a 'make' and noticed that
libpthread did not show up during the make.
At that point I looked at /usr/src/lib
mkdep -f .depend -a -nostdinc -I../../../../netgraph/bluetooth/include -D_KERNEL
-DKLD_MODULE -I- -I../../../../netgraph/bluetooth/include -I. -I@ -I@/dev -I@/../include
-I/usr/obj/usr/local/mnt/src/i386/usr/include
/usr/local/mnt/src/sys/modules/netgraph/bluetooth/bluetooth/../../../../netgra
Buildkernel dies without "device bpf" in the config file.
I think this is due to Sam's commit on 11-14 changing
sys/net/bpf.c and bpf.h.
Anyone else seeing this?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I see these changes were made about four days ago and I seem to be the only one
having problems. BTW, I don't use "device bpf" in my kernel config.
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-
I have two identical installations of -CURRENT on one machine.
The only difference is that one is on a UDMA100 disk and the other
is on a UDMA66 disk. Both have softupdates enabled.
The total times for a make world && make kernel:
UDMA100: 88 minutes
UDMA66 : 95 minutes
Does this seem an approp
Horen wrote:
Posted a week ago the question, didn't get any reaction.
Everything with current from last night works fine but killing
X or logging out ends in a black screen. No way to activate the
display without reboot. Remote login is fine. Typing blind works
too.
I have exactly the same prob
Hiten Pandya wrote:
On Sat, Nov 02, 2002 at 10:38:33AM -0800, walt wrote the words in effect of:
Hiten Pandya wrote:
Hmm, OK.
Let me rephrase it all.
I have a 120G IDE disk, which is under LBA mode. It is the second disk
on my system. I have been using it with my old (julyish) -current
Hiten Pandya wrote:
Hmm, OK.
Let me rephrase it all.
I have a 120G IDE disk, which is under LBA mode. It is the second disk
on my system. I have been using it with my old (julyish) -current for a
while now as a backup disk thingy.
My disk layout:
ad1s1: 8997MB FreeBSD slice
ad1s3: 50995MB
Hiten Pandya wrote:
Hi there.
I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G
harddrive, which is the second one on the system. Sysinstall failed to get
the right geometry of the disk, even though the BIOS was in LBA mode.
My 50G FreeBSD partition (ad1s3) as two parti
Yamada Ken Takeshi wrote:
I have an error for a week and cannot make buildworld.
Where can I find "panic" other than real panic?
===> sbin/gbde
: : : :
cc -O -pipe -mcpu=pentiumpro -I/usr/src/sbin/gbde/../../sys -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c template.c
cc1: warning
John Baldwin wrote:
On 22-Oct-2002 walt wrote:
Alexander Kabaev wrote:
On Tue, 22 Oct 2002 11:08:29 -0700
walt <[EMAIL PROTECTED]> wrote:
I'm confused about the -CURRENT emacs breakage...
...could be worked around by linking
[x]emacs binary with -znocombreloc.
Hmm. I
Alexander Kabaev wrote:
On Tue, 22 Oct 2002 11:08:29 -0700
walt <[EMAIL PROTECTED]> wrote:
I'm confused about the -CURRENT emacs breakage...
...The code
in [x]emacs is not prepared to deal with the change in format and thus will
have to be fixed, or the while issue could be worke
I'm confused about the -CURRENT emacs breakage. Is this
an O.S. breakage which will eventually be fixed, or a
permanent change which will require a patch to emacs?
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
walt wrote:
While compiling the open-motif port on -CURRENT I see this
error during the 'configure' phase. Anyone else seeing this?
checking for vprintf... yes
checking whether sprintf returns void... Bus error (core dumped)
yes
checking for wcslen... yes
Sorry, this is not a -CURRE
While compiling the open-motif port on -CURRENT I see this
error during the 'configure' phase. Anyone else seeing this?
checking for vprintf... yes
checking whether sprintf returns void... Bus error (core dumped)
yes
checking for wcslen... yes
===
This
I'm having problems with emacs 20.7 running under X:
#emacs
Fatal error (11).Segmentation fault (core dumped)
but emacs -nw works fine (i.e. without X).
This started after doing a portupgrade -fa to solve
the _sF symbol problem.
I've recompiled every package that emacs depends on
and still no c
Bruce Evans wrote:
> On Wed, 16 Oct 2002, walt wrote:
>
>
>>Bruce Evans wrote:
>>
>>
>>>Don't use extended partitions directly. It is easy to
>>>make a mess by clobbering the pointers to the logical drive
>>>within them.
>>I ne
Bruce Evans wrote:
> Don't use extended partitions directly. It is easy to
> make a mess by clobbering the pointers to the logical drive
> within them.
I need to ask for clarification on this point. What do you
mean by 'directly'?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
[EMAIL PROTECTED] (Bruce Evans) writes:
> On Tue, 15 Oct 2002, walt wrote:
> > Well, disklabel won't work on an extended/logical partition...
> Um, disklabel works on any slice. E.g.:
> ttyv1:root@gamplex:/tmp> disklabel ad2s3
> #size offsetfst
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, walt writes:
>
>>Would the GEOM framework make it feasible to use a DOS-extended/logical
>>partition for a BSD filesystem?
> We already support that as far as I know, both with and without GEOM
Yes! The r
Would the GEOM framework make it feasible to use a DOS-extended/logical
partition for a BSD filesystem? This would add a great deal of
flexibility for adding disk space to a full filesystem, just as one
example.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
BOUWSMA Beery wrote:
> ...That is, your kernel can mount the NetBSD partitions with their 16
> partitions within, even if `disklabel' doesn't work yet...
Heh, I just mounted the NBSD partition using an un-patched FBSD kernel
with GEOM, even though disklabel (recompiled) refuses to list it.
Here'
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Jens Schweikhardt writes:
>
>>Poul-Henning et al,
>>
>>recently I've tried installing NetBSD on a new disk. I'm not sure if the
>>following is a coincidence (because it never worked before, even without
>>GEOM) or is due to GEOM issues. M
Following the gcc/binutils update:
arch-utils.o(.data+0x40): undefined reference to `bfd_elf32_i386_vec'
*** Error code 1
Stop in /usr/src/gnu/usr.bin/binutils/gdb.
Anyone else seeing this?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mes
I trotted out xfontsel to use as a sharp stick to poke at this
bug. I certainly succeeded at crashing the X server with it
repeatedly, but the crashes are non-deterministic. The same
choice of font and fontsize will not reliably crash each time.
The wierd thing I did find is that, after crashin
1 - 100 of 179 matches
Mail list logo
