sparc64 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 >/tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- >>> Kernel build for GENERIC started on Sat Oct 26 07:58:58 GMT 2002 -- ===> ipfilter ./aicasm: 877 instructions used /tinderbox/sparc64/src/sys/kern/kern_sig.c:77:2: #error "You *really* want COMPAT_FREEBSD4 on -current for a while" mkdep: compile failed *** Error code 1 Stop in /tinderbox/sparc64/obj/tinderbox/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/sparc64/obj/tinderbox/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pppd not working on latest current 2002-10-20
Terry Lambert wrote: > Brooks Davis wrote: > > This isn't going to have an effect on the ability to use kernel ppp for > > other things. The tty orientation of pppd and the outdated, unmodular > > design on ppp(4) have taken care of that. This patch gives people > > the functionality they want (pppd just working) without any major > > entanglements (the whole function is <20 lines). If someone > > wants to make pppd work on arbitrary devices we can deal with that when > > it happens and I frankly doubt it's ever going to since we've got > > netgraph to do that with. > > Depending on the value of "sysctl kern.module_path", if the "if_ppp" > module does not exist, and one of the path components is writeable, > then this would permit you to abuse the pppd to load arbitrary modules > into the kernel. > > So I understand Bakul's complaint. > > But by the same token, "mount" and "ifconfig" have the same problems; > on the other hand, unlike pppd, they are not suid root. Just for the record, mount(8) does not load any kernel module anymore. The kernel will attempt to load the corresponding filesystem module at mount(2) time if it does not find support for it though. Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Type1 font problem (Was: Re: mozilla-devel problems)
According to Ollivier Robert: > During its reading of all fonts available, it get a segv... > Any idea ? Found that at least one of the Type1 fonts I had (installed by XFree86) does bad things to freetype and it was getting a segv. The interesting point is that it happens even if you have disabled the loading of the type1 module. Having the font in /usr/X11R6/lib/X11/fonts/type1 is enough... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current buildworld breakage
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: warnings being treated as errors
/usr/src/sys/crypto/rijndael/rijndael-api-fst.c: In function `rijndael_padEncrypt':
/usr/src/sys/crypto/rijndael/rijndael-api-fst.c:222: warning: implicit declaration of function `panic'
*** Error code 1
This is taken from my rijndael-api-fst.c:
for (i = numBlocks; i > 0; i--) {
rijndaelEncrypt(input, outBuffer, key->keySched, key->ROUNDS);
input += 16; /* this is line 222 */
outBuffer += 1;
}
I can't see how line 222 includes an implicit declaration of 'panic'.
Is your file different?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current buildworld breakage
Thank you for your prompt reply.
From: walt <[EMAIL PROTECTED]>
: ::
>
> I can't see how line 222 includes an implicit declaration of 'panic'.
>
> Is your file different?
>
I do not know why compiler says line 222, but it is
below 222 and my latest source says;
# cat rijndael/rijndael-api-fst.c
::::
switch (cipher->mode) {
case MODE_ECB:
for (i = numBlocks; i > 0; i--) {
rijndaelEncrypt(input, outBuffer, key->keySched, key->RO
UNDS);
input += 16;
outBuffer += 16;
}
padLen = 16 - (inputOctets - 16*numBlocks);
if (padLen > 0 && padLen <= 16)
panic("rijndael_padEncrypt(ECB)");
^^
bcopy(input, block, 16 - padLen);
for (cp = block + 16 - padLen; cp < block + 16; cp++)
*cp = padLen;
rijndaelEncrypt(block, outBuffer, key->keySched, key->ROUNDS);
break;
msg45377/pgp0.pgp
Description: PGP signature
Re: -current buildworld breakage
On Sat, Oct 26, 2002 at 10:13:02PM +0900, Yamada Ken Takeshi wrote:
> # cat rijndael/rijndael-api-fst.c
>
> ::::
> switch (cipher->mode) {
> case MODE_ECB:
> for (i = numBlocks; i > 0; i--) {
> rijndaelEncrypt(input, outBuffer, key->keySched, key->RO
> UNDS);
> input += 16;
> outBuffer += 16;
> }
> padLen = 16 - (inputOctets - 16*numBlocks);
> if (padLen > 0 && padLen <= 16)
> panic("rijndael_padEncrypt(ECB)");
> ^^
> bcopy(input, block, 16 - padLen);
> for (cp = block + 16 - padLen; cp < block + 16; cp++)
> *cp = padLen;
> rijndaelEncrypt(block, outBuffer, key->keySched, key->ROUNDS);
> break;
You don't have the latest sources. Did you use cvsup it
update your sources? If you used cvsup, then you
need to add src-sys-crypto to your cvsup file.
--
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current buildworld breakage
Thank you! From: Craig Rodrigues <[EMAIL PROTECTED]> > You don't have the latest sources. Did you use cvsup it > update your sources? If you used cvsup, then you > need to add src-sys-crypto to your cvsup file. It was my cvsup prroblem. Fixed!! msg45379/pgp0.pgp Description: PGP signature
Re: df problems ?
> This is all very true for 4.7, but what about earlier versions. > > I compiled fsck using 4.7 srcs, includes and hierarchy with 4.0 > libraries and tools, so that I could have an fsck I could use with my > 4.0 CDROM (the latest one I have, unfortunately) to repair any changes > made by my CURRENT system. It does compile with the same errors you get > on a true 4.7 system about unsigned/signed comparisons. It even works as > a program, but it does not repair the filesystem properly to be > compatible with 4.0. You get an instant panic when going multi-user. > This is a real nuisance as it blows my recovery strategy should I ever > need it. If someone could figure out how to fix this I would be grateful > until the time I get my hands on a 5.0 CDROM > I tried it again today and it worked (fsck'ing CURRENT drives with my fsck version 4.7 compiled for 4.0 ). I don't know why it failed yesterday. Is there any way of obtaining a list of superblocks on a fs, apart from making a note of the list newfs produces? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
burncd: ioctl(CDRIOCWRITESPEED): Input/output error
With current from yesterday, I get the following error when trying to burn a cd. I haven't burned one for probably a month or maybe more. If I remove the -s, the results are the same. Does anyone have a suggestion, fix or work around? # burncd -f /dev/acd0c -s 1 data cd0.raw20021022 fixate burncd: ioctl(CDRIOCWRITESPEED): Input/output error Thanks, ed -- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Another 'buildworld' showstopper
Hello, With sources few minutes old (as well as with sources approx. 3h old): ===> gnu/usr.bin/groff/tmac "/usr/src/gnu/usr.bin/groff/tmac/Makefile", line 2: warning: duplicate script for target "-s" ignored [... 12 times repeated] make: don't know how to make doc-common-s. Stop *** Error code 2 Stop in /usr/src/gnu/usr.bin/groff. *** Error code 1 Stop in /usr/src. *** Error code 1 PS: ... and it's an i386 and no alpha (see UPDATING) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 4.7-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-20021025-CURRENT snapshot
jwd> A new 5.0-20021025-CURRENT snapshot is available jwd> via anonymous ftp at usw2.freebsd.org: Wonderful! Is it a time to switch back 'current.FreeBSD.org' name to that machine? -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another 'buildworld' showstopper
> With sources few minutes old (as well as with sources approx. 3h old): > > ===> gnu/usr.bin/groff/tmac > "/usr/src/gnu/usr.bin/groff/tmac/Makefile", line 2: warning: duplicate > script for target "-s" ignored > [... 12 times repeated] > make: don't know how to make doc-common-s. Stop > *** Error code 2 > > Stop in /usr/src/gnu/usr.bin/groff. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > You have to rebuild and install make first. Marc -- "Premature optimization is the root of all evil." -- Donald E. Knuth signature.asc Description: This is a digitally signed message part
Re: 5.0-20021025-CURRENT snapshot
attila> only problem with snapshot.jp at this point is that attila> release does not build: md0 problems That should be a local problem IMO, and I believe it was fixed several hours before (ya, sorry for being lazy.) -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-20021025-CURRENT snapshot
- Daniel Flickinger's Original Message - > Sent: Sun, 27 Oct 2002 01:03:43 +0900 by MAR > > + jwd> A new 5.0-20021025-CURRENT snapshot is available > + jwd> via anonymous ftp at usw2.freebsd.org: > + > + Wonderful! Is it a time to switch back 'current.FreeBSD.org' name to > + that machine? > > NO! it is a fraction of what you have on snapshot.jp.freebsd.org > usw2.freebsd.org has a serious lack of disk space. If/when more disk space is added usw2 can become a standard 5.x distribution site again. Until then, it is limited to a small number of ftp'able install areas and an ISO (or two). -John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Type1 font problem (Was: Re: mozilla-devel problems)
On Sat, 26 Oct 2002, Ollivier Robert wrote: > According to Ollivier Robert: > > During its reading of all fonts available, it get a segv... > > Any idea ? > > Found that at least one of the Type1 fonts I had (installed by XFree86) does > bad things to freetype and it was getting a segv. > > The interesting point is that it happens even if you have disabled the loading > of the type1 module. Having the font in /usr/X11R6/lib/X11/fonts/type1 is > enough... Im my many hours of playing with fonts, I seem to recall that the Freetype / XFT module is perfectly capable of rendering the Type1 fonts. Make sure you take the PATH out of your XftConfig in addition to the XF86Config -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: you need to install a new kernel before an installworld.
Peter Wemm wrote: 'make installworld' without ... a new kernel would be rather messy. ... a reminder of the sequence is probably in order: buildworld buildkernel installkernel reboot installworld reboot This _does_not_work_ because 'installkernel' does not update the bootblocks. It should. Otherwise, 'installkernel' is not filling it's contract: it is not ensuring that the next boot uses the new kernel. An alternative: have installkernel link the new kernel file back to the old location, at least until 5.1. That way, either old or new boot blocks would boot the new kernel. (This may be the better approach all around; it leaves the downgrade option available for a little bit longer.) Tim Kientzle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: you need to install a new kernel before an installworld.
Quoting Tim Kientzle <[EMAIL PROTECTED]>: | Peter Wemm wrote: | | > 'make installworld' without ... a new kernel would be rather messy. | | > ... a reminder of the sequence is probably in order: | > buildworld | > buildkernel | > installkernel | > reboot | > installworld | > reboot | | | This _does_not_work_ because 'installkernel' does | not update the bootblocks. It should. Otherwise, | 'installkernel' is not filling it's contract: it is | not ensuring that the next boot uses the new kernel. | It has worked for me this morning. I seem to have successfully installed and rebooted 3 vastly different machines. Laptop, desktop and a scsi, raid10, server, with no noticable problems. Now you've made me very nervious ;-) ed | An alternative: have installkernel link the new kernel | file back to the old location, at least until 5.1. | That way, either old or new boot blocks would boot | the new kernel. (This may be the better approach | all around; it leaves the downgrade option available | for a little bit longer.) | | Tim Kientzle | | | | | To Unsubscribe: send mail to [EMAIL PROTECTED] | with "unsubscribe freebsd-current" in the body of the message | -- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: you need to install a new kernel before an installworld.
On Sat, Oct 26, 2002 at 11:42:02AM -0700, Tim Kientzle wrote: > Peter Wemm wrote: > > >'make installworld' without ... a new kernel would be rather messy. > > >... a reminder of the sequence is probably in order: > > buildworld > > buildkernel > > installkernel > > reboot > > installworld > > reboot > > > This _does_not_work_ because 'installkernel' does > not update the bootblocks. It should. Otherwise, > 'installkernel' is not filling it's contract: it is > not ensuring that the next boot uses the new kernel. It works fine if you are already running 5.x with the newer bootblocks. You should only have to do the bootblock update once. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Actual probs with 'ipfw'
Hi, I updated my kernel now just like told in the last HEADSUP and hesitate to do a 'make installworld' as also mentioned there... Now, during boot 'ipfw' complaines: ipfw: size mismatch (have 64 want 1064) ipfw: size mismatch (have 52 want 40) ipfw: size mismatch (have 52 want 40) This happens every time I run 'sh /etc/rc.firewall open'. Not to mention, that the firewall is closed perfectly :-/. I didn't run 'mergemaster' because of no installworld. Is that the problem? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Actual probs with 'ipfw'
Matthias Schuendehuette wrote: > Hi, > > I updated my kernel now just like told in the last HEADSUP and hesitate > to do a 'make installworld' as also mentioned there... > > Now, during boot 'ipfw' complaines: > > ipfw: size mismatch (have 64 want 1064) > ipfw: size mismatch (have 52 want 40) > ipfw: size mismatch (have 52 want 40) > > This happens every time I run 'sh /etc/rc.firewall open'. Not to > mention, that the firewall is closed perfectly :-/. > > I didn't run 'mergemaster' because of no installworld. Is that the > problem? No, the problem is that you need to installworld to have an updated ipfw(8) binary. Cheers, Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Type1 font problem (Was: Re: mozilla-devel problems)
Wesley Morgan wrote: > Im my many hours of playing with fonts, I seem to recall that the Freetype > / XFT module is perfectly capable of rendering the Type1 fonts. Make sure > you take the PATH out of your XftConfig in addition to the XF86Config Some fonts have characters with a zero width, and you have to calculate from the left and right bearing, instead. One of the original NCD fonts had this problem, e.g.: XFontStruct *fontp; int w1, w2; ... w1 = fontp->per_char[ charnum].width; w2 = fontp->per_char[ charnum].lbearing + fontp->per_char[ charnum].rbearing; if( w1 != w2) printf( "This is a problem font!\n"); The problem only appears if you do the output a character at a time and take care of spacing yourself, instead of letting the Xlib XText functions deal with it. I had the problem on a terminal emulation program, where the text needed to be rendered fixed cell, in all cases, in order to line up properly, regardless of the font. So I used the "em" of the font, and rendered all characters manually, rather than using the XLib routine, which "did the right thing". What it looks like to me is that someone has made some assumptions about the font fields relationship to cell size, and these are not correct for the font in question. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Actual probs with 'ipfw'
On Saturday 26 October 2002 21:48, you wrote: > No, the problem is that you need to installworld to have an updated > ipfw(8) binary. Confirmed! Thanks a lot! PS: So the HEADSUP-strategy has its limitations... ;-) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 4.7-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
alpha tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- ===> gnu/usr.bin/cc/cc_tools make: Permission denied *** Error code 126 Stop in /h/des/src/gnu/usr.bin/cc. *** Error code 1 Stop in /h/des/src/gnu/usr.bin. *** Error code 1 Stop in /h/des/src/gnu. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Actual probs with 'ipfw'
On Sat, Oct 26, 2002 at 10:04:44PM +0200, Matthias Schuendehuette wrote: > On Saturday 26 October 2002 21:48, you wrote: > > > No, the problem is that you need to installworld to have an updated > > ipfw(8) binary. > > Confirmed! Thanks a lot! > > PS: So the HEADSUP-strategy has its limitations... ;-) You did not reboot to single user mode to installworld. No need to run ipfw with the new kernel before installworld. -current readers are expected to know that. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Actual probs with 'ipfw'
On Saturday 26 October 2002 22:17, you wrote: > You did not reboot to single user mode to installworld. > No need to run ipfw with the new kernel before installworld. > -current readers are expected to know that. Right! What I meant was: "For this reason, you probably want to delay an installworld until you are comfortable that your newer kernel builds are satisfactory." from: Message-ID: <[EMAIL PROTECTED]> But my new kernel build *is* satisfactory now :-) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 4.7-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lack of real long double support
Thus spake M. Warner Losh <[EMAIL PROTECTED]>: > : No. You should assume that for i386, at least, that long double will > : have the right LDBL_ constants. I've had them in my local tree for > : about 3 months now and just haven't found the time to commit to > : -current. I'll find the time right now. > > I've committed the fix to the tree. NetBSD uses these numbers, and > I've been using these numbers on a large number of systems that we > maintain at timing solutions (they were added to our local tree prior > to the 4.5 release, and we've built hundreds of ports since then w/o > any issues). I've had them in my own personal p4 tree for 3 months > with similar results. I submitted patches for this back in May. Could you please close i386/38288? While you're at it, you should probably patch IA64 as well. Other supported platforms should be okay, I think. TIA. (Every time this happens, someone comes along a month later and tells me that _I'm_wrong_ about there ever being a bug.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lack of real long double support
In message: <[EMAIL PROTECTED]> David Schultz <[EMAIL PROTECTED]> writes: : Thus spake M. Warner Losh <[EMAIL PROTECTED]>: : > : No. You should assume that for i386, at least, that long double will : > : have the right LDBL_ constants. I've had them in my local tree for : > : about 3 months now and just haven't found the time to commit to : > : -current. I'll find the time right now. : > : > I've committed the fix to the tree. NetBSD uses these numbers, and : > I've been using these numbers on a large number of systems that we : > maintain at timing solutions (they were added to our local tree prior : > to the 4.5 release, and we've built hundreds of ports since then w/o : > any issues). I've had them in my own personal p4 tree for 3 months : > with similar results. : : I submitted patches for this back in May. Could you please close : i386/38288? While you're at it, you should probably patch IA64 as : well. Other supported platforms should be okay, I think. TIA. : : (Every time this happens, someone comes along a month later and : tells me that _I'm_wrong_ about there ever being a bug.) If I hadn't been using long doubles, day in and day our, for the past two years, I'd likely have agreed with you. However, I've had to look into why weird things happen with long doubles a lot, and have found in general they work pretty good. I'll ask Peter Wemm about IA64. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Request: remove ssh1 fallback
Thus spake Tim Kientzle <[EMAIL PROTECTED]>: > Thus spake Lucky Green <[EMAIL PROTECTED]>: > >>... remove ssh1 fallback from the default ... > > David Schultz <[EMAIL PROTECTED]> wrote: > >Removing SSH 1 ... is going to break compatibility ... > > > POLA: before breaking compatibility, warn people. > It's simple to modify the ssh client so that it > emits a warning message before downgrading > > "Warning: switching to less-secure SSH1 protocol" > > On the server side, you could certainly log > a warning; there may be a way to notify the > connecting user as well. The logged warning > could even include a very brief reference to > the setting required to disable SSH1 entirely. I think you're missing the point. Warnings are fine, but there is little good reason to disable SSH1 entirely. If one end of the connection is forced to fall back to SSH1, it's almost certainly because the user at the other end _doesn't_have_any_other_option_. You're proposing to kick legitimate users off of everyone's FreeBSD boxen because you know better than they do about security. I know SSH1 is insecure, and therefore I don't use it. But I'm not about to unleash a surprise on everyone who uses a machine without SSH2 just so I can hammer the idea into their heads. Breaking POLA isn't a sin, but you'd better have a better reason to do it than ``it lets people do things that are insecure.'' So do rsh, telnet, hosts.equiv, vipw, et al. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Building -CURRENT with 4.5-RELEASE
On Tue, 22 Oct 2002 04:25:23 +0200, you wrote: >Is it possible, or do I need to use a more recent installation to be able to >build -CURRENT? it was possible for me, but i had to go through a lot of hassles installing -CURRENT from within -STABLE. i used the DESTDIR-switch to install everything to /mnt/ (where my -current partition was mounted). but mergemaster failed due to a system call lacking (can't remember which one, i think it tried to start a programm in /mnt/bin which failed because it was linked against libc.so.5 i fixed that by linking libc.so.4 to libc.so.5 temporarily). the next pitfall is mergemaster NOT creating files/directories necessary, thus using it on a clean partition (only installworld'd and installkernel'd) will fail and you have to create some files/directories by hand. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sleeping with "mountlist" locked
Lars Eggert wrote: > Hi, > > just got this when trying to umount a media from an USB CF reader: > > /usr/src/sys/kern/kern_synch.c:146: sleeping with "mountlist" locked > from /usr/src/sys/kern/vfs_mount.c:1321. I have a core dump, but it's of > the second panic. Could you tell us what's the revision of your vfs_mount.c file ? Cheers, Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: df problems ?
On Sat, 26 Oct 2002, Dave Evans wrote: > > This is all very true for 4.7, but what about earlier versions. > > > > I compiled fsck using 4.7 srcs, includes and hierarchy with 4.0 > > libraries and tools, so that I could have an fsck I could use with my > > 4.0 CDROM (the latest one I have, unfortunately) to repair any changes > > made by my CURRENT system. It does compile with the same errors you get > > on a true 4.7 system about unsigned/signed comparisons. It even works as > > a program, but it does not repair the filesystem properly to be > > compatible with 4.0. You get an instant panic when going multi-user. > > This is a real nuisance as it blows my recovery strategy should I ever > > need it. If someone could figure out how to fix this I would be grateful > > until the time I get my hands on a 5.0 CDROM > > > > > I tried it again today and it worked (fsck'ing CURRENT drives with > my fsck version 4.7 compiled for 4.0 ). I don't know why it failed yesterday. > > > Is there any way of obtaining a list of superblocks on a fs, apart from > making a note of the list newfs produces? dumpfs(8) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADSUP: burncd/cdcontrol need to be rebuilt (CDRIO*SPEED changes)
On Sat, 26 Oct 2002 [EMAIL PROTECTED] wrote: > With current from yesterday, I get the following error when trying to > burn a cd. I haven't burned one for probably a month or maybe more. > If I remove the -s, the results are the same. > > Does anyone have a suggestion, fix or work around? > > # burncd -f /dev/acd0c -s 1 data cd0.raw20021022 fixate > burncd: ioctl(CDRIOCWRITESPEED): Input/output error > > Thanks, > > ed I've changed the subject since I guess a HEADSUP may be necessary. Try rebuilding burncd. The CDRIOC*SPEED api was changed to allow the user application to send raw KB/s values whereas before the ioctl took in speeds in multiples of a 1X CDROM (1 = 177KB/s, 2 = 354KB/s, ...) This was necessary to allow the user app to specify a speed of CDR_MAX_SPEED, which means the drive should choose its highest speed. The new versions of cdcontrol and burncd do the translation the kernel used to do so you can still specify flags the same as you always have (i.e. -s 1 like you are doing). -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sleeping with "mountlist" locked
Maxime Henrion wrote: > Lars Eggert wrote: > > >/usr/src/sys/kern/kern_synch.c:146: sleeping with "mountlist" locked > >from /usr/src/sys/kern/vfs_mount.c:1321. I have a core dump, but it's of > >the second panic. > > Could you tell us what's the revision of your vfs_mount.c file ? Just did a buildworld/installworld. I'll let you know if it's still an issue with today's sources (and then also include CVS version numbers.) Thanks, Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Actual probs with 'ipfw'
* De: Matthias Schuendehuette <[EMAIL PROTECTED]> [ Data: 2002-10-26 ] [ Subjecte: Re: Actual probs with 'ipfw' ] > On Saturday 26 October 2002 22:17, you wrote: > > You did not reboot to single user mode to installworld. > > No need to run ipfw with the new kernel before installworld. > > -current readers are expected to know that. > > Right! > > What I meant was: > "For this reason, you probably want to delay an installworld until you > are comfortable that your newer kernel builds are satisfactory." > from: Message-ID: <[EMAIL PROTECTED]> > > But my new kernel build *is* satisfactory now :-) I think he was referring to a kernel built with dateof(his-patches)-1 sources, rather than much older ones. There are more obvious version/ABI skew issues once one updates from so long ago. juli. -- Juli Mallett <[EMAIL PROTECTED]> | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: burncd/cdcontrol need to be rebuilt (CDRIO*SPEED changes)
On Sat, 26 Oct 2002, Nate Lawson wrote: > On Sat, 26 Oct 2002 [EMAIL PROTECTED] wrote: > > With current from yesterday, I get the following error when trying to > > burn a cd. I haven't burned one for probably a month or maybe more. > > If I remove the -s, the results are the same. > > > > Does anyone have a suggestion, fix or work around? > > > > # burncd -f /dev/acd0c -s 1 data cd0.raw20021022 fixate > > burncd: ioctl(CDRIOCWRITESPEED): Input/output error > > > > Thanks, > > > > ed > > I've changed the subject since I guess a HEADSUP may be necessary. > > Try rebuilding burncd. The CDRIOC*SPEED api was changed to allow the user > application to send raw KB/s values whereas before the ioctl took in > speeds in multiples of a 1X CDROM (1 = 177KB/s, 2 = 354KB/s, ...) This > was necessary to allow the user app to specify a speed of CDR_MAX_SPEED, > which means the drive should choose its highest speed. > > The new versions of cdcontrol and burncd do the translation the kernel > used to do so you can still specify flags the same as you always have > (i.e. -s 1 like you are doing). > > -Nate I checked again and my commit had missed the burncd speed conversion. I just committed it -- rev 1.28 burncd.c. Sorry about this. CVSUP, rebuild burncd, and let me know if there are further problems. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: burncd/cdcontrol
what would it take to allow burncd to work on SCSI devices.? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
possible kernel build breakage.
I'm about to do a make world so it's possible a gcc change I've not yet picked up may fix this, but in the meanwhile, I can't compile a kernel because of: ref3# make cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror ../../../ddb/db_examine.c cc1: warnings being treated as errors ../../../ddb/db_examine.c: In function `db_examine': ../../../ddb/db_examine.c:132: warning: unknown conversion type character `y' in format ../../../ddb/db_examine.c:132: warning: too many arguments for format ../../../ddb/db_examine.c: In function `db_print_cmd': ../../../ddb/db_examine.c:216: warning: unknown conversion type character `y' in format ../../../ddb/db_examine.c:216: warning: too many arguments for format *** Error code 1 Stop in /usr/src/sys/i386/compile/REF3. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: possible kernel build breakage.
You need a recompile of GCC. This change was made to accomodate the POSIX %z by renaming the DDB %z to %y, and GCC had to be made aware. * De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-10-26 ] [ Subjecte: possible kernel build breakage. ] > > I'm about to do a make world > so it's possible a gcc change I've not yet picked up > may fix this, but in the meanwhile, I can't compile a kernel > because of: > > ref3# make > cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- > -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica > -I../../../contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common > -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding > -Werror ../../../ddb/db_examine.c > cc1: warnings being treated as errors > ../../../ddb/db_examine.c: In function `db_examine': > ../../../ddb/db_examine.c:132: warning: unknown conversion type > character `y' in format > ../../../ddb/db_examine.c:132: warning: too many arguments for format > ../../../ddb/db_examine.c: In function `db_print_cmd': > ../../../ddb/db_examine.c:216: warning: unknown conversion type > character `y' in format > ../../../ddb/db_examine.c:216: warning: too many arguments for format > *** Error code 1 > > Stop in /usr/src/sys/i386/compile/REF3. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Juli Mallett <[EMAIL PROTECTED]> | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: burncd/cdcontrol
On Sat, 26 Oct 2002, Julian Elischer wrote: > what would it take to allow burncd to work on SCSI devices.? You got it backwards -- is atapicam complete enough to work reliably with cdrecord? There's no reason for us to replicate a more feature-complete port in our src tree. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: burncd/cdcontrol need to be rebuilt (CDRIO*SPEED changes)
Quoting Nate Lawson <[EMAIL PROTECTED]>: | On Sat, 26 Oct 2002 [EMAIL PROTECTED] wrote: | > With current from yesterday, I get the following error when trying to | > burn a cd. I haven't burned one for probably a month or maybe more. | > If I remove the -s, the results are the same. | > | > Does anyone have a suggestion, fix or work around? | > | > # burncd -f /dev/acd0c -s 1 data cd0.raw20021022 fixate | > burncd: ioctl(CDRIOCWRITESPEED): Input/output error | > | > Thanks, | > | > ed | | I've changed the subject since I guess a HEADSUP may be necessary. | | Try rebuilding burncd. The CDRIOC*SPEED api was changed to allow the user | application to send raw KB/s values whereas before the ioctl took in | speeds in multiples of a 1X CDROM (1 = 177KB/s, 2 = 354KB/s, ...) This | was necessary to allow the user app to specify a speed of CDR_MAX_SPEED, | which means the drive should choose its highest speed. Nate, Thanks, for the input. I've still got a problem that I'm going to check. My version was cvsuped and built this morning following Peter's instructions in his HEADS UP email. That is when I saw the problem. I was going to burn releases that I had made this past week just in case :-) /root # ls -l `which burncd` -r-xr-xr-x 1 root wheel 18228 Oct 26 11:11 /usr/sbin/burncd /var/tmp # uname -a FreeBSD worldinternet.org 5.0-CURRENT FreeBSD 5.0-CURRENT #31: Sat Oct 26 07:12:23 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PIII850N i386 worldinternet.org: Thanks, ed | | The new versions of cdcontrol and burncd do the translation the kernel | used to do so you can still specify flags the same as you always have | (i.e. -s 1 like you are doing). | | -Nate | | | To Unsubscribe: send mail to [EMAIL PROTECTED] | with "unsubscribe freebsd-current" in the body of the message | -- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: burncd/cdcontrol need to be rebuilt (CDRIO*SPEED changes)
Quoting Nate Lawson <[EMAIL PROTECTED]>: | | I checked again and my commit had missed the burncd speed conversion. I | just committed it -- rev 1.28 burncd.c. Sorry about this. CVSUP, rebuild | burncd, and let me know if there are further problems. | Thanks, Nate. Please ignore my previous email. I hadn't seen this one. I'm cvsuping now. I'll let you know if it doesn't work, tomorrow. Thanks again, ed - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: possible kernel build breakage.
On Sat, Oct 26, 2002 at 05:08:39PM -0700, Juli Mallett wrote: > You need a recompile of GCC. This change was made to accomodate the POSIX > %z by renaming the DDB %z to %y, and GCC had to be made aware. The recommended upgrade procedure (buildworld, followed by buildkernel etc) should automatically take care of this. Kris msg45416/pgp0.pgp Description: PGP signature
GEOM gets whole disk geometry for slice (instead of slice geometry)
I have disk shared between FreeBSD and M$ Win, two slices, and got incorrect disklabel with GEOM kernel. Namely "cylinders" and "sectors/unit" fields are from _whole_ disk, not from just requested slice. It invalidates previously correct 'c' BSD partition too, 'disklabel' outputs several warnings about it. I am not familiar with GEOM. In which place it senses cylinders and secs/unit? Does anyone saw the same problem too? Specific info attached below. Look at the wrong fields in disklabel. They even can't be corrected using 'disklabel -e'. -- fdisk: can't get disk parameters on /dev/ad0; supplying dummy ones *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=89355 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=89355 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 12514572 (6110 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 778/ head 254/ sector 63 The data for partition 2 is: sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) start 12514698, size 77545692 (37864 Meg), flag 0 beg: cyl 779/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: The data for partition 4 is: -- # /dev/ad0s1c: type: ESDI disk: ad0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 5606 ^^^ must be 778 (or 779?) sectors/unit: 90069840 ^^^ must be 12514572 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 11900172 6144004.2BSD 2048 1638464 # (Cyl. 38*- 778*) b: 6144000 swap# (Cyl.0 - 38*) c: 125145720unused0 0 # (Cyl.0 - 778*) -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[PATCH] disklabel(8) loves to deref NULL with an invalid line.
If you delete from fstype on in a disklabel line and have it try to write
it, its internal parsing routines go boom. I've fixed it locally, and
would like to commit my delta.
%%%
Index: disklabel.c
===
RCS file: /home/ncvs/src/sbin/disklabel/disklabel.c,v
retrieving revision 1.62
diff -b -d -w -u -r1.62 disklabel.c
--- disklabel.c 8 Oct 2002 12:13:19 - 1.62
+++ disklabel.c 27 Oct 2002 01:11:18 -
@@ -921,6 +921,9 @@
{
char c;
+ if (cp == NULL) {
+ return (NULL);
+ }
while (*cp != '\0' && !isspace(*cp) && *cp != '#')
cp++;
if ((c = *cp) != '\0') {
@@ -1233,9 +1236,14 @@
}
pp->p_offset = v;
cp = tp, tp = word(cp);
- for (cpp = fstypenames; cpp < &fstypenames[FSMAXTYPES]; cpp++)
+ for (cpp = fstypenames; cpp < &fstypenames[FSMAXTYPES]; cpp++) {
+ if (cp == NULL) {
+ fprintf(stderr, "line %d: invalid entry\n", lineno);
+ return (1);
+ }
if (*cpp && streq(*cpp, cp))
break;
+ }
if (*cpp != NULL) {
pp->p_fstype = cpp - fstypenames;
} else {
%%%
juli.
--
Juli Mallett <[EMAIL PROTECTED]> | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]
http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
5-current crashing when booting SMP
Over the past few weeks I've had continuous problems booting
my 5-current system with an SMP kernel. Immediately after
the system has booted and the login screen displays the machine
panics. The motherboard is an Abit BP6. Below is the information
provided when it locks up. Based on the kernel panic FAQ I
was able to determine that the suspect function is proctree but I
wasn't able to get it to dump and investigate further. My knowledge
of debugging is almost non existant, any help on the matter would
be appreciated. This has been happening since I updated around
the first week of October.
1st 0xc297f068 process lock (processlock) @ kern_fork.c:571
2nd 0xc0578d00 proctree (proctree) @ kern_fork.c:596
recursed on non-recursive lock (sleepmutex) process lock
kern_fork.c:599 first acquired @ kern_fork.c:571
panic : recurse
cpuid =1 lapic.id=0100
Debugger("panic")
Stopped at Debugger + 0x55:xchg %ebx,in_Debugger.0
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: burncd/cdcontrol
> On Sat, 26 Oct 2002, Julian Elischer wrote: > > what would it take to allow burncd to work on SCSI devices.? > > You got it backwards -- is atapicam complete enough to work reliably with > cdrecord? I don't see why it shouldn't work on -CURRENT. It works fine for me on -STABLE, for oh, months and months - I've burnt > 50 CDs @ 8x on an IDE combo DVD/CDRW laptop drive[0]. Currently on -STABLE with ATAPI-CAM patches from August 20th. With cdrecord[1]. 1 coaster (experimenting with -overburn) to date. > There's no reason for us to replicate a more feature-complete > port in our src tree. Sure. I'm just waiting for ATAPI-CAM to get MFC'd to -STABLE. Cheers, AS [0] Which, thanks to 'atacontrol', is even hot-swappable. :) [1] Cdrecord 1.11a28 (i386-unknown-freebsd4.6) Copyright (C) 1995-2002 Jörg Schilling Using libscg version 'schily-0.6' scsibus1: 1,0,0 100) 'TEAC' 'DW-28E ' '1.0A' Removable CD-ROM Cdrecord 1.11a28 (i386-unknown-freebsd4.6) Copyright (C) 1995-2002 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 Using libscg version 'schily-0.6' atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'TEAC' Identifikation : 'DW-28E ' Revision : '1.0A' Device seems to be: Generic mmc2 DVD-ROM. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R Drive buf size : 1441792 = 1408 KB FIFO size : 4194304 = 4096 KB Track 01: data 695 MB padsize: 30 KB Total size: 799 MB (79:10.30) = 356273 sectors Lout start: 799 MB (79:12/23) = 356273 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type C, low Beta category (C-) (6) ATIP start of lead in: -11640 (97:26/60) ATIP start of lead out: 359849 (79:59/74) Disk type:Long strategy type (Cyanine, AZO or similar) Manuf. index: 3 Manufacturer: CMC Magnetics Corporation Blocks total: 359849 Blocks current: 359849 Blocks remaining: 3576 Starting to write CD/DVD at speed 8 in real TAO mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting new track at sector: 0 Track 01: 695 of 695 MB written (fifo 100%) 8.4x. Track 01: writing 30 KB of pad data. Track 01: Total bytes read/written: 729612288/729643008 (356271 sectors). Writing time: 607.606s Fixating... Fixating time: 33.575s cdrecord: fifo had 11493 puts and 11493 gets. cdrecord: fifo was 0 times empty and 11246 times full, min fill was 93%. msg45420/pgp0.pgp Description: PGP signature
Re: burncd/cdcontrol
cdrecord doesn't do DVDs and jorg Schiller is holding back on DVD mods so he can sell that version.. DVD capable cdrecord is called cdrecord-PRO and costs $100. if he commands from burncd could be piped into a SCSI pipe, then that would probably work... I have an ATAPI dvd writer on a firewire<->atapi converter that connects to CAM via SBP-2. Using some patches for cdrecord that are available on the internet I got it to write fine, so tehatapi and SCSI commands for writing are the same. But that is a hack, because as isaid before, teh cdrecord that REALLY knows about DVDs is not free. On Sat, 26 Oct 2002, Nate Lawson wrote: > On Sat, 26 Oct 2002, Julian Elischer wrote: > > what would it take to allow burncd to work on SCSI devices.? > > You got it backwards -- is atapicam complete enough to work reliably with > cdrecord? There's no reason for us to replicate a more feature-complete > port in our src tree. > > -Nate > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: possible kernel build breakage.
This could do with a note in UPDATING, No? On Sat, 26 Oct 2002, Juli Mallett wrote: > You need a recompile of GCC. This change was made to accomodate the POSIX > %z by renaming the DDB %z to %y, and GCC had to be made aware. > > * De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-10-26 ] > [ Subjecte: possible kernel build breakage. ] > > > > I'm about to do a make world > > so it's possible a gcc change I've not yet picked up > > may fix this, but in the meanwhile, I can't compile a kernel > > because of: > > > > ref3# make > > cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > > -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- > > -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica > > -I../../../contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common > > -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding > > -Werror ../../../ddb/db_examine.c > > cc1: warnings being treated as errors > > ../../../ddb/db_examine.c: In function `db_examine': > > ../../../ddb/db_examine.c:132: warning: unknown conversion type > > character `y' in format > > ../../../ddb/db_examine.c:132: warning: too many arguments for format > > ../../../ddb/db_examine.c: In function `db_print_cmd': > > ../../../ddb/db_examine.c:216: warning: unknown conversion type > > character `y' in format > > ../../../ddb/db_examine.c:216: warning: too many arguments for format > > *** Error code 1 > > > > Stop in /usr/src/sys/i386/compile/REF3. > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > -- > Juli Mallett <[EMAIL PROTECTED]> | FreeBSD: The Power To Serve > Will break world for fulltime employment. | finger [EMAIL PROTECTED] > http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: you need to install a new kernel before aninstallworld.
In message: <[EMAIL PROTECTED]> Tim Kientzle <[EMAIL PROTECTED]> writes: : Peter Wemm wrote: : : > 'make installworld' without ... a new kernel would be rather messy. : : > ... a reminder of the sequence is probably in order: : > buildworld : > buildkernel : > installkernel : > reboot : > installworld : > reboot : : : This _does_not_work_ because 'installkernel' does : not update the bootblocks. It should. Otherwise, : 'installkernel' is not filling it's contract: it is : not ensuring that the next boot uses the new kernel. Are you sure you need new bootblocks? I've not had issues and am pretty careless about when I do installworld vs installkernel. You need them for the 4.x -> 5.0 upgrade, but I didn't think you've needed new ones for a long time now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libfetch/http.c with -Werror
It seems _http_growbuf() should return int at the end of function? Index: http.c === RCS file: /home/ncvs/src/lib/libfetch/http.c,v retrieving revision 1.61 diff -u -r1.61 http.c --- http.c 3 Oct 2002 10:42:19 - 1.61 +++ http.c 27 Oct 2002 06:07:54 - @@ -179,6 +179,7 @@ return (-1); io->buf = tmp; io->bufsize = len; + return (0); } /* -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of npx patch |= PCB_NPXINITDONE?
On Sun, 27 Oct 2002, Daniel Flickinger wrote: > I placed your patch for npx in my kernel builds for > 25 and 26 Oct ... I have not had xemacs under X lock-up > since --and it was downright regular prior. > > Is this the reason? Will the patch be committed? > > Time stamps are GMT. He already committed it. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
