Re: Makefile.inc1 warning
On Fri, Aug 09, 2002 at 07:41:44AM +0200, John Hay wrote: Hi Ruslan, During make release I see a lot of these messages: # make: no target to make. /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/shar e/mk CPUTYPE=i386 -V CPUTYPE returned non-zero status make: no target to make. /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/shar e/mk CPUTYPE=i386 -V CPUTYPE returned non-zero status ## There was a bug in make(1) that got fixed in make/main.c,v 1.68. Because these warning are harmless, I decided to not force the upgrade of installed make(1) in this case from src/Makefile. (This was already reported on -current on August 7, in the Makefile.inc1 thread, and a similar reply.) Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg41715/pgp0.pgp Description: PGP signature
Re: phk malloc() sometimes forget to set errno
In message [EMAIL PROTECTED], Andrey A. Chernov writes:
I found at least one case:
Try this patch:
Index: malloc.c
===
RCS file: /home/ncvs/src/lib/libc/stdlib/malloc.c,v
retrieving revision 1.70
diff -u -r1.70 malloc.c
--- malloc.c30 May 2002 21:59:16 - 1.70
+++ malloc.c9 Aug 2002 07:12:53 -
@@ -1093,6 +1093,7 @@
wrtwarning(recursive call\n);
malloc_active--;
THREAD_UNLOCK();
+ errno = EPERM;
return (0);
}
if (!malloc_started)
@@ -1108,6 +1109,8 @@
THREAD_UNLOCK();
if (malloc_xmalloc !r)
wrterror(out of memory\n);
+if (!r)
+ errno = ENOMEM;
return (r);
}
@@ -1120,6 +1123,7 @@
wrtwarning(recursive call\n);
malloc_active--;
THREAD_UNLOCK();
+ errno = EPERM;
return;
}
if (ptr != ZEROSIZEPTR)
@@ -1142,6 +1146,7 @@
wrtwarning(recursive call\n);
malloc_active--;
THREAD_UNLOCK();
+ errno = EPERM;
return (0);
}
if (ptr !malloc_started) {
@@ -1170,6 +1175,8 @@
THREAD_UNLOCK();
if (malloc_xmalloc err)
wrterror(out of memory\n);
+if (err)
+ errno = ENOMEM;
return (r);
}
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Makefile.inc1 warning
On Fri, Aug 09, 2002 at 07:41:44AM +0200, John Hay wrote: Hi Ruslan, During make release I see a lot of these messages: # make: no target to make. /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/shar e/mk CPUTYPE=i386 -V CPUTYPE returned non-zero status make: no target to make. /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/shar e/mk CPUTYPE=i386 -V CPUTYPE returned non-zero status ## There was a bug in make(1) that got fixed in make/main.c,v 1.68. Because these warning are harmless, I decided to not force the upgrade of installed make(1) in this case from src/Makefile. (This was already reported on -current on August 7, in the Makefile.inc1 thread, and a similar reply.) I missed the part that it was a make problem. I saw a commit to Makefile.inc1 and after that I still had the problem. :-/ I'll update make and try again. Thanks. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: phk malloc() sometimes forget to set errno
On Fri, Aug 09, 2002 at 09:11:02 +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Andrey A. Chernov writes: I found at least one case: Try this patch: I doubt about choosed EPERM code. According to intro(2) it refers to some priviledges required for operation, but recursive call is not restricted due to priviledges. What about of other code, like EFAULT? Other than that it looks good, please commit. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[no subject]
Building of x11-fonts/webfonts gives this message: /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored Which breaks portupgrade Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
w/uptime warning inappropriately under xdm/kdm [patch]...
I've switched one of my desktops to using kdm and I've noticed that
w(1) creates suprious warnings because it can't find the tty entry.
$ w
w: /dev/:0: No such file or directory
w: /dev/:0: No such file or directory
2:41AM up 49 mins, 0 users, load averages: 0.05, 0.04, 0.04
USER TTY FROM LOGIN IDLE WHAT
$
I've included a patch that quiets this. The attached patch is inline
with the behavior from who(1). Are there any objections to it? What
should be the correct behaviour when loggin in via xdm/kdm? Is there
a better way to detect that you're logged in via xdm/kdm? Should w(1)
iterate through utmp/wtmp to get user info? -sc
--
Sean Chittenden
Index: w.c
===
RCS file: /home/ncvs/src/usr.bin/w/w.c,v
retrieving revision 1.54
diff -u -r1.54 w.c
--- w.c 2002/06/07 01:41:54 1.54
+++ w.c 2002/08/09 09:57:17
-491,11 +491,10
char ttybuf[MAXPATHLEN];
(void)snprintf(ttybuf, sizeof(ttybuf), %s%.*s, _PATH_DEV, sz, line);
- if (stat(ttybuf, sb)) {
- warn(%s, ttybuf);
+ if (stat(ttybuf, sb) == 0) {
+ return (sb);
+ } else
return (NULL);
- }
- return (sb);
}
static void
Re: 3 floppy system for -current releases
Hi, I think MSDOS installs are pretty rare and NFS ones even rarer (FTP is easier to setup) Survey time! :) I use NFS installs a lot, both with floppies and with pxeboot'd sysinstall. I've never had much luck with FTP installs from a remote server. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Compiler error XFree86-Server
On Fri, Aug 09, 2002 at 08:13:55AM +0200, Marc Recht wrote:
Because chances are good that the bugs still aren't fixed. I reported a
bug related to optimization with -march=athlon recently and the reply
If you've got a newer Athlon (XP) then you could compile it with -march=athlon-xp.
I've filed a PR with a patch against bsd.cpu.mk (misc/41425) recently.
I'll have to check that out and compare with the athlon-{m,x}p changes in
my tree.
I've got suggests that it's still present in all branches. I get the
impression that not too many people really use gcc3 with heavy
optimization on big stuff like XFree86 yet ... Of course, updating the
XFree86 works like a charm built with -march=athlon-xp .
I do know that compiling XFree86 with a June 2002 GCC 3.1.1 prerelease
works fine on AMD x86-64 running SuSE with -O2 and -march specifying the
Hammer.
system compiler would make bug reports from -CURRENT users even more useful.
Indeed. IMHO going to 3.2 is the best we could do.
IMO going to 3.3 would be much better -- we can actually get our needs
better addressed as the compiler is still in development, but about to
head into code slush. We cannot affect GCC 3.2.1 too much due to it
being on a release branch, and point release.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Comments on Release Building for -current
In the last episode (Aug 08), David O'Brien said: On Sun, Aug 04, 2002 at 08:01:10PM +1000, Bruce Evans wrote: sorry, but some time ago I read here that gcc -O2 breaks our printf() in libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c, ... If someone could find the small segment of code where the optimizer screws up, and write a small program to demonstrate the problem, we would have a good chance of it getting fixed. Er, someone (Dan Lukes) has already done this. See PR 40209. It looks like this PR is against the system GCC 3.1. As such it isn't a very interesting bug report. Someone needs to test to see if this bug exists when using the gcc31 (gcc 3.1.1 release) port. It does. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: About 5.0 and Nvidia drivers
On Mon, Aug 05, 2002 at 12:58:03AM -0400, Alp ATICI wrote: I guess that is never going to be the case. Since ATI does not produce drivers for linux (or any other UNIX) and has no such plans (AFAIK). I don't know why you think that. I sent a week in Germany with ATI's FireGL Linux driver team. http://mirror.ati.com/support/driver.html certainly lists Linux/XFree86 as an OS choice and the various FireGL products. I bet one of these drivers would work with newer Radeon cards. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- === sbin/quotacheck /local0/scratch/des/src/sbin/quotacheck/preen.c:54:18: fsck.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /local0/scratch/des/src/sbin/quotacheck. *** Error code 1 Stop in /local0/scratch/des/src/sbin. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Comments on Release Building for -current
David O'Brien wrote: If someone could find the small segment of code where the optimizer screws up, and write a small program to demonstrate the problem, we would have a good chance of it getting fixed. Er, someone (Dan Lukes) has already done this. See PR 40209. It looks like this PR is against the system GCC 3.1. As such it isn't a very interesting bug report. Someone needs to test to see if this bug exists when using the gcc31 (gcc 3.1.1 release) port. df seems to be a rather nice quick testcase (thanks perky). Compiling libc with -O2, then compiling df with it yields output like this: Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 252M5M:7M54%/ devfs 1.0K 1.0K 0B:0%/dev /dev/da0s1f 3.2G 2.2G 757M75%/usr /dev/da0s1e 252M28M 204M %/var procfs 4.0K 4.0K 0B:0%/proc linprocfs 4.0K 4.0K 0B:0% The system gcc3 and all versions of gcc3 in our ports do this. gcc295 does not. Regards, -- Michael Nottebrock And the reasons? There are no reasons. msg41726/pgp0.pgp Description: PGP signature
Re: Compiler error XFree86-Server
David O'Brien wrote:
I've got suggests that it's still present in all branches. I get the
impression that not too many people really use gcc3 with heavy
optimization on big stuff like XFree86 yet ... Of course, updating the
XFree86 works like a charm built with -march=athlon-xp .
I do know that compiling XFree86 with a June 2002 GCC 3.1.1 prerelease
works fine on AMD x86-64 running SuSE with -O2 and -march specifying the
Hammer.
You might want to try the attached code-snippet I grabbed from the gcc
GNATS. It manages to ICE 3.1 and 3.2 with a lot of optimizations,
including pentium2/3/4 and athlon-* and is believed to trigger the same
bug that borks XFree86 here.
Compile with gcc -O -march=arch -c clacrt.c
Regards,
--
Michael Nottebrock
And the reasons? There are no reasons.
void foo ()
{
struct { float x, y; } c, *cp;
static float z;
while (1)
{
c.y = cp-y + cp-y;
z = c.y + 1.0;
}
}
-current build error
-current build error: mkdep -f .depend -a /usr/src/sbin/quotacheck/quotacheck.c /usr/src/sbin/quotacheck/preen.c /usr/src/sbin/quotacheck/../fsck_ffs/utilities.c /usr/src/sbin/quotacheck/preen.c:54:18: fsck.h: No such file or directory mkdep: compile failed *** Error code 1 Beech -- --- Beech Rintoul - SysAdmin - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: i386 tinderbox failure
=== sbin/quotacheck /local0/scratch/des/src/sbin/quotacheck/preen.c:54:18: fsck.h: No such file or directory Already fixed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Interrupt vs. polling on -current
Hackers, Can anyone shed some light on the following problem: OS: FreeBSD-current DP1 (dmesg attached) Laptop: Toshiba Tecra 8100 (docked) Hardware: 3Com Bluetooth USB dongle, 3Com Bluetooth PC-CARD Xircom CBT PC-CARD (with 16550A UART) First of all, irq 11 gets shared between PC-CARD controller, USB controller, NIC in docking station (see dmesg). Everything that i plug into PC-CARD slots also get irq 11 (which is normal - i think). Also i have disabled interrupt harvesting. My tests are very simple. I plug USB dongle and one PC-CARD and try to pump data between them as fast as possible. The data blocks sizes are between 63 and 1500 bytes. The Xircom card just does not work :( I' getting a lot of silo overflow messages no matter what i try. I checked list archives and source - not much look. Is sio driver totally hopeless? The 3Com PC-CARD is a little bit better, but after some time it also starting to drop bytes. This morning i change 3Com driver to use polling, and, to my extreme surprise it work much, much better now. Also the interrupt load (according to top) has reduced to at least half. I have not noticed any system slow down. So what is up this that? Does that mean that for slow devices like serial ports etc. polling is better? Does anyone tried to use polling in sio driver? I just can't believe that FreeBSD on my Pentium-III/600 can't handle lousy 500-700 interrupts a second from PC-CARD. Can anyone point me into right direction, because i'm obviously doing something wrong here. thanks, max Aug 9 10:10:08 beetle kernel: Copyright (c) 1992-2002 The FreeBSD Project. Aug 9 10:10:08 beetle kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 9 10:10:08 beetle kernel: The Regents of the University of California. All rights reserved. Aug 9 10:10:08 beetle kernel: FreeBSD 5.0-DP1 #20: Thu Aug 8 15:54:09 PDT 2002 Aug 9 10:10:08 beetle kernel: [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BEETLE Aug 9 10:10:08 beetle kernel: Preloaded elf kernel /boot/kernel/kernel at 0xc0374000. Aug 9 10:10:08 beetle kernel: Preloaded elf module /boot/kernel/nmdm.ko at 0xc03740a8. Aug 9 10:10:08 beetle kernel: Timecounter i8254 frequency 1193182 Hz Aug 9 10:10:08 beetle kernel: Timecounter TSC frequency 597786416 Hz Aug 9 10:10:08 beetle kernel: CPU: Pentium III/Pentium III Xeon/Celeron (597.79-MHz 686-class CPU) Aug 9 10:10:08 beetle kernel: Origin = GenuineIntel Id = 0x681 Stepping = 1 Aug 9 10:10:08 beetle kernel: Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE Aug 9 10:10:08 beetle kernel: real memory = 201195520 (196480K bytes) Aug 9 10:10:08 beetle kernel: avail memory = 191938560 (187440K bytes) Aug 9 10:10:08 beetle kernel: Pentium Pro MTRR support enabled Aug 9 10:10:08 beetle kernel: Using $PIR table, 10 entries at 0xc00f4ee0 Aug 9 10:10:08 beetle kernel: npx0: math processor on motherboard Aug 9 10:10:08 beetle kernel: npx0: INT 16 interface Aug 9 10:10:08 beetle kernel: pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard Aug 9 10:10:08 beetle kernel: pci0: PCI bus on pcib0 Aug 9 10:10:08 beetle kernel: pcib1: PCI-PCI bridge at device 1.0 on pci0 Aug 9 10:10:08 beetle kernel: pci1: PCI bus on pcib1 Aug 9 10:10:08 beetle kernel: pci1: display, VGA at device 0.0 (no driver attached) Aug 9 10:10:08 beetle kernel: isab0: PCI-ISA bridge at device 3.0 on pci0 Aug 9 10:10:08 beetle kernel: isa0: ISA bus on isab0 Aug 9 10:10:08 beetle kernel: isab1: PCI-ISA bridge at device 5.0 on pci0 Aug 9 10:10:08 beetle kernel: atapci0: Intel PIIX4 ATA33 controller port 0xfff0-0x at device 5.1 on pci0 Aug 9 10:10:08 beetle kernel: ata0: at 0x1f0 irq 14 on atapci0 Aug 9 10:10:08 beetle kernel: ata1: at 0x170 irq 15 on atapci0 Aug 9 10:10:08 beetle kernel: uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xff80-0xff9f irq 11 at device 5.2 on pci0 Aug 9 10:10:08 beetle kernel: usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 Aug 9 10:10:08 beetle kernel: usb0: USB revision 1.0 Aug 9 10:10:08 beetle kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Aug 9 10:10:08 beetle kernel: uhub0: 2 ports with 2 removable, self powered Aug 9 10:10:08 beetle kernel: uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.00/1.00, addr 2 Aug 9 10:10:08 beetle kernel: uhub1: 4 ports with 4 removable, self powered Aug 9 10:10:08 beetle kernel: pci0: bridge, PCI-unknown at device 5.3 (no driver attached) Aug 9 10:10:08 beetle kernel: pci0: unknown at device 9.0 (no driver attached) Aug 9 10:10:08 beetle kernel: pci_cfgintr_linked: linked (60) to hard-routed irq 11 Aug 9 10:10:08 beetle kernel: pci_cfgintr: 0:11 INTA routed to irq 11 Aug 9 10:10:08 beetle kernel: pcic0: Toshiba ToPIC100 PCI-CardBus Bridge irq 11 at device 11.0 on pci0 Aug 9 10:10:08 beetle kernel: pcic0: PCI Memory allocated: 0x4400 Aug 9 10:10:08 beetle kernel:
Re: Compiler error XFree86-Server
system compiler would make bug reports from -CURRENT users even more useful. Indeed. IMHO going to 3.2 is the best we could do. IMO going to 3.3 would be much better -- we can actually get our needs better addressed as the compiler is still in development, but about to head into code slush. We cannot affect GCC 3.2.1 too much due to it being on a release branch, and point release. But the GCC 3.3 release is targeted after 5.0-RELEASE (for Dec 15). And GCC 3.3.1 for Feb 15 2003. Using a pre-release compiler in a release version is IMHO somewhat risky. gcc 3.2 is scheduled for early August, so there's time enough to import and test it. Maybe even for 3.2.1. And the C++ ABI breakages/fixes will hapen with the 3.2 release... Just my 0.02ยค Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Compiler error XFree86-Server
You might want to try the attached code-snippet I grabbed from the gcc GNATS. It manages to ICE 3.1 and 3.2 with a lot of optimizations, including pentium2/3/4 and athlon-* and is believed to trigger the same bug that borks XFree86 here. XFree works fine (for me) with -O -march=athlon-xp (since days now). Compile with gcc -O -march=arch -c clacrt.c Yeah, this triggers the bug. :-) Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Interrupt vs. polling on -current
500 - 700 interrupts a second is a lot, depending on how long you stay in the interrupt handler before returning. 1 cent of info Johan -Original Message- From: ext Maksim Yevmenkin [mailto:[EMAIL PROTECTED]] Sent: Friday, August 09, 2002 2:19 PM To: [EMAIL PROTECTED] Subject: Interrupt vs. polling on -current Hackers, Can anyone shed some light on the following problem: OS: FreeBSD-current DP1 (dmesg attached) Laptop: Toshiba Tecra 8100 (docked) Hardware: 3Com Bluetooth USB dongle, 3Com Bluetooth PC-CARD Xircom CBT PC-CARD (with 16550A UART) First of all, irq 11 gets shared between PC-CARD controller, USB controller, NIC in docking station (see dmesg). Everything that i plug into PC-CARD slots also get irq 11 (which is normal - i think). Also i have disabled interrupt harvesting. My tests are very simple. I plug USB dongle and one PC-CARD and try to pump data between them as fast as possible. The data blocks sizes are between 63 and 1500 bytes. The Xircom card just does not work :( I' getting a lot of silo overflow messages no matter what i try. I checked list archives and source - not much look. Is sio driver totally hopeless? The 3Com PC-CARD is a little bit better, but after some time it also starting to drop bytes. This morning i change 3Com driver to use polling, and, to my extreme surprise it work much, much better now. Also the interrupt load (according to top) has reduced to at least half. I have not noticed any system slow down. So what is up this that? Does that mean that for slow devices like serial ports etc. polling is better? Does anyone tried to use polling in sio driver? I just can't believe that FreeBSD on my Pentium-III/600 can't handle lousy 500-700 interrupts a second from PC-CARD. Can anyone point me into right direction, because i'm obviously doing something wrong here. thanks, max To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: updated to August 5th kernel broke mozilla
Brooks Davis wrote: I recently updated my laptop's kernel to an August 5th version from an July 23rd one and mozilla started getting connection refused from everything. Lynx worked fine as did other network services like cvsup and ssh. Upgrading mozilla from 1.0_rc? to the latest version corrected the problem, but so did booting with an old kernel so something weird is going on. The ipv6_ipv4mapping variable in rc.conf has been changed to NO, which broke mozilla (mozilla's fault). A patch for the mozilla port has been added to the port to work around the problem. Other people reported this before, see the archives. Regards, -- Michael Nottebrock And the reasons? There are no reasons. msg41737/pgp0.pgp Description: PGP signature
Re: updated to August 5th kernel broke mozilla
Michael Nottebrock wrote: Brooks Davis wrote: I recently updated my laptop's kernel to an August 5th version from an July 23rd one and mozilla started getting connection refused from everything. Lynx worked fine as did other network services like cvsup and ssh. Upgrading mozilla from 1.0_rc? to the latest version corrected the problem, but so did booting with an old kernel so something weird is going on. The ipv6_ipv4mapping variable in rc.conf has been changed to NO And the default value of net.inet6.ip6.v6only to 1. Regards, -- Michael Nottebrock And the reasons? There are no reasons. msg41738/pgp0.pgp Description: PGP signature
partition problem
I have a machine I've been trying to get freebsd-current installed. Everytime I run the installation, it warns me that the freebsd slice does not start on cylinder (sorry, I don't remeber the exact wording) boundary. How can I create the slice that starts with cylinder boundary? I have a 20M harddrive the runs Windows + FreeBSD-current (which I'm trying to get up). I don't mind reinstalling everything but I need to know how to start the freebsd partition on the cylinder boundary. thanks, ed __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Is anyone else having trouble with dump(8) on -current?
[replying to an old message]
In message [EMAIL PROTECTED], Alexander Leidi
nger writes:
On 7 Mai, Benjamin Lewis wrote:
| DUMP: slave couldn't reopen disk: Interrupted system call
Try the attached patch. I also have a similar patch for restore. I don't
like the patch, I think I should use SA_RESTART with sigaction(), so
think about this patch as a proof of concept (if it solves your
problem).
I was just looking at PR bin/18319 when I remembered this message.
Many of the changes in your patch are not necessary I believe, as
read(2) will restart after a signal by default. How about just
fixing the open call that actually triggers the reported error? I
suspect that many of the other cases are either impossible or
extremely unlikely in practice. Could someone who can reproduce the
couldn't reopen disk error try the following?
Ian
Index: tape.c
===
RCS file: /dump/FreeBSD-CVS/src/sbin/dump/tape.c,v
retrieving revision 1.22
diff -u -r1.22 tape.c
--- tape.c 8 Jul 2002 00:29:23 - 1.22
+++ tape.c 9 Aug 2002 22:28:45 -
@@ -740,8 +740,11 @@
* Need our own seek pointer.
*/
(void) close(diskfd);
- if ((diskfd = open(disk, O_RDONLY)) 0)
+ while ((diskfd = open(disk, O_RDONLY)) 0) {
+ if (errno == EINTR)
+ continue;
quit(slave couldn't reopen disk: %s\n, strerror(errno));
+ }
/*
* Need the pid of the next slave in the loop...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Compiler error XFree86-Server
On Fri, Aug 09, 2002 at 09:26:32PM +0200, Marc Recht wrote:
IMO going to 3.3 would be much better -- we can actually get our needs
better addressed as the compiler is still in development, but about to
head into code slush. We cannot affect GCC 3.2.1 too much due to it
being on a release branch, and point release.
But the GCC 3.3 release is targeted after 5.0-RELEASE (for Dec 15).
Yes. But our 5.0-RELEASE is will non-polished; so I think having the
compiler in the same shape is OK if it means we can get bugs fixed and
our needs taken care of.
is IMHO somewhat risky. gcc 3.2 is scheduled for early August, so there's
time enough to import and test it. Maybe even for 3.2.1. And the C++
ABI breakages/fixes will hapen with the 3.2 release...
Many IA-64, and AMD x86-64 bug fixes and improvements aren't merged back
to the 3.{1,2} branch.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On The House-Gift Basket From Origins and Real Simple Magazine!
Warning Unable to process data: multipart/mixed;boundary==_NextPart_000_00B1_52B18C7B.A2703E37
