Re: HEADSUP: pca driver being retired.
On Wed, Aug 13, 2003 at 11:02:23AM +0200, Poul-Henning Kamp wrote: > I plan to remove the pca driver in about a week. > Protest only from actual users respected. Not really 'actual', only 'old'. A lot of time ago I sent a message about "lost speaker" (IIRC) because having both devive in the kernel (pca and speaker) hide the second. Don't really remember the thread. (or maybe a PR? it was on early 2002, I found only this pointer: http://www.gufi.org/ricerca.php3?mode=show&id=freebsd:current:15870) # pca: PCM audio through your PC speaker ## :-( device pca # it break speaker At that time I removed pca and never tryed to re-add. This is just a 'bye-bye pca" :'-( -- Riccardo. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: newsyslog problems with -C
On Sat, Aug 02, 2003 at 02:03:32AM +0200, Riccardo Torrini wrote: > Without creating by hand /var/tmp/{foo,bar} this command fail > # newsyslog -v -F -C -f /usr/local/etc/rotatemailbackup.conf > --> [creating entry for /var/tmp/foo] > --> [creating entry for /var/tmp/bar] > /var/tmp/foo <7Z>: does not exist -> will create. > newsyslog: can't fchmod temp file '/var/tmp/foo.z8FjDcW': \ Bad file descriptor Found (I think :-) # truss newsyslog -v -CC -F -f \ /usr/local/etc/rotatemailbackup.conf /var/tmp/foo [...] lstat("/var/tmp",0xbfbffad0) = 0 (0x0) gettimeofday(0xbfbff500,0x0) = 0 (0x0) getpid() = 84801 (0x14b41) open("/dev/urandom",0x0,00) = 3 (0x3) read(0x3,0xbfbff50c,0x74)= 116 (0x74) close(3) = 0 (0x0) stat("/var/tmp",0xbfbff610) = 0 (0x0) open("/var/tmp/foo.zM4kxLE",0xa02,0600) = 3 (0x3) fchown(0x3,0x3e9,0x6)= 0 (0x0) close(3) = 0 (0x0) fchmod(0x3,0x180)ERR#9 'Bad file descriptor' [...] It seems that last two lines are reversed (close before fchmod). Looking into sources I found two close(fd). Here is the patch: -8<-[ patch ]-8<- # diff -u newsyslog.c.orig newsyslog.c --- newsyslog.c.origSun May 25 18:46:13 2003 +++ newsyslog.c Sat Aug 2 02:28:50 2003 @@ -1764,7 +1764,6 @@ failed = fchown(fd, ent->uid, ent->gid); if (failed) err(1, "can't fchown temp file %s", tempfile); - (void) close(fd); } } -8<-[ patch ]-8<- Now it works, here is the correct flow: [...] open("/dev/urandom",0x0,00) = 3 (0x3) read(0x3,0xbfbff4bc,0x74)= 116 (0x74) close(3) = 0 (0x0) stat("/var/tmp",0xbfbff5c0) = 0 (0x0) open("/var/tmp/foo.zKXXcYJ",0xa02,0600) = 3 (0x3) fchown(0x3,0x3e9,0x6)= 0 (0x0) fchmod(0x3,0x180)= 0 (0x0) rename(0xbfbff680,0x8058060) = 0 (0x0) close(3) = 0 (0x0) --> [freeing entry for /var/tmp/foo] [...] Please commit on both 4.8 and -CURRENT because newsyslog.c 1.25.2.21 (4.8) and newsyslog.c 1.70 (-CURRENT) are equal but the headers. Thanks. -- Riccardo. ( http://www.GUFI.org/~vic/ ) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
newsyslog problems with -C
I have created a private newsyslog.conf with this contents: -8<- /var/tmp/foofoo:mail600 7 * @T00ZBCN /var/tmp/barbar:mail600 7 * @T00ZBCN -8<- Without creating by hand /var/tmp/{foo,bar} this command fail leaving the temporary mkstemp /var/tmp/{foo,bar}.zXX (with XX variable): # cd /var/tmp # newsyslog -v -F -C -f /usr/local/etc/rotatemailbackup.conf --> [creating entry for /var/tmp/foo] --> [creating entry for /var/tmp/bar] /var/tmp/foo <7Z>: does not exist -> will create. newsyslog: can't fchmod temp file '/var/tmp/foo.z8FjDcW': Bad file descriptor # newsyslog -v -F -CC -f /silos/usr/local/etc/rotatemailbackup.conf --> [creating entry for /var/tmp/foo] --> [creating entry for /var/tmp/bar] /var/tmp/foo <7Z>: does not exist -> will create. newsyslog: can't fchmod temp file '/var/tmp/foo.zyXVe1U': Bad file descriptor But it works if I manually 'touch' both {foo,bar} # touch foo bar # newsyslog -v -F -C -f /silos/usr/local/etc/rotatemailbackup.conf --> [creating entry for /var/tmp/foo] --> [creating entry for /var/tmp/bar] /var/tmp/foo <7Z>: --> trimming log --> [freeing entry for /var/tmp/foo] /var/tmp/bar <7Z>: --> trimming log --> [freeing entry for /var/tmp/bar] # newsyslog -v -F -CC -f /silos/usr/local/etc/rotatemailbackup.conf --> [creating entry for /var/tmp/foo] --> [creating entry for /var/tmp/bar] /var/tmp/foo <7Z>: --> trimming log --> [freeing entry for /var/tmp/foo] /var/tmp/bar <7Z>: --> trimming log --> [freeing entry for /var/tmp/bar] It also fails if I remove the mandatory "C" flag from config file. So, how the -C and C parameters are supposed to works? NB: this happens on both 4.8 and recent -CURRENT and only when user:group are specified... -- Riccardo. ( http://www.GUFI.org/~vic/ ) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ReiserFS
On Sun, Jun 22, 2003 at 07:00:26PM +0200, Brad Knowles wrote: > What if it's the same machine? What if they have only the one > machine, so they can't even copy it over to another one, just to > copy it back? What about using a FAT32 exchange partition? On the same disk or on a new one, depending of the size of the data to be moved. And (as the very last resource) you can upload a dump somewhere on internet and then download from the FreeBSD system (or even send it uuencoded by mail :-) -- Riccardo. ( http://www.GUFI.org/~vic/ ) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Info please...xsession
On Thu, Mar 20, 2003 at 09:28:25AM +0100, CARTER Anthony wrote: > Can someone give me their permissions on a users .xsession-errors > file? -rw--- {me} {mygroup} > Doesn't this above file get created automatically if it is deleted? Yes. At least here ;) FYI: I still using XFree86-4.2.1 with wdm started from /etc/ttys. -- Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD/i386 kern.flp flooding again
On Sun, Feb 16, 2003 at 09:03:59PM +0900, Makoto Matsushita wrote: > If you are serious about this, attached below is a current kernel > configuration file for kern.flp kernel named BOOTMFS (attention: it is > only just for boot floppy, not GENERIC nor default installed kernel). > machine i386 > cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > deviceeisa > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > devicebpf # Berkeley packet filter Is this stuff really needed on a boot floppy? Maybe we can leave only I486_CPU? What about removing also device eisa and/or bpf? (I'm just curious, don't expect to be an expert :-) -- Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
calendar(1) badly crashes
I (by mistake) passed a directory instead of a file to calendar(1): # uname -v FreeBSD 5.0-CURRENT #52: Sat Jan 18 00:40:27 CET 2003 ... # calendar -f /some.missing.file.or.dir calendar: no calendar file: ``/some.missing.file.or.dir'' # calendar -f /etc cpp: Internal error: Segmentation fault (program tradcpp0) Please submit a full bug report. See http://www.gnu.org/software/gcc/bugs.html> for instructions. This happens also on previous versions at least up to 11.1.2003. Under 4.x it works a bit better (but don't show file/dir name): # uname -v FreeBSD 4.7-STABLE #33: Thu Oct 24 04:24:42 CEST 2002 ... # calendar -f /some.missing.file.or.dir calendar: no calendar file: ``/some.missing.file.or.dir'' # calendar -f /etc cpp0: Input file `' is a directory Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: devfs permissions after reboot
On 26-Dec-2002 (23:11:27/GMT) Gernot A. Weber wrote: > devfs rule add path uscanner0 mode 666 I used this way: -8<-[ /etc/usbd.conf ]-8<- [...] device "Scanner Epson Perfection 1240U (photo)" product 0x010b vendor 0x04b8 release 0x0114 devname "uscanner[0-9]+" attach "/bin/chmod 666 /dev/${DEVNAME} && echo L16cce > /dev/speaker" detach "echo L16eec > /dev/speaker" The detach label doesn't work (and never worked on last year). Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unrar doesn't work under current
On 18-Dec-2002 (07:33:03/GMT) Kris Kennaway wrote: >> But what about rar/unrar ports that overwrite one each other? > I don't know what you mean here. Try to install /usr/ports/archivers/{rar,unrar} in any order... And then (or even better, before then) look at installed files: # cd /usr/ports/archivers && grep bin/unrar {un,}rar/pkg-plist unrar/pkg-plist:bin/unrar rar/pkg-plist:bin/unrar At this point removing one of each port (rar,unrar) destroy the other bin/unrar. Is this a desidered feature? > And _why_ rar port works (on same file) and unrar not? > (at least this is a but in rar that doesn't do correct locking?) Ooppss, s/but/bug/ (as stated before I need a vacancy :-) Riccardo. PS: we have the same problem at least with autoconf*/automake* pair, where installed files names overlapping. IMVHO think this is a Bad Thing(tm). (Anyway this is not a -CURRENT-only problem) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unrar doesn't work under current
On 18-Dec-2002 (06:52:54/GMT) Kris Kennaway wrote: > This is due to lack of rpc.lockd running on the nfs client and/or > server. Yes, I tryed on a nfs mounted dir from my -CURRENT home machine. This means that this is a pilot error? Again? :-( I'm sorry. I think that I must sleep a little more... But what about rar/unrar ports that overwrite one each other? And _why_ rar port works (on same file) and unrar not? (at least this is a but in rar that doesn't do correct locking?) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
unrar doesn't work under current
Trying to extract a single or multi volume archive doesn't work. Same archive can be extracted fine with unrar under 4.7-STABLE. My -CURRENT from 10 day ago. Tryed to remove and rebuild unrar without luck. rar on -CURRENT also works. Any idea? -8<-[ from 4.7-STABLE ]-8<- # date > sample # rar a sample.rar sample # ll sample* -rw-r--r-- 1 root staff 29 Dec 17 01:35 sample -rw-r--r-- 1 root staff 103 Dec 17 01:35 sample.rar # unrar t sample.rar UNRAR 3.10 beta 1 freeware Copyright (c) 1993-2002 Eugene Roshal Testing archive sample.rar Testing sampleOK All OK -8<-[ from 5.0-CURRENT, same file ]-8<- # uname -v FreeBSD 5.0-RC #47: Sun Dec 8 18:09:42 CET 2002 ... # unrar t sample.rar UNRAR 3.10 beta 1 freeware Copyright (c) 1993-2002 Eugene Roshal Cannot open sample.rar No files to extract # rar t sample.rar RAR 3.00Copyright (c) 1993-2002 Eugene Roshal14 May 2002 Shareware version Type RAR -? for help Testing archive sample.rar Testing sampleOK All OK -8<- Also note that installing rar after unrar overwrite .../bin/unrar :( # cd /usr/ports/archivers && grep ^bin/unrar *rar*/pkg-plist rar/pkg-plist:bin/unrar unrar/pkg-plist:bin/unrar TIA, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The great perl script rewrite - big problem
On 08-Dec-2002 (17:54:49/GMT) Mark Murray wrote: > The Perl rewrite does not affect 4.x, only 5.x. Yes, I know, but I think would be usefull remove it also from 4.x, at least for small job (perl script inline, as in periodic). >> Because FreeBSD.org use postfix I think it already resolved this >> issue, can you distribute your special periodic scripts? What about support for postfix MTA in daily 460? Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The great perl script rewrite - big problem
On 08-Dec-2002 (17:07:02/GMT) Christian Brueffer wrote: > this has already been taken care of: > keramida2002/12/07 15:37:45 PST > Log: > Avoid using perl in the periodic & security scripts. This brings > the base system one step closer to being totally perl-free. And me one step back :-( My system was from December 6. Sorry, pilot error. I'm now rebuilding my world & kernel. -- >>> Kernel build for TRUDY completed on Sun Dec 8 18:27:36 CET 2002 -- Done. Now installing... Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The great perl script rewrite - big problem
I contributed to the great perl script rewrite but seems that we forgot to rewrite some important perl script: # grep -lR perl /etc/periodic/ /etc/periodic/daily/440.status-mailq /etc/periodic/daily/460.status-mail-rejects /etc/periodic/daily/470.status-named /etc/periodic/security/550.ipfwlimit /etc/periodic/security/650.ip6fwlimit I noticed this after installing postfix MTA into my 4.7 home server. BTW: postfix port disable periodic with this variables: # cat /etc/periodic.conf daily_status_mail_rejects_enable="NO" daily_status_include_submit_mailq="NO" daily_submit_queuerun="NO" Because FreeBSD.org use postfix I think it already resolved this issue, can you distribute your special periodic scripts? I tryed to convert 460* myself but the perl line is really too complex for me :-( I think that an awk migration may be appropriate, and also a MFC. Also a Cc: to stable people may be required. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trivial patch: fdisk doesn't recognize my partitions
On 01-Dec-2002 (23:46:00/GMT) Terry Lambert wrote: > WHY ARE WE NOT RESPECTING THE DECISION TO HIDE THE THINGS? > A user installed the software doing the hiding on purpose. > The software changed the ID hide it, on purpose. > Windows ignores these partitions -- on purpose. I'm really sorry for creating that a mess, I started this thread only because fdisk recognize _OTHER_ hidden partition and I would like to add hidden FAT32 to that _existing_ list. Sorry for wasting your time. :( Anyway, if you check this you can find symmetric partition type (as written in .../fdisk.c,v 1.66 2002/10/27 10:52:54 phk): real,{0x01, "Primary DOS with 12 bit FAT"} hidden ,{0x11, "OS/2 BM: hidden DOS with 12-bit FAT"} real,{0x04, "Primary DOS with 16 bit FAT (< 32MB)"} hidden ,{0x14, "OS/2 BM: hidden DOS with 16-bit FAT (< 32MB)"} real,{0x06, "Primary 'big' DOS (>= 32MB)"} hidden ,{0x16, "OS/2 BM: hidden DOS with 16-bit FAT (>= 32MB)"} real,{0x07, "OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX"} hidden ,{0x17, "OS/2 BM: hidden IFS (e.g. HPFS)"} Only for this I added 0x1B/0x1C as hidden version of 0x0B/0x0C. real,{0x0B, "DOS or Windows 95 with 32 bit FAT"} myidea ,{0x1B, "Hidden DOS or Windows 95 with 32 bit FAT"} real,{0x0C, "DOS or Windows 95 with 32 bit FAT (LBA)"} myidea ,{0x1C, "Hidden DOS or Windows 95 with 32 bit FAT (LBA)"} Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trivial patch: fdisk doesn't recognize my partitions
On 29-Nov-2002 (01:34:27/GMT) Bruce Evans wrote: RT>>> I have 4 primary partitions and I use a boot manager (magic.com) [...] RT>>> As far as I know it use an EXOR 0x10 to hide/unhide but fdisk RT>>> doesn't recognize 0x0B/0x0C fat32 when hidden (0x1B/0x1C) PHK>> I think this is very marginal use really... PHK>> But as I said, this is rather marginal and I really don't feel PHK>> it should go in unless this xor-0x10 convention is more widespread. BE> "Hiding" partitions is a bug IMO, so it should have negative BE> support. This convention would break many OS's conventions. BE> E.g., NextSTEP | 0x10 gives BSDI. Yes, indeed. Anyway 0x10-0x1F range seems to be for hidden partition, this is why I go the wrong way. Sorry for wasting time. :( If you check this you can find symmetric partition type (as written in .../fdisk.c,v 1.66 2002/10/27 10:52:54 phk): real,{0x01, "Primary DOS with 12 bit FAT"} hidden ,{0x11, "OS/2 BM: hidden DOS with 12-bit FAT"} real,{0x04, "Primary DOS with 16 bit FAT (< 32MB)"} hidden ,{0x14, "OS/2 BM: hidden DOS with 16-bit FAT (< 32MB)"} real,{0x06, "Primary 'big' DOS (>= 32MB)"} hidden ,{0x16, "OS/2 BM: hidden DOS with 16-bit FAT (>= 32MB)"} real,{0x07, "OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX"} hidden ,{0x17, "OS/2 BM: hidden IFS (e.g. HPFS)"} Only for this I added 0x1B/0x1C as hidden version of 0x0B/0x0C. real,{0x0B, "DOS or Windows 95 with 32 bit FAT"} myidea ,{0x1B, "Hidden DOS or Windows 95 with 32 bit FAT"} real,{0x0C, "DOS or Windows 95 with 32 bit FAT (LBA)"} myidea ,{0x1C, "Hidden DOS or Windows 95 with 32 bit FAT (LBA)"} Riccardo. PS: maybe XOR-0x10 only if <= 0x1F ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Trivial patch: fdisk doesn't recognize my partitions
I have 4 primary partitions and I use a boot manager (magic.com) that install some black magic that hide unused partition, this permit to have multiple 'other-OS' partition that don't know of each other (but, obviously, FreeBSD can see and mount all of them). As far as I know it use an EXOR 0x10 to hide/unhide but fdisk doesn't recognize 0x0B/0x0C fat32 when hidden (0x1B/0x1C) This is the patch, that can be extended easily to cover the range 0x1A-0x1F (0x0A-0x0F when hidden). I simply copied strings from 0x0B/0x0C and added Hidden in front of them :-) Any comment? (I don't know if 0x1B/0x1C are registered as used) # cd /usr/src/sbin/fdisk # diff -u3 fdisk.c.orig fdisk.c --- fdisk.c.origMon Oct 28 14:31:04 2002 +++ fdisk.c Thu Nov 28 22:42:05 2002 @@ -151,6 +151,8 @@ ,{0x16, "OS/2 BM: hidden DOS with 16-bit FAT (>= 32MB)"} ,{0x17, "OS/2 BM: hidden IFS (e.g. HPFS)"} ,{0x18, "AST Windows swapfile"} + ,{0x1B, "Hidden DOS or Windows 95 with 32 bit FAT"} + ,{0x1C, "Hidden DOS or Windows 95 with 32 bit FAT (LBA)"} ,{0x24, "NEC DOS"} ,{0x3C, "PartitionMagic recovery"} ,{0x39, "plan9"} And yes, when FreeBSD is hidden it become 0xB5, so if you have multiple FreeBSDprimary partition I think we must add also this: @@ -195,6 +197,7 @@ ,{0xA7, "NeXTSTEP"} ,{0xA9, "NetBSD"} ,{0xAC, "IBM JFS"} + ,{0xB5, "Hidden FreeBSD/NetBSD/386BSD"} ,{0xB7, "BSDI BSD/386 file system"} ,{0xB8, "BSDI BSD/386 swap"} ,{0xC1, "DRDOS/sec with 12-bit FAT"} # fdisk.orig *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=12592 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=12592 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 27 (0x1b),(unknown) start 63, size 1638567 (800 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 101/ head 254/ sector 63 The data for partition 2 is: sysid 22 (0x16),(OS/2 BM: hidden DOS with 16-bit FAT (>= 32MB)) start 1638630, size 208845 (101 Meg), flag 0 beg: cyl 102/ head 0/ sector 1; end: cyl 114/ head 254/ sector 63 The data for partition 3 is: sysid 27 (0x1b),(unknown) start 1847475, size 3068415 (1498 Meg), flag 0 beg: cyl 115/ head 0/ sector 1; end: cyl 305/ head 254/ sector 63 The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 4915890, size 7775460 (3796 Meg), flag 80 (active) beg: cyl 306/ head 0/ sector 1; end: cyl 789/ head 254/ sector 63 # ./fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=12592 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=12592 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 27 (0x1b),(Hidden DOS or Windows 95 with 32 bit FAT) start 63, size 1638567 (800 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 101/ head 254/ sector 63 The data for partition 2 is: sysid 22 (0x16),(OS/2 BM: hidden DOS with 16-bit FAT (>= 32MB)) start 1638630, size 208845 (101 Meg), flag 0 beg: cyl 102/ head 0/ sector 1; end: cyl 114/ head 254/ sector 63 The data for partition 3 is: sysid 27 (0x1b),(Hidden DOS or Windows 95 with 32 bit FAT) start 1847475, size 3068415 (1498 Meg), flag 0 beg: cyl 115/ head 0/ sector 1; end: cyl 305/ head 254/ sector 63 The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 4915890, size 7775460 (3796 Meg), flag 80 (active) beg: cyl 306/ head 0/ sector 1; end: cyl 789/ head 254/ sector 63 Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Run two copies of named from rc.conf?
On 19-Nov-2002 (04:06:22/GMT) John De Boskey wrote: > I need to kick off 2 name servers. The first is authoritive for > the domain as seen externally and the 2nd which is authoritive > for the internal network. I have only one named running, SOA for torrini.org for external and internal host and SOA for torrini.home for internal only host. It use allow-transfer/allow-query pair into named.conf and it is up and running on a 4.x machine from about an year. Hope this can help. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: anybody help? undefined reference to 'xstrtod' occuring
On 14-Oct-2002 (18:10:16/GMT) David Francheski wrote: > I'm trying to upgrade from a 5.0 DP1 system to the latest -current > (as of last week sometime). I recently asked a similar question: upgrade from a too old -CURRENT (May 15) to a recent one. The solution was some small intermediate update, I use this dates and they worked fine: *default date=2002.08.15.00.00.42 *default date=2002.08.26.00.00.42 *default date=2002.09.09.00.00.42 *default date=2002.09.15.00.00.42 This means 4 more builds, but it worked for me. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: tcsh hang in -current (kse bug?)
On 06-Oct-2002 (23:10:55/GMT) Kris Kennaway wrote: > Can anyone else reproduce this in tcsh? > rpcgen -s `perl -e 'print "a"x5'` > Word too long. Mee too mail. Using {50,500,5000} works, hang only with 5 (not tested with others numbers). Doing: # echo {your_command} print only "word too long" without hang. > And then tcsh will hang in a state unresponsive to signals. And 'ps -auxwww' was unable to find neither rpcgen nor perl. All of this with a not too recent system, build on 24.9.2002 with: *default date=2002.09.09.00.00.42 Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Access to ide cdrom/cd writer bugged?
I'm trying to understand why when accessing file to cdrom their contents change every time (in case of big file, at least). I usally backup some stuff (mail, sources, scanned images) and add to cdrom a files.md5 with the md5 keys of all files. (yes, I'm a bit paranoid :-) With my last system (-CURRENT of May 8, 2002) all works fine but after a recent build with an old date [1] (see my thread about make world from pre-gcc_3.1 to last -CURRENT post-gcc_3.2) seems that all file are damaged. Because I tryed a lot of old backup (10 cd-r) and all fails md5 check I tryed with 'another' OS ;) And (obviuosly?) all contents are correct. And now the question: what changed in ata-driver from May 8 to Aug 15? Is a know issue? Can I enable/disable some new feature of ata to recheck files? Probably I need some new world, but after recent post of various kernel panic I prefer to remain with my old system. Anyway, is some date from Aug 15 to today usable to step a bit forward? Riccardo. [1] (I used this: *default date=2002.08.15.00.00.42) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
It works ! (was Re: Unable to buildworld (new record, 18"))
On 08-Sep-2002 (19:54:17/GMT) Riccardo Torrini wrote: >> There have been at least two gcc upgrades since then. I believe >> the easiest way to upgrade to today's -current would be to install >> a fairly recent snapshot ... instead of trying to debug ... > I have tryed with a middle version (1 jul 2002) but it fails without > and with make includes before build, now I'm trying with cvsup from > 15 aug 2002 (as written by Munish Chopra on 1 sep: IIRC current was > in good shape between August 12-15, 17, 18, 22-24) ... Ok. All done. My start point was really too old, anyway this is the full story: - starting from -CURRENT of 8 May, used as desktop (full of bells and whistles, homes on a nfs disk on a safe -STABLE local server :-) - cvsuped daily and compiled w/out install at least once a week (this before holidays). - tryed to upgrade to latest -CURRENT last week w/out success, with a lot of error, maybe due to double gcc update (2.95 -> 3.1 -> 3.2) - cvsuped back to 1 jul, new buildworld, failed - found mail into archives speaking about some "good shape" days - cvsuped again to 15 aug, new buildworld, failed - added some switches: -DNOCLEAN, -DNO_WERROR, -DNOCRYPT (one at a time, every time world go forward a bit) - build complete, kernel complete, install complete, reboot ... and Yes! I forgot mergemaster :( - new full buildworld w/out switches, complete fine. new kernel, another full install, mergemaster :-) reboot. NB: build done w/out CPUTYPE (usually was =p3) and with CFLAGS= -O2 -pipe Hoping this can help others not-too-current users. Upgrade always possible, even from old versions (with some care) Now last doubt: after next upgrade to post-gcc_3.2 is a complete port rebuild necessary because c++ ports stop working or not? Thanks a lot, Riccardo, now more-current :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to buildworld (new record, 18")
On 08-Sep-2002 (13:56:34/GMT) Giorgos Keramidas wrote: > There have been at least two gcc upgrades since then. I believe the > easiest way to upgrade to today's -current would be to install a > fairly recent snapshot from http://snapshots.jp.FreeBSD.org/ instead > of trying to debug the many ways in which a buildworld can fail. I'm obstinate :) I have tryed with a middle version (1 jul 2002) but it fails without and with make includes before build, now I'm trying with cvsup from 15 aug 2002 (as written by Munish Chopra on 1 sep: IIRC current was in good shape between August 12-15, 17, 18, 22-24) and it is still compiling (I'm crossing fingers)... If it complete (I hope it complete) is -CURRENT of 15 aug 2002 a reasonable version to install and to use to jump to today ones? Any comment? Thanks again, Riccardo. PS: It stopped on stage 4:libraries, something about crypt, now is running again with -DNO_WERROR -DNOCLEAN -DNOCRYPT ;^) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to buildworld (new record, 18")
On 07-Sep-2002 (21:55:22/GMT) Giorgos Keramidas wrote: >> /usr/include/sys/_types.h:71: declaration does not declare anything >> *** Error code 1 > Which revision of /usr/include/sys/_types.h do you have? # ident /usr/include/sys/_types.h /usr/include/sys/_types.h: $FreeBSD: src/sys/sys/_types.h,v 1.7 2002/08/25 19:26:31 mike Exp $ # ident /usr/include/stdlib.h /usr/include/stdlib.h: $FreeBSD: src/include/stdlib.h,v 1.41 2002/09/06 11:23:32 tjr Exp $ > What is at, around, and near line 71 of /usr/include/sys/_types.h ? # cat -n /usr/include/sys/_types.h | grep -C4 "71" 67 * character set plus one extra value (WEOF), and must be at least 16 bits. 68 */ 69 typedef int __ct_rune_t; 70 typedef __ct_rune_t __rune_t; 71 typedef __ct_rune_t __wchar_t; 72 typedef __ct_rune_t __wint_t; 73 74 /* 75 * mbstate_t is an opaque object to keep conversion state during multibyte After some unsuccesfull buildworld I tryed updating includes but got the same error. May be because my -CURRENT is pre-gcc_3.1 ? Can I (Must I?) upgrade to an intermediate version between May and now? Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to buildworld (new record, 18")
On 07-Sep-2002 (21:00:28/GMT) Riccardo Torrini wrote: >> Have you read through UPDATING? > Yes, more and more ... I added -DNO_WERROR without luck > I also found two PR speaking about wchar_t (31864 and 40084). > I'm about to remove contrib/gcc tree and cvsuping again... No, same error :( Any other ideas? ===> gnu/usr.bin/gperf/doc c++ -O2 -pipe-D__FBSDID=__RCSID -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc In file included from /usr/include/stdio.h:44, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.h:57, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc:21: /usr/include/sys/_types.h:71: declaration does not declare anything *** Error code 1 Thanks again, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to buildworld (new record, 18")
On 07-Sep-2002 (20:22:42/GMT) Kris Kennaway wrote: >> My -CURRENT is pre-gcc_3.1, running very fine from early May. >> I'm in between some big update? Where I'm wrong? > Have you read through UPDATING? Yes, more and more, after every cvsup. I added -DNO_WERROR without luck, I also found two PR speaking about wchar_t (31864 and 40084). There is something related to a new internal declaration I think. One moment, ... are you speaking about this? 20020510: Due to the way CVS works, it may not properly update src/contrib/gcc to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc and then do a cvs update. I'm about to remove contrib/gcc tree and cvsuping again... Thanks, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern kern_sig.c (fwd)
On 13-Aug-2002 (15:06:48/GMT) Riccardo Torrini wrote: > ...important data are on NFS -CURRENT server... No, I means -STABLE server (obvious :) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern kern_sig.c (fwd)
On 13-Aug-2002 (13:59:39/GMT) Tim Robbins wrote: > What about chpass, vipw, and the other pw_edit() consumers? vipw > works correctly wrt suspending with ^Z on 4.6-RELEASE, but does > not on -CURRENT. vipw works _perfectly_ here, on a not-too-current -CURRENT, from tcsh I can suspend (^Z), list jobs (jobs), resume (fg) and I can continue editing, with the cursor exactly in the same place. This is a SMP machine, dual pIII/500, I use as my desktop (important data are on NFS -CURRENT server :P) from 3.0, so it can contain a lot of old (unsed) file, maybe even a.out ones... # uname -v FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002 What changed from my (really) old (pre gcc_3.1) current? Riccardo. PS: world and ports compiled with some 'insane' options (-O2): CPUTYPE=p3 CFLAGS= -O2 -pipe NOPROFILE= true COMPAT3X= yes COMPAT4X= yes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CAM-ATAPI status?
On 13-Aug-2002 (00:27:51/GMT) Nate Lawson wrote: > You'll be happy to tell them sys/dev/ata/atapi-cam.c: WOW ! > Fri Aug 9 20:51:53 2002 UTC (3 days, 3 hours ago) by sos > Add the ability to use ATAPI devices via CAM. I'm back from holidays and I'm still reading over 1200 old messages of -CURRENT (last 3 weeks). My -CURRENT is not so current :\, I have a pre gcc_3.1, is now safe to rebuild or I'd read _all_ old mail before? > See /sys/conf/NOTES for usage. I think this is a 'stupid' question, but before this message I looked only into /sys/i386/conf/NOTES for configurations, why the one in /sys/conf/ is different and why they are two? If /sys/alpha/conf/NOTES and /sys/i386/conf/NOTES are only {alpha,i386} specific, why some part are duplicated? I am confused :\ Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: custom kernel
On 24-Jun-2002 (11:36:34/GMT) Makoto Matsushita wrote: >> The only (I think) user configurable file under /usr/src tree is >> the custom kernel file, pointed by KERNCONF in /etc/make.conf. > "cd /usr/src; make {build,install}kernel" with > KERNCONF=YOUR_KERNEL_CFG > KERNCONFDIR=/path/to/dir/of/YOUR_KERNEL_CFG/file/mentioned/above > seems working (but I don't test it). Thanks to all hints (also to who link it out of /usr/src tree). This one is what I prefer but it doesn't work on -STABLE, can we back port this 3 lines of diffs also to 4.x ? # diff -u2 /usr/src/Makefile.inc1.orig /usr/src/Makefile.inc1 --- /usr/src/Makefile.inc1.origMon Apr 29 20:42:50 2002 +++ /usr/src/Makefile.inc1 Tue Jun 25 20:05:28 2002 @@ -402,9 +402,10 @@ KRNLCONFDIR= ${KRNLSRCDIR}/${TARGET}/conf KRNLOBJDIR=${OBJTREE}${KRNLSRCDIR} +KERNCONFDIR?= ${KRNLCONFDIR} BUILDKERNELS= INSTALLKERNEL= .for _kernel in ${KERNCONF} -.if exists(${KRNLCONFDIR}/${_kernel}) +.if exists(${KERNCONFDIR}/${_kernel}) BUILDKERNELS+= ${_kernel} .if empty(INSTALLKERNEL) @@ -440,5 +441,6 @@ cd ${KRNLCONFDIR}; \ PATH=${TMPPATH} \ - config ${CONFIGARGS} -d ${KRNLOBJDIR}/${_kernel} ${_kernel} + config ${CONFIGARGS} -d ${KRNLOBJDIR}/${_kernel} \ + ${KERNCONFDIR}/${_kernel} .endif .if !defined(NOCLEAN) && !defined(NO_KERNELCLEAN) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
custom kernel
The only (I think) user configurable file under /usr/src tree is the custom kernel file, pointed by KERNCONF in /etc/make.conf. To avoid unwanted removal can we locate that file under any other place and point it (also by KERNCONF or some new black magic) with full path? Is this possible (or already done) ? TIA, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Floppy only 8.3 filenames
On 23-Jun-2002 (05:36:10/GMT) Bruce Evans wrote: > msdos doesn't exist in -current (it has been renamed to msdosfs)... Aarrgghh! When it happens? I'm sure to miss something but here mount_msdos works (and in my /etc/fstab I have msdos not msdosfs). Is a manual removal required or would be done by installworld? This means that I must remove also all non May 8 mount files, mount_{fdesc kernfs mfs msdos null portal umap union} ? (yes, my world is from may 8 (pre gcc_3.1), I'm rebuilding it now) # cd /sbin && ls -l mount* -r-xr-xr-x 1 root wheel 381700 May 8 02:48 mount -r-xr-xr-x 1 root wheel 74320 May 8 02:48 mount_cd9660 -r-xr-xr-x 5 root wheel 73512 May 8 02:48 mount_devfs -r-xr-xr-x 1 root wheel 73032 May 8 02:48 mount_ext2fs -r-xr-xr-x 1 root wheel 64420 Apr 28 2001 mount_fdesc -r-xr-xr-x 5 root wheel 73512 May 8 02:48 mount_fdescfs -r-xr-xr-x 1 root wheel 378796 May 8 02:48 mount_ifs -r-xr-xr-x 1 root wheel 60608 Dec 19 2000 mount_kernfs -r-xr-xr-x 5 root wheel 73512 May 8 02:48 mount_linprocfs -r-xr-xr-x 1 root wheel 158764 Apr 28 2001 mount_mfs -r-xr-xr-x 1 root wheel 347084 Apr 28 2001 mount_msdos -r-xr-xr-x 1 root wheel 380812 May 8 02:48 mount_msdosfs -r-xr-xr-x 1 root wheel 377564 May 8 02:48 mount_nfs -r-xr-xr-x 1 root wheel 372328 May 8 02:48 mount_ntfs -r-xr-xr-x 1 root wheel 64868 Apr 28 2001 mount_null -r-xr-xr-x 1 root wheel 73404 May 8 02:48 mount_nullfs -r-xr-xr-x 1 root wheel 406108 May 8 02:48 mount_nwfs -r-xr-xr-x 1 root wheel 375968 Apr 28 2001 mount_portal -r-xr-xr-x 1 root wheel 414108 May 8 02:48 mount_portalfs -r-xr-xr-x 5 root wheel 73512 May 8 02:48 mount_procfs -r-xr-xr-x 1 root wheel8988 May 8 02:48 mount_smbfs -r-xr-xr-x 5 root wheel 73512 May 8 02:48 mount_std -r-xr-xr-x 1 root wheel 72776 May 8 02:48 mount_udf -r-xr-xr-x 1 root wheel 77752 Apr 28 2001 mount_umap -r-xr-xr-x 1 root wheel 87300 May 8 02:48 mount_umapfs -r-xr-xr-x 1 root wheel 64932 Apr 28 2001 mount_union -r-xr-xr-x 1 root wheel 73532 May 8 02:48 mount_unionfs -r-xr-xr-x 1 root wheel 390668 May 8 02:48 mountd Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sendmail
I'm unable to hide: > X-Authentication-Warning: ...goofy set sender to foobar using -f neither using this m4 macros: define(`confTRUSTED_USERS', ``goofy'') FEATURE(`use_ct_file') nor editing sendmail.cf adding T class. Tgoofy I'm using sendmail 8.12.3 on 4.6-PRERELEASE and 5.0-CURRENT but no difference. Just ignore it :\ Any hint will be appreciated. TIA, Riccardo. PS: I'm not sure where to ask, here, on -STABLE or on -QUESTIONS, if this is the wrong list sorry for wasting your time, feel free to forward to the right list. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
I need USB and DEVFS info
I have a USB scanner (Epson Perfection 1240U) and a digital camera (Agfa CL18). The first is identified as uscanner0 and work really well, the second show up as ugen{0,0.1,0.2,0.3} With -CURRENT and DEVFS both come up with read/write enable only for root, so I added this line for scanner to etc/usbd.conf: attach "/bin/chmod 666 /dev/${DEVNAME} && echo L16cce > /dev/speaker" This enable my user to use scanner. I tryed the same with digital camera but (I think) DEVFS reset protections to read only. # chmod go+w /dev/ugen0* riccardo@trudy[0]: ll /dev/ugen* crw-rw-rw- 1 root operator 114, 0 Jun 9 14:37 /dev/ugen0 crw-rw-rw- 1 root operator 114, 1 Jun 9 14:37 /dev/ugen0.1 crw-rw-rw- 1 root operator 114, 2 Jun 9 14:43 /dev/ugen0.2 crw-rw-rw- 1 root operator 114, 3 Jun 9 14:37 /dev/ugen0.3 riccardo@trudy[0]: gphoto2 --camera "Agfa CL18" --list-files *** Error *** An error occurred in the io-library ('Error writing to the port'): No error description available *** Error ('Error writing to the port') *** [...] riccardo@trudy[1]: ll /dev/ugen* crw-rw-rw- 1 root operator 114, 0 Jun 9 14:37 /dev/ugen0 crw-r--r-- 1 root operator 114, 1 Jun 9 14:37 /dev/ugen0.1 crw-r--r-- 1 root operator 114, 2 Jun 9 14:43 /dev/ugen0.2 crw-r--r-- 1 root operator 114, 3 Jun 9 14:37 /dev/ugen0.3 Trying the list/download photo command from root works. After some command gphoto2 lockup and mark itself as a 'D' process (D = process in disk (or other short term, uninterruptible) wait) and I must reboot to remove it :\ Is a status=D process really unbreakable? And why it become 'D'? And why procections reset to 644 after accessing /dev/ugen* device? Any other hint ? (no, I cannot buy a more expensive camera). TIA, Riccardo. PS: I'd like to buy an USB (cheaper) printer: Epson C40UX. Under linuxprinting.org seems well supported using a ghostscript driver, so I choose this one. The only obscure point is FreeBSD USB driver that is different from Linux one. Is this printer working? Any -CURRENT or -STABLE user with this (or other cheaper) USB printers? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
usbd.core
This block crashes usbd with: ...(usbd), uid 0: exited on signal 11 (core dumped) I have a pre-GCC_3.1: (FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002) -8<-[ /etc/usbd.conf ]-8<- device "Scanner Epson Perfection 1240U (photo)" # Perfection1240(0x010b), EPSON(0x04b8), rev 0x0114 product 0x010b vendor 0x04b8 release 0x0114 devname "uscanner[0-9]+" attach "/bin/chmod 666 /dev/${DEVNAME} && echo L16cce > /dev/speaker" ## attach "/bin/chmod 666 /dev/uscanner0 && echo L16cce > /dev/speaker" detach "echo L16eec > /dev/speaker" -8<- (gdb) bt #0 0x280e7dd6 in strncpy () from /usr/lib/libc.so.5 #1 0x80494d4 in sigprocmask () #2 0x804a6c7 in sigprocmask () #3 0x8048cc3 in sigprocmask () Adding a comment before 'device' solves the problem: -8<- # device [...] -8<- Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Add a Makefile.user on /usr/src and /usr/ports
To support fancy user and they own targets would be nice an infrastructure that check and (if it exist) include a file (named Makefile.user or .local or similar) with personal targets either under /usr/src than /usr/ports. This can save a lot of typing building various things (for example timing build phase or saving logs) only migrating this file from a machine to another. I was able to patch /usr/src/Makefile and /usr/ports/Makefile myself, any comment will be appreciated (even negative ones). TIA, Riccardo. -[ /usr/src ]- # diff -u Makefile.orig Makefile --- Makefile.orig Mon Jun 3 21:33:16 2002 +++ MakefileFri Jun 7 00:21:16 2002 @@ -108,6 +108,10 @@ PATH= /sbin:/bin:/usr/sbin:/usr/bin MAKE= PATH=${PATH} make -m ${.CURDIR}/share/mk -f Makefile.inc1 +.if exists(${.CURDIR}/Makefile.user) +.include "${.CURDIR}/Makefile.user" +.endif + # # Handle the user-driven targets, using the source relative mk files. # -[ /usr/ports ]- # diff -u Makefile.orig Makefile --- Makefile.orig Mon Dec 31 02:29:06 2001 +++ MakefileFri Jun 7 00:12:14 2002 @@ -55,6 +55,9 @@ PORTSTOP= yes .include +.if exists(${.CURDIR}/Makefile.user) +.include "${.CURDIR}/Makefile.user" +.endif index: @rm -f ${.CURDIR}/INDEX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Please test PAUSE on non-Intel processors
On 24-May-2002 (14:25:53/GMT) John Baldwin wrote: > Please compile the attached test program and run it... FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002 CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387fbff [...] FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs # ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbff7dc -> 0xbfbff7a0 FreeBSD 4.5-STABLE #9: Mon Apr 22 16:54:08 CEST 2002 CPU: IDT WinChip 2 (199.90-MHz 586-class CPU) Origin = "CentaurHauls" Id = 0x585 Stepping = 5 Features=0x8000b5 # ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffb98 -> 0xbfbffb5c FreeBSD 4.5-STABLE #4: Mon Apr 22 17:39:58 GMT 2002 CPU: IDT WinChip C6 (199.74-MHz 586-class CPU) Origin = "CentaurHauls" Id = 0x541 Stepping = 1 Features=0x8000b5 # ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffb9c -> 0xbfbffb60 FreeBSD 4.4-STABLE #3: Sun Sep 25 11:26:23 GMT 2001 CPU: i486 SX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x45b Stepping = 11 Features=0x2 # ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffba0 -> 0xbfbffb64 FreeBSD 4.5-STABLE #3: Mon Apr 22 14:54:18 GMT 2002 CPU: Cyrix 6x86MX (200.46-MHz 686-class CPU) Origin = "CyrixInstead" Id = 0x600 Stepping = 0 DIR=0x0753 Features=0x80a135 # ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffbb8 -> 0xbfbffb7c Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Any matrox users?
On 24-May-2002 (04:12:16/GMT) Seth Hettich wrote: > I'd be interested to know if any other -current users with a > G200 AGP are having problems. Only many months ago, when running moused before starting X (either from xdm/wdm or startx) forced mouse pointer in the upper right corner. But not now. It happens on X_4.1.x if I remember... # uname -v FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002 [...] # dmesg [...] agp0: mem 0xe000-0xe7ff at device 0.0 on pci0 [...] vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 I can send you complete dmesg and kernel file, if can help. Riccardo. BTW: I compiled XFree-4 _WITHOUT_ any special magic woodoo, only with 'make' (no GXX_something). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh
On 19-May-2002 (18:27:40/GMT) Riccardo Torrini wrote: > I have "set implicitcd". But it would be honoured only when a > directory is specified on a line itself, not after a pipe (IMHO). Or (even better), when a directory is followed by a "/" ? Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh
On 19-May-2002 (18:12:00/GMT) Mark Peek wrote: >>If exists a directory named "sort" tcsh chdir to that dir instead of >>executing sort present in path (and no, I have no "." anywere in path) >>And it also happen with non existent commands: >># pwd >>/usr/src/contrib >># find . -name Makefile | libreadline >># pwd >>/usr/src/contrib/libreadline > I tried to reproduce this problem but it worked fine for me. > This could be due to something in your .cshrc file. I have "set implicitcd". But it would be honoured only when a directory is specified on a line itself, not after a pipe (IMHO). Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
tcsh
If exists a directory named "sort" tcsh chdir to that dir instead of executing sort present in path (and no, I have no "." anywere in path) # pwd /usr/src/contrib # find . -name Makefile | sort # pwd /usr/src/contrib/sort # cd .. # find . -name Makefile | /usr/bin/sort ./bind/Makefile ./bind/bin/Makefile [...] And it also happen with non existent commands: # pwd /usr/src/contrib # find . -name Makefile | libreadline # pwd /usr/src/contrib/libreadline Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
df
I manually mount nfs fs after a reboot (current -> stable) and if I do a "df" I got two different output. First time it get garbled, all other times it is aligned. I'm alone? # FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002 [...] # df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/ad0s4a127023 69449 4741359%/ devfs 1 1 0 100%/dev /dev/ad0s4e1270238373 108489 7%/var /dev/ad0s4f 3259600 2685561 31327190%/usr procfs 4 4 0 100%/proc silos:/home 19692918 16405246 171223991%/silos/home silos:/usr8130540 5879432 160066579%/silos/usr # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s4a12702369449 4741359%/ devfs 11 0 100%/dev /dev/ad0s4e127023 8373 108489 7%/var /dev/ad0s4f 3259600 2685561 31327190%/usr procfs 44 0 100%/proc silos:/home 19692918 16405246 171223991%/silos/home silos:/usr8130540 5879432 160066579%/silos/usr Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/usr/ports/emulators/bochs on -CURRENT
# grep BOCHS /etc/make.conf WITH_BOCHS_CPU_LEVEL= 6 WITH_BOCHS_PROCESSORS= 1 # uname -v FreeBSD 5.0-CURRENT #34: Wed May 8 02:31:46 CEST 2002 [...] # cd /usr/ports/emulators/bochs && make [...] gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' [...] c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include -I.. -I./.. -I../instrument/stubs -I./../instrument/stubs cdrom.cc -o cdrom.o In file included from cdrom.cc:40: /usr/include/arpa/inet.h:102: conflicting types for `typedef __uint32_t socklen_t' ../osdep.h:105: previous declaration as `typedef int socklen_t' gmake[1]: *** [cdrom.o] Error 1 gmake[1]: Leaving directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' gmake: *** [iodev/libiodev.a] Error 2 *** Error code 2 I tryed with cdrom support disabled in Makefile and it go forward: # diff -u0 Makefile.orig Makefile --- Makefile.orig Thu May 16 09:48:29 2002 +++ MakefileThu May 16 10:32:58 2002 @@ -34 +34 @@ -CONFIGURE_ARGS=--enable-cdrom \ +CONFIGURE_ARGS=--disable-cdrom \ # make clean && make [...] c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include-I. -I./. -Iinstrument/stubs -I./instrument/stubs logio.cc -o logio.o c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include-I. -I./. -Iinstrument/stubs -I./instrument/stubs main.cc -o main.o main.cc: In function `int bx_init_hardware()': main.cc:1177: `i' undeclared (first use this function) main.cc:1177: (Each undeclared identifier is reported only once main.cc:1177: for each function it appears in.) gmake: *** [main.o] Error 1 *** Error code 2 I (badly?) hacked main.cc to remove line 1177 and it compile fine. # diff -u0 main.cc.orig main.cc --- main.cc.origWed Mar 27 17:05:14 2002 +++ main.cc Thu May 16 11:02:38 2002 @@ -1177 +1177 @@ - BX_CPU(0)->local_apic.set_id (i); + // BX_CPU(0)->local_apic.set_id (i); I'm not able to check if it run until 19:00 CEST because I compile it from a remote ssh. And I think that commenting previous line is really bad :-) Can you (help me to) check what is wrong (my config, my -CURRENT, port, ...)? TIA, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make includes
On 14-May-2002 (06:21:18/GMT) Ruslan Ermilov wrote: > I'm still unsure about the name; I'd have liked to rename it to > "includesinstall" but that is too long. U, buildworld, installworld, buildkernel, installkernel... It would be: buildinclude{s}, installinclude{s} just to be simmetric :) And is only one (or two) character longer than installkernel... my .02 EUR Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Who broke 'make clean' for ports ?
On 10-May-2002 (17:44:21/GMT) Garrett Rooney wrote: >> Ok, thanks. Sorry for alarm but I don't see any message before >> my own. Can I back-cvsup to a stable date? When (sh)it happens? > the change is just a few hours old. you can just remove expat2 > from the LIB_DEPENDS in textproc/gettext/Makefile and you should > be fine for now. Yes, it works. Thanks again. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Who broke 'make clean' for ports ?
On 10-May-2002 (17:31:32/GMT) Garrett Rooney wrote: > there's a circular dependency that was just introduced to gettext. > gettext now depends on expat, which depends on gmake, which depends > on gettext. > it's a known problem, and is being worked on. Ok, thanks. Sorry for alarm but I don't see any message before my own. Can I back-cvsup to a stable date? When (sh)it happens? Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Who broke 'make clean' for ports ?
On 10-May-2002 (17:26:56/GMT) Dan Nelson wrote: >> After a cvsup of 10 minutes ago either on 5.0-CURRENT and on >> 4.6-PRERELEASE (both of May 8, 02:46 CEST) making a >> # make clean >> into /usr/ports/deve/gettext spawn zillions(!) of make process, >> lead to cpu load average at 96.xx before a reboot :-( > Syntax errors (or defining things that bsd.port.mk wants to control > itself) in /etc/make.conf can cause this. What things? I don't'think. Why into /usr/ports/astro/luna works? Without changing my /etc/make.conf obviously... Anyway this are my 4.6 and 5.0 make.conf(s) -8<-[ 4.6-PRERELEASE ]-8< KERNCONF= SILOS CFLAGS= -O2 -pipe NOPROFILE= true USA_RESIDENT= NO SUP_UPDATE= yes SUP=/usr/local/bin/cvsup SUPFLAGS= -g -L 2 -z SUPFILE=/usr/local/etc/cvsup.stable PORTSSUPFILE= /usr/local/etc/cvsup.ports SENDMAIL_MC=/etc/mail/silos.mc # Resume ##FETCH_BEFORE_ARGS=-rR -o $${file}.resume ##FETCH_AFTER_ARGS=&& mv $${file}.resume $${file} # Ports WITHOUT_CUPS= yes # qpopper WITHOUT_IPV6= yes -8<-[ 5.0-CURRENT ]-8<- KERNCONF= TRUDY CPUTYPE=p3 CFLAGS= -O2 -pipe NOPROFILE= true COMPAT3X= yes COMPAT4X= yes XFREE86_VERSION=4 USA_RESIDENT= NO SUP_UPDATE= yes SUP=/usr/local/bin/cvsup SUPFLAGS= -g -L 2 -z SUPFILE=/usr/local/etc/cvsup.current PORTSSUPFILE= /usr/local/etc/cvsup.ports SENDMAIL_MC=/etc/mail/trudy.mc # Resume ##FETCH_BEFORE_ARGS=-rR -o $${file}.resume ##FETCH_AFTER_ARGS=&& mv $${file}.resume $${file} # Ports A4= yes # ghostscript-gnu WITH_GPHOTO2= yes # sane-backends WITH_GIMP= yes # sane-frontends # mplayer WITH_GUI= yes WITH_DVD= yes WITH_VORBIS=yes # bocsh WITH_BOCHS_CPU_LEVEL= 6 WITH_BOCHS_PROCESSORS= 1 # libmpeg2 WITH_SDL= yes Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Who broke 'make clean' for ports ?
On 10-May-2002 (17:01:26/GMT) Riccardo Torrini wrote: > into /usr/ports/deve/gettext s/deve/devel/ I use make clean to show dependencies before install/update. No, I don't use neither pkg_update nor portupgrade. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Who broke 'make clean' for ports ?
After a cvsup of 10 minutes ago either on 5.0-CURRENT and on 4.6-PRERELEASE (both of May 8, 02:46 CEST) making a # make clean into /usr/ports/deve/gettext spawn zillions(!) of make process, lead to cpu load average at 96.xx before a reboot :-( Up to yesterday it works. Doing this into others ports works... Riccardo. PS: I think this must sent to -stable and -ports too... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl scripts that need rewiting - Any volunteers?
On 09-May-2002 (15:38:45/GMT) Mark Murray wrote: >> I tryed this one. I'm not a committer, just a volunteer :-) > You're on! Please put appropriate (c) on this (Preferably > 2-clause BSD license) and I'll commit it for you :-) Ahemm, I'm not sure to have done correct job. Please review last version of this script from my site: ftp://castle.torrini.org/pub/FreeBSD/spkrtest-current and modify if I miss or don't understand something ;) Thanks. Riccardo. PS: I think that man page (/usr/src/usr.sbin/spkrtest/spkrtest.8) should be changed to remove perl(1): # diff -u2 spkrtest.8.orig spkrtest.8 --- spkrtest.8.orig Fri Jul 13 17:36:02 2001 +++ spkrtest.8 Thu May 9 20:43:40 2002 @@ -40,5 +40,4 @@ .Sh SEE ALSO .Xr dialog 1 , -.Xr perl 1 , .Xr spkr 4 .Sh HISTORY or to include sh(1): # diff -u2 spkrtest.8.orig spkrtest.8 --- spkrtest.8.orig Fri Jul 13 17:36:02 2001 +++ spkrtest.8 Thu May 9 20:58:46 2002 @@ -40,5 +40,5 @@ .Sh SEE ALSO .Xr dialog 1 , -.Xr perl 1 , +.Xr sh 1 , .Xr spkr 4 .Sh HISTORY To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Status of USB subsystem.
On 03-May-2002 (13:22:48/GMT) Josef Karthauser wrote: > If anyone has any others that they've not revealed I'd like to know > please. I don't really know if is related, but gphoto2 doesn't work with my camera because of different linux<->freebsd usb channel usage (i think). > Also, if anyone particularly fancies helping out I'd be very grateful. > [...] I'm prepared to back everything out if required ... If this can lead me to have a working usb driver for my digital camera (a cheaper agfa cl18) with gphoto2 (or something _much_ light, like a command line tool or a kernel driver to mount as a filesystem) I can help you with all my free time for testing any (non destructive) change. > I ask for your patience... You are welcome :-) Riccardo. PS: Please don't break uscanner, I use it with an Epson Perfection 1200U. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bochs panic on current
I asked for same problem some time ago to this list and to ports without answer, anyone out there running bochs on current? I have installed bochs from ports but I was unable to start any sample image from support site, all fails with same error: Event type: PANIC Device: [APIC0] Message: [APIC0] failed assertion "irr[vector] == 1" at apic.cc:573 # uname -v FreeBSD 5.0-CURRENT #32: Tue Apr 23 08:21:16 CEST 2002 [...] Maybe something related to my dual proc mobo (asus P2B-DS) ? Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: truss
On 28-Apr-2002 (17:56:47/GMT) Harti Brandt wrote: > RA>On a fresh current i get this > RA># truss /bin/echo hello > RA>truss: cannot open /proc/13245/mem: No such file or directory > RA>truss: cannot open /proc/curproc/mem: No such file or directory > You need to mount procfs. Mee too message. I tryed same command, 1st time I got same error. I checked with df if /proc was mounted and than trussed again and it show me calls not failing any more. Some timeout of procfs ? # uname -v FreeBSD 5.0-CURRENT #32: Tue Apr 23 08:21:16 CEST 2002 [...] Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unable to start bochs
I'm trying to run bochs without success. I'd like to know if is a -CURRENT or -PORTS issue. I have an Asus P2B-DS with dual pIII/500. Is crash related? # bochs [...] Event type: PANIC Device: [APIC0] Message: [APIC0] failed assertion "irr[vector] == 1" at apic.cc:573 Riccardo. dmesg.gz Description: dmesg.gz
Please HELP with Zyxel Prestige P641 (router adsl)
Please, I need some help, my adsl access router (Zyxel Prestige P641) blow up last night (really exploded). A sourface mounted capacitor CP53 exploded destroying mother board. I need a zoomed scan of that area or even better of schematics of power section of the router, to try to adjust myself. You can see a zoomed image of explosion here: http://www.torrini.org/riccardo/images/p641-explosion.jpg Yes, this is a bit of off topic, please excuse me, but with router I can continue cvsup/debug/report of -CURRENT ;^) Thanks in advance, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.2.0 with G200 fail to start with signal 10
On 20-Mar-2002 (20:29:26/GMT) Will Andrews wrote: >> With last update of world and ports I'm unable to start XFree86. >> I have a matrox G200 (agp) and I have tryed with and without the >> WITH_MATROX_GXX_DRIVER=yes but I got only a signal 10, core dump > What is your pkg_info -Ia? I removed _all_ ports and reinstalled them on 17, 18 and 19 march. > I committed an updated version of the Matrox driver for > XFree86-4-Server, maybe you don't have that? cvsup-ed at 22:45 of 20.03.2002 (GMT+1, italy time). and updated -libraries, -clients and -servers. # ls /var/db/pkg/ | grep XFree86 XFree86-4.2.0_1,1 XFree86-FontServer-4.2.0 XFree86-Server-4.2.0 XFree86-clients-4.2.0_2 XFree86-documents-4.2.0 XFree86-font100dpi-4.2.0 XFree86-font75dpi-4.2.0 XFree86-fontCyrillic-4.2.0 XFree86-fontDefaultBitmaps-4.2.0 XFree86-fontEncodings-4.2.0 XFree86-fontScalable-4.2.0 XFree86-libraries-4.2.0_1 After a lot of test, finally I _found_ it ! I was able to start xdm (not wdm for now) _ONLY_ after killing moused and using /dev/psm0 directly from /etc/X11/XF86Config. This is the message that help me (changing /dev/sysmouse to 666 doesn't help): (EE) Mouse0: Write to mouse failed For wdm maybe something related to PAM, I'm looking deep into archived mail. I can live in the meantime even with xdm :-) X-Server compiled _without_ WITH_MATROX_GXX_DRIVER magic flag. As a little side effect I lost all eight consoles, switching works but with black screen (even num-lock change state and any command seems to 'at least' light on the hd led). If you need any log from /var/log/ feel free to ask me. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86 4.2.0 with G200 fail to start with signal 10
With last update of world and ports I'm unable to start XFree86. I have a matrox G200 (agp) and I have tryed with and without the WITH_MATROX_GXX_DRIVER=yes but I got only a signal 10, core dump when starting X. At the same time I switched my MoBo from tyan trinity with k6 to a asus p2b-ds dual processor p3/500. I have a recent system (fresh compile with SMP enabled): # uname -v FreeBSD 5.0-CURRENT #24: Sun Mar 17 00:32:04 CET 2002 and I double check all update cycle (make update, buildworld, buildkernel, installkernel, installworld, mergemaster, reboot) I removed also _all_ ports and reinstalled them. Also tryed to recreate a config for XFree from screatch but it crash always with signal 10 (and sometimes with signal 6). At this time I am not sure where is (can be?) the problem, mobo, graphic card, -current or xfree. Any hint? TIA, Riccardo. PS: My previous message with ACPI info get lost, neither bounced nor accepted. And I am using correct local masquerading and my ISP that has record for reverse resolution also. Spam from .kr instead is accepted to list. Exists any other method for _serious_ user/tester to send to list? Thanks again. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
automatic reboot without panic writing to local fat32 fs
Copying remote files (large backup, 200/300Megs) from my home file server (4.5-STABLE) using nfs or ftp or scp to a local msdos fat32 partition reboot machine without any error :-( Yes, local machine that has msdos mounted fs is -CURRENT: # uname -v FreeBSD 5.0-CURRENT #22: Tue Mar 5 20:50:06 CET 2002... I completely destroy two partitions, trashed filesystem and lost all contents (ok, it was backuped ;) copying files over them. I need a format from floppy to resume. I was even unable to remove some strange named files (files with non ascii-7 chars I suppose). Initially I think to a nfs related problem, but it happens even using ftp and scp, not only cp. I splitted large files into smaller ones, 8Megs each, and tryed to copy into a foreach loop, pausing 10/15secs between copies. But it reboot all the times, and _all_ means a very high number (I lost the count, but over 20). All the (unwanted) test was with and without X, fsck-ing in single user by hand (just to be informed of what get lost). Activity led stay solid-rock-on all the copy time, after 70/80 Megs mouse locks up for a while and then machine reboot without any other message. Again, copying to a local ufs fs and than from local ufs to local fat32 works fine (I just finished to restore them). NB: I used this config on the last 3 years, upgrading both server (now 4.5) and my machine at least once at a month. Copying from local ufs or fat32 to remote nfs file server work fine (for now :-). If some dmesg, /var/log/messages or kernel config can help I can post to list or provide a link to my home ftp/http to save bandwidth and don't flood the list. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: devfs(5) Permissions
On 03-Mar-2002 (17:02:35/GMT) Crist J. Clark wrote: > I think some people missed the point of the earlier question. I'm really sorry :( Next time I'll double read the messages. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: devfs(5) Permissions
On 03-Mar-2002 (16:31:36/GMT) Crist J. Clark wrote: > How does one change the permissions on dynamically created > devices? That is, when the node comes into existence, it has > the permissions I want, and not necessarily the defaults. You can (must?) use /etc/rc.devfs [...] # Setup DEVFS, ie permissions, links etc. [...] Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-CURRENT makebuild world fails
On 03-Mar-2002 (08:20:46/GMT) Thierry Herbelot wrote: >> cc: Internal compiler error: program cc1 got fatal signal 11 > a signal 11 is generally linked to bad memory chips ...and/or overclocked CPU :) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usb product identified as ugen
On 28-Feb-2002 (19:33:04/GMT) Riccardo Torrini wrote: > port 2 addr 2: full speed, power 400 mA, config 1, \ > product 0x07d1(0x07d1), ScanLogic(0x04ce), rev 1.05 >ugen0 [...] > port 2 addr 2: full speed, self powered, config 1, \ > USB to IDE(0x0002), USB to IDE(0x04ce), rev 2.60 >umass0 Do you know why 'power 400 mA' changed to 'self powered' ? Is this important? External HD case has only USB cable... And why product changed from 0x07d1 to 0x0002? If I understand correctly those numbers are product ID and manufacturer, and the object attacched is the same from wed. Any other idea? In the meantime I make a new world :) ...FreeBSD 5.0-CURRENT #19: Fri Mar 1 03:57:49 CET 2002 Riccardo. PS: Next week I must return this device to my friend :( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
core, crash, panic auto-reboot
cvsup on 2002.02.28.20.00 (GMT+1) with build and install. Last day spent with Scott to try to install external usb to ide hd, a lot of debug enabled (usb, umass, ugen). Here my collection of error messages. Going to cvsup again. Machine rebooted automagically _without_ any other message, so I lost my previous message. The only difference from previous boot was a "boot -v", machine started 10 minutes before crash. Also unable to use gdb, it crashes badly :( # ssh silos fatal process exception: page fault, fault VA = 0x235 Segmentation fault (core dumped) # ls -l *core ls: sshMcore: No such file or directory -rw--- 1 riccardo staff 958464 Mar 1 01:15 tcsh.core # ssh silos ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/rtld.c:570 Abort (core dumped) # ssh silos ÿQÿÿëq‰öƒÄøQ‹ ዃ4:fatal process exception: page fault, fault VA = 0x16714 Segmentation fault (core dumped) # top ELF interpreter /usr/ not found Abort Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usb product identified as ugen
On 28-Feb-2002 (06:57:50/GMT) Riccardo Torrini wrote: > The only difference in /dev was -ugen{0,0.1,0.2} +xpt0 :( > ># camcontrol rescan 0 > Re-scan of bus 0 was successful > ># camcontrol devlist -v > scbus0 on umass-sim0 bus 0: > scbus-1 on xpt0 bus 0: > < >at scbus-1 target -1 lun -1 (xpt0) I notice also that usbdevs changed output from: # usbdevs -v -d Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), \ VIA(0x), rev 1.00 uhub0 port 1 powered port 2 addr 2: full speed, power 400 mA, config 1, \ product 0x07d1(0x07d1), ScanLogic(0x04ce), rev 1.05 ugen0 to: # usbdevs -d -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), \ VIA(0x), rev 1.00 uhub0 port 1 powered port 2 addr 2: full speed, self powered, config 1, \ USB to IDE(0x0002), USB to IDE(0x04ce), rev 2.60 umass0 Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usb product identified as ugen
On 28-Feb-2002 (05:05:40/GMT) Scott Long wrote: >> Anyway, ugen0 disappear from /dev/ but _no_ umass0 appear, >> only xpt0... > The debug trace looks very good. I think this is the only good news... > No umass0 device should appear in /dev. Instead, you should > get a da device. Do 'camcontrol devlist -v' and you should > see the bus (represented as umass-sim) and a 'da' and 'pass' > device for the drive. The only difference in /dev was -ugen{0,0.1,0.2} +xpt0 :( # camcontrol rescan 0 Re-scan of bus 0 was successful # camcontrol devlist -v scbus0 on umass-sim0 bus 0: scbus-1 on xpt0 bus 0: < >at scbus-1 target -1 lun -1 (xpt0) > It also sounds like you have other issues with the device > not always attaching or detaching correctly. You mean broken usb, broken device or bad luck? > This is a weakness of the umass driver, so you'll have to > experiment a bit to see what works for you. I'm here. I can _any_ sort of experiment you may need (except opening case of external hd :-) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usb product identified as ugen
On 27-Feb-2002 (23:17:15/GMT) Scott Long wrote: > Is the umass device compiled into the kernel, or loaded as a > module? If it's a module, is it loaded before you attach the > drive? The usb daemon isn't smart enough yet to load it... Now I have all compiled in. Something happens... -8<-[ from my kernel ]-8<- options DEBUG #Guess :) # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device pass# Passthrough device (direct SCSI access) # USB support device uhci# UHCI PCI->USB interface device usb # USB Bus (required) device ugen# Generic device umass # Disks/Mass storage - Requires scbus+da device uscanner# Scanners # Hints from Scott Long options USB_DEBUG options UGEN_DEBUG options UMASS_DEBUG -8<-[ dmesg ]-8<- uhci0: port 0xe400-0xe41f irq 10 \ at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: ScanLogic product 0x07d1, rev 1.00/1.05, addr 2 All test with and without verbose boot, single or normal has no differences but when I detached usb cable _after_ boot it show up as umass0 (at least into the /var/log/messages). Also doing a manual camcontrol rescan 0 have same results. I attach (part of) messages (compressed), sorry for that. Anyway, ugen0 disappear from /dev/ but _no_ umass0 appear, only xpt0... Riccardo. messages.gz Description: messages.gz
Re: usb product identified as ugen
On 27-Feb-2002 (23:17:15/GMT) Scott Long wrote: I forgot this piece of messages, it happens only once, when I manually detached usb cable but never again when I rescan it. -8<-[ messages ]-8<- ...kernel: ugen0: at uhub0 port 2 (addr 2) disconnected ...kernel: ugen0: detached ...kernel: usbd_new_device: addr=2, getting first desc failed ...kernel: uhub0: device problem, disabling port 2 ...kernel: umass0: USB to IDE USB to IDE, rev 1.10/2.60, \ addr 2, 8070i (ATAPI) over Bulk-Only ...kernel: umass0: Max Lun is 0 ...kernel: umass-sim:0:-1:-1:XPT_PATH_INQ:. ...kernel: umass0:0:0:-1: Attached to scbus0 as device 0 ...kernel: scbus0: scanning for umass0:0:0:-1 ...kernel: umass-sim:0:-1:-1:XPT_PATH_INQ:. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usb product identified as ugen
On 27-Feb-2002 (18:35:18/GMT) Scott long wrote: > You don't mention how your kernel is presently configured > or what other troubleshooting you've done, so all you can > hope to receive are wild guesses like: Usually I don't make stupid questions (I think), sorry for wasting your time, but after 4 auto-reboot on last 24 hours I'm not sure of nothing, even of my name :) > - Configure a kernel with the umass, scbus, and da devices, > along with the standard usb devices. This is documented > in both the GENERIC config file and NOTES... Sorry, last time I checked comment I got (for device umass): USB Iomega Zip 100 Drive (Requires scbus and da) so I think that was only for Zip, not for all. > (as I assume that you are running -current) Yes, of course (from 3.0). I missing only da devices :( Going to rebuild world and kernel... [...after 4 hours...] puff, puff, pant, pant... reboot... :( The same, ugen0, ugen0.1 and ugen0.2 but build seems fine, it compile all world and kernel without need of NO_WERROR. > - There may be a bug. A bug would be better than a need for a custom driver for win. Have you any idea of what can I check now? Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
usb product identified as ugen
A friend of mime give me (only for some days) an external usb hard disk device (a normal ide 2.5" with an interface from ide to usb, self powered). When I attach I got this info, I need it show as umass to mount the msdos (fat32) file system on it, right? Need I some special kernel configuration? Like adding the scsi subsystem or that misterious device is not supported? Or other stuff that don't get loaded automagically? (I manually wrapped long lines) # usbdevs -v -d Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), \ VIA(0x), rev 1.00 uhub0 port 1 powered port 2 addr 2: full speed, power 400 mA, config 1, \ product 0x07d1(0x07d1), ScanLogic(0x04ce), rev 1.05 ugen0 TIA, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Today's panic on boot problem
On 26-Feb-2002 (17:27:19/GMT) Mike Silbersack wrote: > I'm experiencing the same double panic on boot that PHK is > now; are we the only ones, or is it just that nobody else > has updated recently? Mee too, just survied to 4 auto-reboot without messages... Trying with a boot -v I see a keyboard check as last message, I forgot to write down it. Sorry. I can reboot again with that explosive kernel (if _really_ necessary). Now reverted to kernel and modules of 24 Feb (but only kernel and modules, _not_ world) and it is stable (but no speaker). cvsup-ed 3 times on 26.2.2002 (compile take 3/4 hours here). BTW: On built of 25 (to recover /dev/speaker) I noticed some stranges: doing man, ps, even ls make a core dump (sometimes). I'm sure that all is in sync: kern, modules, world and etc. Tryed with and without X, with and without ACPI, normal boot or single user. No differences. As mentioned on my previous mail having both PCA and SPEAKER compiled into kernel kill /dev/speaker. With only speaker or none of them (but loading atspeaker after boot) lead me to a working /dev/speaker. All other stuff doesn't no matter. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
I have found /dev/speaker :-)
On 15-Feb-2002 (22:17:10/GMT) Dan Nelson wrote: > If you find out what killed /dev/speaker, let us know, too :) On 23-Feb-2002 (22:03:56/GMT) Dag-Erling Smorgrav wrote: >>> # kldload atspeaker >> This doesn't work. I'm missing something obvious? > Not that I can see... works for me Now /dev/speaker is in place again. I found his killer... I removed _all_ hints from /boot/device.hints and _all_ device from my custom kernel, than added again one line at a time... After 42 {build,install}kernel I found it again in /dev/ Compiling kernel with both this lines kill /dev/speaker and leave only /dev/pcaudio and /dev/pcaudioctl. Using only one at a time works fine. Also kldload atspeaker, if none of them are present into kernel, works (thank DES for hint). # pca: PCM audio through your PC speaker ## :-( device pca #Play IBM BASIC-style noises out your speaker device speaker After good news the bad ones: detaching uscanner0 doesn't execute my code, only play tune on attach, as on mid December :( Ricardo. -8<-[ /etc/usbd.conf ]-8<- [...] devname "uscanner[0-9]+" attach "/bin/chmod 666 /dev/${DEVNAME} && echo L16cce > /dev/speaker" detach "echo L16eec > /dev/speaker" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT in pretty good shape, after all
On 23-Feb-2002 (21:12:12/GMT) Dag-Erling Smorgrav wrote: > Riccardo Torrini <[EMAIL PROTECTED]> writes: >> Anyway, any plan to fix build breakage? > Sure: [...] This works. Thanks. >> I really need build to (try to?) locate missing /dev/speaker :( ># kldload atspeaker This doesn't work. I'm missing something obvious? # kldstat Id Refs AddressSize Name 13 0xc010 2c7b4c kernel 21 0xc1981000 3000 daemon_saver.ko # kldload atspeaker # kldstat Id Refs AddressSize Name 14 0xc010 2c7b4c kernel 21 0xc1981000 3000 daemon_saver.ko 31 0xc27c6000 3000 atspeaker.ko # echo cde >/dev/speaker /dev/speaker: Operation not supported. # ls -ld /dev/*speaker* ls: No match. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT in pretty good shape, after all
On 23-Feb-2002 (19:23:17/GMT) Julian Elischer wrote: > I forgot the :-) [...] >> On Sat, Feb 23, 2002 at 10:35:44AM -0800, Julian Elischer wrote: >> > that could change real soon! >> >> I certainly *hope* not. If you plan to break it, you plan to break it, >> but I hope you don't plan to render it unstable. There is a difference I'm -CURRENT from 3.0 and I can confirm that (if handled with care) is really usable. I have contributed only with bug report and not with lines of code or patches, but I think that bug report can help also. Anyway, any plan to fix build breakage? ---8<--- In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40, from /usr/src/lib/libkvm/kvm_file.c:54: /usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int' /usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int' /usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `(' ---8<--- I really need build to (try to?) locate missing /dev/speaker :( Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Don't remove sc.0 from hints...
On 15-Feb-2002 (22:17:10/GMT) Dan Nelson wrote: > Same thing wrt floppy devices, I think. If you don't have hints > lines, they don't get probed. hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" May be. Or not. Even with _all_ this lines commented I get the floppy controller detected (but no floppy drive). Anyway... please please please, I want /dev/speaker back :-( Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Don't remove sc.0 from hints...
...or strange things happens. When trying to discover why /dev/speaker disappears from my last build (cvsupped on Feb 14, 20:21 CET) I commented sc.0 lines on /boot/device.hints. Big mistake :-) I think some sort of auto-pilot must stop this. Initial boot without sc.0 hint hide all highlight messages, going from Booting [/boot/kernel/kernel]... directly to login: prompt. And playing with vi and scroll back and forward (on console) lead me to an automatic reboot without and message (neither crash nor panic). I just uncommented sc.0 lines and all go right way, pfiuu :-) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: USB detach crashes possibly fixed
On 14-Feb-2002 (08:29:50/GMT) Brian Fundakowski Feldman wrote: > Please try this change (already committed to -CURRENT) and let me > know if crashes due to detaching USB devices specifically have been > eliminated. I cvsupped on Feb 14, 20:21 CET (GMT+1, Italian time), recompiled both world & kernel (yes, runned mergemaster also :-) and messages show that device attach and detach (before I got only attach) ...kernel: uscanner0: EPSON Perfection1240, rev 1.00/1.14, addr 2 ...kernel: uscanner0: at uhub0 port 1 (addr 2) disconnected ...kernel: uscanner0: detached _BUT_ I lost /dev/speaker. I don't know if this is related to patch but with my previous installed build (a bit old, of December 11, 2001) I have those lines on /etc/usbd.conf: attach "/bin/chmod 666 /dev/${DEVNAME} && echo L16cce > /dev/speaker" detach "echo L16eec > /dev/speaker" and I got a small tune on attach but nothing on detach. Now I am unable to play notes on /dev/speaker. Any hint? TIA, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usdb missing detaches ???
On 10-Feb-2002 (20:42:26/GMT) Vladimir B. " Grebenschikov wrote: I can get -current to mount the stick in the camera but it won't umount the filesystem on detach. > ums0: detached > uhub1: detached I have the same problem here: I added this to /etc/usbd.conf: ---8<--- device "Scanner Epson, modello Perfection1240 (photo)" # Perfection1240(0x010b), EPSON(0x04b8), rev 0x0114 product 0x010b vendor 0x04b8 release 0x0114 devname "uscanner[0-9]+" attach "/bin/chmod 666 /dev/${DEVNAME} && echo L16cce > /dev/speaker" ## attach "/bin/chmod 666 /dev/uscanner0 && echo L16cce > /dev/speaker" detach "echo L16eec > /dev/speaker" ---8<--- And this happens to /var/log/messages, but I got tune played only on device attach, not on detach (attach/detach means cycle power to scanner, without touching usb cable). -8<-[ /var/log/messages ]-8<- ...kernel: uscanner0: EPSON Perfection1240, rev 1.00/1.14, addr 2 ...kernel: uscanner0: at uhub0 port 1 (addr 2) disconnected and after usage, when power off: ...kernel: uscanner0: detached If I understand manuals and examples attach/detach can run _any_ action I want. Or not? Riccardo. PS: chmod is needed to use xscanimage from my user. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ftpd STOR and STOU work the same ?
On 05-Jan-2002 (19:47:53/GMT) Mike Heffner wrote: >> I noticed a strange behaviour, sending a file twice create >> version even if sunique is off, on all versions I can test. > This is intentional... This is black magic. I hate it. I hope this would be (soon) documented _OR_ make configurable. ...or at least tell me where I can un-patch myself ;) > If you are running an anonymous file drop, you don't want > guest users to be able to overwrite the files of others... I'm over 18 (really 36 :-). I would like to decide myself. I lost two weeks trying to figure why it doesn't work. > If you need to upload, and overwrite a file, you might try > setting up a restricted user for this purpose, that only > has write access to a single directory. Why? Assume I have a very restricted /incoming dir (111) and one or two levels or restricted dir under that (.../foo/bar/) also with mode=111, and assume that a file named write-me is placed in that dir owned by anonimous, mode +w. Nothing can imagine files and dir if is unable to list them, so only authorized users or automatic robots can read/write under that deep path. Are you following me? Assume also that I am in my home, with my local lan isolated from internet or at work (same as above because ftp is _only_ an internal service). Assume also that I need 2^n (a very large number) different users to write on my ftp a sort of report, all the times with the same name. I can't delete/put because dir is not writable. Do you think this is a 'too-crazy' request? > Mike Thanks for your time, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ftpd STOR and STOU work the same ?
On 29-Dec-2001 (16:49:06/GMT) Riccardo Torrini wrote: > I noticed a strange behaviour, sending a file twice create > version even if sunique is off, on all versions I can test. > This includes: > - FreeBSD 5.0-CURRENT #0: Sun Dec 9 08:37:55 CET 2001 > - FreeBSD 4.4-STABLE #6: Fri Oct 12 21:44:36 CEST 2001 > - FreeBSD 4.5-PRERELEASE #0: Fri Dec 28 18:47:34 CET 2001 > all updated with cvsup and a fresh installed 4.2 from cdrom: > - FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 Also tested on other versions on the same range (4.2 - 5.0) and noticed that happens only with anonimous (ftp) user but _not_ with regular users. Hope this can help... Tryed with /etc/inetd.conf standard config where ftpd runs with -l and with my own custom -llSA, the same. Tryed from local (ftp localhost) and from remote machine, even with another OS (hpux and openbsd). The same. I'm really sad. I'm (pretty) sure isn't a 'pilot-error'. Please comfirm this... Thanks again. Riccardo. PS: For those which missed original message here is an archived copy (sorry, long line): http://www.GUFI.org/ricerca.php3?mode=show&id=ml:freebsd-current:192316 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ftpd STOR and STOU work the same ?
I noticed a strange behaviour, sending a file twice create version even if sunique is off, on all versions I can test. This includes: - FreeBSD 5.0-CURRENT #0: Sun Dec 9 08:37:55 CET 2001 - FreeBSD 4.4-STABLE #6: Fri Oct 12 21:44:36 CEST 2001 - FreeBSD 4.5-PRERELEASE #0: Fri Dec 28 18:47:34 CET 2001 all updated with cvsup and a fresh installed 4.2 from cdrom: - FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 This is my test bed (incoming is writeable, mod=777), following a log with my -CURRENT box (but other versions works the same): # cd /etc && ftp localhost [...anonymous login...] 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp> pwd 257 "/" is current directory. ftp> dir 150 Opening ASCII mode data connection for '/bin/ls'. total 1 drwxrwxrwx 2 0 0 512 Dec 29 15:58 incoming 226 Transfer complete. ftp> cd incoming 250 CWD command successful. ftp> dir 150 Opening ASCII mode data connection for '/bin/ls'. 226 Transfer complete. Ok, starting with clean dir. Toggling sunique twice to make sure it is off and sendind a small file: ftp> sunique Store unique on. ftp> sunique Store unique off. ftp> put motd local: motd remote: motd 150 Opening BINARY mode data connection for 'motd'. 100% |***|61 00:00 ETA 226 Transfer complete. 61 bytes sent in 0.00 seconds (19.98 KB/s) ftp> put motd local: motd remote: motd 150 Opening BINARY mode data connection for 'motd.1'. 100% |***|61 00:00 ETA 226 Transfer complete. 61 bytes sent in 0.00 seconds (13.87 KB/s) ftp> dir 150 Opening ASCII mode data connection for '/bin/ls'. total 2 -rw-r--r-- 1 69 0 61 Dec 29 16:02 motd -rw-r--r-- 1 69 0 61 Dec 29 16:02 motd.1 226 Transfer complete. Also tryed with debug enabled (debug command from client) and noticed that server use a different command when in unique mode _but_ either STOR than STOU create a unique file name :-( [...deleting all previous test file, starting with clean dir...] ftp> debug Debugging on (debug=1). ftp> put motd local: motd remote: motd ---> TYPE I 200 Type set to I. ---> EPSV 229 Entering Extended Passive Mode (|||49176|) ---> STOR motd 150 Opening BINARY mode data connection for 'motd'. 100% |***|61 00:00 ETA 226 Transfer complete. 61 bytes sent in 0.00 seconds (18.77 KB/s) ftp> put motd local: motd remote: motd ---> EPSV 229 Entering Extended Passive Mode (|||49177|) ---> STOR motd 150 Opening BINARY mode data connection for 'motd.1'. 100% |***|61 00:00 ETA 226 Transfer complete. 61 bytes sent in 0.00 seconds (18.81 KB/s) ftp> sunique Store unique on. ftp> put motd local: motd remote: motd ---> EPSV 229 Entering Extended Passive Mode (|||49178|) ---> STOU motd 150 Opening BINARY mode data connection for 'motd.2'. 100% |***|61 00:00 ETA 226 Transfer complete (unique file name:motd.2). 61 bytes sent in 0.00 seconds (19.01 KB/s) Yes, also tryed with passive off, all the same. I avoid to send that log, saving a lot of band. And GET works fine, with either unique on or off. I need overwrite to enable upload of a single file to a write disabled dir. Last question: using ftp from command line or from a cron job start with a different passive mode set, maybe a cron job doesn't read login.conf setting? Need explicit passive setting in script? Using ftp -p doesn't set passive mode the same from command line or from cron job. Is this a toggle or a force? Thanks for reading so much. Riccardo. PS: I'm subscribed only to -current, sorry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: spam
On 22-Dec-2001 (22:23:24/GMT) aaron wrote: [...removed CC: because I suppose all subscribed this list...] >> any address found in the archives is automatically subscribed Any address found N times (where N >> reasonably high number, like 10, because we can not really assume that the archives are clean). > b) distribute power of moderation (*) We can adopt Wf2Q+ from Luigi for this :-) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
On 02-Nov-2001 (12:58:55/GMT) Cyrille Lefevre wrote: >>> because `echo' nicely removes \n's from env vars when it prints them. >> des@des ~% foo='bar >> quote> baz' >> des@des ~% echo $foo >> bar >> baz >> des@des ~% /bin/echo $foo >> bar >> baz > humm! what shell ($SHELL) are you using ? Here (5.0-CURRENT 31-Oct and 4.4-STABLE 12-Oct), with /bin/sh works fine: % /bin/sh # foobar="foo > bar" # echo $foobar foo bar # echo $SHELL /bin/sh Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
uscanner and devfs
With world of 31 oct I finally make my new scanner visible. It appear under /dev as uscanner0 and on console I got the notify: uscanner0: EPSON Perfection1240, rev 1.00/1.14, addr 2 and if I switch it off I got: uscanner0: at uhub0 port 1 (addr 2) disconnected uscanner0: detached and sane is able to use it, it works. But... .../dev/uscanner is owned by root:operator with mode 644 and only root can use it, I changed mode to 666 and also my user can scan. So the question: /dev/uscanner0 is a dynamic entry under DEVFS and I am unable to change mode to 666 at boot time if scanner is off. How can I make it reboot resistant, or how can I change protection every time I switch it on? Yes, I know that /etc/rc.devfs is executed only at boot time. Is /etc/usbd.conf usable also for chown/chmod commands? Must usbd be running (I have no usbd now but it attach/detach the same). TIA, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFmail and libc.so.3
On 27-Oct-2001 (12:28:50/GMT) Riccardo Torrini wrote: I have the same problem of 27 october with src and world of last 31 oct, xfmail doesn't work with libc.so.3 from compat3x (either from ports or from COMPAT3X=yes), it crashes. Any ideas? The only method to make it happy is this hack: -8<-[ before ]-8<- # ldconfig -r | grep libc.so 33:-lc.5 => /usr/lib/libc.so.5 67:-lc.3 => /usr/lib/compat/libc.so.3 89:-lc.4 => /usr/lib/compat/libc.so.4 -8<-[ hack ]-8<- # cd /usr/lib # mv compat/libc.so.3 compat/libc.so.3-NO_THANKS # ln -s libc.so libc.so.3 -8<-[ after ]-8<- # ldconfig -r | grep libc.so 33:-lc.5 => /usr/lib/libc.so.5 66:-lc.3 => /usr/lib/libc.so.3 89:-lc.4 => /usr/lib/compat/libc.so.4 Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFmail and libc.so.3
To upgrade from xfree-3 to xfree-4 I removed all my installed ports but I lost mail program (I use XFMail, sorry for this :-) It compile and install fine but crashes with this message: The application crashed due to fatal error All unfinished messages were saved _: Report the bug with all the relevant information using the "Bug report" facility Missing or failed fl_initialize()--Invalid argument I tryed demos from xform and they works, so I examied source of xfmail and discovered that is use libc.so.3, seems that xforms crashes with original libc.so.3 and works with libc.so.5 I installed compat3x from ports and recompiled world three times (sigh) also with recent cvsup (last update this morning, GMT+1) with COMPAT3X=yes and COMPAT4X=yes in /etc/make.conf but it crashes the same. Finally I tryed this (HACK?) and it works for me. -8<-[ before ]-8<- # ldconfig -r | grep libc.so 33:-lc.5 => /usr/lib/libc.so.5 67:-lc.3 => /usr/lib/compat/libc.so.3 89:-lc.4 => /usr/lib/compat/libc.so.4 -8<-[ hack ]-8<- # cd /usr/lib # mv compat/libc.so.3 compat/libc.so.3-NO_THANKS # ln -s libc.so libc.so.3 -8<-[ after ]-8<- # ldconfig -r | grep libc.so 33:-lc.5 => /usr/lib/libc.so.5 66:-lc.3 => /usr/lib/libc.so.3 89:-lc.4 => /usr/lib/compat/libc.so.4 And now XFMail works :-) This is my first message after a week of blackout... Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86-4 required?
Is a real need for ports under -CURRENT to require (from a week or two, I don't remember) XFree86-libraries? They asks for XFree86-libraries-4.1.0, but I have 3.3.6_10 installed. Can I (safetly) mix 3.3.6 and 4.1.0? Is the upgrade from 3.3.6 to 4.1.0 really needed? Planned? I haven't set XFREE86_VERSION=4 (or anything else) in make.conf I updated again ports tree now, on my -STABLE and -CURRENT boxes, but xfree-4-libraries are still neeed (even imake-4) STABLE# cd /usr/ports/graphics/xv && make clean ===> Cleaning for libtool-1.3.4_2 ===> Cleaning for jpeg-6b ===> Cleaning for png-1.2.0 ===> Cleaning for tiff-3.5.5 ===> Cleaning for XFree86-3.3.6_10 ===> Cleaning for xv-3.10a_2 CURRENT# cd /usr/ports/graphics/xv && make clean ===> Cleaning for gettext-0.10.35 ===> Cleaning for gmake-3.79.1 ===> Cleaning for imake-4.1.0 ## (SEE NOTE) ===> Cleaning for libtool-1.3.4_2 ===> Cleaning for jpeg-6b ===> Cleaning for png-1.2.0 ===> Cleaning for tiff-3.5.5 ===> Cleaning for freetype2-2.0.4 ===> Cleaning for XFree86-libraries-4.1.0 ## (SEE NOTE) ===> Cleaning for xv-3.10a_2 NOTE: are taken from /usr/ports/distfiles/xc/X410src*, over 40MB of compressed archive. Yes, my -STABLE box is very slow P75 :( Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New features for -current
Over than an year ago (9.9.2000) I submitted a pr (kern/21154) to ask renaming from actual *_saver.ko to saver_*.ko of saver modules to uniform names under /boot/kernel as sound (snd_*), interfaces (if_*), splash (splash_*) and netgraph (ng_*). I tryed to figure where are used and I found only /etc/rc.i386: kldstat -v | grep -q _saver || kldload ${saver}_saver need to be changed to: kldstat -v | grep -q saver_ || kldload saver_${saver} Is this really so stupid? I think order is important... Another question: I noticed good support for USB peripherals like scanner, mp3 player (rio) mouse and ethernet but nothing to use a photo camera (yes, I buy an inexpensive usb digital photo camera, Agfa ePhoto-CL18) and I try to compile gphoto because it recently added support for CL-18 (w/out success). Would be a great idea add /dev/uphoto and even better a sort of photo-file-system, where read is mapped to download image, unlink to delete and maybe create file to take a picture so we can use ls, cp, rm and touch to access photo camera... Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Upgrade from old -CURRENT with this week src
After a successfull (?) upgrade from my old -CURRENT of Apr, 28 (usual stuff, buildworld, buildkernel, installkernel, installworld and mergemaster) I was unable to boot from yesterday night :( Yes, now it works, but first a little overview of my hardware: - MoBo Tyan Trinity S1590S, last bios, with K6-2/350 - 512MB ram pc133 (2x256) - ad0: 6197MB [12592/16/63] at ata0-master UDMA33 - acd0: CD-RW at ata1-master PIO3 - acd1: CDROM at ata1-slave PIO4 I rebuild because changed network card from ex0 to fxp0 :-) Now boot hangs after discovery ad0 and try to access cd burner even if I start with kernel.GENERIC (or kernel.GENERIC with debug) and loops around a reset of ide bus. Sorry for manually copy messages, I haven't serial console :( -8<- acd0: REQUEST_SENSE command timeout - resetting ata1: resetting devices .. done [...] -8<- and again, again, again (every 10" or less). Sometimes, instead of REQUEST_SENSE I got a MODE_SENSE_BIG, the rest the same). Also tryed with a cd inside, but no differences. Things go better starting with old kernel, from Apr 28, cd burner is identified and mounted (but system is a little explosive, and all commands make core around :-) As last resort, before removing ide cable from cd rom and burner I disabled second ide from BIOS and IT_WORKS. pfiuuu... Maybe something related to acpi or burncd changes? But I (think I) don't have ACPI... # acpidump acpidump: Can't find ACPI information Can I try to debug a little better? Can this help (or is already know?) I have from first day (3 year ago) APM disabled in BIOS, never added it to kernel configuration, and bios setting for OS PnP to no. Riccardo. PS: I can live w/out cdrom and burner for a little... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Different host behaviour
On 03-Oct-2001 (14:14:57/GMT) Bernd Walter wrote: >> Yes, my -CURRENT is really old, but I'm reading this list... ;) > That's your problem. Pilot error :-( Ok, sorry for that. > You see that this has been fixed at least since a month: > ticso@cicely9> uname -v > FreeBSD 5.0-CURRENT #1: Tue Sep 11 11:27:34 CEST 2001 Have you a suggestion of a date of a _not_too_much_ dangerous -current to cvs? I really want to build world again, so I can avoid this really stupid questions... 0:-) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Different host behaviour
Different behaviour from 4.4 to 5.0 of host command. Why? Yes, I got finally delegation for reverse (with RFC 2317). Yes, my -CURRENT is really old, but I'm reading this list... ;) And sorry for long lines with custom formatting. Using nslookup from either 4.4 and 5.0 give me same results (tryed with an external dns, to minimize my config problems): # nslookup 217.58.169.99 151.1.1.1 Server: dns.it.net Address: 151.1.1.1 Name:gw-fi.esaote.com Address: 217.58.169.99 Aliases: 99.169.58.217.in-addr.arpa -8<-[ 4.4-STABLE ]-8<- # uname -a FreeBSD silos.home.torrini.org 4.4-STABLE FreeBSD 4.4-STABLE #5: Sun Sep 16 05:34:02 CEST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SILOS i386 # host 217.58.169.99 99.169.58.217.IN-ADDR.ARPA is a nickname for 99.96-28.169.58.217.IN-ADDR.ARPA 99.96-28.169.58.217.IN-ADDR.ARPA domain name pointer gw-fi.esaote.com -8<-[ 5.0-CURRENT ]-8<- # uname -a FreeBSD trudy.home.torrini.org 5.0-CURRENT FreeBSD 5.0-CURRENT #17: Sat Apr 28 03:30:53 CEST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TRUDY i386 # host 217.58.169.99 99.169.58.217.IN-ADDR.ARPA is a nickname for 99.96-28.169.58.217.IN-ADDR.ARPA Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DEVFS behaviour
Maybe this is a stupid(?) question, but how DEVFS is supposed to work with softlink? How can I make them reboot-resistant? With old /dev (the directory) any file-dir-link created under that dir was permanent, but with new /dev (the virtual one) any link doesn't survive at reboot :-( If there is a default place for adding a ln command please tell me, I need for this three: # ln -s mixer1 mixer # ln -s dsp1.0 dsp # ln -s acd0c cdrom _or_ can I inform DEVFS that I need "mixer" and not "mixer1" ? TIA, Ciao, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syslogd and -a
On 02-Jul-01 (04:20:44/GMT) Crist J. Clark wrote: >> It seems the -a option for syslogd does not work 100%. > Hmmm... Looks like, > # syslogd -a 192.168.1.0/29 > Will work and, > # syslogd -a 192.168.1.1/29 > Won't. Under 4.3-STABLE is the same. To capure log from router I added (in rc.conf) -a 192.168.22.254/32:* because with all log enabled I notice that with ..22.0/24 syslod refused to accept requests from network :-( Ciao, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can a program ignore all signals?
I'm trying to obtain a dump of a (working) cd disk on FreeBSD 5.0-CURRENT #17: Sat Apr 28 03:30:53 CEST 2001 I also have a 4.3-STABLE machine but I cannot test on it because it has no cd... The machine is all ide/ata, one hd, one cd and a writer. ---[ short-dmesg ]--- atapci0: port ... ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 [...] ad0: 6197MB [12592/16/63] at ata0-master UDMA33 acd0: CD-RW at ata1-master PIO3 acd1: CDROM at ata1-slave PIO4 ---[ /short-dmesg ]--- # isoinfo -i /dev/acd0c -l shows me a dir listing (w/out mounting it), also disk mount fine as iso_9660 (no extension, short names, only level-1, no RR nor Joliet) I tryed with (from my user and from root): # cp /dev/acd0c /tmp/mydump.iso Activity led on cd stay on, nothing happens :-( Killing process fail. Any signal fail. From same shell (tcsh) neither ^C, ^Z, ^\ or any other key combination works nor from another shell (either from same user and from root) with all signals showed by kill -l. Tryed more and more... Killing shell leave process running, with PPID=1 instead of PPID=(same pid of tcsh) Only shutdown stop it, but with message: "some processes would not die; ps axl advised" After reboot all partitions are clean, no need of fsck. Maybe cp is the wrong command to obtaining an iso image dump, but why it survive kill? Is normal? Pilot error? How can I make a copy of a self made (or even better of _ANY_ data cd) without archiving all iso images on hd? I noticed /dev/acd0t1 appears (I'm using DEVFS) under /dev after isoinfo. Can I (must ?) use that instead of acd0c? Yes, under another os (?) I am able to copy it :-( Ciao++ Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ** HEADS UP **: sys/miscfs file systems moved
On 23-May-01 (09:53:13/GMT) Ruslan Ermilov wrote: > - FDESC, FIFO, NULL, PORTAL, PROC, UMAP and UNION file > systems were repo-copied from sys/miscfs to sys/fs. > - Renamed the following file systems and their modules: > fdesc -> fdescfs, portal -> portalfs, union -> unionfs. > - Renamed corresponding kernel options: > FDESC -> FDESCFS, PORTAL -> PORTALFS, UNION -> UNIONFS. Maybe this is a good moment to ask for rename modules from *_saver.ko to saver_*.ko to follow other layouts as for if_ for interfaces, ng_ for netgraph, splash_ for splash screen and snd_ for sound (as i asked into PR kern/21154)? I know it is _ONLY_ a cosmetic change, but I think may be one of the simple ;) BTW: Apart from sources, the only reference to *saved.ko modules on a running system is into /etc/rc.i386: kldstat -v | grep -q _saver || kldload ${saver}_saver and must be changed to kldstat -v | grep -q saver_ || kldload saver_${saver} Thanks for your time, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: evil ATA
On 16-May-01 (15:14:50/GMT) Phil Knaack wrote: >> on udma controller. take a look at sysctl hw.atamodes (may look >> like 'dma,---,---,dma') and try change it to PIO mode. > I noticed a few days ago that a new command was added to -current, > called "atacontrol". This command provides a real handy way... Maybe I am missing some important information, but on my -CURRENT box (FreeBSD 5.0-CURRENT #17: Sat Apr 28 03:30:53 CEST 2001) I'm unable to find hw.atamodes :-( # sysctl -a | grep -i hw.ata hw.ata.ata_dma: 1 hw.ata.wc: 0 hw.ata.tags: 0 hw.ata.atapi_dma: 0 On the other (FreeBSD 4.3-STABLE #3: Wed Apr 25 10:14:54 CEST 2001) box they are in the right place: # sysctl -a | grep -i hw.ata hw.ata.ata_dma: 1 hw.ata.wc: 0 hw.ata.tags: 0 hw.atamodes: pio,---,---,---, Ciao, Riccardo. PS: It is safer a world this days? I wouldn't like to loose all files and rest only with lost+found as on HEADS-UP of same days ago... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: nroff -man broken?
On 25-Apr-01 (07:18:57/GMT) Ruslan Ermilov wrote: > There was a problem caused by broken `make cleandir' behavior. > Make sure you have src/share/mk/bsd.obj.mk, revision 1.35. # $FreeBSD: src/share/mk/bsd.obj.mk,v 1.35 2001/04/23 14:47:40 ru Exp $ Going to make another world this night :( Ciao, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: nroff -man broken?
On 25-Apr-01 (07:55:22/GMT) Sheldon Hearn wrote: > Check for catpages in */man/en.ISO_8859-1/cat* as well, > using your own locale-dependent directory, of course. Only have /usr/share/man/en.ISO_8859-1/ but all dirs under this path (cat[1-9n] and cat1aout) are empty :-( # gzip -l cat1/man.1.gz compressed uncompr. ratio uncompressed_name 67 115 57.3% cat1/man.1 # gzip -cd cat1/man.1.gz|hd 00 4d414e28 31290909 09467265 65425344 |MAN(1)...FreeBSD| 10 2047656e 6572616c 20436f6d 6d616e64 | General Command| 20 73204d61 6e75616c 2009094d 414e2831 |s Manual ..MAN(1| 30 290a0a0a 0a0a0a0a 0a0a0a0a 0a0a0a0a |)...| 40 0a0a0a0a 0a0a0a0a 0a0a0a0a 0a0a0a0a || * 70 Even removing cat1/man.1.gz man re-create same empty file. Also making man formatting by hand show same error: # gzip -cd /usr/share/man/man1/man.1.gz | nroff -man mdoc error: end-macro (.em) respecification is not allowed. (#20) Should this have been `.Em ...'? User Abort. Ciao, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Boot messages
On 25-Apr-01 (01:31:59/GMT) Garrett Wollman wrote: > The ``can't assign resources'' messages indicate that the > devices are legacy ISA devices for which a non-PnP-aware > driver is compiled into the kernel. These include devices > such as keyboard... This means that I can remove this lines? Sure? -8<-[ /usr/src/sys/i386/conf/TRUDY ]-8<- # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 device atkbd device psm # Floppy drives device fdc # Serial (COM) ports device sio 1 # pca: PCM audio through your PC speaker device pca > AIUI such messages are currently disabled unless one boots in > verbose mode. Under -CURRENT boot is supposed to be 'extra_verbose' (IMHO). Ciao, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Boot messages
On 24-Apr-01 (23:19:59/GMT) Dima Dorfman wrote: >> WARNING: Driver mistake: repeat make_dev("pcaudio") >> WARNING: Driver mistake: repeat make_dev("pcaudioctl") > As it says, this is a driver mistake. It's a bug. Ok. It happens from first days of devfs. I'm looking into gnats but there isn't any reference to it. Must send a PR? >> unknown: can't assign resources... > This is not a bug. This is an FAQ. Yes. I know. I'll try to explain better: where can I find a list of unsupported PnP devices? I only have an ethernet isa card (ex0) and a sound isa card (AWE64). Where all that PnP devices come from? Here is my dmesg: [...] pca0 at port 0x40 on isa0 ex0: at port 0x300-0x30f irq 10 on isa0 ex0: Manual config, 16-bit bus, board id 0x006, stepping 0x0 ex0: Ethernet address 00:aa:00:ad:44:7c sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm1: on sbc0 midi0: on sbc0 midi1: on sbc0 joy0: at port 0x200-0x207 on isa0 midi2: at port 0x620-0x623,0xa20-0xa23,0xe20-0xe23 on isa0 emu2: DRAM size = 512KB unknown: can't assign resources pca1: at port 0x61 on isa0 WARNING: Driver mistake: repeat make_dev("pcaudio") WARNING: Driver mistake: repeat make_dev("pcaudioctl") unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources [...] And this? What is it? isa0: unexpected small tag 14 Thanks in advance, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Boot messages
I'm trying to understand why this happens at boot and if is my fault (maybe), strange hardware or undocumented feature :) isa0: unexpected small tag 14 unknown: can't assign resources pca1: at port 0x61 on isa0 WARNING: Driver mistake: repeat make_dev("pcaudio") WARNING: Driver mistake: repeat make_dev("pcaudioctl") unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources What kind of hardware is inside my case? I have only an AWE64 and an Intel Pro/10 (both isa devices) and I am using devfs so how can I make_dev() something? And also why soft links into /dev get lost after reboot? How can I make them persistent? Must do every boot? Any help appreciated. Thanks. Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message