Re: fast rate of major FreeBSD releases to STABLE
Actually, I don't see how RELENG_X branch will help. %-\ I would suggest this scheme: branch "." - as now, the recent versions branch "sec" - versions bump strictly at 1-st of january and 1-st of july, other updates fix only security issues. That would be really great improvement to ports, but not sure community has enough programmers among port maintaners, so it's just another dream :o( > This looks like another call to have RELENG_x branches on ports, with > which I agree. -- системный администратор ООО "Сиб-ЭкоМеталл" тел. (3912) 609942 (144) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
make buildworld issue on 6.2 stable
uname -a FreeBSD sagan.cai 6.2-STABLE FreeBSD 6.2-STABLE #0: Sat May 5 23:34:08 CST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAGAN i386 The results of make buildworld on this system: ide -k _crunched_chroot_stub chroot.lo cc -static -o rescue rescue.o cat.lo chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo pax.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo sh.lo stty.lo sync.lo test.lo rcp.lo csh.lo atacontrol.lo badsect.lo bsdlabel.lo camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo gbde.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo mount.lo mount_cd9660.lo mount_ext2fs.lo mount_msdosfs.lo mount_nfs.lo mount_ntfs.lo mount_nullfs.lo mount_std.lo mount_udf.lo mount_umapfs.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo rtsol.lo savecore.lo slattach.lo spppcontrol.lo startslip.lo swapon.lo sysctl.lo tunefs.lo umount.lo atm.lo atmconfig.lo fore_dnld.lo ilmid.lo ping6.lo ipf.lo sconfig.lo fdisk.lo dhclient.lo gzip.lo bzip2.lo tar.lo vi.lo id.lo chroot.lo /usr/obj/usr/src/rescue/rescue/../librescue/exec.o /usr/obj/usr/src/rescue/rescue/../librescue/getusershell.o /usr/obj/usr/src/rescue/rescue/../librescue/login_class.o /usr/obj/usr/src/rescue/rescue/../librescue/popen.o /usr/obj/usr/src/rescue/rescue/../librescue/rcmdsh.o /usr/obj/usr/src/rescue/rescue/../librescue/sysctl.o /usr/obj/usr/src/rescue/rescue/../librescue/system.o -lcrypt -ledit -lkvm -ll -lm -ltermcap -lutil -lcrypto -latm -lalias -lbsdxml -lcam -lcurses -ldevstat -lipsec -lipx -lgeom -lkiconv -lmd -lreadline -lsbuf -lufs -lz -lbz2 -larchive ifconfig.lo(.text+0x4df8): In function `print_chaninfo': : undefined reference to `IEEE80211_IS_CHAN_PASSIVE' *** Error code 1 Stop in /usr/obj/usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue/rescue. *** Error code 1 Stop in /usr/src/rescue. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src I haven't seen anyone else get this error so I think it is just this system. Any thoughts? cheers shaun -- Shaun Branden: Alchemist and Bit Bender PGP and contact details in the headers. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thu, 24 May 2007 19:31:49 -0600 Scott Long <[EMAIL PROTECTED]> wrote: > Robert Marella wrote: > > On Thu, 24 May 2007 18:46:09 -0300 > > JoaoBR <[EMAIL PROTECTED]> wrote: > > > >> On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote: > >>> ping# uname -a > >>> FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: > >>> Wed May 23 15:19:22 EEST 2007 > >>> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 > >>> > >>> (compiled from sources updated immediately before the build > >>> started, no later than 10.00 UTC on 23.5.2007) > >>> > >>> k3b is working absolutely fine on this box, I just managed to burn > >>> a CD followed by a DVD. > >> so that is funny now > >> so i tried and indeed I can write an iso with cdrecord > >> > >> which is your k3b version? I have k3b 1.0_2 > >> > >> > >> > >> > > I finally upgrade my amd64 and K3B works perfect without the patch. > > Dmesg stiil complains with the same warnings. > > > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > > > and when I am ripping > > > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > > > But all is working. > > > > These errors can be safely ignored. They are a side effect of the CAM > probe device sending normal commands to the drive, and the ATA driver > intercepting the responses. This will be fixed on a broad scale in > the future. > > Scott > I was already under that impression. I was using the patch for the last several weeks and I just updated to today's stable. K3B is working fine without the patch. I will continue to ignore those messages ;) Robert P.S. A personal thank you for all you do for FreeBSD ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Friday 25 May 2007 00:46:09 JoaoBR wrote: > On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote: > > ping# uname -a > > FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May > > 23 15:19:22 EEST 2007 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 > > > > (compiled from sources updated immediately before the build started, no > > later than 10.00 UTC on 23.5.2007) > > > > k3b is working absolutely fine on this box, I just managed to burn a CD > > followed by a DVD. > > so that is funny now > so i tried and indeed I can write an iso with cdrecord > > which is your k3b version? I have k3b 1.0_2 Same here. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] "In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates." -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
Robert Marella wrote: On Thu, 24 May 2007 18:46:09 -0300 JoaoBR <[EMAIL PROTECTED]> wrote: On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote: ping# uname -a FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23 15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 (compiled from sources updated immediately before the build started, no later than 10.00 UTC on 23.5.2007) k3b is working absolutely fine on this box, I just managed to burn a CD followed by a DVD. so that is funny now so i tried and indeed I can write an iso with cdrecord which is your k3b version? I have k3b 1.0_2 I finally upgrade my amd64 and K3B works perfect without the patch. Dmesg stiil complains with the same warnings. acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 and when I am ripping acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 But all is working. These errors can be safely ignored. They are a side effect of the CAM probe device sending normal commands to the drive, and the ATA driver intercepting the responses. This will be fixed on a broad scale in the future. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Corrupt fonts-alias (Re: xorg 7.2 start problem)
On Fri, May 25, 2007 at 11:59:51AM +1200, Mark Kirkwood wrote: > Kris Kennaway wrote: > > > >Grr, OK. Well, you might have got it wrong, so we still need to see a > >portupgrade log from someone who followed the directions. > > Kris, > > FWIW - I followed the instructions in UPDATING - unfortunately I did 'em > pretty much as I read 'em... so I noticed the CAVEAT *after* the > upgrade and mergebase was complete - doh! > > So I installed x11/xorg after the upgrade, and promptly got the 'cannot > open fixed'... which was sorted by reinstalling misc and font-misc-misc > and font-cursor-misc. Is installing xorg after the upgrade a likely > cause of problems? Nope. > Also, ahem, I didn't script the upgrade, so no log sorry :-(. I've got > another (6-STABLE) box to do later, so I'll log that one ... promise... OK Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installworld breaks
On Thu, 24 May 2007, [EMAIL PROTECTED] wrote: cvsup and built around 20.30 BST cd /usr/src; make -f Makefile.inc1 install ===> share/info install ===> include install creating osreldate.h from newvers.sh touch: not found ***error code 127 Stop in /usr/src/include ***error code 1 I tried cd usr.bin/touch && make && make install but it does not seem to have any effect any offers? cheers find / -name touch ?? -- Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" *--* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *--* ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Corrupt fonts-alias (Re: xorg 7.2 start problem)
Kris Kennaway wrote: Grr, OK. Well, you might have got it wrong, so we still need to see a portupgrade log from someone who followed the directions. Kris, FWIW - I followed the instructions in UPDATING - unfortunately I did 'em pretty much as I read 'em... so I noticed the CAVEAT *after* the upgrade and mergebase was complete - doh! So I installed x11/xorg after the upgrade, and promptly got the 'cannot open fixed'... which was sorted by reinstalling misc and font-misc-misc and font-cursor-misc. Is installing xorg after the upgrade a likely cause of problems? Also, ahem, I didn't script the upgrade, so no log sorry :-(. I've got another (6-STABLE) box to do later, so I'll log that one ... promise... Cheers Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Corrupt fonts-alias (Re: xorg 7.2 start problem)
On Fri, May 25, 2007 at 12:45:52AM +0200, Nicolas Rachinsky wrote: > * Kris Kennaway <[EMAIL PROTECTED]> [2007-05-24 17:08 -0400]: > > > Unfortunately portupgrade (nor portupgrade-devel) cannot yet handle > > > the rigors of the xorg upgrade without a small bit of help: > > > > > > # portupgrade -Rf libXft > > > > > > before you do the portupgrade -a? > > > > No, that is to avoid a dependency loop involving libXft and > > xorg-libraries because of a bug in how portupgrade orders > > dependencies. > > Ah. I didn't really use portupgrade, I just used it to sort the > ports I wanted to update. Grr, OK. Well, you might have got it wrong, so we still need to see a portupgrade log from someone who followed the directions. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Corrupt fonts-alias (Re: xorg 7.2 start problem)
* Kris Kennaway <[EMAIL PROTECTED]> [2007-05-24 17:08 -0400]: > > Unfortunately portupgrade (nor portupgrade-devel) cannot yet handle > > the rigors of the xorg upgrade without a small bit of help: > > > > # portupgrade -Rf libXft > > > > before you do the portupgrade -a? > > No, that is to avoid a dependency loop involving libXft and > xorg-libraries because of a bug in how portupgrade orders > dependencies. Ah. I didn't really use portupgrade, I just used it to sort the ports I wanted to update. And after seeing this (and the failures), I rebuilt libXft and convinced ld-elf.so to use the library in /usr/local in preference of the one in /usr/X11R6. The following rebuild of the fonts worked fine. Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thu, 24 May 2007 18:46:09 -0300 JoaoBR <[EMAIL PROTECTED]> wrote: > On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote: > > > > ping# uname -a > > FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed > > May 23 15:19:22 EEST 2007 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 > > > > (compiled from sources updated immediately before the build > > started, no later than 10.00 UTC on 23.5.2007) > > > > k3b is working absolutely fine on this box, I just managed to burn > > a CD followed by a DVD. > > so that is funny now > so i tried and indeed I can write an iso with cdrecord > > which is your k3b version? I have k3b 1.0_2 > > > > I finally upgrade my amd64 and K3B works perfect without the patch. Dmesg stiil complains with the same warnings. acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 and when I am ripping acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 But all is working. Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installworld breaks
Clock in sync? That's the usual cause for things like this. Steve - Original Message - From: <[EMAIL PROTECTED]> cvsup and built around 20.30 BST cd /usr/src; make -f Makefile.inc1 install ===> share/info install ===> include install creating osreldate.h from newvers.sh touch: not found ***error code 127 Stop in /usr/src/include ***error code 1 I tried cd usr.bin/touch && make && make install but it does not seem to have any effect This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote: > > ping# uname -a > FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23 > 15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING > amd64 > > (compiled from sources updated immediately before the build started, no > later than 10.00 UTC on 23.5.2007) > > k3b is working absolutely fine on this box, I just managed to burn a CD > followed by a DVD. so that is funny now so i tried and indeed I can write an iso with cdrecord which is your k3b version? I have k3b 1.0_2 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: installworld breaks
On Thu, May 24, 2007 at 09:46:30PM +0100, [EMAIL PROTECTED] wrote: > cvsup and built around 20.30 BST > cd /usr/src; make -f Makefile.inc1 install > ===> share/info install > ===> include install > creating osreldate.h from newvers.sh > touch: not found > ***error code 127 > > Stop in /usr/src/include > ***error code 1 > > I tried cd usr.bin/touch && make && make install > but it does not seem to have any effect > > any offers? Usually means system time is wrong or went backwards. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld broken?
On Thu, May 24, 2007 at 11:57:46PM +0300, Abdullah Ibn Hamad Al-Marri wrote: > /usr/src/sys/modules/procfs/../../fs/procfs/procfs_regs.c: In function > `procfs_doprocregs': > /usr/src/sys/modules/procfs/../../fs/procfs/procfs_regs.c:96: warning: > implicit declaration of function `PROC_ASSERT_HELD' > /usr/src/sys/modules/procfs/../../fs/procfs/procfs_regs.c:96: warning: > nested extern declaration of `PROC_ASSERT_HELD' > *** Error code 1 It looks like this has already been fixed. See Dag-Erling Smørgrav's email a short while ago. Wait an hour or so, then update your sources and try again. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
installworld breaks
cvsup and built around 20.30 BST cd /usr/src; make -f Makefile.inc1 install ===> share/info install ===> include install creating osreldate.h from newvers.sh touch: not found ***error code 127 Stop in /usr/src/include ***error code 1 I tried cd usr.bin/touch && make && make install but it does not seem to have any effect any offers? cheers -- Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Corrupt fonts-alias (Re: xorg 7.2 start problem)
On Thu, May 24, 2007 at 10:42:38PM +0200, Nicolas Rachinsky wrote: > * Kris Kennaway <[EMAIL PROTECTED]> [2007-05-24 16:19 -0400]: > > On Thu, May 24, 2007 at 03:00:11PM +0200, Nicolas Rachinsky wrote: > > > * Peter Jeremy <[EMAIL PROTECTED]> [2007-05-24 21:40 +1000]: > > > > I've found this problem on one system (the one where I thought the > > > > upgrade had gone the most cleanly). font-alias _is_ installed but > > > > most of my pcf.gz files are corrupt (20 bytes long). > > > > > > > > 'portupgrade -f' on my fonts is fixing this but I'm not exactly sure > > > > why it occurred to start with. > > > > > > bdftopcf fails if it uses the old library from X11R6. The 20 bytes are > > > the compressed empty output of the failing bdftopcf. > > > > Sounds like it is being upgraded out of order, we need a full log to > > figure out why. > > Isn't this already known and the reason for the advice in > /usr/port/UPDATING > > Unfortunately portupgrade (nor portupgrade-devel) cannot yet handle > the rigors of the xorg upgrade without a small bit of help: > > # portupgrade -Rf libXft > > before you do the portupgrade -a? No, that is to avoid a dependency loop involving libXft and xorg-libraries because of a bug in how portupgrade orders dependencies. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld broken?
Hello, cc -O2 -fno-strict-aliasing -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/procfs/../../fs/procfs/procfs_mem.c cc -O2 -fno-strict-aliasing -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/procfs/../../fs/procfs/procfs_note.c cc -O2 -fno-strict-aliasing -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/procfs/../../fs/procfs/procfs_regs.c /usr/src/sys/modules/procfs/../../fs/procfs/procfs_regs.c: In function `procfs_doprocregs': /usr/src/sys/modules/procfs/../../fs/procfs/procfs_regs.c:96: warning: implicit declaration of function `PROC_ASSERT_HELD' /usr/src/sys/modules/procfs/../../fs/procfs/procfs_regs.c:96: warning: nested extern declaration of `PROC_ASSERT_HELD' *** Error code 1 Stop in /usr/src/sys/modules/procfs. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Corrupt fonts-alias (Re: xorg 7.2 start problem)
* Kris Kennaway <[EMAIL PROTECTED]> [2007-05-24 16:19 -0400]: > On Thu, May 24, 2007 at 03:00:11PM +0200, Nicolas Rachinsky wrote: > > * Peter Jeremy <[EMAIL PROTECTED]> [2007-05-24 21:40 +1000]: > > > I've found this problem on one system (the one where I thought the > > > upgrade had gone the most cleanly). font-alias _is_ installed but > > > most of my pcf.gz files are corrupt (20 bytes long). > > > > > > 'portupgrade -f' on my fonts is fixing this but I'm not exactly sure > > > why it occurred to start with. > > > > bdftopcf fails if it uses the old library from X11R6. The 20 bytes are > > the compressed empty output of the failing bdftopcf. > > Sounds like it is being upgraded out of order, we need a full log to > figure out why. Isn't this already known and the reason for the advice in /usr/port/UPDATING Unfortunately portupgrade (nor portupgrade-devel) cannot yet handle the rigors of the xorg upgrade without a small bit of help: # portupgrade -Rf libXft before you do the portupgrade -a? Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Corrupt fonts-alias (Re: xorg 7.2 start problem)
On Thu, May 24, 2007 at 03:00:11PM +0200, Nicolas Rachinsky wrote: > * Peter Jeremy <[EMAIL PROTECTED]> [2007-05-24 21:40 +1000]: > > I've found this problem on one system (the one where I thought the > > upgrade had gone the most cleanly). font-alias _is_ installed but > > most of my pcf.gz files are corrupt (20 bytes long). > > > > 'portupgrade -f' on my fonts is fixing this but I'm not exactly sure > > why it occurred to start with. > > bdftopcf fails if it uses the old library from X11R6. The 20 bytes are > the compressed empty output of the failing bdftopcf. > > Nicolas Sounds like it is being upgraded out of order, we need a full log to figure out why. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thursday 24 May 2007 21:48:04 JoaoBR wrote: > On Thursday 24 May 2007 15:15:51 you wrote: > > On Wed, 23 May 2007 17:40:25 -0300 > > > > [EMAIL PROTECTED] ~> uname -a > > FreeBSD asus64.konav201.local 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Apr > > 17 17:38:20 HST 2007 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 > > > > [EMAIL PROTECTED] ~> dmesg | grep acd > > acd0: DMA limited to UDMA33, device found non-ATA66 cable > > acd0: DVDR at ata1-master UDMA33 > > acd1: DVDROM at ata1-slave UDMA33 > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x0 > > > > K3B works fine after build kernel/world on above date. > > Hi > so you are suggesting a rollback? I compiled on may 21st and 23rd and as > Joe Altman confirmed too it's not working anymore on amd64 ... on i386 it's > ok, may be this is a good moment then to change my backup strategy and use > usb mem chips and kick atapicam out of the kernel ping# uname -a FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23 15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 (compiled from sources updated immediately before the build started, no later than 10.00 UTC on 23.5.2007) k3b is working absolutely fine on this box, I just managed to burn a CD followed by a DVD. A. -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] "In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates." -- anon | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg 7.2 start problem
On Thu, May 24, 2007 at 11:46:24AM +0400, grimnir wrote: > You can try to install x11-fonts/font-alias port, this may fix the problem. nope: jhengis~ % pkg_info | grep font-alias font-alias-1.0.1X.Org Font aliases pkg_info: show_file: can't open '+COMMENT' for reading This does not seem to be the problem. Unless its that +COMMENT to-do, not quite sure what that means, I have to admit. Cheerio. -- SDF Public Access UNIX System - http://sdf.lonestar.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thu, 24 May 2007 16:41:01 -0300
JoaoBR <[EMAIL PROTECTED]> wrote:
>
>
> On Thursday 24 May 2007 16:10:02 Robert Marella wrote:
> > On Thu, 24 May 2007 15:48:04 -0300
> > >
> > > Hi
> > > so you are suggesting a rollback? I compiled on may 21st and 23rd
> > > and as Joe Altman confirmed too it's not working anymore on
> > > amd64 ... on i386 it's ok, may be this is a good moment then to
> > > change my backup strategy and use usb mem chips and kick atapicam
> > > out of the kernel
> >
> > Well, now I'm scared! I usually update via build kernel/world on
> > Fridays but I missed a week or two. I was planing on doing it
> > tomorrow.
> >
> > I don't think I'll have a need for K3B so for test purposes I will
> > do it today and report back in an hour or so.
> >
> > Wish me luck.
> >
>
> my dear ... no luck in site at this moment, don't wast your time,
> patience is what you need now and a tail -f on cvs-src ;)
>
>
>
Please forgive an old man's failing memory. I have two systems running
6 stable. One is i386 and the other amd64. Back in April a patch was
made available for the K3B problem. It fixed both of the systems.
I updated the i386 on May 4th and the patch was no longer needed but I
never updated the amd64 so it is running K3B with the patch. I am in
the process of updating the amd64 and will test it without and with the
patch.
I have attached the patch in case you never saw it.
RobertRCS file: /space/mirror/ncvs/src/sys/dev/ata/atapi-cam.c,v
retrieving revision 1.50
diff -u -r1.50 atapi-cam.c
--- atapi-cam.c 14 Mar 2007 01:59:00 - 1.50
+++ atapi-cam.c 27 Apr 2007 19:26:09 -
@@ -729,7 +743,7 @@
* issued a REQUEST SENSE automatically and that operation
* returned without error.
*/
- if (request->u.atapi.saved_cmd != 0 && request->error == 0) {
+ if (request->u.atapi.sense.key != 0 && request->error == 0) {
bcopy (&request->u.atapi.sense, &csio->sense_data, sizeof(struct atapi_sense));
csio->ccb_h.status |= CAM_AUTOSNS_VALID;
}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: src/sys/fs/procfs procfs_regs.c
Doug White <[EMAIL PROTECTED]> writes: > Log: > Fix assertion accidentally changed to HEAD version. This was breaking the > RELENG_6 build. > > Pointy hat to: des Apologies for the breakage, which should be fixed now. I was working through my MFC reminder backlog and got a little ahead of myself. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thursday 24 May 2007 16:10:02 Robert Marella wrote: > On Thu, 24 May 2007 15:48:04 -0300 > > > > Hi > > so you are suggesting a rollback? I compiled on may 21st and 23rd > > and as Joe Altman confirmed too it's not working anymore on amd64 ... > > on i386 it's ok, may be this is a good moment then to change my > > backup strategy and use usb mem chips and kick atapicam out of the > > kernel > > Well, now I'm scared! I usually update via build kernel/world on > Fridays but I missed a week or two. I was planing on doing it tomorrow. > > I don't think I'll have a need for K3B so for test purposes I will do > it today and report back in an hour or so. > > Wish me luck. > my dear ... no luck in site at this moment, don't wast your time, patience is what you need now and a tail -f on cvs-src ;) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error from freebsd-stable Digest, Vol 207, Issue 6
On Thursday 24 May 2007 12:12:34 Joe Altman wrote:
> >
> > __FBSDID("$FreeBSD: src/sys/dev/ata/atapi-cam.c,v 1.42.2.5
> > 2007/05/15
> > 16:19:42 thomas Exp $");
>
> I am, and I just wanted to acknowledge your message, unfortunately I
> won't be able to further look into it immediately, as I'm about to
> leave for vacation... I'm keeping it on my inbound list, feel free to
> ping me if I don't get back to you within 2 weeks.
>
> All the best,
> Thomas.
>
> I have no clue why someone would insert changes into source, find
> (assuming he saw the discussion in April, on this list) those changes
> problematic, change the source somewhat to remedy those problems, put
> further changes into the source either causing new problems or
> reintroducing the old one; and when told at least once that "Hey,
> there is a problem here; what can you tell me?" replies "Sorry, I'm on
> vacation."
same as ipfw some weeks ago :S
lucky us that atapicam is an exotic driver and not so widely used and still
more lucky us that it is atapicam and not ahd or aac right? Sorry dear
clients our mail cluster is out of service and when it does not work in three
weeks or so please give me a new call ok ...
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thu, 24 May 2007 15:48:04 -0300 JoaoBR <[EMAIL PROTECTED]> wrote: > > On Thursday 24 May 2007 15:15:51 you wrote: > > On Wed, 23 May 2007 17:40:25 -0300 > > > > [EMAIL PROTECTED] ~> uname -a > > FreeBSD asus64.konav201.local 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue > > Apr 17 17:38:20 HST 2007 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 > > > > [EMAIL PROTECTED] ~> dmesg | grep acd > > acd0: DMA limited to UDMA33, device found non-ATA66 cable > > acd0: DVDR at ata1-master UDMA33 > > acd1: DVDROM at ata1-slave UDMA33 > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x0 > > > > K3B works fine after build kernel/world on above date. > > > > Hi > so you are suggesting a rollback? I compiled on may 21st and 23rd > and as Joe Altman confirmed too it's not working anymore on amd64 ... > on i386 it's ok, may be this is a good moment then to change my > backup strategy and use usb mem chips and kick atapicam out of the > kernel > > Well, now I'm scared! I usually update via build kernel/world on Fridays but I missed a week or two. I was planing on doing it tomorrow. I don't think I'll have a need for K3B so for test purposes I will do it today and report back in an hour or so. Wish me luck. Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Thursday 24 May 2007 15:15:51 you wrote: > On Wed, 23 May 2007 17:40:25 -0300 > > [EMAIL PROTECTED] ~> uname -a > FreeBSD asus64.konav201.local 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Apr > 17 17:38:20 HST 2007 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 > > [EMAIL PROTECTED] ~> dmesg | grep acd > acd0: DMA limited to UDMA33, device found non-ATA66 cable > acd0: DVDR at ata1-master UDMA33 > acd1: DVDROM at ata1-slave UDMA33 > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x0 > > K3B works fine after build kernel/world on above date. > Hi so you are suggesting a rollback? I compiled on may 21st and 23rd and as Joe Altman confirmed too it's not working anymore on amd64 ... on i386 it's ok, may be this is a good moment then to change my backup strategy and use usb mem chips and kick atapicam out of the kernel -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error
On Wed, 23 May 2007 17:40:25 -0300 JoaoBR <[EMAIL PROTECTED]> wrote: > > > On Wednesday 23 May 2007 14:03:18 Jeremy Chadwick wrote: > > On Wed, May 23, 2007 at 01:49:33PM -0300, JoaoBR wrote: > > > > > acd0: CDRW at ata0-master UDMA33 > > > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > > > cd0 at ata0 bus 0 target 0 lun 0 > > > > cd0: Removable CD-ROM SCSI-0 > > > > device cd0: 33.000MB/s transfers > > > > cd0: cd present [1 x 2048 byte records] > > > > acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 > > > > acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 > > > > sure, but as make kernel KERNCONF=blabla after building world > > > may be that I am running amd64 is the problem? > > > > I only run i386, so I can't confirm/deny. Sorry. :-( > > ok I compiled on i386 it's ok, also k3b works fine > > I recompiled amd64 world and kernel to be sure and the problem > persists > Aloha JoaoBR [EMAIL PROTECTED] ~> uname -a FreeBSD asus64.konav201.local 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Apr 17 17:38:20 HST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~> dmesg | grep acd acd0: DMA limited to UDMA33, device found non-ATA66 cable acd0: DVDR at ata1-master UDMA33 acd1: DVDROM at ata1-slave UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x0 K3B works fine after build kernel/world on above date. HTH Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam cd error from freebsd-stable Digest, Vol 207, Issue 6
On Thu, May 24, 2007 at 05:16:47AM +, [EMAIL PROTECTED] wrote:
>3. atapicam cd error (JoaoBR)
>
> --
>
> Message: 3
> Date: Wed, 23 May 2007 12:44:20 -0300
> From: JoaoBR <[EMAIL PROTECTED]>
> Subject: atapicam cd error
> To: freebsd-stable@freebsd.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hi, some knows how to solve this problema or what it is?
>
> acd0: CDRW at ata0-master UDMA33
> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
> cd0 at ata0 bus 0 target 0 lun 0
> cd0: Removable CD-ROM SCSI-0 device
> cd0: 33.000MB/s transfers
> cd0: cd present [1 x 2048 byte records]
> acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00
> acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00
You can use google, or the search feature at archive for -stable to
find previous discussion. It appears that it is a result of changes to
atapi-cam.c. I suggest searching for the error message in April's
-stable archive; and then my query on -questions in May.
I've been waiting for it to bite someone else, so that I could offer
this:
I wrote to the maintainer for atapi-cam.c, and here is his reply:
* Joe Altman, 2007-05-19 :
> My apologies for disturbing you; I imagine that you are quite busy,
> but I wonder if you are the thomas listed here:
>
> __FBSDID("$FreeBSD: src/sys/dev/ata/atapi-cam.c,v 1.42.2.5
> 2007/05/15
> 16:19:42 thomas Exp $");
I am, and I just wanted to acknowledge your message, unfortunately I
won't be able to further look into it immediately, as I'm about to
leave for vacation... I'm keeping it on my inbound list, feel free to
ping me if I don't get back to you within 2 weeks.
All the best,
Thomas.
I have no clue why someone would insert changes into source, find
(assuming he saw the discussion in April, on this list) those changes
problematic, change the source somewhat to remedy those problems, put
further changes into the source either causing new problems or
reintroducing the old one; and when told at least once that "Hey,
there is a problem here; what can you tell me?" replies "Sorry, I'm on
vacation."
Speaking for myself, I'd think that introducing things that might
break stuff on Friday is a basic "Don't Do That" sort of thing. I'm
sure that there is at least one SysAdmin here that knows what that's
about.
Oh, I forgot: it's free, so who am I to complain; especially about
breaking something as frivolous as atapicam.
And yet, people are concerned that an ascii art figure of a daemon
might project an unprofessional image of the project?
Removing atapicam as a kernel module remedied the entire issue for me.
There is, I believe predictably, a noticeable difference in the way
the Plextor performs. I say believe, because I know it is a subjective
impression on my part.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
make buildworld failing - multiple definitions of pam_* in libpam
Hello, I've been trying to update my system recently. (using cvsup to sync the sources, *default release=cvs tag=RELENG_6) uname -a FreeBSD machine.somewhere 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #2: Thu Sep 28 23:13:24 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOYAU_IPFW amd64 make buildworld ... cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_setcred.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_setenv.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_start.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_strerror.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_verror.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_vinfo.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_vprompt.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/pam_debug_log.c cc -O -pipe -fPIC -I/usr/src/lib/libpam/libpam -I/usr/src/lib/libpam/libpam/../../../contrib/openpam/include -DLIB_MAJ=3 -DOPENPAM_MODULES_DIR='"/usr/lib/"' -std=iso9899:1999 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_static.c ld -o openpam_static_modules.o -r --whole-archive openpam_static.o ../modules/pam_chroot/libpam_chroot.a ../modules/pam_deny/libpam_deny.a ../modules/pam_echo/libpam_echo.a ../modules/pam_exec/libpam_exec.a ../modules/pam_ftpusers/libpam_ftpusers.a ../modules/pam_group/libpam_group.a ../modules/pam_guest/libpam_guest.a ../modules/pam_krb5/libpam_krb5.a ../modules/pam_ksu/libpam_ksu.a ../modules/pam_lastlog/libpam_lastlog.a ../modules/pam_login_access/libpam_login_access.a ../modules/pam_nologin/libpam_nologin.a ../modules/pam_opie/libpam_opie.a ../modules/pam_opieaccess/libpam_opieaccess.a ../modules/pam_passwdqc/libpam_passwdqc.a ../modules/pam_permit/libpam_permit.a ../modules/pam_radius/libpam_radius.a ../modules/pam_rhosts/libpam_rhosts.a ../modules/pam_rootok/libpam_rootok.a ../modules/pam_securetty/libpam_securetty.a ../modules/pam_self/libpam_self.a ../modules/pam_ssh/libpam_ssh.a ../modules/pam_tacplus/libpam_tacplus.a ../modules/pam_unix/libpam_unix.a ../modules/pam_deny/libpam_deny.a(pam_deny.o)(.text+0x50): In function `pam_sm_open_sessio
Re: xorg 7.2 start problem
Peter Jeremy wrote: On 2007-May-23 11:06:46 +0300, Iulian M <[EMAIL PROTECTED]> wrote: On Wednesday 23 May 2007, Andriy Babiy wrote: Fatal server error: could not open default font 'fixed' On another thread the conclusion was that installing x11-fonts/font-alias solved the fixed font problem. I've found this problem on one system (the one where I thought the upgrade had gone the most cleanly). font-alias _is_ installed but most of my pcf.gz files are corrupt (20 bytes long). 'portupgrade -f' on my fonts is fixing this but I'm not exactly sure why it occurred to start with. Hey guys, [EMAIL PROTECTED]:~> uname -a FreeBSD shire.freebsdbrasil.com.br 7.0-CURRENT FreeBSD 7.0-CURRENT #11: Wed May 16 15:18:51 BRT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SHIRE i386 Here, the following resolved it for me: [EMAIL PROTECTED]:~> cd /usr/ports/x11-fonts/font-misc-misc [EMAIL PROTECTED]:~> make clean deinstall reinstall [EMAIL PROTECTED]:~> cd /usr/ports/x11-fonts/font-cursor-misc [EMAIL PROTECTED]:~> make clean deinstall reinstall And, finally: [EMAIL PROTECTED]:~> startx Done! :) -- Atenciosamente, Felippe de Meirelles Motta FreeBSD Brasil LTDA. http://www.freebsdbrasil.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg 7.2 start problem
* Peter Jeremy <[EMAIL PROTECTED]> [2007-05-24 21:40 +1000]: > I've found this problem on one system (the one where I thought the > upgrade had gone the most cleanly). font-alias _is_ installed but > most of my pcf.gz files are corrupt (20 bytes long). > > 'portupgrade -f' on my fonts is fixing this but I'm not exactly sure > why it occurred to start with. bdftopcf fails if it uses the old library from X11R6. The 20 bytes are the compressed empty output of the failing bdftopcf. Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test locale in C? All my tests fail.
Oliver Fromme wrote:
Artem Kuchin wrote:
I have a very stupid problem. I cannot convert to upper
or lower case using manually set locale (setlocale(..)).
A very simple program:
[...]
printf("IS UPPER ?: %d\n",isupper('?'));
printf("IS UPPER ?: %d\n",isupper('?'));
printf("IS LOWER ?: %d\n",islower('?'));
That's a common pitfall. Chars are signed by default on
FreeBSD, and the isupper() etc. function take an int type
argument. That means that characters >= 128 end up as
negative numbers, so they fail all isupper() and islower()
checks, and toupper()/tolower() don't touch them at all.
The solution is to typecast the constants to unsigned char
explicitly, like this: isupper((unsigned char) '?') etc.
Your program will work fine then.
My stupid. I should've noticed that. Thank you very much!
Issue closed.
--
Regards,
Artem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg 7.2 start problem
On 2007-May-23 11:06:46 +0300, Iulian M <[EMAIL PROTECTED]> wrote: >On Wednesday 23 May 2007, Andriy Babiy wrote: >> Fatal server error: >> could not open default font 'fixed' > >On another thread the conclusion was that installing x11-fonts/font-alias >solved the fixed font problem. I've found this problem on one system (the one where I thought the upgrade had gone the most cleanly). font-alias _is_ installed but most of my pcf.gz files are corrupt (20 bytes long). 'portupgrade -f' on my fonts is fixing this but I'm not exactly sure why it occurred to start with. -- Peter Jeremy pgpQxy0LPiiRS.pgp Description: PGP signature
Re: How to test locale in C? All my tests fail.
Artem Kuchin wrote:
> I have a very stupid problem. I cannot convert to upper
> or lower case using manually set locale (setlocale(..)).
>
> A very simple program:
> [...]
> printf("IS UPPER ?: %d\n",isupper('?'));
> printf("IS UPPER ?: %d\n",isupper('?'));
> printf("IS LOWER ?: %d\n",islower('?'));
> printf("IS LOWER ?: %d\n",islower('?'));
> printf("LOCALE %s\n",setlocale(LC_CTYPE,NULL));
> printf("1: TO UPPER %c TO LOWER %c\n",toupper('?'),tolower('?'));
> printf("1-0: TO UPPER %c TO LOWER %c\n",toupper('?'),tolower('?'));
> printf("2: TO UPPER %c TO LOWER %c\n",toupper('r'),tolower('R'));
> [...]
> IS UPPER ?: 0
> IS UPPER ?: 0
> IS LOWER ?: 0
> IS LOWER ?: 0
> LOCALE ru_RU.CP1251
> 1: TO UPPER ? TO LOWER ?
> 1-0: TO UPPER ? TO LOWER ?
> 2: TO UPPER R TO LOWER r
That's a common pitfall. Chars are signed by default on
FreeBSD, and the isupper() etc. function take an int type
argument. That means that characters >= 128 end up as
negative numbers, so they fail all isupper() and islower()
checks, and toupper()/tolower() don't touch them at all.
The solution is to typecast the constants to unsigned char
explicitly, like this: isupper((unsigned char) '?') etc.
Your program will work fine then.
Best regards
Oliver
PS: You should also #include
PPS: This is not a FreeBSD-specific pitfall. The ISO-C
standard does not specify the signedness of chars, and
most implementations (but not all) seem to prefer to
have chars signed by default. So, in order to write
portable programs, you always need to typecast if the
difference between signed and unsigned matters in your
application.
PPPS: I think follow-ups should go to the -standards
mailing list.
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"With sufficient thrust, pigs fly just fine. However, this
is not necessarily a good idea. It is hard to be sure where
they are going to land, and it could be dangerous sitting
under them as they fly overhead." -- RFC 1925
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test locale in C? All my tests fail.
Massimo Fusaro wrote:
From the setlocale(3) manual page:
... A locale argument of NULL causes setlocale() to return the
current locale. ...
Right. that why i first
call
setlocale(LC_CTYPE, "ru_RU.CP1251");
to set locale
and the call
setlocale(LC_CTYPE,NULL);
to check what locale is currently set.
I tried without call setlocale(LC_CTYPE,NULL);
- no difference.
--
Regards,
Artem
--
-max
2007/5/24, Artem Kuchin <[EMAIL PROTECTED]>:
Maybe it is the wrong list, but maybe someone can quickly
help me out.
I have a very stupid problem. I cannot convert to upper
or lower case using manually set locale (setlocale(..)).
A very simple program:
#include
#include
#include
main(){
char *b=setlocale(LC_CTYPE, "ru_RU.CP1251");
if (!b){
printf("FAILED! %d\n",errno);
}
else {
printf("OK: %s %d\n",b,errno);
printf("IS UPPER й: %d\n",isupper('й'));
printf("IS UPPER Й: %d\n",isupper('Й'));
printf("IS LOWER й: %d\n",islower('й'));
printf("IS LOWER Й: %d\n",islower('Й'));
printf("LOCALE %s\n",setlocale(LC_CTYPE,NULL));
printf("1: TO UPPER %c TO LOWER
%c\n",toupper('ж'),tolower('Ж')); printf("1-0: TO UPPER %c
TO LOWER %c\n",toupper('Я'),tolower('я')); printf("2: TO
UPPER %c TO LOWER %c\n",toupper('r'),tolower('R')); }
}
Output is always:
OK: ru_RU.CP1251 0
IS UPPER й: 0
IS UPPER Й: 0
IS LOWER й: 0
IS LOWER Й: 0
LOCALE ru_RU.CP1251
1: TO UPPER ж TO LOWER Ж
1-0: TO UPPER Я TO LOWER я
2: TO UPPER R TO LOWER r
й,ж,я - is lower case leters and
Й,Ж,Я - is upper case
As you see, it simply does not work at all.
It seems like the locale is "C" but as you see
setlocale returned ru_RU.CP1251
tested on 6.2, 5.4 and 4.10 - all the same.
What am i doing wrong?
(except posting in the wrong list ;)
--
Regards,
Artem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test locale in C? All my tests fail.
From the setlocale(3) manual page:
... A locale argument of NULL causes setlocale() to return the
current locale. ...
--
-max
2007/5/24, Artem Kuchin <[EMAIL PROTECTED]>:
Maybe it is the wrong list, but maybe someone can quickly
help me out.
I have a very stupid problem. I cannot convert to upper
or lower case using manually set locale (setlocale(..)).
A very simple program:
#include
#include
#include
main(){
char *b=setlocale(LC_CTYPE, "ru_RU.CP1251");
if (!b){
printf("FAILED! %d\n",errno);
}
else {
printf("OK: %s %d\n",b,errno);
printf("IS UPPER й: %d\n",isupper('й'));
printf("IS UPPER Й: %d\n",isupper('Й'));
printf("IS LOWER й: %d\n",islower('й'));
printf("IS LOWER Й: %d\n",islower('Й'));
printf("LOCALE %s\n",setlocale(LC_CTYPE,NULL));
printf("1: TO UPPER %c TO LOWER %c\n",toupper('ж'),tolower('Ж'));
printf("1-0: TO UPPER %c TO LOWER %c\n",toupper('Я'),tolower('я'));
printf("2: TO UPPER %c TO LOWER %c\n",toupper('r'),tolower('R'));
}
}
Output is always:
OK: ru_RU.CP1251 0
IS UPPER й: 0
IS UPPER Й: 0
IS LOWER й: 0
IS LOWER Й: 0
LOCALE ru_RU.CP1251
1: TO UPPER ж TO LOWER Ж
1-0: TO UPPER Я TO LOWER я
2: TO UPPER R TO LOWER r
й,ж,я - is lower case leters and
Й,Ж,Я - is upper case
As you see, it simply does not work at all.
It seems like the locale is "C" but as you see
setlocale returned ru_RU.CP1251
tested on 6.2, 5.4 and 4.10 - all the same.
What am i doing wrong?
(except posting in the wrong list ;)
--
Regards,
Artem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
Artem Kuchin wrote: > Ahh, well, i just forgot. Of course it is not for a long time > now. But anyhow, why locale in C does not work? And how 'so' lib > is selected for an executable? How OS selected so.5 or so.6 for a > executable file? During compile-time linking (when ld(1) is called), usually the newest version of the library is used (note that libfoo.so is usually a symlink to the newest libfoo.so.*). At runtime, the dynamic linker (rtld(1)) uses the same library version that was used during compilation. If you want a binary to use a different version, you have to recompile it. (Well, there are ways to trick the dynamic linker via libmap.conf and environment variables, but that will break if the libraries in question aren't 100% ABI compatible.) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Passwords are like underwear. You don't share them, you don't hang them on your monitor or under your keyboard, you don't email them, or put them on a web site, and you must change them very often. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to test locale in C? All my tests fail.
Maybe it is the wrong list, but maybe someone can quickly
help me out.
I have a very stupid problem. I cannot convert to upper
or lower case using manually set locale (setlocale(..)).
A very simple program:
#include
#include
#include
main(){
char *b=setlocale(LC_CTYPE, "ru_RU.CP1251");
if (!b){
printf("FAILED! %d\n",errno);
}
else {
printf("OK: %s %d\n",b,errno);
printf("IS UPPER й: %d\n",isupper('й'));
printf("IS UPPER Й: %d\n",isupper('Й'));
printf("IS LOWER й: %d\n",islower('й'));
printf("IS LOWER Й: %d\n",islower('Й'));
printf("LOCALE %s\n",setlocale(LC_CTYPE,NULL));
printf("1: TO UPPER %c TO LOWER %c\n",toupper('ж'),tolower('Ж'));
printf("1-0: TO UPPER %c TO LOWER %c\n",toupper('Я'),tolower('я'));
printf("2: TO UPPER %c TO LOWER %c\n",toupper('r'),tolower('R'));
}
}
Output is always:
OK: ru_RU.CP1251 0
IS UPPER й: 0
IS UPPER Й: 0
IS LOWER й: 0
IS LOWER Й: 0
LOCALE ru_RU.CP1251
1: TO UPPER ж TO LOWER Ж
1-0: TO UPPER Я TO LOWER я
2: TO UPPER R TO LOWER r
й,ж,я - is lower case leters and
Й,Ж,Я - is upper case
As you see, it simply does not work at all.
It seems like the locale is "C" but as you see
setlocale returned ru_RU.CP1251
tested on 6.2, 5.4 and 4.10 - all the same.
What am i doing wrong?
(except posting in the wrong list ;)
--
Regards,
Artem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
Karol Kwiatkowski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Artem Kuchin wrote: Karol Kwiatkowski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Artem Kuchin wrote: Stanislaw Halik wrote: On Thu, May 24, 2007, Artem Kuchin wrote: What i don't understand, is how the appropriate 'so' is selected? How freebsd known which so to load this libc.so.5 or this libc.so.6 [...snip...] But anyhow, why locale in C does not work? And how 'so' lib is selected for an executable? How OS selected so.5 or so.6 for a executable file? My understanding is, it is hardcoded into the executable during compilation/linking time. You can check linked libraries with ldd(1) command: $ ldd `which perl` /usr/bin/perl: libperl.so => /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so (0x2807c000) libm.so.5 => /lib/libm.so.5 (0x28192000) libcrypt.so.4 => /lib/libcrypt.so.4 (0x281a7000) libutil.so.7 => /lib/libutil.so.7 (0x281c) libc.so.7 => /lib/libc.so.7 (0x281cd000) Oh, hell... I just realized that i need to rebuild EVERYTHING in EVERY jail after this upgrade from 5 to 6. Even if something seem to work it does not mean it will not fail in some rare case. Still, does not explain why freshly compile locale test in C does not work. Weird. -- Regards, Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Artem Kuchin wrote: > Karol Kwiatkowski wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> Artem Kuchin wrote: >>> Stanislaw Halik wrote: On Thu, May 24, 2007, Artem Kuchin wrote: > What i don't understand, is how the appropriate 'so' > is selected? How freebsd known which so to load > this > libc.so.5 > or this > libc.so.6 [...snip...] > But anyhow, > why locale in C does not work? And how 'so' lib is selected for an > executable? How OS selected so.5 or so.6 for a executable file? My understanding is, it is hardcoded into the executable during compilation/linking time. You can check linked libraries with ldd(1) command: $ ldd `which perl` /usr/bin/perl: libperl.so => /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so (0x2807c000) libm.so.5 => /lib/libm.so.5 (0x28192000) libcrypt.so.4 => /lib/libcrypt.so.4 (0x281a7000) libutil.so.7 => /lib/libutil.so.7 (0x281c) libc.so.7 => /lib/libc.so.7 (0x281cd000) HTH, Karol - -- Karol Kwiatkowski OpenPGP 0x06E09309 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVVl5ezeoPAwGIYsRCCnBAJ4ttUXin+lSbiTR65EC4/XkeYa3sgCdH0eC EMri5q9OKSLQnlPLhhEZ1ug= =fe7i -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2-STABLE Hard Freeze while using RAID1 on Adaptec 1210SA
On Thu, May 24, 2007 at 01:11:38AM +0200, Gheorghe Ardelean wrote: > > Hi, > > I am trying to use two SATA II disks over an Adaptec 1210SA PCI SATA > Controller (based on SiI 3112 SATA150 chip). > > While trying to use the disks I get shortly the following message and the > system is hard freezing soon after that. > > May 14 15:47:32 noname kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry > left) LBA=238231007 > > If I move the HDD's in a computer with VIA SATA150 on board or nVIDIA > SATA150 the RAID system is working without problems with the same version > of FreeBSD. > > Are there any known problems with this Adaptec controller or is the > combination controller SATA150 and HDD SATA300 not well supported? > Is there a way to fix this? > > The system is installed on a 3rd disk (IDE). Hello, I had similar problems with 1210SA controller. As I know this controller is a little defective and it is not supported correctly by FreeBSD. There were a lot of discussions about issues with Adaptec 1210SA and SiI 3112- based controllers, but all of these discussions didn't give a solution. In other words I don't know how to solve this problem. I guess only the way is to throw it out of the window :( -- Kind Regards, Alexander Shikoff [EMAIL PROTECTED] Mob.: +380 67 946 31 49 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
Karol Kwiatkowski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Artem Kuchin wrote: Stanislaw Halik wrote: On Thu, May 24, 2007, Artem Kuchin wrote: What i don't understand, is how the appropriate 'so' is selected? How freebsd known which so to load this libc.so.5 or this libc.so.6 ? Did you recompile Perl after the last installworld? If not, do so. No i did not do it explicitelly. However, i think buildworl should do it, or it is not a part of the "world" anymore? It's not, for quite some time now: http://lists.freebsd.org/pipermail/freebsd-announce/2002-May/000823.html Ahh, well, i just forgot. Of course it is not for a long time now. But anyhow, why locale in C does not work? And how 'so' lib is selected for an executable? How OS selected so.5 or so.6 for a executable file? -- Regards, Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Artem Kuchin wrote: > Stanislaw Halik wrote: >> On Thu, May 24, 2007, Artem Kuchin wrote: >>> What i don't understand, is how the appropriate 'so' >>> is selected? How freebsd known which so to load >>> this >>> libc.so.5 >>> or this >>> libc.so.6 >>> ? >> >> Did you recompile Perl after the last installworld? If not, do so. > > No i did not do it explicitelly. However, i think buildworl should > do it, or it is not a part of the "world" anymore? It's not, for quite some time now: http://lists.freebsd.org/pipermail/freebsd-announce/2002-May/000823.html HTH, Karol - -- Karol Kwiatkowski OpenPGP 0x06E09309 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVUHxezeoPAwGIYsRCE3fAJsG4FkZLZOvBZNYuyXtKXq9NFvLCQCgjOrA dhZE9J1EBFrwfFBsGODhHHo= =qh2p -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg 7.2 start problem
On Wednesday 23 May 2007, Kris Kennaway wrote: > On Wed, May 23, 2007 at 11:06:46AM +0300, Iulian M wrote: > > > > Yep... you have to rebuild everything. Not to fix the error but just > > because you don't read other threads on the ML > > > > > > On another thread the conclusion was that installing x11-fonts/font-alias > > solved the fixed font problem. > > Speaking of not reading other threads, you might also look closer to > home ;) I admit i haven't read all the threads but when i had the "fixed font" problem i've read that installing font-alias solves the problem ... and it did. > > Adding font-alias would just be treating the next symptom, and then > you'll probably find that something else still doesn't work because it > is also missing. i know it's not that important but i like the idea of having to install only the apps i use. > > As I've said a *number* of times already (and as is mentioned in the > UPDATING instructions), install the x11/xorg port to obtain a complete > installation. > > Kris After 2 days of compiling on my laptop ... if i can avoid compiling anything i will :) .I still haven't updated kdevelop & kdesdk since they are already in /usr/local and still work after the upgrade ( maybe because of lib/compat )... anyway since they work they will stay like this until next kde update. If you want to be on the safe side you are right install x11/xorg ... but then again ... if you really want to be on the really safe side ... stick with -RELEASE ;-) And btw i'm experiencing some crashes/locks with the new xorg ... 6.9 used to run for weeks without problems ... 7.2 still has to reach 24h without a problem - but maybe more on a new thread if i'll have more info. -- Best Regards, Iulian Margarintescu http://www.erata.net [EMAIL PROTECTED] (spamassassin & pf & spamd all said it's OK to make it public ;-) ) Key ID: 0x03176E5CEDEFF7AB I prefer plain text email pgpH76xADb7Li.pgp Description: PGP signature
Re: xorg 7.2 start problem
>Hmm, I have the x11/xorg port, same problem "could not open default font >'fixed'" Oh, well. So now I have an X-less system, Don't mind so much myself, >but my other family members freaked out :( They thought the shell prompt was >an error message! You can try to install x11-fonts/font-alias port, this may fix the problem. --- With the best regards, Dmitry Kroupenier. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broken locale after upgrade to 6-STABEL from 5-STABLE
On Thu, May 24, 2007, Artem Kuchin wrote: >>> What i don't understand, is how the appropriate 'so' >>> is selected? How freebsd known which so to load >>> this >>> libc.so.5 >>> or this >>> libc.so.6 >>> ? >> Did you recompile Perl after the last installworld? If not, do so. > No i did not do it explicitelly. However, i think buildworl should > do it, or it is not a part of the "world" anymore? There's no Perl in the base system anymore; symlinking after a library bump leads to errors, as ABI has changed. -- Whenever you find that you are on the side of the majority, it is time to reform. -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
