Broken multimedia/dvdauthor repaired at last
I just found a way to ''repair'' dvdauthor which is broken since several months. It suffices to comment two lines - 1082 and 1083 - in subreader.c like so: //fribidi_set_mirroring (FRIBIDI_TRUE); //fribidi_set_reorder_nsm (FRIBIDI_FALSE); # cd /usr/ports/multimedia/dvdauthor # make This produces the error message. Change subreader.c as said. # vi work/dvdauthor-0.6.14/src/subreader.c # make install It works for me. Don't know what is missing now. But lxdvdrip which requires dvdauthor is working as usual. :) Hope it helps everybody else. -- Harald Weis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE completed...
Ken Smith kensm...@cse.buffalo.edu writes: Just a quick note in case there are people here who aren't subscribed to the freebsd-announce@ mailing list. We have completed the 8.0-RELEASE cycle. Details about the release are available from the main web site, in particular the announcement itself is available here: http://www.freebsd.org/releases/8.0R/announce.html Thanks for all the help with testing during the release process, as well as your continued support of FreeBSD. A few hours ago, i tested 8.0-RELEASE's installation by CD with a spare hard disk. There is no problem. So now i'm upgrading my main desktop. 7.2-RELEASE - 8.0-RELEASE. Thanks! -- I understood perfectly. That's the Mafia style, isn't is? -- Jack Woltz, Chapter 1, page 61 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on powerpc/powerpc
TB --- 2009-11-29 17:16:56 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 17:16:56 - starting RELENG_8 tinderbox run for powerpc/powerpc TB --- 2009-11-29 17:16:56 - cleaning the object tree TB --- 2009-11-29 17:17:13 - cvsupping the source tree TB --- 2009-11-29 17:17:13 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/powerpc/powerpc/supfile TB --- 2009-11-29 17:52:03 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 17:52:03 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 17:52:03 - 0.79 user 8.12 system 2107.49 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2009-11-29 17:29:23 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 17:29:23 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2009-11-29 17:29:23 - cleaning the object tree TB --- 2009-11-29 17:29:35 - cvsupping the source tree TB --- 2009-11-29 17:29:35 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/sparc64/sparc64/supfile TB --- 2009-11-29 18:06:48 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 18:06:48 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 18:06:48 - 0.52 user 7.51 system 2245.26 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Broken multimedia/dvdauthor repaired at last
Hi, Reference: From: Harald Weis ha...@free.fr Date: Sun, 29 Nov 2009 16:43:14 +0100 Message-id: 20091129154314.ga2...@pollux.local.net Harald Weis wrote: I just found a way to ''repair'' dvdauthor which is broken since several months. It suffices to comment two lines - 1082 and 1083 - in subreader.c like so: //fribidi_set_mirroring (FRIBIDI_TRUE); //fribidi_set_reorder_nsm (FRIBIDI_FALSE); # cd /usr/ports/multimedia/dvdauthor # make This produces the error message. Change subreader.c as said. # vi work/dvdauthor-0.6.14/src/subreader.c # make install It works for me. Don't know what is missing now. But lxdvdrip which requires dvdauthor is working as usual. :) Hope it helps everybody else. Please use send-pr so this will be seen by those who can commit your fix. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text not quoted-printable, HTML or Base64: http://asciiribbon.org Vote For Smoke Free Bavarian Pubs Restaurants http://berklix.org/~jhs/nim/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE completed...
On Fri, Nov 27, 2009 at 09:33:04AM +0100, Roland Smith wrote:
On Thu, Nov 26, 2009 at 09:57:58PM -0800, Gary Kline wrote:
Altho I am still some time from having my migration from the
1998 Kayak - 2009 Dell done and working, will it be possible
to upgrade my 32bit 7.2-R, p4 to a 64bit 8.0?
It is possible, but not easy. Upgrading from 7.x to 8.0 on the same
architecture is not that hard IMHO. Upgrading from i386 to amd64 on the same
release is doable but tricky; you need a spare root partition to install the
amd64 binaries. Combining these two sounds like a big can of worms to me. My
advice would be _not_ to do it.
Yes, and for now I'll stick with simply going from v7 to
v8--in the 32-bit release... Lots of stuff to get-working
PLUS the server migration from ancient to new. ---eventually
i'll take a _long_ breath.
It would be far easier to just install 8.0 on the new machine and migrate your
data and configuration files. You are going to have to build your ports from
scratch anyway, because you're switching to another architecture and another
major release.
As far as I know, the on-disk filesystem format hasn't changed. (unless your
old machine is still running UFS1. The default now is UFS2)
Pretty sure I'm using the default. UFS2.
There are a couple of differences between 7.x and 8.0;
* The USB stack has been rewritten. I've had to change the following in
/etc/devfs.rules: replace add path 'usb*' mode 0660 group usb with add
path 'usb/*' mode 0660 group usb
Roland, would you please update your webpage? No hurry, but
by sometime early in '10. I do rely on others' datapoints.
But now tat I'm having to do some real work in this migration,
it's time to learn about some things I've let slide.
{ One far, far OT question here: who can explain what dovecot
is/does? why it even exists? I'm familiar with MTA's, like
sendmail; likewise with MUA's, like evo, kmail, and mutt.
It's time to learn another level of complexity, evidently}
* The name of the tty devices has changed in /etc/ttys; ttydN - ttyuN
(impacts /etc/ttys)
What impact is this likely to have on my server? The more
ttys we've got, the better, for a term/xterm/cmdline like me.
But because I've only used my Kayak as a server, I don't think
I touched much in tty-land. *But* I probably will. I can't see
just letting a heavy-duty dual-core suck up so many kilowats.
--Okay, I'll get off the soapbox now:)
* There have been a lot of changes in the kernel configuration. If you want a
custom kernel, start anew from the 8.0 GENERIC kernel so you don't miss
anything.
Could somebody who's running a 32biter send a GENERIC from
8.0 so I can diff?
* A lot of changes as well in /etc/src.conf (the file that defines which parts
of the system are built from source)
* Network cards show up in dmesg and ifconfig, but not as devices in /dev (but
that could be a configuration error on my part.)
Sorry, you left me in the dust with /etc.src.conf. I though
the entire system was built from source. Examples, please?
Since you're switching to another CPU, things like cache size will have a
major inpact. WRT single versus multi cores, my impression has been that the
individual cores in a multi-core intel CPU are somewhat slower that the core
of a similarly clocked single-core CPU. (based on some informal testing I've
done with povray). If your workloads are capable of running on multiple cores
(e.g. make jobs, different programs running concurrently) there will be a
significant speed increase.
You only _need_ amd64 if you are running out of address space on the i386
architecture. Having said that, I've been running amd64 on my desktop since
5.3-RELEASE more or less because I can, and it has worked fine ever since. Be
aware though that there are a few (most binary) ports that do not work on
amd64. You can see that in the port Makefiles by looking for things like
NOT_FOR_ARCHS and ONLY_FOR_ARCHS.
For whatever I do, 32 bits has been fine. I spend virtually
my entire bg working in the 64bit world, which used to be:
supercomputer-level processing.
HTH,
Yup; this has been a serious help; you it will robably keep me
from stepping in it [[ a mine-field ]] when I move to 8.0 or
8.1 next year.
gary
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.31a release of
Re: 8.0-RELEASE completed...
On Sun, 29 Nov 2009 11:30:18 -0800
Gary Kline kl...@thought.org wrote:
{ One far, far OT question here: who can explain what dovecot
is/does? why it even exists? I'm familiar with MTA's, like
sendmail; likewise with MUA's, like evo, kmail, and mutt.
It's time to learn another level of complexity, evidently}
Dovecot is an IMAP/POP3 server - sendmail lets you send mail, dovecot
lets you fetch it from a remote server.
--
Bruce Cran
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on arm/arm
TB --- 2009-11-29 19:54:25 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 19:54:25 - starting RELENG_8_0 tinderbox run for arm/arm TB --- 2009-11-29 19:54:25 - cleaning the object tree TB --- 2009-11-29 19:54:37 - cvsupping the source tree TB --- 2009-11-29 19:54:37 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/arm/arm/supfile TB --- 2009-11-29 20:30:26 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 20:30:26 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 20:30:26 - 0.64 user 6.36 system 2161.30 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-arm-arm.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on i386/pc98
TB --- 2009-11-29 19:54:25 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 19:54:25 - starting RELENG_8_0 tinderbox run for i386/pc98 TB --- 2009-11-29 19:54:25 - cleaning the object tree TB --- 2009-11-29 19:54:45 - cvsupping the source tree TB --- 2009-11-29 19:54:45 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/i386/pc98/supfile TB --- 2009-11-29 20:32:06 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 20:32:06 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 20:32:06 - 0.85 user 11.05 system 2261.36 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on i386/i386
TB --- 2009-11-29 19:54:25 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 19:54:25 - starting RELENG_8_0 tinderbox run for i386/i386 TB --- 2009-11-29 19:54:25 - cleaning the object tree TB --- 2009-11-29 19:54:45 - cvsupping the source tree TB --- 2009-11-29 19:54:45 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/i386/i386/supfile TB --- 2009-11-29 20:32:06 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 20:32:06 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 20:32:06 - 0.88 user 11.37 system 2261.72 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on amd64/amd64
TB --- 2009-11-29 19:54:25 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 19:54:25 - starting RELENG_8_0 tinderbox run for amd64/amd64 TB --- 2009-11-29 19:54:25 - cleaning the object tree TB --- 2009-11-29 19:54:52 - cvsupping the source tree TB --- 2009-11-29 19:54:52 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/amd64/amd64/supfile TB --- 2009-11-29 20:32:27 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 20:32:27 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 20:32:27 - 1.03 user 12.86 system 2282.81 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE completed...
On Sun, Nov 29, 2009 at 07:47:28PM +, Bruce Cran wrote:
On Sun, 29 Nov 2009 11:30:18 -0800
Gary Kline kl...@thought.org wrote:
{ One far, far OT question here: who can explain what dovecot
is/does? why it even exists? I'm familiar with MTA's, like
sendmail; likewise with MUA's, like evo, kmail, and mutt.
It's time to learn another level of complexity, evidently}
Dovecot is an IMAP/POP3 server - sendmail lets you send mail, dovecot
lets you fetch it from a remote server.
There is one thing Dovecot offers (purely as a nicety; it has no
relation to the IMAP/POP3 functionality of the daemon per se) which is
unlike other IMAP/POP3 daemon -- its own SASL implementation. This
allows for MTAs like Postfix and Exim to use the SASL feature of Dovecot
to do user/pass authentication:
http://wiki.dovecot.org/Sasl
I consider this a major plus, given that I avoid Cyrus software like the
plague.
If you maintain a server which runs both a public-facing MTA which
permits users to send mail through it (via SMTP AUTH) and an IMAP/POP3
daemon, then this feature of Dovecot is a blessing. Getting it to work
with Postfix is incredibly simple -- 4 lines in main.cf, and a single
line in master.cf; no need to rebuild all your software to link to a
library, blah blah...
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE completed...
On Sun, Nov 29, 2009 at 11:30:18AM -0800, Gary Kline wrote: There are a couple of differences between 7.x and 8.0; * The USB stack has been rewritten. I've had to change the following in /etc/devfs.rules: replace add path 'usb*' mode 0660 group usb with add path 'usb/*' mode 0660 group usb Roland, would you please update your webpage? Coincidentally, I just did that today. :-) * The name of the tty devices has changed in /etc/ttys; ttydN - ttyuN (impacts /etc/ttys) What impact is this likely to have on my server? The more ttys we've got, the better, for a term/xterm/cmdline like me. Not a lot. If you haven't changed /etc/ttys, mergemaster will take care of it for you. I always change this file, to mark the console as insecure (meaning you have to give the root password to log into single user mode). Note that this change only affects the dialup lines. On my machines I always disable them. * There have been a lot of changes in the kernel configuration. If you want a custom kernel, start anew from the 8.0 GENERIC kernel so you don't miss anything. Could somebody who's running a 32biter send a GENERIC from 8.0 so I can diff? Go to the following URI: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/conf/GENERIC?only_with_tag=RELENG_8_0_0_RELEASE Click on 'download' to get the file, or select it for a diff between another version. * A lot of changes as well in /etc/src.conf (the file that defines which parts of the system are built from source) * Network cards show up in dmesg and ifconfig, but not as devices in /dev (but that could be a configuration error on my part.) Sorry, you left me in the dust with /etc/src.conf. I though the entire system was built from source. Examples, please? This file contains variables that will be used during a system build from source. The main use is to have the system skip building things you don't need. E.g. if you don't have bluetooth devices in your server, you can set WITHOUT_BLUETOOTH=yes in /etc/src.conf, and the system will not build kernel modules and programs that relate to bluetooth. See src.conf(5) for a complete list of settings (with explanations) you can apply in this file. I tend to disable everything I don't need, because bugs and vulnerabilities in things that are not built and installed cannot harm me. And it cuts down on build time as well. I tend to build my own kernel for mostly the same reasons. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpUr4FCKY8WC.pgp Description: PGP signature
Re: Broken multimedia/dvdauthor repaired at last
On Sun, Nov 29, 2009 at 07:26:53PM +0100, Julian H. Stacey wrote: Hi, Reference: From: Harald Weis ha...@free.fr Date: Sun, 29 Nov 2009 16:43:14 +0100 Message-id: 20091129154314.ga2...@pollux.local.net Harald Weis wrote: I just found a way to ''repair'' dvdauthor which is broken since several months. It suffices to comment two lines - 1082 and 1083 - in subreader.c like so: //fribidi_set_mirroring (FRIBIDI_TRUE); //fribidi_set_reorder_nsm (FRIBIDI_FALSE); # cd /usr/ports/multimedia/dvdauthor # make This produces the error message. Change subreader.c as said. # vi work/dvdauthor-0.6.14/src/subreader.c # make install It works for me. Don't know what is missing now. But lxdvdrip which requires dvdauthor is working as usual. :) Hope it helps everybody else. Please use send-pr so this will be seen by those who can commit your fix. Okay, done. Harald ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: PUC Serial I/O problem - copy of gnats-filed bug report (as discussed previously)
On Sat, Nov 28, 2009 at 09:43:25PM -0600, Karl Denninger wrote: Karl Denninger wrote: Jeremy Chadwick wrote: On Fri, Nov 27, 2009 at 12:54:17PM -0600, Karl Denninger wrote: For what its worth, USB-based serial adapters also fail in the same way, but faster (they have NEVER been reliable in this regard, and this hasn't improved) There must be a regression of some kind, given that some FreeBSD developers have stated in the past that FTDI-based USB serial adapters work great: http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/041615.html Original thread: http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/041610.html I don't know where works great has come from. Certainly not my experience in heavy use. For non-modem-control heavy use, it works ok. I use an 8-port fanout on 7.x to drive process control and it's stable. However, for heavy modem use (e.g. Hylafax) it has NEVER been stable - although in 8.x it won't even manage to send ONE 10-page fax most of the time, where under 7.x it would randomly fail in that use. Then again the puc() driver based serial I/O was completely stable under 7.x and now, with the new architecture it will get one or two jobs through it before it blows up. -- Karl FYI I downgraded back to 7.2-STABLE (it was a bit hairy but I got it to work after a small amount of screwing around) via sources and again the machine and those serial ports are 100% stable with the old driver infrastructure. The uart() infrastructure in 8.x has to be considered broken and unusable for modems at this point folks. I recognize that nobody flagged it until just before the release (I hadn't tried it until RC2, and thus didn't know) but this is a literal dagger in the heart of anyone who needs to put an actual modem on an 8.x box using the common cards out there, and I assume it will bite just as hard for things like a dial-in console as it will for a fax server. Karl, I agree with you in this regard. However, I'm not sure what to recommend to you with regards to getting this issue the proper attention it needs. I fully agree with the Severity (serious) and Priority (high) of the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/140947 Ed Schouten appears to be giving this attention, but I'd recommend that Email communication include mar...@freebsd.org, just in case it turns out that puc(4) needs some changes. I'm certain Ed will do his best to assist tracking this one down. :-) -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on powerpc/powerpc
TB --- 2009-11-29 20:32:06 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 20:32:06 - starting RELENG_8_0 tinderbox run for powerpc/powerpc TB --- 2009-11-29 20:32:06 - cleaning the object tree TB --- 2009-11-29 20:32:22 - cvsupping the source tree TB --- 2009-11-29 20:32:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/powerpc/powerpc/supfile TB --- 2009-11-29 21:07:06 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:07:06 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:07:06 - 0.58 user 7.85 system 2099.48 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on ia64/ia64
TB --- 2009-11-29 20:30:26 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 20:30:26 - starting RELENG_8_0 tinderbox run for ia64/ia64 TB --- 2009-11-29 20:30:26 - cleaning the object tree TB --- 2009-11-29 20:30:38 - cvsupping the source tree TB --- 2009-11-29 20:30:38 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/ia64/ia64/supfile TB --- 2009-11-29 21:07:23 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:07:23 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:07:23 - 0.62 user 7.59 system 2217.14 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on sparc64/sparc64
TB --- 2009-11-29 20:32:28 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 20:32:28 - starting RELENG_8_0 tinderbox run for sparc64/sparc64 TB --- 2009-11-29 20:32:28 - cleaning the object tree TB --- 2009-11-29 20:32:39 - cvsupping the source tree TB --- 2009-11-29 20:32:39 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/sparc64/sparc64/supfile TB --- 2009-11-29 21:09:13 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:09:13 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:09:13 - 0.65 user 7.52 system 2205.60 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8_0 tinderbox] failure on mips/mips
TB --- 2009-11-29 20:32:06 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 20:32:06 - starting RELENG_8_0 tinderbox run for mips/mips TB --- 2009-11-29 20:32:06 - cleaning the object tree TB --- 2009-11-29 20:32:14 - cvsupping the source tree TB --- 2009-11-29 20:32:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8_0/mips/mips/supfile TB --- 2009-11-29 21:10:54 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:10:54 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:10:54 - 0.41 user 4.93 system 2327.89 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8_0-mips-mips.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on amd64/amd64
TB --- 2009-11-29 21:07:06 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 21:07:06 - starting RELENG_8 tinderbox run for amd64/amd64 TB --- 2009-11-29 21:07:06 - cleaning the object tree TB --- 2009-11-29 21:07:24 - cvsupping the source tree TB --- 2009-11-29 21:07:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/amd64/amd64/supfile TB --- 2009-11-29 21:41:32 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:41:32 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:41:32 - 0.96 user 9.89 system 2066.02 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on i386/i386
TB --- 2009-11-29 21:09:13 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 21:09:13 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2009-11-29 21:09:13 - cleaning the object tree TB --- 2009-11-29 21:09:25 - cvsupping the source tree TB --- 2009-11-29 21:09:25 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/i386/supfile TB --- 2009-11-29 21:43:05 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:43:05 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:43:05 - 0.55 user 8.07 system 2032.02 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on arm/arm
TB --- 2009-11-29 21:07:23 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 21:07:23 - starting RELENG_8 tinderbox run for arm/arm TB --- 2009-11-29 21:07:23 - cleaning the object tree TB --- 2009-11-29 21:07:30 - cvsupping the source tree TB --- 2009-11-29 21:07:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/arm/arm/supfile TB --- 2009-11-29 21:45:26 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:45:26 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:45:26 - 0.35 user 4.69 system 2282.47 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-arm-arm.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_8 tinderbox] failure on i386/pc98
TB --- 2009-11-29 21:10:54 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-29 21:10:54 - starting RELENG_8 tinderbox run for i386/pc98 TB --- 2009-11-29 21:10:54 - cleaning the object tree TB --- 2009-11-29 21:11:05 - cvsupping the source tree TB --- 2009-11-29 21:11:05 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/pc98/supfile TB --- 2009-11-29 21:48:12 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-11-29 21:48:12 - ERROR: unable to cvsup the source tree TB --- 2009-11-29 21:48:12 - 0.48 user 7.62 system 2238.04 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
how to get the UFSID of a mounted filesystem ?
I observer that when I mount a UFS filesystem using the device name then the entry vanishes from /dev/ufsid, and glabel list no longer shows the device. Which begs the question, how do I find out the ufsid of a mountde filesystem (e.g. '/' so that I can change it's fstab entry for the next reboot?) Am slightly embarassed to have to ask for help! Am sure this was easy and in dmesg last time I did this... -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: how to get the UFSID of a mounted filesystem ?
In the last episode (Nov 30), Pete French said: I observer that when I mount a UFS filesystem using the device name then the entry vanishes from /dev/ufsid, and glabel list no longer shows the device. Which begs the question, how do I find out the ufsid of a mountde filesystem (e.g. '/' so that I can change it's fstab entry for the next reboot?) Am slightly embarassed to have to ask for help! Am sure this was easy and in dmesg last time I did this... Easiest way is to run dumpfs on the device you currently have mounted. The fsid will be on the 2nd line of the output: (r...@studio) /root# dumpfs /dev/da2s1a | head -2 magic 19540119 (UFS2) timeSun Nov 29 18:19:39 2009 superblock location 65536 id [ 49b21fba 667e8575 ] Next easiest is to run mount -v as root, which will give you the fsid, but byte-swapped so you have to mess with it to get a value that matches what glabel expects: /dev/ufsid/49b21fba667e8575 on /tmp/z (ufs, local, soft-updates, fsid ba1fb24975857e66) -- Dan Nelson dnel...@allantgroup.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: how to get the UFSID of a mounted filesystem ?
On Mon, 30 Nov 2009, Pete French wrote: I observer that when I mount a UFS filesystem using the device name then the entry vanishes from /dev/ufsid, and glabel list no longer shows the device. Which begs the question, how do I find out the ufsid of a mountde filesystem (e.g. '/' so that I can change it's fstab entry for the next reboot?) Am slightly embarassed to have to ask for help! Am sure this was easy and in dmesg last time I did this... You can run dumpfs, eg line=`dumpfs 2 /dev/null $1 | head | grep superblock\ location` eval `echo $line | sed -nEe 's/superblock location.*id.*\[ (.*) (.*)\ ]/printf %0x $((0x\1 32 | 0x\2))/p'` I use this in a script to determine the ID so I can modify fstab after the install has finished. -- 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 signature.asc Description: This is a digitally signed message part.
Re: how to get the UFSID of a mounted filesystem ?
Perhaps dumpfs? Pete French petefre...@ticketswitch.com wrote: I observer that when I mount a UFS filesystem using the device name then the entry vanishes from /dev/ufsid, and glabel list no longer shows the device. Which begs the question, how do I find out the ufsid of a mountde filesystem (e.g. '/' so that I can change it's fstab entry for the next reboot?) Am slightly embarassed to have to ask for help! Am sure this was easy and in dmesg last time I did this... -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
