Re: rc_ng apm enable not run
On Fri, 21 Jun 2002 18:53:11 +0200 Ronald Klop [EMAIL PROTECTED] wrote: Hello, In the rc_ng is 'apm -e enable' not run if I have apm_enable=YES and/or apmd_enable=YES in my rc.conf. But apmd is run with the last option. uhh... my fault :( I don't know how I missed /etc/rc.i386 when I was doing the porting. I'll have a chance to work on it Sunday, unless someone else beats me to it. Cheers, Mike Makonnen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Martin Blapp wrote: Hi, I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. is it enough to setenv GCC=/usr/local/bin/gcc31, then make install ? TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Fri, Jun 21, 2002 at 06:50:49PM +0200, Thierry Herbelot wrote: I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. is it enough to setenv GCC=/usr/local/bin/gcc31, then make install ? No. make CC=gcc31 CXX=g++31 clean install To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: i386 tinderbox failure
On Sunday, June 16, 2002, at 06:32 AM, Dag-Erling Smorgrav wrote: Bruce Evans [EMAIL PROTECTED] writes: This is caused by an old bogus include path in Makefiles (still needed :-(), a bogus #include in drm and new newspace pollution in sys/select.h. drm includes sys/select.h, although this header is essentially user-only. sys/select.h now includes signal.h. signal.h declares psignal(3) which is quite different from psignal(9). ISTR that all includes of sys/select.h in the kernel were changed to includes of sys/selinfo.h. There seems to have been a lot of bitrot since then. Eric, can you fix this? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] In the meantime, the removal of sys/select.h gets us building again here. I'm not actually using the module so can't speak about its functionality. Cheers, Jerry Hicks [EMAIL PROTECTED] Index: src/sys/dev/drm/drm_os_freebsd.h === RCS file: /home/ncvs/src/sys/dev/drm/drm_os_freebsd.h,v retrieving revision 1.5 diff -u -r1.5 drm_os_freebsd.h --- src/sys/dev/drm/drm_os_freebsd.h31 May 2002 23:19:50 - 1.5 +++ src/sys/dev/drm/drm_os_freebsd.h15 Aug 2002 02:11:39 - @@ -17,7 +17,9 @@ #include sys/uio.h #include sys/filio.h #include sys/sysctl.h +#if 0 #include sys/select.h +#endif #include vm/vm.h #include vm/pmap.h #include machine/pmap.h To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: error in ncurses in 'make buildworld'
On Fri, 21 Jun 2002, David O'Brien wrote: On Fri, Jun 21, 2002 at 11:11:39AM +0400, Igor Roboul wrote: igorr@sysadm~ gcc -Wall qq.c qq.c: In function `main': qq.c:16: warning: float format, double arg (arg 3) --- I have expected this igorr@sysadm~ ./a.out 123 123.00 0.124861 0.04861--- Pay attention 123 I don't get the same results with a system built today. $ cc -v ..snip.. gcc version 3.1 [FreeBSD] 20020509 (prerelease) $ cc -Wall qq.c The program and strtod.c (not dtoa.c like I said in previous mail) must be compiled with gcc -O2 to cause problems. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
world is bõrken...
=== gnu/usr.bin/binutils/doc
echo @set VERSION 2.12.0 [FreeBSD] 2002-04-10 gasver.texi
makeinfo --no-validate -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib
/binutils/gas/doc -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binu
tils/ld -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/bfd/d
oc -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils -
I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc -I /ban
g/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc --no-split -I
/bang/src/gnu/usr.bin/binutils/doc -I /bang/src/gnu/usr.bin/binutils/doc/../../
../../contrib/binutils /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/bi
nutils/gas/doc/as.texinfo -o as.info
/bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texin
fo:2108: warning: Info cannot handle `:' in index entry `@code{:} (label)'.
/bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texin
fo:2109: warning: Info cannot handle `:' in index entry `label (@code{:})'.
/bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texin
fo:3927: warning: Info cannot handle `:' in index entry `listing control: new pa
ge'.
/bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texin
fo:4814: warning: Info cannot handle `:' in index entry `listing control: paper
size'.
/bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texin
fo:4903: warning: Info cannot handle `:' in index entry `listing control: subtit
le'.
/bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texin
fo:5391: warning: Info cannot handle `:' in index entry `listing control: title
line'.
gzip -cn as.info as.info.gz
echo @set VERSION 2.12.0 [FreeBSD] 2002-04-10 ldver.texi
makeinfo --no-validate -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib
/binutils/gas/doc -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binu
tils/ld -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/bfd/d
oc -I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils -
I /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc -I /ban
g/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc --no-split -I
/bang/src/gnu/usr.bin/binutils/doc -I /bang/src/gnu/usr.bin/binutils/doc/../../
../../contrib/binutils /bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/bi
nutils/ld/ld.texinfo -o ld.info
/bang/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld/ld.texinfo:32
02: warning: Info cannot handle `:' in index entry `:@var{phdr}'.
gzip -cn ld.info ld.info.gz
make: don't know how to make annotate.info. Stop
*** Error code 2
Stop in /bang/src/gnu/usr.bin/binutils.
*** Error code 1
Stop in /bang/src/gnu/usr.bin.
*** Error code 1
--
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
UFS2 related message?
Hello all, After the import of UFS2 patch into -current, I get the following messages. pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes Is it related to UFS2 by anyway? FYI, here's what got with my disks. % df -i Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on /dev/ad0s2a254063 91341 14239739%2615 608714% / devfs 1 1 0 100% 0 0 100% /dev /dev/ad0s3e 7185161 4473874 213647568% 227116 1574354 13% /home /dev/ad0s2f 2787666 1668475 89617865% 176288 522078 25% /usr /dev/ad0s2e254063 10456 223282 4%1653 618333% /var procfs 4 4 0 100% 1 0 100% /proc linprocfs 4 4 0 100% 1 0 100% /usr/compat/linux/proc /dev/ad0s13663652 2542176 112147669% 0 0 100% /dos % Thanks in advance, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[Patch] Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On 2002-06-21 14:33 +0200, Stefan Esser [EMAIL PROTECTED] wrote: Following up to my own mail: Seems that translate.c is built from other directories as well, not just from within OSmesa. See the following patch, which is files/patch-GL_mesa_src_Imakefile on my system: --- lib/GL/mesa/src/Imakefile.orig Wed May 2 17:06:02 2001 +++ lib/GL/mesa/src/Imakefile Fri Jun 21 15:49:39 2002 @@ -51,6 +51,13 @@ #include Library.tmpl +#if defined(__GNUC__) __GNUC__ = 3 +#define ObjectCompile(options) RemoveFile($@) @@\ + ClearmakeOSName \ + $(CC) -c $(CFLAGS) options $*.c -o $@ || \ + $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ +#endif + LibraryObjectRule() SubdirLibraryRule($(OBJS)) Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On 2002-06-21 16:35 +0200, Martin Blapp [EMAIL PROTECTED] wrote: I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. Sorry, but the compiler bug has been present in the port version of GCC-3.1 as well, a few weeks ago, and existed in the version to become GCC-3.1.1 ... I opened a PR at gcc.org, didn't get any feedback, yet. Why mess around with a buggy compiler if a working one is around ? Only a single source file triggers the optimizer bug, and the work-around should be appropriate until the compiler is fixed, IMHO. Why don't we update the pre 3.1 gcc in CURRENT to a working one ? I'm sure that there is a lot of work being done to keep up with the latest gcc versions. It just isn't that simple to upgrade such a crucial build tool (if compiling a new gcc fails, then make world doesn't have much of a chance of succeeding ...) Yes, I turned on -O and O2 again ;-) Did the GCC-3.1 from ports compile translate.c with optimization turned on ??? It didn't, just one or two weeks ago. Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hi Stefan, Did the GCC-3.1 from ports compile translate.c with optimization turned on ??? It didn't, just one or two weeks ago. GCC3.1.1 Prerelease. Yes it did. I removed the patch andd added -O and -O2 again. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hi, make CC=gcc31 CXX=g++31 clean install This currently doesn't work with the Xfree86 ports. CC is hardcoded there. Could the maintainer please fix this ? I also had to fix OO to work with this. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: UFS2 related message?
By chance, is this a new installation? A month or so ago I was adding a drive to a -current system and I discovered that the newfs defaults were setting insanely large block/fragment/inode sizes and I could not even do a 'make world' on that partition. Had to completely reinstall and override the defaults. On Sat, 22 Jun 2002, Munehiro Matsuda wrote: Hello all, After the import of UFS2 patch into -current, I get the following messages. pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes Is it related to UFS2 by anyway? FYI, here's what got with my disks. % df -i Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on /dev/ad0s2a254063 91341 14239739%2615 608714% / devfs 1 1 0 100% 0 0 100% /dev /dev/ad0s3e 7185161 4473874 213647568% 227116 1574354 13% /home /dev/ad0s2f 2787666 1668475 89617865% 176288 522078 25% /usr /dev/ad0s2e254063 10456 223282 4%1653 618333% /var procfs 4 4 0 100% 1 0 100% /proc linprocfs 4 4 0 100% 1 0 100% /usr/compat/linux/proc /dev/ad0s13663652 2542176 112147669% 0 0 100% /dos % Thanks in advance, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 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
binutils doc still broken
sp.info gasp.info.gz ln -sf /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/\ all-cfg.texi gdb-cfg.texi make: don't know how to make remote.texi. Stop remote.texi does not exist in /usr/src. The obvious fix of removing remote.texi from the Makefile doesn't work because of /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/\ gdb.texinfo:8824: @include `remote.texi': No such file or directory. makeinfo: Removing output file `gdb.info' due to errors; use --force to\ preserve. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: binutils doc still broken
On Sat, Jun 22, 2002 at 09:59:44AM -0700, Steve Kargl wrote: make: don't know how to make remote.texi. Stop remote.texi does not exist in /usr/src. The obvious fix of removing remote.texi from the Makefile doesn't work because of I just took a larger hammer and just turned off docs. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: binutils doc still broken
On Sat, Jun 22, 2002 at 10:05:38AM -0700, David O'Brien wrote: On Sat, Jun 22, 2002 at 09:59:44AM -0700, Steve Kargl wrote: make: don't know how to make remote.texi. Stop remote.texi does not exist in /usr/src. The obvious fix of removing remote.texi from the Makefile doesn't work because of I just took a larger hammer and just turned off docs. FWIW, I solved the problem by reanimating remote.texi from the Attic, to where it was relegated with the message that it did not make it into GDB 5.0. But of course it needs sorting out. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: UFS2 related message?
In message [EMAIL PROTECTED], Munehiro Matsuda writes: Hello all, After the import of UFS2 patch into -current, I get the following messages. pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes Is it related to UFS2 by anyway? Yes, this seems to be related to UFS2. Please send an email to [EMAIL PROTECTED] with the output of dumpfs from that partition (or upload the file and send him the URL) Please also tell him if you ran any of the posted versions of the UFS2 patch or not. -- 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
Kernel panic with suser_cred and rm
Hello everybody, I upgraded to today's -CURRENT and upon reboot with the new kernel, experienced a panic. Since I did not see it reported here yet, here is some info. More available on request, but I do not have a serial console and therefore had to transcribe everything by hand. Also, there was no core dump. (How can I force it?) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02054bc stack pointer = 0x10:0xceb1db5c frame pointer = 0x10:0xceb1db60 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 48 (rm) kernel: type 12 trap, code= 0 Stopped at suser_cred+0x1c:cmpl $0,0x4(%edx) db trace suser_cred chkiq ufs_inactive ufs_vnoperate vput unlink syscall syscall_with_err_pushed --- syscall (10, FreeBSD ELF, unlink) eip = 0x804af7b, esp = 0xbfbffc7c ebp = 0xbfbffd08 db show locks exclusive sleep mutex Giant r= 0 (0xc03ed260) locked @ ../../../vm/vm_fault.c:202 FreeBSD fonix.adamsfamily.xx 5.0-CURRENT FreeBSD 5.0-CURRENT #46: Sat Jun 15 17:57:46 CEST 2002 [EMAIL PROTECTED]:/usr/home/cc/build/freebsd/src/sys/i386/compile/FONIX i386 dmesg is not available from the failing kernel, but the only could sleep with... messages came from the soundcard driver. The panic happens also in single-user mode, in my case most easily triggered with the use of rm(1). If you need any more info, just ask. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: binutils doc still broken
On Sat, 22 Jun 2002, David O'Brien wrote: On Sat, Jun 22, 2002 at 09:59:44AM -0700, Steve Kargl wrote: make: don't know how to make remote.texi. Stop remote.texi does not exist in /usr/src. The obvious fix of removing remote.texi from the Makefile doesn't work because of I just took a larger hammer and just turned off docs. I worked around this locally by checking out the old version of remote.texi. It was live in gdb.291 but is dead in gdb. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: you should probably track current@ these days...
Date: Sat, 22 Jun 2002 07:49:17 -0700 (PDT) From: David Wolfskill [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: UFS2, superblocks, and UFS compatability I had noted phk's message about Kirk's commitatron being readied for action; I was, however, slightly surprised by some of the results of yesterday's (daily) build of -CURRENT. I had expected (and a quick, ex post facto, look at Kirk's commit message confirms) that the intent was to maintain compatability with UFS1. What surprised me was that after building yesterday's -CURRENT successfully (actually, without incident at all), I poked around a bit, then re-booted to -STABLE. (I'm tracking both -STABLE and -CURRENT on the same physical disk, using different slices. Although I build -CURRENT daily, and do some reality checks, I still do the bulk of the work with the machines in question -- such as anything that updates the CVS repository -- in -STABLE. This probably reflects a rather conservative nature on my part.) The surprise was that -STABLE's fsck was rather expressively unhappy about the file systems that had been mounted while running -CURRENT. In particular, STABLE's fsck claimed that the superblock for each such file system was corrupt. I found (empirically) that running fsck (and allowing it to recover the superblock from the backup superblock at 32) for each of these files systems, then rebooting, made STABLE much less unhappy. :-} The -CURRENT code appears to be able to use a UFS1 file system OK -- I was able to boot back to -CURRENT again in preparation for building today's -CURRENT -- but it appears to me (and I haven't looked at the code to verify this) that something in the superblock is getting updated in a way that isn't completely compatable with UFS1, at least if the file system is updated. If this is intended, mention of it in UPDATING might be useful. If it's not, I'll be happy to help narrow down where things go awry and test the results of (proposed) patches. (Whether they are patches to -CURRENT, -STABLE, or both.) Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] Trying to support or use Microsoft products makes about as much sense as painting the outside of a house with watercolors. My hope was that you would be able to switch painlessly between new and old systems. To make this work, I made a change to fsck on April 7th: RCS file: /usr/ncvs/src/sbin/fsck_ffs/setup.c,v: revision 1.30 date: 2002/04/07 05:16:33; author: mckusick; state: Exp; lines: +25 -61 When checking the alternate superblock, we used to copy any fields that might have changed, then did a byte-by-byte comparison with the alternate. If any unused fields got used, they had to be added to the exception list. Such changes caused too many false alarms. So, I have changed the comparison algorithm to compare a selected set of fields that are not expected to change. This new algorithm causes far fewer false hits and still does a good job of detecting problems when they have really occurred. In particular, this change should ease the transition to kernels supporting UFS2 which make some significant changes to the superblock. Sponsored by: DARPA, NAI Labs This was supposed to get MFC'ed back to 4.X, though I am not sure if that ever happened. Because of the breakup of fsck into fsck and fsck_ffs I am not sure how one goes back and makes changes to whet used to be fsck/setup.c. Anyway, if your fsck_ffs is running with a copy of setup.c that predates this change, then it will bitch about the superblock being corrupted and recover by using the first alternate. You can avoid the bitching by using `fsck -b16 ...' to override the integrity check. Given that you have had the problem, I expect that others will as well, so I will make a note in the UPDATING notes to suggest the use of `fsck -b16 ...' when going back to using filesystems on 4.X systems. Kirk McKusick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Floppy only 8.3 filenames
Hi, i am sure on my old 4.x system i was able to mount my floppy-disc and can use long filenames, but on my -current mount -t msdos /dev/fd0 /mnt leads to 8.3 lowercase and mount -t msdos /dev/fd0c /mnt the first time to 8.3 uppercase and the following to 8.3 lowercase... Does my mind playing with me??? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Floppy only 8.3 filenames
MS-DOS can only handle 8.3 file names. It's by design (MS not FreeBSD). /snip/ mount -t msdos /dev/fd0 /mnt /snip/ -- Peter Hessler [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Floppy only 8.3 filenames
/dev/ad0s1 /dosmsdos rw 0 0 looks quite longfilenamed on my FAT32 slice since ages... On Sat, 2002-06-22 at 22:48, Peter Hessler wrote: MS-DOS can only handle 8.3 file names. It's by design (MS not FreeBSD). /snip/ mount -t msdos /dev/fd0 /mnt /snip/ -- Peter Hessler [EMAIL PROTECTED] 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: Floppy only 8.3 filenames
- Original Message - From: Jan Stocker [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, June 22, 2002 4:50 PM Subject: Re: Floppy only 8.3 filenames /dev/ad0s1 /dosmsdos rw 0 0 looks quite longfilenamed on my FAT32 slice since ages... On Sat, 2002-06-22 at 22:48, Peter Hessler wrote: MS-DOS can only handle 8.3 file names. It's by design (MS not FreeBSD). /snip/ mount -t msdos /dev/fd0 /mnt /snip/ -- Peter Hessler [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message ugh top-posting... perhaps try forcing it with -o longnames ? Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/bkw/ +[+++[-]-]+..+.+++.-.[+---]++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Floppy only 8.3 filenames
This really helps and further mounts without the option will mount the floppy with longnames, but i am sure i never used such an option. Thanx Jan On Sat, 2002-06-22 at 23:07, Brian K. White wrote: - Original Message - From: Jan Stocker [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, June 22, 2002 4:50 PM Subject: Re: Floppy only 8.3 filenames /dev/ad0s1 /dosmsdos rw 0 0 looks quite longfilenamed on my FAT32 slice since ages... On Sat, 2002-06-22 at 22:48, Peter Hessler wrote: MS-DOS can only handle 8.3 file names. It's by design (MS not FreeBSD). /snip/ mount -t msdos /dev/fd0 /mnt /snip/ -- Peter Hessler [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message ugh top-posting... perhaps try forcing it with -o longnames ? Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/bkw/ +[+++[-]-]+..+.+++.-.[+---]++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani 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: UFS2 related message?
The problem with running out of inodes is now fixed and checked in on freefall. You need to pick up /sys/ufs/ffs/ffs_alloc.c revision 1.94 or later. For those that care, the log entry describing the problem: revision 1.94 date: 2002/06/22 21:24:58; author: mckusick; state: Exp; lines: +2 -2 This patch fixes a problem whereby filesystems that ran out of inodes in a cylinder group would fail to check for free inodes in other cylinder groups. This bug was introduced in the UFS2 code merge two days ago. An inode is allocated by calling ffs_valloc which calls ffs_hashalloc to do the filesystem scan. Ffs_hashalloc walks around the cylinder groups calling its passed allocator (ffs_nodealloccg in this case) until the allocator returns a non-zero result. The bug is that ffs_hashalloc expects the passed allocator function to return a 64-bit ufs2_daddr_t. When allocating inodes, it calls ffs_nodealloccg which was returning a 32-bit ino_t. The ffs_hashalloc code checked a 64-bit return value and usually found random non-zero bits in the high 32-bits so decided that the allocation had succeeded (in this case in the only cylinder group that it checked). When the result was passed back to ffs_valloc it looked at only the bottom 32-bits, saw zero and declared the system out of inodes. But ffs_hashalloc had really only checked one cylinder group. The fix is to change ffs_nodealloccg to return 64-bit results. Sponsored by: DARPA NAI Labs. Submitted by: Poul-Henning Kamp [EMAIL PROTECTED] Reviewed by:Maxime Henrion [EMAIL PROTECTED] Kirk McKusick =-=-=-=-=-= To: [EMAIL PROTECTED] Subject: UFS2 related message? Date: Sat, 22 Jun 2002 20:45:01 +0900 From: Munehiro Matsuda [EMAIL PROTECTED] Hello all, After the import of UFS2 patch into -current, I get the following messages. pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes Is it related to UFS2 by anyway? FYI, here's what got with my disks. % df -i Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on /dev/ad0s2a254063 91341 14239739%2615 608714% / devfs 1 1 0 100% 0 0 100% /dev /dev/ad0s3e 7185161 4473874 213647568% 227116 1574354 13% /home /dev/ad0s2f 2787666 1668475 89617865% 176288 522078 25% /usr /dev/ad0s2e254063 10456 223282 4%1653 618333% /var procfs 4 4 0 100% 1 0 100% /proc linprocfs 4 4 0 100% 1 0 100% /usr/compat/linux/proc /dev/ad0s13663652 2542176 112147669% 0 0 100% /dos % Thanks in advance, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] 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: cvs commit: src/sys/pc98/pc98 sio.c src/sys/conf options options.i386 options.ia64 options.pc98 src/sys/dev/sio sio.c sioreg.h
On Thu, Jun 20, 2002 at 05:25:11PM +0200, Dag-Erling Smorgrav wrote: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: It doesn't boot, however FWIW, once I reverted your changes to sio,c and sioreg.h, it only got as far as: Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0xfc330a30... sio1: gdb debugging port Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #10: Thu Jun 20 17:17:50 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/alpha/compile/DSA panic: lockmgr: locking against myself panic Stopped at 0xfc4f0e44: zapnot v0,#0xf,v0 v0=0x6 db trace db reset halted CPU 0 What kernel version did you run before? To reduce the timerange: I am running a version around 17th june. -- 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
Current kernel panic
I get this with a current kernel compiled just a few minute ago (SMP) Can't get to debugger as keystyrokes don't work Kernel from the 19th before UFS2 works fine. Additional routing options:. Mounting NFS file systems:. Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0c00 fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01d4e39 stack pointer = 0x10:0xd19a7b8c frame pointer = 0x10:0xd19a7b8c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 233 (rm) trap number = 12 panic: page fault cpuid = 1; lapic.id = 0c00 boot() called on cpu#1 syncing disks... panic: bdwrite: buffer is not busy cpuid = 1; lapic.id = 0c00 boot() called on cpu#1 Uptime: 13s pfs_vncache_unload(): 1 entries remaining Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Stopped CPU 1 == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
locate.mklocatedb requires perl which may not be installed
Hi,
I just installed a system today using the 5.0-CURRENT-20020621-JPSNAP.iso
CDROM and noticed that when I attempted to run /etc/periodic/weekly/310.locate
so that I could use locate to find some files that it spewed out:
Perl is not installed, try 'pkg_add -r perl'
Rather than simply installing perl (I'll get to that later)
I decided to track down what was calling it. Turns out that
/usr/libexec/locate.mklocatedb was the culprit. I then modified
locate.mklocatedb to use awk rather than perl. Here's the diff:
--- locate.mklocatedb.orig Thu Jun 20 17:07:43 2002
+++ locate.mklocatedb Sat Jun 22 18:09:03 2002
@@ -76,14 +76,15 @@
$code $bigrams $filelist || exit 1
locate -d $filelist / | $bigram | $sort -nr | head -128 |
-perl -ne '/^\s*[0-9]+\s(..)$/ print $1 || exit 1' $bigrams || exit 1
+awk '{if (/^[ ]*[0-9]+[ ]+..$/) {printf(%s,$2)} else {exit 1}}'
+$bigrams
+ || exit 1
locate -d $filelist / | $code $bigrams || exit 1
exit
else
if $sortcmd $sortopt $filelist; then
$bigram $filelist | $sort -nr |
- perl -ne '/^\s*[0-9]+\s(..)$/ print $1 || exit 1' $bigrams
+ awk '{if (/^[ ]*[0-9]+[ ]+..$/) {printf(%s,$2)} else {exit 1}}'
+$bigrams
|| exit 1
$code $bigrams $filelist || exit 1
else
This seems to be working for me. It could likely be improved upon by the
perl and/or awk some expert out there. (I'm actually more familiar with
awk than perl but I wouldn't claim that my awk translation is the most
efficient either.)
--
Bob WillcoxIf practice makes perfect, and nobody's perfect,
[EMAIL PROTECTED] why practice?
Austin, TX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: locate.mklocatedb requires perl which may not be installed
On Sat, Jun 22, 2002 at 06:22:27PM -0500, Bob Willcox wrote: Rather than simply installing perl (I'll get to that later) I decided to track down what was calling it. Turns out that /usr/libexec/locate.mklocatedb was the culprit. I then modified locate.mklocatedb to use awk rather than perl. Here's the diff: Thanks, committed. BTW, please take care about how your MUA handles ^I's vs. ' '. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: locate.mklocatedb requires perl which may not be installed
On Sat, Jun 22, 2002 at 05:55:47PM -0700, David O'Brien wrote: On Sat, Jun 22, 2002 at 06:22:27PM -0500, Bob Willcox wrote: Rather than simply installing perl (I'll get to that later) I decided to track down what was calling it. Turns out that /usr/libexec/locate.mklocatedb was the culprit. I then modified locate.mklocatedb to use awk rather than perl. Here's the diff: Thanks, committed. BTW, please take care about how your MUA handles ^I's vs. ' '. :-) Hmm, strange. The first awk line had the ^I's converted to spaces and the second one didn't. Digging into this abit deeper, it seems that my MUA (mutt) probably wasn't to blame afterall. It appears that I must have hosed this up myself while editing the file. :-( Bob -- Bob WillcoxIf practice makes perfect, and nobody's perfect, [EMAIL PROTECTED] why practice? Austin, TX To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/pc98/pc98 sio.c src/sys/conf options options.i386 options.ia64 options.pc98 src/sys/dev/sio sio.c sioreg.h
Bernd Walter [EMAIL PROTECTED] writes: What kernel version did you run before? To reduce the timerange: I am running a version around 17th june. So am I. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sparc64 tinderbox failure
/usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c: In function `mi_engine': /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:223: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:245: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:258: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:269: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:278: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:287: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:294: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:359: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c: In function `st_optionneg': /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:511: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:525: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:543: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:560: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c: In function `st_connectinfo': /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:615: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:631: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:649: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:668: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/engine.c:679: warning: cast from pointer to integer of different size /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/listener.c: In function `mi_thread_handle_wrapper': /usr/home/des/tinderbox/sparc64/src/contrib/sendmail/libmilter/listener.c:508: warning: cast to pointer from integer of different size === lib/libmp === lib/libnetgraph === lib/libopie === lib/libpam === lib/libpam/modules === lib/libpam/modules/pam_deny === lib/libpam/modules/pam_echo === lib/libpam/modules/pam_exec /usr/home/des/tinderbox/sparc64/src/lib/libpam/modules/pam_exec/pam_exec.c: In function `_pam_exec': /usr/home/des/tinderbox/sparc64/src/lib/libpam/modules/pam_exec/pam_exec.c:66: warning: passing arg 2 of `execv' from incompatible pointer type /usr/home/des/tinderbox/sparc64/src/lib/libpam/modules/pam_exec/pam_exec.c: In function `_pam_exec': /usr/home/des/tinderbox/sparc64/src/lib/libpam/modules/pam_exec/pam_exec.c:66: warning: passing arg 2 of `execv' from incompatible pointer type === lib/libpam/modules/pam_ftp === lib/libpam/modules/pam_ftpusers === lib/libpam/modules/pam_kerberosIV === lib/libpam/modules/pam_krb5 === lib/libpam/modules/pam_ksu /usr/home/des/tinderbox/sparc64/src/lib/libpam/modules/pam_ksu/pam_ksu.c:54: warning: `pam_sm_authenticate' defined but not used /usr/home/des/tinderbox/sparc64/src/lib/libpam/modules/pam_ksu/pam_ksu.c:91: warning: `pam_sm_setcred' defined but not used === lib/libpam/modules/pam_lastlog === lib/libpam/modules/pam_login_access === lib/libpam/modules/pam_nologin === lib/libpam/modules/pam_opie === lib/libpam/modules/pam_opieaccess === lib/libpam/modules/pam_passwdqc /usr/home/des/tinderbox/sparc64/src/contrib/pam_modules/pam_passwdqc/pam_passwdqc.c: In function `converse': /usr/home/des/tinderbox/sparc64/src/contrib/pam_modules/pam_passwdqc/pam_passwdqc.c:145: warning: assignment discards qualifiers from pointer target type /usr/home/des/tinderbox/sparc64/src/contrib/pam_modules/pam_passwdqc/pam_passwdqc.c: In function `pam_sm_chauthtok': /usr/home/des/tinderbox/sparc64/src/contrib/pam_modules/pam_passwdqc/pam_passwdqc.c:367: warning: assignment discards qualifiers from pointer target type /usr/home/des/tinderbox/sparc64/src/contrib/pam_modules/pam_passwdqc/passwdqc_random.c: In function `_passwdqc_random': /usr/home/des/tinderbox/sparc64/src/contrib/pam_modules/pam_passwdqc/passwdqc_random.c:69: warning: comparison between signed and unsigned
sparc64 tinderbox failure
=== games/adventure
=== games/arithmetic
=== games/atc
=== games/backgammon
=== games/backgammon/backgammon
=== games/backgammon/teachgammon
=== games/battlestar
=== games/bcd
=== games/bs
=== games/caesar
=== games/canfield
=== games/canfield/canfield
=== games/canfield/cfscores
=== games/cribbage
=== games/dm
=== games/factor
=== games/fish
=== games/fortune
=== games/fortune/fortune
=== games/fortune/strfile
=== games/fortune/datfiles
=== games/fortune/unstr
=== games/grdc
=== games/hack
=== games/hangman
=== games/larn
=== games/mille
/usr/home/des/tinderbox/sparc64/src/games/mille/move.c: In function `playcard':
/usr/home/des/tinderbox/sparc64/src/games/mille/move.c:348: warning: comparison is
always false due to limited range of data type
/usr/home/des/tinderbox/sparc64/src/games/mille/save.c: In function `save':
/usr/home/des/tinderbox/sparc64/src/games/mille/save.c:137: warning: passing arg 2 of
`varpush' from incompatible pointer type
/usr/home/des/tinderbox/sparc64/src/games/mille/save.c: In function `rest_f':
/usr/home/des/tinderbox/sparc64/src/games/mille/save.c:166: warning: passing arg 2 of
`varpush' from incompatible pointer type
/usr/home/des/tinderbox/sparc64/src/games/mille/varpush.c: In function `varpush':
/usr/home/des/tinderbox/sparc64/src/games/mille/varpush.c:71: warning: comparison of
distinct pointer types lacks a cast
=== games/morse
=== games/number
=== games/phantasia
=== games/piano
=== games/pig
=== games/pom
=== games/ppt
=== games/primes
=== games/quiz
=== games/rain
=== games/random
=== games/robots
=== games/rogue
=== games/sail
/usr/home/des/tinderbox/sparc64/src/games/sail/sync.c: In function `Write':
/usr/home/des/tinderbox/sparc64/src/games/sail/sync.c:131: warning: cast to pointer
from integer of different size
=== games/snake
=== games/snake/snake
=== games/snake/snscore
=== games/trek
/usr/home/des/tinderbox/sparc64/src/games/trek/utility.c: In function `syserr':
/usr/home/des/tinderbox/sparc64/src/games/trek/utility.c:149: warning: passing arg 1
of `printf' makes pointer from integer without a cast
=== games/wargames
=== games/worm
=== games/worms
=== games/wump
=== gnu
=== gnu/lib
=== gnu/lib/csu
=== gnu/lib/libgcc
=== gnu/lib/libdialog
=== gnu/lib/libregex
=== gnu/lib/libregex/doc
regex.texi:876: warning: unlikely character , in @var.
regex.texi:880: warning: unlikely character , in @var.
regex.texi:1126: warning: Info cannot handle `:' in index entry `@samp{[:} in regex'.
regex.texi:1127: warning: Info cannot handle `:' in index entry `@samp{:]} in regex'.
=== gnu/lib/libreadline
=== gnu/lib/libreadline/history
=== gnu/lib/libreadline/history/doc
/usr/home/des/tinderbox/sparc64/src/gnu/lib/libreadline/history/doc/../../../../../contrib/libreadline/doc/hstech.texinfo:451:
warning: unlikely character [ in @var.
/usr/home/des/tinderbox/sparc64/src/gnu/lib/libreadline/history/doc/../../../../../contrib/libreadline/doc/hstech.texinfo:451:
warning: unlikely character ] in @var.
=== gnu/lib/libreadline/readline
=== gnu/lib/libreadline/readline/doc
=== gnu/lib/libstdc++
=== gnu/lib/libstdc++/doc
make: don't know how to make iostream.info. Stop
*** Error code 2
Stop in /usr/home/des/tinderbox/sparc64/src/gnu/lib/libstdc++.
*** Error code 1
Stop in /usr/home/des/tinderbox/sparc64/src/gnu/lib.
*** Error code 1
Stop in /usr/home/des/tinderbox/sparc64/src/gnu.
*** Error code 1
Stop in /usr/home/des/tinderbox/sparc64/src.
*** Error code 1
Stop in /usr/home/des/tinderbox/sparc64/src.
*** Error code 1
Stop in /usr/home/des/tinderbox/sparc64/src.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
sparc64 tinderbox failure
=== games/snake
=== games/snake/snake
=== games/snake/snscore
=== games/trek
/usr/home/des/tinderbox/sparc64/src/games/trek/utility.c: In function `syserr':
/usr/home/des/tinderbox/sparc64/src/games/trek/utility.c:149: warning: passing arg 1
of `printf' makes pointer from integer without a cast
=== games/wargames
=== games/worm
=== games/worms
=== games/wump
=== gnu
=== gnu/lib
=== gnu/lib/csu
=== gnu/lib/libgcc
=== gnu/lib/libdialog
=== gnu/lib/libregex
=== gnu/lib/libregex/doc
regex.texi:876: warning: unlikely character , in @var.
regex.texi:880: warning: unlikely character , in @var.
regex.texi:1126: warning: Info cannot handle `:' in index entry `@samp{[:} in regex'.
regex.texi:1127: warning: Info cannot handle `:' in index entry `@samp{:]} in regex'.
=== gnu/lib/libreadline
=== gnu/lib/libreadline/history
=== gnu/lib/libreadline/history/doc
/usr/home/des/tinderbox/sparc64/src/gnu/lib/libreadline/history/doc/../../../../../contrib/libreadline/doc/hstech.texinfo:451:
warning: unlikely character [ in @var.
/usr/home/des/tinderbox/sparc64/src/gnu/lib/libreadline/history/doc/../../../../../contrib/libreadline/doc/hstech.texinfo:451:
warning: unlikely character ] in @var.
=== gnu/lib/libreadline/readline
=== gnu/lib/libreadline/readline/doc
=== gnu/lib/libstdc++
=== gnu/lib/libsupc++
=== gnu/lib/libobjc
=== gnu/lib/libg2c
=== gnu/usr.bin
=== gnu/usr.bin/bc
=== gnu/usr.bin/binutils
=== gnu/usr.bin/binutils/libiberty
=== gnu/usr.bin/binutils/libbfd
/usr/home/des/tinderbox/sparc64/src/contrib/binutils/bfd/elf-eh-frame.c: In function
`_bfd_elf_discard_section_eh_frame':
/usr/home/des/tinderbox/sparc64/src/contrib/binutils/bfd/elf-eh-frame.c:416: warning:
comparison between signed and unsigned
=== gnu/usr.bin/binutils/libopcodes
=== gnu/usr.bin/binutils/libbinutils
=== gnu/usr.bin/binutils/addr2line
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/ar
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/as
=== gnu/usr.bin/binutils/as/sparc64-freebsd
=== gnu/usr.bin/binutils/gasp
=== gnu/usr.bin/binutils/ld
=== gnu/usr.bin/binutils/nm
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/objcopy
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/objdump
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/ranlib
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/readelf
=== gnu/usr.bin/binutils/size
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/strings
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/strip
../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname':
bucomm.o(.text+0x4e0): warning: mktemp() possibly used unsafely; consider using
mkstemp()
=== gnu/usr.bin/binutils/doc
/usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texinfo:2108:
warning: Info cannot handle `:' in index entry `@code{:} (label)'.
/usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texinfo:2109:
warning: Info cannot handle `:' in index entry `label (@code{:})'.
/usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texinfo:3927:
warning: Info cannot handle `:' in index entry `listing control: new page'.
/usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texinfo:4814:
warning: Info cannot handle `:' in index entry `listing control: paper size'.
/usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texinfo:4903:
warning: Info cannot handle `:' in index entry `listing control: subtitle'.
/usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc/as.texinfo:5391:
warning: Info cannot handle `:' in index entry `listing control: title line'.
/usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld/ld.texinfo:3202:
warning: Info cannot handle `:' in
Re: UFS2 related message?
From: Wesley Morgan [EMAIL PROTECTED] Date: Sat, 22 Jun 2002 10:51:36 -0400 (EDT) ::By chance, is this a new installation? A month or so ago I was adding a ::drive to a -current system and I discovered that the newfs defaults were ::setting insanely large block/fragment/inode sizes and I could not even do ::a 'make world' on that partition. Had to completely reinstall and override ::the defaults. No, I've been using my system for over a year now. :-) Well, the problem seems to have been fixed by patch from Kirk McKusick. Thanks for follow up anyway, Haro ::On Sat, 22 Jun 2002, Munehiro Matsuda wrote: :: :: Hello all, :: :: After the import of UFS2 patch into -current, I get the following messages. :: :: pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes :: pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes :: pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: UFS2 related message?
From: Poul-Henning Kamp [EMAIL PROTECTED] Date: Sat, 22 Jun 2002 20:27:58 +0200 ::After the import of UFS2 patch into -current, I get the following messages. :: ::pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes ::pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes ::pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes :: ::Is it related to UFS2 by anyway? :: ::Yes, this seems to be related to UFS2. :: ::Please send an email to [EMAIL PROTECTED] with the output of ::dumpfs from that partition (or upload the file and send him ::the URL) :: ::Please also tell him if you ran any of the posted versions of the ::UFS2 patch or not. The problem seems have been fixed by Kirk McKusick with ffs_alloc.c rev1.94. Thank you for your follow up, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: UFS2 related message?
From: Kirk McKusick [EMAIL PROTECTED] Date: Sat, 22 Jun 2002 14:31:02 -0700 ::The problem with running out of inodes is now fixed and checked in ::on freefall. You need to pick up /sys/ufs/ffs/ffs_alloc.c revision ::1.94 or later. For those that care, the log entry describing the ::problem: Thank you very much. It seems to have fixed my problem. Keep up the excellent work. Thank you, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Floppy only 8.3 filenames
On 22 Jun 2002, Jan Stocker wrote: i am sure on my old 4.x system i was able to mount my floppy-disc and can use long filenames, but on my -current mount -t msdos /dev/fd0 /mnt leads to 8.3 lowercase and mount -t msdos /dev/fd0c /mnt the first time to 8.3 uppercase and the following to 8.3 lowercase... msdos doesn't exist in -current (it has been renamed to msdosfs), so mount -t msdos ... should just print a message about mount_msdos not being found. Perhaps you have an old version of mount_msdos. It might not work, since the mount family is one of the main areas where -current breaks binary compatibility. Similarly for the msdos module, except breakage of binary compatibility is normal for all modules. Getting a different result the second time (after loading a module) looks more like a problem with the module than with the mount program. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
