Re: updating xorg-libraries 7.2 to 7.2.1
Stephen Montgomery-Smith wrote: > I think that the easiest way (i.e. least disruption) is to add to each > of the X11R6 scripts a test at their beginning to see if X11R6 is a > symlink to /usr/local, and have the scripts do nothing if this is the > case. Umm, no. The easiest way to fix this is in rc.subr, to prevent it from running scripts with the same name more than once. A fix for that problem is currently under discussion. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bug in BSD tar?
Steven Hartland wrote: > - Original Message - From: "Colin Percival" <[EMAIL PROTECTED]> >>> tar -xvzf test.tar.gz >>> tar: Ignoring unknown extended header keyword `SCHILY.dev' >>> tar: Ignoring unknown extended header keyword `SCHILY.ino' >>> tar: Ignoring unknown extended header keyword `SCHILY.nlink' >>> cantiquedeno\353l1_loop.wav >>> tar: Error exit delayed from previous errors >> >> This looks like fairly typical symptoms of gnutar being broken. What >> makes you think that the archive created by BSD tar was invalid? > > As a filename should have no bearing on what extended headers > are set. Why not? In this case, bsdtar is detecting that the file name contains non-7-bit-ascii characters and is emitting a pax header for that reason; and since it can't suppress the pax header entirely, it goes ahead and emits the "not vital but potentially useful" headers for the device #, inode #, number of links, and high precision timestamps. I still see no evidence that bsdtar is doing anything wrong. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On Monday 28 May 2007 13:35, Daniel O'Connor wrote: > > Yes, there is also a loader/pxeboot in the same directory. > > As kib@ told me, do not install this loader on your disk > > which may destroy your data. > > I see the binaries, I was thinking of trying one with a USB flash > boot disk, I'll unplug my actual disks for safety :) Alas I still get a BTX halted after replacing loader with one from that URL :( int=000d err= efl=00030002 eip=2aca eax=0900 ebx=55aa ecx= edx=0180 esi= edi= ebp=03f0 esp=03da cs=f000 ds=9e02 es=1400fs= gs= ss=9e02 cs:eip=2e 0f 01 16 1c 2c 0f 20-c0 0c 01 0f 22 c0 b8 28 00 8e d8 0f 20 c0 24 fe-0f 22 c0 eb 00 66 58 c3 ss:esp=02 9e 00 00 20 22 01 41-02 9e 24 72 0f 08 00 00 46 02 80 01 3a 07 10 00-01 00 00 00 00 14 00 00 BTX halted (ds might be 9e82, not sure, shot is blury..) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpZx6qfppQfS.pgp Description: PGP signature
Re: bug in BSD tar?
- Original Message - From: "Colin Percival" <[EMAIL PROTECTED]> expand it errors with the following: [log] tar -xvzf test.tar.gz tar: Ignoring unknown extended header keyword `SCHILY.dev' tar: Ignoring unknown extended header keyword `SCHILY.ino' tar: Ignoring unknown extended header keyword `SCHILY.nlink' cantiquedeno\353l1_loop.wav tar: Error exit delayed from previous errors [/log] This looks like fairly typical symptoms of gnutar being broken. What makes you think that the archive created by BSD tar was invalid? As a filename should have no bearing on what extended headers are set. Steve 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: bug in BSD tar?
Steven Hartland wrote: > When compressing files with specific filenames it appears that BSD > tar is creating invalid archives which when handed to gnutar to ^ > expand it errors with the following: > [log] > tar -xvzf test.tar.gz > tar: Ignoring unknown extended header keyword `SCHILY.dev' > tar: Ignoring unknown extended header keyword `SCHILY.ino' > tar: Ignoring unknown extended header keyword `SCHILY.nlink' > cantiquedeno\353l1_loop.wav > tar: Error exit delayed from previous errors > [/log] This looks like fairly typical symptoms of gnutar being broken. What makes you think that the archive created by BSD tar was invalid? Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bug in BSD tar?
When compressing files with specific filenames it appears that BSD tar is creating invalid archives which when handed to gnutar to expand it errors with the following: [log] tar -xvzf test.tar.gz tar: Ignoring unknown extended header keyword `SCHILY.dev' tar: Ignoring unknown extended header keyword `SCHILY.ino' tar: Ignoring unknown extended header keyword `SCHILY.nlink' cantiquedeno\353l1_loop.wav tar: Error exit delayed from previous errors [/log] This archive contains just a single file with no special attributes yet BSD seems to be doing something strange due to the filename only. The following is the out of the filename using ls and find: [EMAIL PROTECTED]:music> ls -l cantiquede* -rw-r--r-- 1 user group 1766066 Feb 8 20:54 cantiquedeno?l1_loop.wav [EMAIL PROTECTED]:music> find . -name can\* ./cantiquedenoël1_loop.wav I've tested creating the tar with gtar and all is well when expanded so I can only conclude at this point that BSD is broken in some way by this strange filename. tar --version bsdtar 1.01.020, libarchive 1.02.006 Copyright (C) 2003-2004 Tim Kientzle Steve 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: Xorg 7.2 upgrade - success!
Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote (28/5/07): After that, I created a new xorg.conf (using X -configure) and added my settings to it (keyboard language). Even xdm works (it still doesn't look good, but it never has)! Try out my Xresources, Xsetup_0, and Xstartup_0 if you don't like xdm as it is... If you have x11/xscreensaver installed it'll look great! [EMAIL PROTECTED] ~]% cat /usr/local/lib/X11/xdm/Xresources ! $Xorg: Xresources,v 1.3 2000/08/17 19:54:17 cpqbld Exp $ ! ! ! ! ! $XFree86: xc/programs/xdm/config/Xres.cpp,v 1.6 2003/01/04 03:11:31 dawes Exp $ ! xlogin*allowRootLogin: false xlogin*login.translations: #override \ CtrlR: abort-display()\n\ F1: set-session-argument(failsafe) finish-field()\n\ F2: set-session-argument(twm) finish-field()\n\ F3: set-session-argument(fluxbox) finish-field()\n\ F12: set-session-argument(shutdown)finish-field()\n\ Delete: delete-character()\n\ Left: move-backward-character()\n\ Right: move-forward-character()\n\ Home: move-to-begining()\n\ End: move-to-end()\n\ CtrlKP_Enter: set-session-argument(failsafe) finish-field()\n\ KP_Enter: set-session-argument() finish-field()\n\ CtrlReturn: set-session-argument(failsafe) finish-field()\n\ Return: set-session-argument() finish-field() *allowRootLogin:false xlogin*geometry: 310x200+0-0 xlogin*greeting: Welcome to Hydra xlogin*namePrompt: Login: xlogin*fail: Login incorrect xlogin*greetFont: -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso8859-1 xlogin*font: -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso8859-1 xlogin*promptFont: -adobe-helvetica-bold-r-normal--18-180-75-75-p-103-iso8859-1 xlogin*failFont: -adobe-helvetica-bold-r-normal--18-180-75-75-p-103-iso8859-1 xlogin*greetFont: -adobe-helvetica-bold-o-normal--17-120-100-100-p-92-iso8859-1 xlogin*font: -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 xlogin*promptFont: -adobe-helvetica-bold-r-normal--12-120-75-75-p-70-iso8859-1 xlogin*failFont: -adobe-helvetica-bold-o-normal--14-140-75-75-p-82-iso8859-1 xlogin*borderWidth: 1 xlogin*frameWidth: 1 xlogin*innerFramesWidth: 1 xlogin*shdColor: green xlogin*hiColor: green xlogin*background: black xlogin*foreground: green xlogin*greetColor: green xlogin*failColor: red *Foreground: green *Background: #f0 xlogin*useShape: true xlogin*logoPadding: 10 !EOF !! [EMAIL PROTECTED] ~]% cat /usr/local/lib/X11/xdm/Xstartup_0 killall xmatrix [EMAIL PROTECTED] ~]% cat /usr/local/lib/X11/xdm/Xsetup_0 #!/bin/sh # $Xorg: Xsetup_0,v 1.3 2000/08/17 19:54:17 cpqbld Exp $ #xconsole -geometry 480x130-0-0 -daemon -notify -verbose -fn fixed -exitOnFail /usr/local/bin/xscreensaver-hacks/xmatrix -root & #/usr/X11R6/lib/X11/xdm/chooser [EMAIL PROTECTED] ~]% Sorry, I know I'm sad... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Some local rc scripts running twice
> Date: Sun, 27 May 2007 16:34:19 -0300 > From: Duane Whitty <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > Hi Pascal, > > Much thanks! > > On Sunday, 27 May 2007 at 14:11:13 +0200, Pascal Hofstee wrote: > > On Sun, 2007-05-27 at 03:48 -0300, Duane Whitty wrote: > > > Has anyone else encountered local rc scripts running > > > twice? I thought I saw something about this on one > > > of the @freebsd.org lists but my search efforts haven't > > > located it yet. > > > > In assuming "local rc scripts" means anything installed by ports ... i > > am assuming you installed a fresh Xorg-7.2 and now at some point ended > > up with the /usr/X11R6 -> /usr/local symlink. > > > > If the above assumption holds true ... did you run the mergebase.sh > > script as suggested in /usr/ports/UPDATING ? > > > > The above assumptions are correct and mergebase.sh did run. > > > Most significantly .. this script adds the following entry to > > your /etc/rc.conf > > > > local_startup="/usr/local/etc/rc.d" > > > > This was the problem. Adding this to my /etc/rc.conf manually > fixed everything up for me. Thanks! > > > > > The default entry in /etc/defaults/rc.conf still > > references /usr/X1R6/etc/rc.d as well ... since the latter is now a > > symlink to the former, both rc.d-paths contain the same scripts. > > > > If your rc.conf doesn't contain the aforementioned entry, that would > > explain why local rc-scripts are started twice. > > > > Yeah, that does it explain it. The mergebase.sh script failed > unfortunately and I needed to take manual steps to complete > the upgrade process. > > When the script failed due to conflicting files I deleted the > files that were listed, re-ran the script, got the same conflicts, > and then created the symlink myself. Unfortunately, the rc.conf > entry didn't get added as well. I am left wondering if other > things that were supposed to happen did not happen. > > When operator error complicates matters, as it has in this case, > no script can deal with all possible scenarios. So, to all the > people who worked on making this upgrade happen, please don't > take this as a criticism of the script or upgrade process If ./etc is mounted read-only, the file is not updated and I got no warning about the failure from the script. As a result I need to hand-edit both rc.conf and periodic to fix stuff properly. I don't suspect having a RO /etc is all that common, but I am sure others will hit this, too. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpyD3NrahhSH.pgp Description: PGP signature
Re: debuging a hung kernel
Redirecting from @net to @stable. Please, remove @net from future mails. On Monday 28 May 2007 11:54, Robert Watson wrote: > On Mon, 28 May 2007, Julian Elischer wrote: > > Nikos Vassiliadis wrote: > >> On Monday 28 May 2007 10:57, Julian Elischer wrote: > >>> Nikos Vassiliadis wrote: > On Tuesday 22 May 2007 10:06, I wrote: > > Hello everybody, > > > > I just managed to lock my box and I want to report it > >>> > >>> define "lock"? > >>> > >>> Does it still respond to on the keyboard? > >> > >> No, but I was trying to break to the debugger with > >> myself. I assume that it is > >> equivalent to the combination you wrote, or not? > >> > >>> (Assuming you have the debugger in your kernel?). > >> > >> Yes, I have included my kernel configuration, see bellow. > >> > >>> Does it still ping? > >> > >> no, ARP does not work as well. > > > > nasty.. do you have IPMI? sometimes that allows you to generate an NMI > > that could theoretically be made to drop to the debugger. I have a Dell PowerEdge 750 sitting at work, which I think has IPMI. I'll be able to try a few things next week, since I will be off work for this week. > > > > I've not had success with that but I have heard others have. > > An increase number of server motherboards have an NMI button on the > motherboard, possibly exposed outside the case, but generally not. > > I've not tested it in over a year, but a few years ago I added an > MP_WATCHDOG kernel option that causes one of the CPUs in an SMP system > to become a dedicated watchdog CPU, checking to see if the OS is alive > enough to process timer tickets. If a counter isn't updated, it > generates an NMI to the debugger from the watchdog CPU. The idea here > is that, as the number of CPUs increases, the cost of dedicating a CPU > for debugging stuff gets lower. However, there have been quite a few > scheduler changes in the last few years, and it's possible that the > watchdog no longer properly excludes other work from being scheduled, > and that further work is required. In particular, I believe it relies > on 4BSD's "pull" scheduling model and a lack of per-CPU workers, so the > mechanism may require some rethinking. Unfortunately, I have not an SMP system available. Is there a mechanism which I can use to schedule a break to the debugger after n seconds or events? I am looking if ichwd(4) can help, though that needs investigation since I have not used watchdog facilities before. Thanks Julian & Robert. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Change in memory tracking in recent 6-STABLE?
On 2007-May-28 11:29:05 +0200, Ulrich Spoerlein <[EMAIL PROTECTED]> wrote: >I'm using symon to monitor memory usage among several FreeBSD machines. >After updating to a recent 6-STABLE, the amount of memory no longer adds >up to the total physical memory. The "inactive" counter is way too >small. As well as "active", "inactive" and "free", there is "cache", "wired" and "buffers". Check the following sysctls: vfs.bufspace (bytes) vm.stats.vm.v_active_count (pages) vm.stats.vm.v_inactive_count (pages) vm.stats.vm.v_wire_count (pages) vm.stats.vm.v_cache_count (pages) vm.stats.vm.v_free_count (pages) -- Peter Jeremy pgpk2DiaJSXDl.pgp Description: PGP signature
Change in memory tracking in recent 6-STABLE?
Hi there, I'm using symon to monitor memory usage among several FreeBSD machines. After updating to a recent 6-STABLE, the amount of memory no longer adds up to the total physical memory. The "inactive" counter is way too small. Which recent changes could have caused this? Is it a bug in symon or in FreeBSD? An example of the difference can be found here: http://coyote.dnsalias.net/memory.png Ulrich Spoerlein -- "The trouble with the dictionary is you have to know how the word is spelled before you can look it up to see how it is spelled." -- Will Cuppy ___ 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 2007-May-24 16:19:07 -0400, Kris Kennaway <[EMAIL PROTECTED]> wrote: >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. Looking closer, I was wrong about it being a clean upgrade in my case. The ports INDEX and INDEX.db (though not the ports tree) would have been "corrupted" (by my regular ports tree update) partway through the portupgrade. I suspect it can be put down to operator error but can provide my upgrade logs if you want to investigate. -- Peter Jeremy pgpD5wNF0iUZV.pgp Description: PGP signature
Xorg 7.2 upgrade - success!
Hello, Just a quick-ish note to thank everyone involved in making the Xorg upgrade process: thank you all! I just upgraded a ThinkPad T41 (running 6.2-stable / i386 from early april) following the upgrade process in /usr/ports/UPDATING. The only "trick" I had to use was this (which I found on the -x11 mailinglist): mkdir /usr/local/oldX11 mv /usr/X11R6/* /usr/local/oldX11/ before running mergebase.sh After that, I created a new xorg.conf (using X -configure) and added my settings to it (keyboard language). Even xdm works (it still doesn't look good, but it never has)! Again, thanks for all the hard work! -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: updating xorg-libraries 7.2 to 7.2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Stephen Montgomery-Smith wrote: > Also, the last change you propose vis a vis man pages, is that actually > necessary - I would have thought that the overhead in searching both > local and X11R6 would be fairly negligable. Hence my description of it as "trivial". Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGWoZA8Mjk52CukIwRCKTxAKCQrZpUXVl7AjdfBhvypccSJ3/SwACaAziQ ChOdO/g+rpwqUDHTluC5Qgw= =0UsD -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]"
