Re: can't mount root after upgrade to RELENG_6
On Sunday 25 December 2005 21:37, David Syphers wrote: > yggdrasil> cat /etc/fstab > # DeviceMountpoint FStype Options Dump > Pass# /dev/ad0s1b noneswapsw 0 > 0 /dev/ad0s1a / ufs rw 1 Just to humor us, can you first mount root then the swap device? So swap those entries. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with groff in FreeBSD 6.0 buildworld
On Friday 23 December 2005 20:54, Telegin Gennady wrote: > /usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/ >src/preproc/grn/main.cpp:692: error: expected primary-expression before > '<'token > /usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/ >src/preproc/grn/main.cpp:694: error: expected primary-expression before '>' > token > Can you paste line 690-700. This looks like a cvs merge conflict to me. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfilter upgrade issue
On Friday 23 December 2005 14:51, Koen Martens wrote: > Melvyn Sopacua wrote: > >On Friday 23 December 2005 11:12, Koen Martens wrote: > >>Just a smallish issue with ipfilter and upgrading from 5.4 to 6-STABLE. > >>The ipfilter implementation in the 6-STABLE kernel errs on the commands > >>sent by the 5.4 ipf binary. This can be an issue when you are upgrading > >>remotely without serial console and you have IPFILTER_DEFAULT_BLOCK > >>enabled: after rebooting in the 6-STABLE kernel no firewall rules will > >>be loaded and you cannot access the box anymore to make installworld.. > > > >Just wondering - is COMPAT5X in the kernel? > > Well, COMPAT_FREEBSD5 is.. Sounds like a note for UPDATING then :) -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfilter upgrade issue
On Friday 23 December 2005 11:12, Koen Martens wrote: > Just a smallish issue with ipfilter and upgrading from 5.4 to 6-STABLE. > The ipfilter implementation in the 6-STABLE kernel errs on the commands > sent by the 5.4 ipf binary. This can be an issue when you are upgrading > remotely without serial console and you have IPFILTER_DEFAULT_BLOCK > enabled: after rebooting in the 6-STABLE kernel no firewall rules will > be loaded and you cannot access the box anymore to make installworld.. Just wondering - is COMPAT5X in the kernel? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lsof on 6.0
On Thursday 22 December 2005 16:27, Danny Braniss wrote: > > > > Do you have a mount which is a symlink? > > > > > > no, but many nfs. > > > minbari> mount > > > 132.65.16.100:/d/6 on / (nfs) > Breakpoint 1 at 0x402779: file dmnt.c, line 159. > (gdb) run > Starting program: > /home/pobj/r+d/ports/sysutils/lsof/work/lsof_4.77A.freebsd/ls of > lsof: WARNING: access /root/.lsof_shuttle-3: No such file or directory > lsof: WARNING: can't open /root/.lsof_shuttle-3: Read-only file system > > Breakpoint 1, dev2udev (c=0xe) at dmnt.c:159 > 159 if (ln != dn) > (gdb) print sr > $1 = -1 > (gdb) print ln > $2 = 0x525140 "132.65.16.100:/d/8" > (gdb) print dn > $3 = 0x525140 "132.65.16.100:/d/8" As I figured, statsafely (which wraps around stat(2)) returns -1 on your nfs mount, therefore ss never gets set. I've got no idea what the "user device random seed" is needed for, so I suggest you file a pr with the above info. Additionally, you can try the following patch to see why exactly the stat(2) call fails: --- dmnt.c.orig Mon Oct 3 15:22:52 2005 +++ dmnt.c Thu Dec 22 16:51:23 2005 @@ -163,6 +163,9 @@ dn = (char *)NULL; if (sr) continue; + else + (void)fprintf(stderr, "%s: cannot stat %s: %s\n", Pn, ln, strerror(errno)); + ss = 1; s = (u_int)sb.st_ino ^ (u_int)sb.st_rdev; break; -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lsof on 6.0
On Thursday 22 December 2005 14:51, Danny Braniss wrote: > > On Thursday 22 December 2005 12:36, Danny Braniss wrote: > > > > On Thu, 22 Dec 2005 10:12:17 +0200 > > > > > > > > Danny Braniss <[EMAIL PROTECTED]> wrote: > > > > > i keep getting: > > > > > lsof: can't determine user device random seed. > > > > > is it only me? > > > > > > > > both as a normal user and as root. > > > > I don't see the message you are referring to. > > > > > > either root, or just a mere mortal, just typing lsof, no arguments: > > > > > > shuttle-3> lsof > > > lsof: can't determine user device random seed. > > > > Do you have a mount which is a symlink? > > no, but many nfs. > minbari> mount > 132.65.16.100:/d/6 on / (nfs) nfs mounted root. I think that's the problem. If you can compile as follows: env CFLAGS='-g -pipe' STRIP= make install then run: gdb /usr/local/sbin/lsof At gdb: (gdb) break dmnt.c:159 (gdb) run When breaking: (gdb) print sr (gdb) print ln (gdb) print dn -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lsof on 6.0
On Thursday 22 December 2005 12:36, Danny Braniss wrote: > > On Thu, 22 Dec 2005 10:12:17 +0200 > > > > Danny Braniss <[EMAIL PROTECTED]> wrote: > > > i keep getting: > > > lsof: can't determine user device random seed. > > > is it only me? > > both as a normal user and as root. > > I don't see the message you are referring to. > > either root, or just a mere mortal, just typing lsof, no arguments: > > shuttle-3> lsof > lsof: can't determine user device random seed. Do you have a mount which is a symlink? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em bad performance
On Wednesday 21 December 2005 17:55, Danny Braniss wrote: > this particular mb, intel sr1435vp2, has 2 ethernets, > one is an Intel '82547EI Gigabit Ethernet Controller', the other is > a Marvell (which seems that the driver is around the corner). > > the em performance under 6.0-stable is half of any other box i have, > and a similar mb running linux gives about 1GB, so > > Q: any ideas what can be wrong? With or without polling. Seen reports of polling enabled drivers without polling enabled are very slow. According to polling(4), em is polling capable. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mplayer-plugin/firefox/mozilla and pthread_testcancel (Was: Re: advice please)
On Wednesday 21 December 2005 15:29, Daniel Eischen wrote: > My apologies. Your previous email sounded like you had built > ports on 5.x and then upgraded some of them on 6.x Nps. I kept the old /usr/local around as /stable/usr/local to copy over configs and apache's webroot, but I don't see how that could've interfered, as I didn't add it to my PATH or anything fishy like that. In fact, I did ldd -a /usr/local/bin/mplayer|grep pthread and it only showed libpthread.so.2. > You might want to check /etc/libmap.conf just to make sure > you don't have anything mapped to libpthread.so.1. all .2 > > it's an error in mplayer-plugin, unless you tell me it works for you, > > then the only thing that makes sense is the use of nvidia-driver. > > That has been a problem in the past, but I thought they released > a newer driver that works correctly with libpthread and libthr. Latest of everything. Portstree last updated Dec 17. Recompiled mplayer without WITH_NVIDIA didn't make a difference. It just doesn't get outof the loop in PlayNode(), but I'm not farmiliar with the conditions mentioned therein. Just trying to figure out if this is a local problem, pthreads problem or that the port is broken (with certain combinations). -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mplayer-plugin/firefox/mozilla and pthread_testcancel (Was: Re: advice please)
On Wednesday 21 December 2005 14:57, Daniel Eischen wrote: > On Wed, 21 Dec 2005, Melvyn Sopacua wrote: > > On Wednesday 21 December 2005 00:51, Daniel Eischen wrote: > > > On Tue, 20 Dec 2005, Melvyn Sopacua wrote: > > > > [Switching to Thread 0x8bce400 (LWP 100139)] > > > > 0x28a80952 in pthread_testcancel () from /usr/lib/libpthread.so.2 > > > > (gdb) where > > > > #0 0x28a80952 in pthread_testcancel () from /usr/lib/libpthread.so.2 > > > > #1 0x2a17f52a in playNode () > > > > from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so > > > > #2 0x2a181a1c in playPlaylist () > > > > from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so > > > > #3 0x28a722f9 in pthread_create () from /usr/lib/libpthread.so.2 > > > > #4 0x28b1f367 in _ctx_start () from /lib/libc.so.6 > > > > > > You've probably got things linked to two different versions of > > > libpthread. Please see /usr/ports/UPDATING, section 20050722. > > > > It's a clean install (well, 5.x to a new slice, then recompiled after > > boot). > > Please read the UPDATING section. You have to rebuild all your > ports now that you are using 6.x. You can't just upgrade firefox > and mplayer plugin. I didn't. I built all ports from scratch or used 6-stable packages. I think it's an error in mplayer-plugin, unless you tell me it works for you, then the only thing that makes sense is the use of nvidia-driver. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mplayer-plugin/firefox/mozilla and pthread_testcancel (Was: Re: advice please)
On Wednesday 21 December 2005 02:08, Melvyn Sopacua wrote:
> On Wednesday 21 December 2005 00:51, Daniel Eischen wrote:
> > On Tue, 20 Dec 2005, Melvyn Sopacua wrote:
> Seems like an error in the plugin though.
Source directories
searched: /work/usr/ports/www/mplayer-plugin/work/mplayerplug-in:$cdir:$cwd
(gdb) where
#0 0x28a808ad in pthread_testcancel () from /usr/lib/libpthread.so.2
#1 0x2a1d40d2 in playNode (local_td=0x8b7ed00, local_list=0x8dad000,
local_url=0xbf1f5770
"http://movies.apple.com/movies/wb/v_for_vendetta/v_for_vendetta-tlr2_h480.mov";,
local_mmsstream=0, usefps=0xbf1f5754, nomouseinput=0xbf1f5750,
maybeplaylist=0xbf1f574c)
at Source/plugin-threads.cpp:765
Source/plugin-thread.cpp/756:
while (1) {
It never reaches a condition to break outof that and that's quite a loop.
mplayer isn't even there anymore...
--
Melvyn Sopacua
[EMAIL PROTECTED]
FreeBSD 6.0-STABLE
Qt: 3.3.5
KDE: 3.4.3
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mplayer-plugin/firefox/mozilla and pthread_testcancel (Was: Re: advice please)
On Wednesday 21 December 2005 00:51, Daniel Eischen wrote: > On Tue, 20 Dec 2005, Melvyn Sopacua wrote: > > [Switching to Thread 0x8bce400 (LWP 100139)] > > 0x28a80952 in pthread_testcancel () from /usr/lib/libpthread.so.2 > > (gdb) where > > #0 0x28a80952 in pthread_testcancel () from /usr/lib/libpthread.so.2 > > #1 0x2a17f52a in playNode () > > from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so > > #2 0x2a181a1c in playPlaylist () > > from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so > > #3 0x28a722f9 in pthread_create () from /usr/lib/libpthread.so.2 > > #4 0x28b1f367 in _ctx_start () from /lib/libc.so.6 > > You've probably got things linked to two different versions of > libpthread. Please see /usr/ports/UPDATING, section 20050722. It's a clean install (well, 5.x to a new slice, then recompiled after boot). But: cat /var/db/pkg/compat5x-i386-5.4.0.8/+REQUIRED_BY mplayer-0.99.7_7 nvidia-driver-1.0.8174 opera-8.51.20051114 So, recompiled. gdb looks a bit different, but the problem is the same. 0x28a8135f in pthread_testcancel () from /usr/lib/libpthread.so.2 (gdb) where #0 0x28a8135f in pthread_testcancel () from /usr/lib/libpthread.so.2 #1 0x28a79d80 in pthread_mutexattr_init () from /usr/lib/libpthread.so.2 #2 0x in ?? () It's spinning an endless loop, so depending on when you attach or continue and send a stop signal, output is different: 0x2a1cd572 in playNode () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so (gdb) where #0 0x2a1cd572 in playNode () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #1 0x2a1cfa1c in playPlaylist () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #2 0x28a722f9 in pthread_create () from /usr/lib/libpthread.so.2 #3 0x28b1f367 in _ctx_start () from /lib/libc.so.6 (gdb) where #0 0x2a1b3138 in ?? () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #1 0x2a1cd525 in playNode () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #2 0x2a1cfa1c in playPlaylist () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #3 0x28a722f9 in pthread_create () from /usr/lib/libpthread.so.2 #4 0x28b1f367 in _ctx_start () from /lib/libc.so.6 Going to recompile with debug symbols and see if that makes more sense. Seems like an error in the plugin though. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mplayer-plugin/firefox/mozilla and pthread_testcancel (Was: Re: advice please)
On Tuesday 20 December 2005 23:20, dick hoogendijk wrote: > On Tue, 20 Dec 2005 22:46:30 +0100 > > Melvyn Sopacua <[EMAIL PROTECTED]> wrote: > > On Tuesday 20 December 2005 22:01, dick hoogendijk wrote: > > > On Tue, 20 Dec 2005 21:49:21 +0100 > > > > > > Melvyn Sopacua <[EMAIL PROTECTED]> wrote: > > > > On Tuesday 20 December 2005 21:36, dick hoogendijk wrote: > > > > > I used to be able to play (windows) mplayer2 files and *.mov > > > > > files with my native mozilla browser and mplayerplug-in > > > > > installed. Lately that does not work anymore. Mozilla just > > > > > crashes, firefox starts up the mplayerplug-in and than stops > > > > > (hangs). > > > > > > > > Did this start after upgrading firefox to 1.5? > > > > Related: > > > > does: > > > > find /usr/X11R6/include/firefox /usr/X11R6/include/mozilla -type > > > > f \ -print |xargs grep nsPluginThread > > > > > > > > yield any results? > > > > > > I can't remember if the firefox upgrade was related. I _do_ upgrade > > > both browsers if portupgrade says there is a newer version. I do > > > have the latest firefox installed also. > > > > > > The results for the above find command: > > > > > > /usr/X11R6/include/mozilla/oji/nsIThreadManager.h:typedef struct > > > _nsPluginThread > > > nsPluginThread; /usr/X11R6/include/mozilla/oji/nsIThreadManager.h: > > > GetCurrentThread(nsPluginThread* *threadID) = > > > 0; /usr/X11R6/include/mozilla/oji/nsJVMManager.h: > > > GetCurrentThread(nsPluginThread* *threadID); > > > > Hmm, so Mozilla still provides compatibility for oji java plugins, > > where firefox doesn't. > > I just took a quick look at mplayerplugin source and can't find any > > references to PRThread. The plugin uses the provided top-level > > interfaces. Did you recompile the plugin? > > I recompiled mozilla, firefox and the plugin I recompiled a couple of > times. To no use. Mozilla just crashes, firefox shows the > "plugin-window" and does nothing. I never used the option "without-gui" > btw. > > > I just installed it and it doesn't really work for me (opens a new > > window iso playing in the designated space, probably because I didn't > > compile mplayer using WITHOUT_GUI), but doesn't crash anything either. > > I tried the apple movie trailers. > > Yeah, only difference it that when I try to open an movie trailer, > mozilla coredumps and firefox stops with a blank plugin-window. Hope > that somebody knows how to solve this. I liked mplayerplug-in very > much. It seems the only way to have some multimedia with > mozilla/firefox. Plus, it *used* to work ;-( Well, I know now that my mplayer/.config was the cause of it not playing in it's own space. I used vo=gl2,xv. xv is the one that plays in the designated space. However, I've got problems too, if I use the stop command or go to another page while the plugin is still loaded - gdb shows: Url: http://www.apple.com/trailers/fox/x3/ Action: click one of the HD teasers then click stop: [Switching to Thread 0x8bce400 (LWP 100139)] 0x28a80952 in pthread_testcancel () from /usr/lib/libpthread.so.2 (gdb) where #0 0x28a80952 in pthread_testcancel () from /usr/lib/libpthread.so.2 #1 0x2a17f52a in playNode () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #2 0x2a181a1c in playPlaylist () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #3 0x28a722f9 in pthread_create () from /usr/lib/libpthread.so.2 #4 0x28b1f367 in _ctx_start () from /lib/libc.so.6 Url: http://www.apple.com/trailers/fox/x3/ Action: click medium on the 'normal' trailers, play it, stop if you want, then click backbutton: [Switching to Thread 0x8901800 (LWP 100094)] 0x28a822bb in __error () from /usr/lib/libpthread.so.2 (gdb) where #0 0x28a822bb in __error () from /usr/lib/libpthread.so.2 #1 0x28a80905 in pthread_testcancel () from /usr/lib/libpthread.so.2 #2 0x2a17f52a in playNode () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #3 0x2a181a1c in playPlaylist () from /usr/X11R6/lib/browser_plugins/mplayerplug-in-qt.so #4 0x28a722f9 in pthread_create () from /usr/lib/libpthread.so.2 #5 0x28b1f367 in _ctx_start () from /lib/libc.so.6 -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: advice please
On Tuesday 20 December 2005 22:01, dick hoogendijk wrote: > On Tue, 20 Dec 2005 21:49:21 +0100 > > Melvyn Sopacua <[EMAIL PROTECTED]> wrote: > > On Tuesday 20 December 2005 21:36, dick hoogendijk wrote: > > > I used to be able to play (windows) mplayer2 files and *.mov files > > > with my native mozilla browser and mplayerplug-in installed. Lately > > > that does not work anymore. Mozilla just crashes, firefox starts up > > > the mplayerplug-in and than stops (hangs). > > > > Did this start after upgrading firefox to 1.5? > > Related: > > does: > > find /usr/X11R6/include/firefox /usr/X11R6/include/mozilla -type f \ > > -print |xargs grep nsPluginThread > > > > yield any results? > > I can't remember if the firefox upgrade was related. I _do_ upgrade > both browsers if portupgrade says there is a newer version. I do have > the latest firefox installed also. > > The results for the above find command: > > /usr/X11R6/include/mozilla/oji/nsIThreadManager.h:typedef struct > _nsPluginThread > nsPluginThread; /usr/X11R6/include/mozilla/oji/nsIThreadManager.h: > GetCurrentThread(nsPluginThread* *threadID) = > 0; /usr/X11R6/include/mozilla/oji/nsJVMManager.h: > GetCurrentThread(nsPluginThread* *threadID); Hmm, so Mozilla still provides compatibility for oji java plugins, where firefox doesn't. I just took a quick look at mplayerplugin source and can't find any references to PRThread. The plugin uses the provided top-level interfaces. Did you recompile the plugin? I just installed it and it doesn't really work for me (opens a new window iso playing in the designated space, probably because I didn't compile mplayer using WITHOUT_GUI), but doesn't crash anything either. I tried the apple movie trailers. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: advice please
On Tuesday 20 December 2005 21:36, dick hoogendijk wrote: > I used to be able to play (windows) mplayer2 files and *.mov files with > my native mozilla browser and mplayerplug-in installed. Lately that > does not work anymore. Mozilla just crashes, firefox starts up the > mplayerplug-in and than stops (hangs). Did this start after upgrading firefox to 1.5? Related: does: find /usr/X11R6/include/firefox /usr/X11R6/include/mozilla -type f \ -print |xargs grep nsPluginThread yield any results? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports security branch
On Tuesday 20 December 2005 13:26, rihad wrote: > Imagine: Foo 1.2.3 that > was current at the time of FreeBSD 6.0 release gets a severe vuln after > some time. Some admins upgrade to the latest and greatest Foo 1.2.9, > others to Foo 1.2.7 (probably with not recently updated ports tree)... If 1.2.7 is secure, there is no problem. If 1.2.7 is not, portaudit will not let you upgrade. It seems to me, you need to farmiliarize yourself first with the mechanisms in place already, before shooting it. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports security branch
On Tuesday 20 December 2005 12:39, Marwan Burelle wrote: > The point is not that this is always true, but that you have to handle > those kinds of problems if you want to maintain a security branch for > ports. The point is, that it is irrelevant. Ports are independant of the base system. There is no need for a security branch of the ports tree. The ports that rely on specifics in the base system, handle it themselves via BROKEN, FreeBSD_version and friends. The ports tree is only tagged for a specific release, so that release cdroms can be made. The only thing that makes sense is pre-compiled packages being updated for security branches of the base system - but, that is only worth-while if there's a large enough userbase that has an /etc/make.conf without NO_ flags. Since for example I have no need for Kerberos, I cannot use the FreeBSD provided packages for the ones that make sense, as they all link libgssapi (subversion pulls it in through www/neon, smbclient because of ports/90238 and thus kde*). -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports security branch
On Tuesday 20 December 2005 12:03, Marwan Burelle wrote: > Relying on the maintainer work is a good starting point, you may trust > him for doing only the needed updates for those ports that requier > security concerns. But even here, major updates of widely used libs > imply rebuild of most of the ports, even when no security issue > arises. No it doesn't. Only with static linking or when interfaces changed, which is not always the case. The fact that the gnome project is fond of changing library versions with every release doesn't mean there aren't sane projects. Typically security patches do not update library versions, allthough it is possible if the interface is insecure by design. Example: freetype was updated wc -l /var/db/pkg/freetype2-2.1.10_2/+REQUIRED_BY 111 /var/db/pkg/freetype2-2.1.10_2/+REQUIRED_BY Not a single port rebuilt, 111 packages re-packed, but that's it. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports security branch
On Tuesday 20 December 2005 11:49, Yann Golanski wrote: > Quoth Melvyn Sopacua on Tue, Dec 20, 2005 at 11:43:55 +0100 > > > I had one that was safe to run in cron (in fact it ran in > > periodic/daily), but uses a cvs tree of ports, not cvsup to save > > time[1]. I lost it with a disk crash, but was going to recreate it > > anyway, might as well do it now if people are interested. > > Yeah, I'm interested. > > How did you deal with ports doing a "make config" before updating?... > That was the crunch for me -- hence lots of portupgrade hanging. Hmm, not sure why that's an issue. Maybe because I set PATH in my script? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports security branch
On Tuesday 20 December 2005 11:18, rihad wrote: > Yann Golanski wrote: > > Quoth rihad on Tue, Dec 20, 2005 at 10:25:59 +0400 > > > >>Is there a security branch for the FreeBSD ports collection? Let's say, > >>I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages > >>(i.e., those on the CD). Running security/portaudit after a while > >>reveals that some of the installed packages have vulnerabilities. Am I > >>on my own to go grab the fresh ports tree, and upgrade the affected > >>software, suffering all the intricacies of the move by myself? Debian > >>GNU/Linux has its security package updates, OpenBSD has a separately > >>maintained "errata" ports branch (it's very likely you still get to > >>download a newer release of the software, though). > > > > Attached is a script I use to update my machines. It works fine but > > you need to understand what it does and not run it blindly. DO NOT put > > that in cron, there lies pain! > > > > Otherwise, just run the script and it will update all your ports for > > you. It'll even mail you with the updated ports. > > [script snipped] > > A very interesting script for its own purpose, but I'm afraid this > doesn't answer my question at all. FreeBSD accepts limited responsibility for what is in /usr/ports. Maintaining security is not one of them. > Perhaps seeing the way that e.g. > Debian deals with the upgrade problem might shed some light on the > issue. Hell, FreeBSD does exactly that for the base world+kernel, too! > Not for the ports, though. See above. Instead of focusing on the method, focus on the end-goal: you want security updates on your ports and the script posted attempts to provide that. I had one that was safe to run in cron (in fact it ran in periodic/daily), but uses a cvs tree of ports, not cvsup to save time[1]. I lost it with a disk crash, but was going to recreate it anyway, might as well do it now if people are interested. [1] cvsup allthough faster on the entire tree cannot update a single directory. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Release schedule for 2006
On Sunday 18 December 2005 20:46, martinko wrote: > # sysctl hw.acpi.cpu > hw.acpi.cpu.cx_supported: C1/1 > hw.acpi.cpu.cx_lowest: C1 > hw.acpi.cpu.cx_usage: 100.00% > > and, imho, cx_supported should list all available states, doesn't matter > what is in rc.conf. (well, at least i reckon it's supposed to work that > way.) > > but: > > i already had 3 Cx states back on 5.3. > and when i had them, C2 was used most often (and C3 wasn't at all iirc). > > so what has changed in the system please and how am i to get back my > states please ?? This is exactly the thing you need to report via send-pr. Developers won't be aware of regression errors if they don't get reported. Cx states are configured via acpi, so I'd visit the acpi list and prepare a dump of your acpicode for the developers to look at. See acpidump(8) for details. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS UDP mounts on RELENG_6?
On Sunday 18 December 2005 15:12, Oliver Brandmueller wrote: > Hi. > > On Sun, Dec 18, 2005 at 01:45:37PM +0100, Oliver Brandmueller wrote: > > Which kind GigE Interface do you use? I'm currently checking different > > things. I have another RELENG_6 machine where everything works fine, > > which has a slightly older system at the moment. Luckily it's still in > > the testing phase, so I'm currently updating and see if everything is > > still working after update. This one has bge interfaces (and is amd64). > > OK. UDP NFS works as expected with amd64/bge on RELENG_6 of today. It > does not work in the same network on i386/em for me. Still > investigating. To rule out NFS, do something like syslogging remotely (also UDP). -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Release Schedule for 2006
On Sunday 18 December 2005 15:02, Uwe Laverenz wrote: > On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote: > > It looks like in the course of writing your long email you forgot to > > describe any of the problems you are having. > > I don't know his exact problems either, but I could name you a few > examples that currently reduce the fun of using FreeBSD: > > - The sound sytem is broken in FreeBSD in all 5.x and 6 versions, and I > would like to listen to a few mp3-files from time to time. Define broken? I put snd_ich_load="YES" into /boot/loader.conf, nothing in the kernel and it just works. Listening to SomaFM's Groovesalad via mpg123 as I type. > - Keeping the system and the ports up to date gets more and more time > consuming and risky (especially when compared to an "apt-get update && > apt-get upgrade"). For example, the last devel/pear update in the > ports crashed my PHP installations on 2 development machines (still no > clue how to fix this). That's independant of -stable/-current or any FreeBSD release for that matter, but if you have a PR to look at... -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Release schedule for 2006
On Sunday 18 December 2005 01:13, Kevin Oberman wrote: > > Date: Sat, 17 Dec 2005 18:14:01 +0100 > > From: martinko <[EMAIL PROTECTED]> > > > > Kevin Oberman wrote: > > >>Date: Fri, 16 Dec 2005 14:29:39 -0600 > > >>From: Craig Boston <[EMAIL PROTECTED]> > > >>Sender: [EMAIL PROTECTED] > > >> > > >>>-cpu0: on acpi0 > > >>>+cpu0: on acpi0 > > >>> > > >>>Q: Guessing that's a formatting difference, rather then 6.x not > > >>> recognizing the states (sysctl hw.acpi.cpu.cx_supported confirms 4 > > >>> states) > > >> > > >>Not sure on this, but you're probably better off using EST anyway as I > > >>think it gives you more control over the processor frequency. > > > > > > No. There is no conflict between Cx states and EST. Cx states specifies > > > how deeply the CPU will sleep when idle. EST controls processor speed > > > and voltage. In most cases, your REALLY want to use both of these. They > > > are very significant in saving power. (Of course, USB tends to limit > > > the effectiveness of Cx states. I need to run without USB to get really > > > good battery life and to make suspend (S3) really ut power drain. > > > > Kevin, > > > > I used to have 3 Cx states supported when I started with FreeBSD on > > version 5.3. Since I upgraded to 5.4 and recently to 6.0, all I can see > > is just one supported Cx state. I much wonder why. (?) > > What value do you have in /etc/rc.conf (if any) for > performance_cx_lowest? It defaults to HIGH which will limit you to only > the most power hungry sleep state (simple halt). This was made the > default because some hardware was breaking when this was defaulted to > LOW. T0 get other Cx states to be utilized, add > 'performance_cx_lowest="LOW"' to /etc/rc.conf. Doesn't affect hw.acpi.cpu.cx_supported though, so that's the thing to check: # sysctl hw.acpi.cpu.cx_supported; grep performance /etc/rc.conf|wc -l hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 C4/185 0 -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Update from 6.0-RELEASE fails
On Saturday 17 December 2005 22:55, Frank Steinborn wrote: > > > ===> libexec/bootpd (install) > > > install -s -o root -g wheel -m 555 bootpd /usr/libexec > > > strip: /usr/libexec/bootpd: Memory exhausted > Melvyn Sopacua wrote: > > strip /usr/libexec/bootpd > > strip: '/usr/libexec/bootpd': No such file alright: cp /usr/obj/usr/src/libexec/bootpd/bootpd /tmp/ strip /tmp/bootpd If that works, rm -rf /usr/obj and redo. See if memory is still exhausted after installworld, but do it in single user mode if you didn't. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Update from 6.0-RELEASE fails
On Saturday 17 December 2005 21:34, Frank Steinborn wrote: > Melvyn Sopacua wrote: > > Can you strip bootpd after install? > > If you mean whether I can run "strip bootpd": > > kellerkind:/usr/src# strip bootpd > strip: 'bootpd': No such file > > I'm clueless at the moment. strip /usr/libexec/bootpd -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Update from 6.0-RELEASE fails
On Saturday 17 December 2005 17:37, Frank Steinborn wrote: > Kris Kennaway wrote: > > > strip: /usr/libexec/bootpd: Memory exhausted > > > > Well, is it? > > I don't think so, i have nothing in logs that something is going to be > killed and i still have space in swap. Can you strip bootpd after install? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Release schedule for 2006
On Friday 16 December 2005 21:45, Peter Jeremy wrote: > EST - Enhanced SpeedStep > TM2 - Thermal Monitor 2 Hm, guess I'll play with mbmon to see if this shows more then one monitor (assuming the 2 is the number of, not the protocol version). > >-pci0: at device 29.7 (no driver attached) > >+ehci0: mem > >0xf4fffc00-0xf4ff irq 11 at device 29.7 on pci0 > >+ehci0: [GIANT-LOCKED] > > > >Kudos! > > I'm still trying to get my USB2 to do anything more than probe :-( Ouch, well guess I'll have to find that memory stick I should have around here somewhere. > >-Timecounter "TSC" frequency 1398819442 Hz quality 800 > >-Timecounters tick every 10.000 msec > >+Timecounter "TSC" frequency 1398819606 Hz quality 800 > >+Timecounters tick every 1.000 msec > > > >Q: This is a big scarey difference :p This isn't a printf bug I presume? > > Which bit? The TSC is notoriously unstable and a relative change of > 1.2e-7 can be ignored. If you look at kern.clockrate, you'll see that > hz now defaults to 1000. Ah! That explains why rtc was complaining on 5.x but magically stopped doing that on 6. > >-acd0: CDRW at ata1-master PIO4 > >+acd0: CDRW at ata1-master UDMA33 > > > >That's *very* nice! > > Again, that's just a change in defaults. Problems were found with DMA to > ATAPI devices so the decision was made to default to PIO4 in 5.x. You can > set hw.ata.atapi_dma to 1 in 5.x if you want to (see acd(4)). Problems as in long waits on `burncd blank` and subsequent i/o errors and unmountable disks that disappear after reboot? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Release schedule for 2006
On Friday 16 December 2005 20:42, Mark Linimon wrote: > And, if someone ever wants to write that 5.X vs 6.X vs 7.X feature list > comparison, now would be a good time :-) Well, here's a nice start (and a question or two slipped in) - dmesg diff between two GENERIC kernels 5 vs 6 stable of the same date, same hardware. Noise reduced (mem range flips on hw, 'same' entries): -FreeBSD 5.4-STABLE #3: Sun Nov 20 03:52:04 CET 2005 -[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC +FreeBSD 6.0-STABLE #1: Wed Dec 7 01:36:46 CET 2005 +[EMAIL PROTECTED]:/usr/obj/usr/current/src/sys/GENERIC Features=0xa7e9f9bf + Features2=0x180 Q: What are those extra features and are they useful? ;-) +npx0: [FAST] -cpu0: on acpi0 +cpu0: on acpi0 Q: Guessing that's a formatting difference, rather then 6.x not recognizing the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) -ACPI link \\_SB_.PCI0.LNKB has invalid initial irq 11, ignoring +pci_link1: BIOS IRQ 11 for 0.31.INTB is invalid Q: Could this be midi? +uhci0: [GIANT-LOCKED] +uhci1: [GIANT-LOCKED] +uhci2: [GIANT-LOCKED] Q: Again - is this formatting or are these (and the ones below) still under Giant in 6.x but not in 5.x? -pci0: at device 29.7 (no driver attached) +ehci0: mem 0xf4fffc00-0xf4ff irq 11 at device 29.7 on pci0 +ehci0: [GIANT-LOCKED] +usb3: EHCI version 1.0 +usb3: companion controllers, 2 ports each: usb0 usb1 usb2 +usb3: on ehci0 +usb3: USB revision 2.0 +uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 +uhub3: 6 ports with 6 removable, self powered Kudos! -atapci0: port 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 -ata0: channel #0 on atapci0 -ata1: channel #1 on atapci0 -pcm0: port 0xbc40-0xbc7f,0xb800-0xb8ff mem 0xf4fff400-0xf4fff4ff,0xf4fff800-0xf4fff9ff irq 5 at device 31.5 on pci0 -pcm0: +atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf at device 31.1 on pci0 +ata0: on atapci0 +ata1: on atapci0 +pci0: at device 31.5 (no driver attached) Didn't have snd_ich_load="YES" in loader.conf yet. pcm0 appears the same and is GIANT-LOCKED on 6. +atkbd0: [GIANT-LOCKED] +psm0: [GIANT-LOCKED] -Timecounter "TSC" frequency 1398819442 Hz quality 800 -Timecounters tick every 10.000 msec +Timecounter "TSC" frequency 1398819606 Hz quality 800 +Timecounters tick every 1.000 msec Q: This is a big scarey difference :p This isn't a printf bug I presume? -acd0: CDRW at ata1-master PIO4 +acd0: CDRW at ata1-master UDMA33 That's *very* nice! -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slightly OT, getting errors from members on this list
On Thursday 15 December 2005 15:56, Fabian Keil wrote: > > From: [EMAIL PROTECTED] > > Quite annoying. $ tail -2 /usr/local/etc/postfix/sender_access [EMAIL PROTECTED] 501 Access denied: Owner not interested in what is broken on your end -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tracking multiple machine
On Thursday 15 December 2005 15:36, Massimo Lusetti wrote: > I've commented out the KERNCONF definition and used the GENERIC kernel > and all went fine... ?! > The name of my kernel is spelled correctly. Is the kernconf in /usr/src/sys/i386/conf still there and is it real file (not a symlink to a file on the hostmachine)? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld tries to write to DESTDIR?
On Thursday 18 September 2003 09:58, Mike Porter wrote: > On Wednesday 17 September 2003 07:19 pm, John Polstra wrote: > > On 18-Sep-2003 Doug White wrote: > > > > It always used to work to set DESTDIR for both the buildworld and the > > installworld. Shouldn't it still? Personally, I think it is worthy > > of a PR. > > Maybe its just me, but DESTDIR sounds like (and according to the error > message, appears to act like) the location to place built files in a > buildworld context. Check any automake setup: DESTDIR is the install prefix. Of course one is free deviate from this GNU autotools naming convention. However - IMO it doesn't serve any purpose during buildworld, as you expect to set the build location with MAKEOBJDIR (which also sounds like the location to place built files). -- Melvyn === FreeBSD ghost.lan.webteckies.org 4.8-STABLE FreeBSD 4.8-STABLE #5: Tue Sep 2 17:36:05 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GHOST i386 === pgp0.pgp Description: signature
Re: -STABLE broken?
On Monday 11 August 2003 00:10, The Hermit Hacker wrote: > On Sun, 10 Aug 2003, Melvyn Sopacua wrote: > > > I'm trying a cvsup again but I think something was > > > borken. Any ideas? > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2003-August/002512.html > > http://lists.freebsd.org/pipermail/freebsd-stable/2003-August/002526.html > > > > If you can get it to work, I suggest you revert to before Sat Aug 9 > > 16:21:17 2003 UTC. > > 'K, but how does this help fix the problem? I read both postings when > they were originally posted, and tried to upgrade as well after teh PAE > stuff was committed ... no USB devices, and I didn't enable PAE, but my > server crashes after a few hours ... just backtracked to an Aug 7th > kernel, whcih so far appears to be good ... but, again, that still doesn't > help come up with a solution to the problem :( It does not only enable PAE but also rewrites a large portion of the vm infrastructure. If you can't get a panic, or core, then I would stick a ps and sysctl -a vm in a crontab */2 and see where it leads. The patch changes a lot of things in a lot of parts of the kernel, so even if I would understand most of it an educated guess without a kerneldump is nothing more than a guess. The original poster had a production server running into trouble and asked about any known issues, so I told him how to get his server back in shape, so he can worry about the why part later, in a debug environment. I have one old box to migrate this week, which is a non-critical box with a lot of diskspace, so I could do two seperate installs and compare notes. -- Melvyn === FreeBSD ghost.lan.webteckies.org 4.8-STABLE FreeBSD 4.8-STABLE #2: Sat Aug 2 19:45:34 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GHOST i386 === pgp0.pgp Description: signature
Re: NEC 1300A DVD-R writing
On Saturday 05 July 2003 21:01, Melvyn Sopacua wrote: > so I just bought a NEC 1300A, primarily, because it allows me to write DVD+ > and -RW. Using DVD-R discs (and currently no options to try other media, > due to shops being closed), I'm unable to write anything, using either the > dvd+rwtools port, or the dvdrtools. [ ... ] > READ DVD STRUCTURE[#E]: > Data Recordable Area: 16621272 > MediaID: PRINCO Ok, I finally found the cause listed on the NEC site: http://www.necd.de/faq_detail.php?id=573&frage=286 It seems Princo DVD-R is not supported and I need to wait for new firmware (or buy new media :). -- Melvyn === FreeBSD ghost.lan.webteckies.org 4.8-STABLE FreeBSD 4.8-STABLE #0: Sat Jul 5 18:39:46 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GHOST i386 === ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hardcoded krb reference in ports/postfix
On Tuesday 01 July 2003 20:10, Vivek Khera wrote: > >>>>> "MS" == Melvyn Sopacua <[EMAIL PROTECTED]> writes: > > MS> You removed a very relevant piece from my original mail: > MS> "Since sysutils/libchk doesn't report this as unreferenced ... " > > MS> I don't use kerberos, but that apparently doesn't mean, there aren't > libraries MS> still linked with it. Maybe, when I have time on my hands, > I'll sort out the MS> 4.2 legacy stuff or even re-install my machine, but > in the meanwhile, a knob MS> is very welcome. > > There is not a single binary on your system that references libkrb.a. > It just isn't possible. That's right, it's an archive, but the shared counterparts are there too. So some app some where, prolly wants to use those. -- Melvyn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hardcoded krb reference in ports/postfix
On Tuesday 01 July 2003 20:11, Vivek Khera wrote:
> >>>>> "MS" == Melvyn Sopacua <[EMAIL PROTECTED]> writes:
>
> MS> I kept the logic and applied the right actions for the postfix
> Makefile.inc. MS> It's attached as patch, but I can do a send-pr if you
> prefer.
>
> Cool. Thanks. I'll add this (and an adapted version for SASL1) for
> the postfix 2.0.13 update.
>
Ok, here's the proper patch.
The single quotes are necessary, since make(1) doesn't understand numerical
comparisons, so you need the variable as variable.
I don't see any harm in ${PORTSDIR} being available as it's value in
Makefile.inc, so I didn't bother there.
Hope this helps you better :)
--
Melvyn
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
