Re: Dislike the way port conflicts are handled now
On 16/01/2010 6:57 π.μ., Greg Larkin wrote: Craig Whipp wrote: On Jan 15, 2010, at 9:44 AM, Kirk Strauser wrote: Until recently, it seems like port dependencies were handled at installation time. Lately, they're handled any time I try to do anything with a port. I absolutely detest the new behavior. Example cases: OLD WAY: $ cd /usr/ports/something/foo22 $ make $ pkg_delete foo21-2.1 $ make install NEW WAY $ cd /usr/ports/something/foo22 $ make === foo22 conflicts with installed package(s): foo21-2.1 $ make fetch === foo22 conflicts with installed package(s): foo21-2.1 $ curse --type=copious $ pkg_delete foo21-2.1 $ make install This isn't just a hypothetical pain in the butt. An example was being unable to build databases/mysql51-client because mysql-client-5.0.something was installed. I understand not being able to *install* it, but to be prevented from *building* it? In most circumstances, I want to be able to delete the old package and install the new one with minimal downtime. As another example, can you imagine not being able to even run make fetch on something huge like OpenOffice until you uninstalled the old version? In the mean time, I've been editing the port's Makefile to remove the CONFLICTS line long enough to finish building. That's not very helpful for those ports that don't actually build until you run make install, but at least I can get the distfile download out of the way. -- Kirk Strauser I agree. I've found that this can interfere with portmaster's -o option, used to replace an installed port with one of a different origin. In my case, databases/mysql41-server with databases/mysql55-server. - Craig This change was based on a recent PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=137855) and made it into the tree a couple of weeks ago: http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r1=1.631;r2=1.632 Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? Regards, Greg While I build most of my personal packages using ports-mgmt/tinderbox, this option would be very useful. I routinely run make fetch on remote machines to retrieve large distfiles, and wouldn't want the installed dependencies to interfere with that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: GELI file systems unusable after glabel label operations
On Sat, Jan 16, 2010 at 12:38:14AM -0600, Scott Bennett wrote: 2) Create the geli device /dev/daXsYP.eli, and then create a label on that, yielding /dev/label/bar. [not sure what the utility of this is, since the label will only appear after the geil provider has been attached] The important point here is that one of the above methods must be used *before* the file system is created and the data loaded into it. Attempting either method *after* data are loaded will result in loss of the data. Maybe not immediately, but since both the filesystem and geom can use the last sector, there will be trouble. :-) The examples in the glabel manpage should how to set up a label correctly. Perhaps this provides a possible recovery method. As you read it, would it be possible to build an altered version of geli(8) that would simply use the existing key file without generating a new one to do a geli init operation? If so, it would certainly be worth my trouble to do that. In theory it is possible, I guess. But the salt is 512 bytes long. So it can have 2^512 different values. That is 1.340×10^154 different values, and you'd have to test them all. And by testing I mean use the modified 'geli init' to generate a key, and then try if the key works, i.e. check if the relevant sector decrypted with that key yields a valid UFS2 superblock. Suppose you wrote a program capable of testing 10^9 keys every second, which sounds like quite alot to me. It would still be running for 2^512/1e9/(3600*24*365) = 4.25×10^137 years! So in practice, this is a hopeless task. And I think that the proper way to nest geoms is too obvious (at least for = the developers/maintainers) to explicitly list in the handbook. If you know that geoms store metadata in their last sector, the proper way to nest them is to use the different devices for each geom stage, so that each has their own metadata sector. Well, it wasn't at all obvious to me, and reading the parts that mention metadata being written to the last sector suggests, if anything, that labeling and encryption are incompatible because both write to the last sector, i.e., to the *same* sector. The idea of the last sector being different for the two operations is not at all apparent. Well, it should be different, otherwise they overwrite the same sector. Ipso facto you should nest providers... Say you want to have a labeled, encrypted device on /dev/da0s1d. First, you create the label; glabel label ‐v foo /dev/da0s1d A device /dev/label/foo now appears. This device is one sector smaller than /dev/da0s1d, because the last sector of /dev/da0s1d is used for the glabel metadata. Now we want to create an encrypted device, so we do: geli init -l 256 /dev/label/foo geli attach /dev/label/foo This will create /dev/label/foo.eli. Again, /dev/label/foo.eli is one sector smaller than /dev/label/foo, because the last sector of /dev/label/foo contains the geli metadata. If one uses geli init -l 256 /dev/da0s1d geli attach /dev/da0s1d this will create and attach /dev/da0s1d.eli, but /dev/label/foo will be destroyed, because 'geli init' overwrites glabel's metadata! Below I've tried to sketch the last sectors of the device, with the extents of the geom-ed devices and the location of the metadata below. -- /dev/da0s1d ...N-5N-4N-3N-2 N-1N | | | | | | geli |glabel| -- /dev/label/foo --- /dev/label/foo.eli Nested geom devices are the only way to keep the metadata safe. Hope this helps, 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) pgpWo80zoDjvn.pgp Description: PGP signature
Re: OOo question.....
On Saturday 16 January 2010, Gary Kline wrote: this may be offtopic but it does deal with our OO.org port. a friend sent me a very nice slideshow in powerpoint format. I've saved it (and the original) somewhere in the evolution directory so all the photos are safe. first question is: can I save an individial image using Openoffice? Select the slide then right click on the image and select Save as Picture near the bottom of the menu. If you're lucky this will work - I've tried this with 3 different MS Powerpoint files and it worked fine with two of them but didn't even give me the Save as Picture option with the other one :-( Second q is howto use them for my desktop backgrounds in KDE since, upon rebuild and relaunch, everything is black. the first question is howto save a separate image? or are there other tools to do this? [neither xv nor gv work] Right click on a blank piece of the KDE desktop and select Configure Desktop. This should open with the Change the background settings icon highlighted. In the Background section click the Picture radio button and click the folder icon on the right to browse to your selected image. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On Fri, Jan 15, 2010 at 11:57:35PM -0500, Greg Larkin typed: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Craig Whipp wrote: On Jan 15, 2010, at 9:44 AM, Kirk Strauser wrote: Until recently, it seems like port dependencies were handled at installation time. Lately, they're handled any time I try to do anything with a port. I absolutely detest the new behavior. Example cases: OLD WAY: $ cd /usr/ports/something/foo22 $ make $ pkg_delete foo21-2.1 $ make install NEW WAY $ cd /usr/ports/something/foo22 $ make === foo22 conflicts with installed package(s): foo21-2.1 $ make fetch === foo22 conflicts with installed package(s): foo21-2.1 $ curse --type=copious $ pkg_delete foo21-2.1 $ make install This isn't just a hypothetical pain in the butt. An example was being unable to build databases/mysql51-client because mysql-client-5.0.something was installed. I understand not being able to *install* it, but to be prevented from *building* it? In most circumstances, I want to be able to delete the old package and install the new one with minimal downtime. As another example, can you imagine not being able to even run make fetch on something huge like OpenOffice until you uninstalled the old version? In the mean time, I've been editing the port's Makefile to remove the CONFLICTS line long enough to finish building. That's not very helpful for those ports that don't actually build until you run make install, but at least I can get the distfile download out of the way. -- Kirk Strauser I agree. I've found that this can interfere with portmaster's -o option, used to replace an installed port with one of a different origin. In my case, databases/mysql41-server with databases/mysql55-server. - Craig This change was based on a recent PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=137855) and made it into the tree a couple of weeks ago: http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r1=1.631;r2=1.632 Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? The fetch and build targets do NOT create any conflicts. I think this solution was totally wrong and the commit should be reverted. Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
A question about ptrace
I'm trying to port a program using ptrace from Linux to FreeBSD.
For this reason I'm trying to understand how ptrace on FreeBSD works.
Below is a sample program I've written which fork()'s and executes
true after calling PT_TRACE_ME. Having read the manual page of ptrace
I assume the printf() in parent should print SIGTRAP but it gives:
Segmentation fault: 11
Can someone help me figure out the problem?
TIA.
#include assert.h
#include signal.h
#include stdio.h
#include stdlib.h
#include string.h
#include sys/types.h
#include sys/ptrace.h
#include sys/wait.h
#include unistd.h
int main(void)
{
int status;
pid_t pid;
char *const myargv[] = { true, NULL };
pid = fork();
if (0 pid)
abort();
else if (!pid) {
ptrace(PT_TRACE_ME, 0, 0, 0);
execvp(myargv[0], myargv);
}
else {
assert(0 waitpid(pid, status, 0));
assert(WIFSTOPPED(status));
assert(0 == ptrace(PT_TO_SCE, pid, 0, 0));
assert(0 waitpid(pid, status, 0));
assert(WIFSTOPPED(status));
printf(%s\n, strsignal(WSTOPSIG(status)));
ptrace(PT_KILL, pid, 0, 0);
return 0;
}
}
--
Regards,
Ali Polatel
pgpstnH78DWR1.pgp
Description: PGP signature
Re: Dislike the way port conflicts are handled now
On Fri, Jan 15, 2010 at 11:57:35PM -0500, Greg Larkin typed: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Craig Whipp wrote: On Jan 15, 2010, at 9:44 AM, Kirk Strauser wrote: Until recently, it seems like port dependencies were handled at installation time. Lately, they're handled any time I try to do anything with a port. I absolutely detest the new behavior. Example cases: OLD WAY: $ cd /usr/ports/something/foo22 $ make $ pkg_delete foo21-2.1 $ make install NEW WAY $ cd /usr/ports/something/foo22 $ make === foo22 conflicts with installed package(s): foo21-2.1 $ make fetch === foo22 conflicts with installed package(s): foo21-2.1 $ curse --type=copious $ pkg_delete foo21-2.1 $ make install This isn't just a hypothetical pain in the butt. An example was being unable to build databases/mysql51-client because mysql-client-5.0.something was installed. I understand not being able to *install* it, but to be prevented from *building* it? In most circumstances, I want to be able to delete the old package and install the new one with minimal downtime. As another example, can you imagine not being able to even run make fetch on something huge like OpenOffice until you uninstalled the old version? In the mean time, I've been editing the port's Makefile to remove the CONFLICTS line long enough to finish building. That's not very helpful for those ports that don't actually build until you run make install, but at least I can get the distfile download out of the way. -- Both methods have their advantages, and disadvantages. With the old method (deferred check), a person could attempt to install a port, only to find that after spending a lot of time fetching, extracting, and building the port, that it could not be installed because of a conflict. This can't happen with the new (early check). Fortunately, there is a (largely undocumented) knob in bsd.port.mk that will allow you to bypass the conflict check by defining DISABLE_CONFLICTS in your build environment. So it's not necessary to edit the port Makefiles just to tinker with ports that conflict with other, already-installed ports: simply change your second example to: make -C /usr/ports/something/foo22 DISABLE_CONFLICTS=1 drink_beer --type=copious Kirk Strauser I agree. I've found that this can interfere with portmaster's -o option, used to replace an installed port with one of a different origin. In my case, databases/mysql41-server with databases/mysql55-server. This is more of a problem. But the author of portmaster could put a workaround into place. - Craig This change was based on a recent PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=137855) and made it into the tree a couple of weeks ago: http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r1=1.631;r2=1.632 Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? I think that's a good idea. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem w/ mysql extension installation
jaymax wrote:
phpmyadmin requires the mysql extension which is apparently not included in
the mysql54 ports
Well, PHP modules aren't provided at all by the mysqlNN-{client,server,scripts}
ports. You want databases/php5-mysql or databases/php5-mysqli
I have certainly been able to install phpmyadmin with mysql-5.4.x from the
ports -- it works perfectly well.
Installing it from
/usr/ports/databases/php5-mysql ==
---
---
---
In file included from /usr/local/include/php/main/../main/php_config.h:2839,
from /usr/local/include/php/Zend/zend_config.h:1,
from /usr/local/include/php/Zend/zend.h:53,
from /usr/local/include/php/main/php.h:34,
from
/usr/ports/databases/php5-mysql/work/php-5.2.12/ext/mysql/php_mysql.c:32:
/usr/local/include/php/ext/php_config.h:1:30: error: ext/mysql/config.h: No
such file or directory
*** Error code 1
1 error
*** Error code 1
Stop in /usr/ports/databases/php5-mysql.
Indeed /usr/local/include/php/ext/mysql/config.h is not present!
Should this have been installed with the mysql installation or from a
dependency?
How can I correct this ?
Not sure what went wrong here, but .../ext/mysql/config.h is part of the
php5-mysql module you're trying to install:
% pkg_which /usr/local/include/php/ext/mysql/config.h
php5-mysql-5.2.12
That file shouldn't be referenced from that location when building the
php5-mysql module -- rather it should use a version of it included with
the PHP sources.
I see from your later message that this problem has gone away for you,
however, for the benefit of the archives, the best thing to do in this
circumstance is generally to 'make clean' in the port concerned and start
again from the beginning. If the problem goes away, then it was probably
a transient local problem. On the other hand, if it persists, then its
likely to be a configuration problem on your system, or a bad interaction
between that port and something else you've got installed. It might be
a bug in the port, but considering how popular the combination of php and
MySQL is, chances are hundreds or thousands of other people would have
experienced the same thing, and the problem would have been fixed in short
order.
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
signature.asc
Description: OpenPGP digital signature
Force use of latest version of Apache
As a relatively new user of FreeBSD, I am confused about what to put in the '/etc/make.conf' file to force the use of Apache22+. I was thinking that perhaps: APACHE_PORT=www/apache22 might be correct. I was reading the bsd.apache.mk file and noticed that several older settings were depreciated. I have the latest version of Apache installed and I want to insure that I don't inadvertently end up with several different versions, or an older version installed. -- Carmel carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
Em Sáb, 2010-01-16 às 07:00 -0500, b. f. escreveu: On Fri, Jan 15, 2010 at 11:57:35PM -0500, Greg Larkin typed: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Craig Whipp wrote: On Jan 15, 2010, at 9:44 AM, Kirk Strauser wrote: Until recently, it seems like port dependencies were handled at installation time. Lately, they're handled any time I try to do anything with a port. I absolutely detest the new behavior. Example cases: OLD WAY: $ cd /usr/ports/something/foo22 $ make $ pkg_delete foo21-2.1 $ make install NEW WAY $ cd /usr/ports/something/foo22 $ make === foo22 conflicts with installed package(s): foo21-2.1 $ make fetch === foo22 conflicts with installed package(s): foo21-2.1 $ curse --type=copious $ pkg_delete foo21-2.1 $ make install This isn't just a hypothetical pain in the butt. An example was being unable to build databases/mysql51-client because mysql-client-5.0.something was installed. I understand not being able to *install* it, but to be prevented from *building* it? In most circumstances, I want to be able to delete the old package and install the new one with minimal downtime. As another example, can you imagine not being able to even run make fetch on something huge like OpenOffice until you uninstalled the old version? In the mean time, I've been editing the port's Makefile to remove the CONFLICTS line long enough to finish building. That's not very helpful for those ports that don't actually build until you run make install, but at least I can get the distfile download out of the way. -- Besides. when port is installed, and you try to build , the ports gets the include files from filesystem (thus getting for includes...) this makes you break , or worst... make a port that is a mix of both... that for sure is not what you want... This way (the new way) forces you to delete the package before build. it is radical, but it is safer... that is why I choose FreeBSD Sergio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NDIS panics (Was: Can I rescan for new PCI devices? Or should hotplugging Expresscards work?)
On 1/11/10, Paul B Mahol one...@gmail.com wrote: On 1/11/10, Bob Johnson fbsdli...@gmail.com wrote: On 1/9/10, Paul B Mahol one...@gmail.com wrote: On 12/16/09, Bob Johnson fbsdli...@gmail.com wrote: I'm using an ExpressCard for wireless networking because there seems to be no driver for the internal card in my laptop (and NDIS panics the system). The Expresscard shows up as a PCI device and works fine, How are you using NDIS and when system panic what is displayed? I tried to use ndisgen with the internal Dell 1397 card. I don't have details available right now, although if you need them I can try it again. When I did the kldload the system spit out error messages about unknown symbols and then panic-ed. I did some searching of the archives and found a message describing the same symptoms, and the response posted was that it indicated that the Windows driver made API calls that were not implemented in the NDIS wrapper. This was a 64-bit Windows driver and an amd64 FreeBSD system. Similar results in both FreeBSD 7.2 and 8.0. It appears that kern/132672 is describing the same or a very similar issue. It also suggests that there is a more fundamental problem than the unrecognized symbols. I can try to reproduce the problem tonight if you want me to. Thanks, If you have debug kernel, then make breakpoint for MSCALL2 (kldload ndis.ko before that): `break MSCALL2' Should be `break w86_64_call2' Then load ndisgen module. Then single step it with `s' it should panic after few steps. At least this is issue I'm experiencing on amd64, it fails in DriverEntry(). with the same virtual address as in kern/132672. -- Paul B Mahol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie gmirror questions
On Saturday 16 January 2010 00:34:52 Mike Clarke wrote: I'm about to upgrade to more disk space and I'm tempted use this as an opportunity to get two disks and implement gmirror. Before I go ahead there's a few aspects of mirroring I'm not sure about and would appreciate some advice. I'm using grub for multi booting. Does this introduce any problems if I want to boot into Windows or Linux on one of the other partitions? Gmirror stores the metadata at the last sector of each disk. So this shouldn't be a problem. But other operating systems might overwrite this data if you're not careful during the paritioning. The gmirror manpage describes the procedure for handling kernel dumps using the prefer balance algorithm in the early stages of booting and then switching to round-robin in the /etc/rc.local script. It then goes on to say that If on the next boot a component with a higher priority will be available, the prefer algorithm will choose to read from it and savecore(8) will find nothing. Does this only arise if I've made some change to the configuration of the mirror between the dump and the reboot or is there some instances when the priority automatically changes? Priority never changes automatically. Some of the articles I've read about gmirror suggest setting the balance to round-robin while others just leave this at the default setting of split. Am I right in assuming that round-robin would give better performance, and does it make much noticeable difference in real terms. In particular am I likely to see a reduction in performance using gmirror compared with what I would get with just a normal single disk. Assuming you have two or more regular HDDs, I can recommend updating to 8-STABLE and using the load algorithm. It has had some major improvements lately, and is now the default. It should give equal or better read performance in comparison to a single disk in all cases. The performance of split and round-robin is very dependent on the access patterns and stripe size (for split). Finally, recent articles say to set kern.geom.debugflags to 17 when creating a mirror on a mounted drive while older articles say to set it to 16. Although I'll probably be creating the mirror on my disks before copying my system onto them so I don't really need to worry about setting this flag but I'm curious to know the difference between using the two values. The sysctl is a bitfield, so 17 (0x11) enables some extra stuff compared to 16 (0x10). See geom(4), section DIAGNOSTICS for more details. -- Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Force use of latest version of Apache
On 1/16/10 7:52 AM, Carmel wrote: As a relatively new user of FreeBSD, I am confused about what to put in the '/etc/make.conf' file to force the use of Apache22+. I was thinking that perhaps: APACHE_PORT=www/apache22 might be correct. I was reading the bsd.apache.mk file and noticed that several older settings were depreciated. I have the latest version of Apache installed and I want to insure that I don't inadvertently end up with several different versions, or an older version installed. What kind of problem are you having? I've found that once I install an Apache port, all dependent ports use the installed port, it's only when I've installed a dependent port (such as PHP) without Apache already installed that I get an obsolete version of Apache. -Bill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On 01/15/2010 10:57 PM, Greg Larkin wrote: This change was based on a recent PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=137855) and made it into the tree a couple of weeks ago: http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r1=1.631;r2=1.632 Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? Regards, Greg I'd love that. The new behavior isn't a bad default, but it needs an override. Wait a minute; rewind. Isn't that what make -DDISABLE_CONFLICTS does? -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
syslog - ipmon(8) logs to a wrong log file?
This is on FreeBSD 9.0-CURRENT ia64. I've ipfilter built into the kernel, with logging enabled: options IPFILTER options IPFILTER_DEFAULT_BLOCK options IPFILTER_LOG It works fine, but logs to a wrong file. I run ipmon with -Ds options: # ps ax|grep ipmon 740 ?? Ss 1:28.09 /sbin/ipmon -Ds # D is for deamon mode, and s is to log via syslog. According to ipmon(8): The default facility when compiled and installed is security. So I've in /etc/syslog.conf: security.* /var/log/ipfilter.log but I get all ipmon messages in /var/log/messages. According to my /etc/syslog.conf this file shouldn't have ipmon messages: *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages What am I doing wrong? Please advise many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SOLVED: Re: syslog - ipmon(8) logs to a wrong log file?
On Sat, Jan 16, 2010 at 04:23:37PM +, Anton Shterenlikht wrote: This is on FreeBSD 9.0-CURRENT ia64. I've ipfilter built into the kernel, with logging enabled: options IPFILTER options IPFILTER_DEFAULT_BLOCK options IPFILTER_LOG It works fine, but logs to a wrong file. I run ipmon with -Ds options: # ps ax|grep ipmon 740 ?? Ss 1:28.09 /sbin/ipmon -Ds # D is for deamon mode, and s is to log via syslog. According to ipmon(8): The default facility when compiled and installed is security. So I've in /etc/syslog.conf: security.* /var/log/ipfilter.log but I get all ipmon messages in /var/log/messages. According to my /etc/syslog.conf this file shouldn't have ipmon messages: *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages It seems that despite using option s facility is still local0. So adding local0.* /var/log/ipfilter.log to /etc/syslog.conf puts all ipmon logs to /var/log/ipfilter.log -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
getting firewall logs via /etc/periodic/daily ?
I'd like to receive the firewall logs together with the usual /etc/periodic/daily email. What's the easiest/safest way to achieve this? Shall I add my own script under /etc/periodic/daily? Shall I modify an existing script, e.g. 310.accounting? Please advise many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: getting firewall logs via /etc/periodic/daily ?
Anton Shterenlikht wrote:
I'd like to receive the firewall logs together
with the usual /etc/periodic/daily email.
What's the easiest/safest way to achieve this?
Shall I add my own script under /etc/periodic/daily?
Shall I modify an existing script, e.g. 310.accounting?
Sure -- you can add your own scripts to the periodic jobs. For things that
aren't part of the base system, the usual place is
/usr/local/etc/periodic/{daily,weekly,monthly,security}
If you decide to adapt one of the system scripts to do what you want, it's
best to copy it to /usr/local/periodic/whatever/ and change the prefix of the
configuration variables inside it. When writing a periodic script, you
generally want the following boilerplate at the top of the file:
# If there is a global system configuration file, suck it in.
#
if [ -r /etc/defaults/periodic.conf ]
then
. /etc/defaults/periodic.conf
source_periodic_confs
fi
plus you should take care to set the return code of the script carefully:
0 means 'everything OK', 1 means 'you might want to look at this output',
2 means 'oops, you configured the script wrong' and 2 means 'it's all gone
a bit pear shaped'. periodic(8) has more detail.
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
signature.asc
Description: OpenPGP digital signature
wpa_supplicant - Did I do something wrong?
Hello,
Last night I installed FreeBSD 8.0-RELEASE on my Acer Aspire One 150 Bw
(Model NO: ZG5), I had no problems installing it. The problems started
when I was configuring the Wireless card (Atheros 5424/2424).
In /etc/wpa_supplicant.conf I put:
network={
ssid=Thomson40BE60
psk=
}
Then, in /etc/rc.conf I put:
ifconfig_ath0=WPA DHCP
hostname=dasp-netbook.PTbox.org
After that, I tried to start the network, by using the following
command:
/etc/netstart
And I get this:
dasp-netbook# dmesg -a |grep wpa
Jan 15 21:18:34 wpa_supplicant[1177]: Line 3: network block was not
terminated properly.
Jan 15 21:18:34 wpa_supplicant[1177]: Line 3: failed to parse network
block.
Jan 15 21:18:34 wpa_supplicant[1177]: Failed to read or parse
configuration '/etc/wpa_supplicant.conf'.
Jan 15 21:19:13 wpa_supplicant[1346]: Failed to initialize driver
interface
(This was my fault, I forget the } in the end of the
file /etc/wpa_supplicant.conf)
Starting wpa_supplicant.
/etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant
Starting wpa_supplicant.
/etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant
Starting wpa_supplicant.
/etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant
Jan 15 22:59:20 dasp-netbook wpa_supplicant[1246]: Failed to initialize
driver interface
After this, I went to google to search for a solution, and I find
somewhere that I should change my Wireless configuration on /etc/rc.conf
to:
wlans_ath0=wlan0
ifconfig_wlan0=WPA DHCP
After that I was able to start the network without problems. The only
question that I have, is if I did something wrong, because I have alot o
strange messages in .log files.
- /etc/rc.conf:
blanktime=300
inetd_enable=YES
keymap=pt.iso.acc
moused_enable=YES
saver=daemon
sshd_enable=YES
#ifconfig_ath0=WPA DHCP
wlans_ath0=wlan0
ifconfig_wlan0=WPA DHCP
#ifconfig_re0=DHCP
hostname=dasp-netbook.PTbox.org
- /etc/wpa_supplicant.conf:
network={
ssid=Thomson40BE60
psk=
}
- uname -a:
FreeBSD dasp-netbook.PTbox.org 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0:
Tue Jan 5 16:02:27 UTC 2010
r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386
- ifconfig -a:
re0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500
options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC
ether 00:1e:68:ab:b6:af
media: Ethernet autoselect (none)
status: no carrier
ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
2290
ether 00:22:69:0b:2d:db
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
status: associated
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
options=3RXCSUM,TXCSUM
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
1500
ether 00:22:69:0b:2d:db
inet 192.168.2.3 netmask 0xff00 broadcast 192.168.2.255
media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11g
status: associated
ssid Thomson40BE60 channel 1 (2412 Mhz 11g) bssid 00:18:f6:ec:b2:23
regdomain 101 indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF TKIP 2:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan
bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS
wme burst roaming MANUAL
- /var/log/messages:
Jan 16 05:55:58 dasp-netbook wpa_supplicant[337]:
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jan 16 05:55:58 dasp-netbook kernel: wlan0: link state changed to DOWN
Jan 16 05:56:01 dasp-netbook wpa_supplicant[337]:
CTRL-EVENT-SCAN-RESULTS
Jan 16 05:56:01 dasp-netbook wpa_supplicant[337]: Trying to associate
with 00:18:f6:ec:b2:23 (SSID='Thomson40BE60' freq=2412 MHz)
Jan 16 05:56:01 dasp-netbook wpa_supplicant[337]: Associated with
00:18:f6:ec:b2:23
Jan 16 05:56:01 dasp-netbook kernel: wlan0: link state changed to UP
Jan 16 05:56:01 dasp-netbook wpa_supplicant[337]: WPA: Key negotiation
completed with 00:18:f6:ec:b2:23 [PTK=CCMP GTK=TKIP]
Jan 16 05:56:01 dasp-netbook wpa_supplicant[337]: CTRL-EVENT-CONNECTED -
Connection to 00:18:f6:ec:b2:23 completed (reauth) [id=0 id_str=]
Jan 16 05:56:04 dasp-netbook dhclient: New IP Address (wlan0):
192.168.2.3
Jan 16 05:56:04 dasp-netbook dhclient: New Subnet Mask (wlan0):
255.255.255.0
Jan 16 05:56:04 dasp-netbook dhclient: New Broadcast Address (wlan0):
192.168.2.255
Jan 16 05:56:04 dasp-netbook dhclient: New Routers (wlan0):
192.168.2.254
Jan 16 06:01:04 dasp-netbook
Re: Dislike the way port conflicts are handled now
Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? Regards, Greg I'd love that. The new behavior isn't a bad default, but it needs an override. Wait a minute; rewind. Isn't that what make -DDISABLE_CONFLICTS does? I believe that he is talking about changing _when_ the check for conflicts is made; whereas DISABLE_CONFLICTS ignores the check, regardless of when it is made. A late check is preferable to using DISABLE_CONFLICTS, because with that knob you can shoot yourself in the foot by mistakenly installing one port on top of another. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Newbie gmirror questions
Forwarded Message: Newbie gmirror questions Newbie gmirror questions Saturday, January 16, 2010 12:34 AM From: Mike Clarke jmc-freeb...@milibyte.co.uk To: freebsd-questions@freebsd.org I'm about to upgrade to more disk space and I'm tempted use this as an opportunity to get two disks and implement gmirror. Before I go ahead there's a few aspects of mirroring I'm not sure about and would appreciate some advice. I'm using grub for multi booting. Does this introduce any problems if I want to boot into Windows or Linux on one of the other partitions? The gmirror manpage describes the procedure for handling kernel dumps using the prefer balance algorithm in the early stages of booting and then switching to round-robin in the /etc/rc.local script. It then goes on to say that If on the next boot a component with a higher priority will be available, the prefer algorithm will choose to read from it and savecore(8) will find nothing. Does this only arise if I've made some change to the configuration of the mirror between the dump and the reboot or is there some instances when the priority automatically changes? Some of the articles I've read about gmirror suggest setting the balance to round-robin while others just leave this at the default setting of split. Am I right in assuming that round-robin would give better performance, and does it make much noticeable difference in real terms. In particular am I likely to see a reduction in performance using gmirror compared with what I would get with just a normal single disk. Finally, recent articles say to set kern.geom.debugflags to 17 when creating a mirror on a mounted drive while older articles say to set it to 16. Although I'll probably be creating the mirror on my disks before copying my system onto them so I don't really need to worry about setting this flag but I'm curious to know the difference between using the two values. -- Mike Clarke ** Hi Mike, I' ve just (ok, two weeks ago) completed a gmirror setup so can tell about what I know about this process However, my setup is not the same as yours because I' m not in a multi boot situation. I let others give their opinion regarding GRUB. I do guess that your OS-es are on a separate disk and in FreeBSD you will create a mirror with the two identical disks using gmirror. I've used round-robin because that's what the handbook suggested. I used kern.geom.debugflags = 17 because I looked at the handbook and guessed the other articles which suggested 16 were not up to date and it worked flawlessly. BrgdsDino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Secure method for fetching freebsd sources ?
Greetings, Which is the *secure* way of fetching freebsd sources? Cvsup looks prone to MiM attacks, CTM looks promising, but only if I have been member of the appropriate ctm list since the release of 8.0. (it seems that the ctm deltas on the ftp are not signed.). Do FreeBSD cvs servers support ssh instead of rsh access as OpenBSD server do? Other alternatives? Please note that this is not a theoretical question. I really have a system which i'll put in a place I don't trust, so I'll try to encrypt everything from the disk to the connections which I will use for updating. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Sound (micro-)interrupts with 8.0 stable/snd_hda/mplayer/vlc
Hello, I'm not really sure what the right list is since I cannot isolate the part of the system which cause the problem : I could use a little help on a weird sound issue I'm struggling with : 1. Description : When playing audio files, the sound has from few to many micro-interrupts (less than 1/4 of a second), randomly but frequently (so this is not hard to reproduce). This seem to occur : . with any file (I can pick a random audio file to experience it) . with either mp3 or flaac encoded files . with mplayer (from the ports collection or hand compiled from svn), either with oss or sdl audio output (although sdl seems to have less interrupts) . with vlc but . not with ffplay . apparently not with xine . apparently not with amarok - so I doubt this may be a harware or a driver issue. and on a almost idle 4GB RAM machine running only KDE-4 and firefox-3 no hints shows in /var/log/messages 2. Config : I'm running : . 8.0-STABLE FreeBSD amd64 . full zfs (no ufs) (files are on a slow disk pool (5400 rpm) but moving them to the fast system disk (7200 rpm) doesn't change anything . on a (bios up to date) P5Q3 ASUS motherboard . with snd_hda sound driver 3. Detailed sound config : --- % cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: HDA Realtek ALC888 PCM #0 Analog at cad 0 nid 1 on hdac0 kld snd_hda [MPSAFE] (1p:2v/1r:1v channels duplex default) pcm1: HDA Realtek ALC888 PCM #1 Analog at cad 0 nid 1 on hdac0 kld snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex) pcm2: HDA Realtek ALC888 PCM #2 Digital at cad 0 nid 1 on hdac0 kld snd_hda [MPSAFE] (1p:1v/0r:0v channels simplex) pcm3: HDA Realtek ALC888 PCM #3 Digital at cad 0 nid 1 on hdac0 kld snd_hda [MPSAFE] (1p:1v/0r:0v channels simplex) % sysctl -a | grep -i pcm dev.pcm.0.%desc: HDA Realtek ALC888 PCM #0 Analog dev.pcm.0.%driver: pcm dev.pcm.0.%parent: hdac0 dev.pcm.0.play.vchans: 2 dev.pcm.0.play.vchanmode: fixed dev.pcm.0.play.vchanrate: 48000 dev.pcm.0.play.vchanformat: s16le:2.0 dev.pcm.0.rec.vchans: 1 dev.pcm.0.rec.vchanmode: fixed dev.pcm.0.rec.vchanrate: 48000 dev.pcm.0.rec.vchanformat: s16le:2.0 dev.pcm.0.buffersize: 16384 dev.pcm.0.bitperfect: 0 dev.pcm.1.%desc: HDA Realtek ALC888 PCM #1 Analog dev.pcm.1.%driver: pcm dev.pcm.1.%parent: hdac0 dev.pcm.1.play.vchans: 1 dev.pcm.1.play.vchanmode: fixed dev.pcm.1.play.vchanrate: 48000 dev.pcm.1.play.vchanformat: s16le:2.0 dev.pcm.1.rec.vchans: 1 dev.pcm.1.rec.vchanmode: fixed dev.pcm.1.rec.vchanrate: 48000 dev.pcm.1.rec.vchanformat: s16le:2.0 dev.pcm.1.buffersize: 16384 dev.pcm.1.bitperfect: 0 dev.pcm.2.%desc: HDA Realtek ALC888 PCM #2 Digital dev.pcm.2.%driver: pcm dev.pcm.2.%parent: hdac0 dev.pcm.2.play.vchans: 1 dev.pcm.2.play.vchanmode: passthrough dev.pcm.2.play.vchanrate: 48000 dev.pcm.2.play.vchanformat: s16le:2.0 dev.pcm.2.buffersize: 16384 dev.pcm.2.bitperfect: 0 dev.pcm.3.%desc: HDA Realtek ALC888 PCM #3 Digital dev.pcm.3.%driver: pcm dev.pcm.3.%parent: hdac0 dev.pcm.3.play.vchans: 1 dev.pcm.3.play.vchanmode: passthrough dev.pcm.3.play.vchanrate: 48000 dev.pcm.3.play.vchanformat: s16le:2.0 dev.pcm.3.buffersize: 16384 dev.pcm.3.bitperfect: 0 4. mplayer output details : . mplayer output for mp3 (no error nor warning message) : == Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 mpg123: Can't rewind stream by 1606 bits! AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000-176400) Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3) == AO: [oss] 44100Hz 2ch s16le (2 bytes per sample) . mplayer output for flaac (no error nor warning message) : == Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 987.7 kbit/69.99% (ratio: 123457-176400) Selected audio codec: [ffflac] afm: ffmpeg (FFmpeg FLAC audio decoder) == AO: [oss] 44100Hz 2ch s16le (2 bytes per sample) 5. ports compile options -- a) mplayer % cat mplayer/options # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for mplayer-0.99.11_14 _OPTIONS_READ=mplayer-0.99.11_14 WITHOUT_DEBUG=true WITH_RTCPU=true WITH_OCFLAGS=true WITH_SIMD=true WITH_IPV6=true WITH_X11=true WITH_X11XV=true WITH_X11DGA=true WITH_X11GL=true WITHOUT_X11XIN=true WITH_X11VM=true WITHOUT_X11XVMC=true WITHOUT_GUI=true WITH_SDL=true WITH_VIDIX=true WITHOUT_SKINS=true WITH_FREETYPE=true WITHOUT_RTC=true WITHOUT_ARTS=true WITHOUT_ESOUND=true WITHOUT_JACK=true WITHOUT_NAS=true WITHOUT_OPENAL=true WITH_LIBUNGIF=true WITHOUT_AALIB=true
Re: Dislike the way port conflicts are handled now
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 b. f. wrote: Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? Regards, Greg I'd love that. The new behavior isn't a bad default, but it needs an override. Wait a minute; rewind. Isn't that what make -DDISABLE_CONFLICTS does? I believe that he is talking about changing _when_ the check for conflicts is made; whereas DISABLE_CONFLICTS ignores the check, regardless of when it is made. A late check is preferable to using DISABLE_CONFLICTS, because with that knob you can shoot yourself in the foot by mistakenly installing one port on top of another. b. That's exactly what I proposed. The bsd.port.mk could be patched to support a new variable (EARLY_CONFLICT_CHECK=yes or somesuch) that shifts the check-conflict target from its old position (part of the install sequence) to its new position (fetch?). The default behavior (no mods to /etc/make.conf) would revert to the old conflict checking method. This may be something for portmgr@ to chime in on, and I'm cc'ing them now. There could be other reasons for this change that I'm unaware of. References for portmgr: http://www.freebsd.org/cgi/query-pr.cgi?pr=137855 - PR to change check-conflicts target position in bsd.port.mk http://www.mail-archive.com/freebsd-questions@freebsd.org/msg227363.html - the thread archive Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLUgxx0sRouByUApARAqQBAJ9EYQlAe7gJpFasl3NmPlg8v4U3jQCfae1V dkSJqw520Z9DJQe0fIhGzkc= =2sdF -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On Sat, Jan 16, 2010 at 01:01:47PM -0500, b. f. wrote: Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? Regards, Greg I'd love that. The new behavior isn't a bad default, but it needs an override. Wait a minute; rewind. Isn't that what make -DDISABLE_CONFLICTS does? I believe that he is talking about changing _when_ the check for conflicts is made; whereas DISABLE_CONFLICTS ignores the check, regardless of when it is made. A late check is preferable to using DISABLE_CONFLICTS, because with that knob you can shoot yourself in the foot by mistakenly installing one port on top of another. Best: check for conflicts early, error out early if there are conflicts so one doesn't waste hours compiling something and checking/installing dependencies and so on Middling: check for conflicts late Worst: don't check for conflicts at all Yeah, sounds about right. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpIylI974DaW.pgp Description: PGP signature
Re: A question about ptrace
Ali Polatel yazmış: I'm trying to port a program using ptrace from Linux to FreeBSD. snip Answering myself after some more reading and trying... assert(0 == ptrace(PT_TO_SCE, pid, 0, 0)); The third argument of this call should be 1 not 0. -- Regards, Ali Polatel pgpVCOf0yCg27.pgp Description: PGP signature
need a Mencoder expert
I have a VOB file that I need to convert to something playable on a Sony Walkman NWZ-E344. The walkman wants an ASF container, resolution of 320x240 (or less), wmv9 codec, wma 2 codec, 30 frames per second, video bitrate of less than or equal to 768k. I cannot seem to get a mencoder (nor ffmpeg) encoding line to work. Here's some data on a video that works: $ ffmpeg -i Butterfly.wmv [wmv3 @ 0x29707c10]Extra data: 8 bits left, value: 0 Seems stream 1 codec frame rate differs from container frame rate: 1000.00 (1000/1) - 29.97 (3/1001) Input #0, asf, from 'Butterfly.wmv': Duration: 00:00:08.21, start: 5.00, bitrate: 1126 kb/s Stream #0.0: Audio: wmav2, 44100 Hz, stereo, s16, 96 kb/s Stream #0.1: Video: wmv3, yuv420p, 320x208, 768 kb/s, 29.97 tbr, 1k tbn, 1k tbc mplayer -identify Butterfly.wmv Playing Butterfly.wmv. ASF file format detected. ID_AUDIO_ID=1 [asfheader] Audio stream found, -aid 1 ID_VIDEO_ID=2 [asfheader] Video stream found, -vid 2 VIDEO: [WMV3] 320x208 24bpp 1000.000 fps 768.0 kbps (93.8 kbyte/s) ID_FILENAME=Butterfly.wmv ID_DEMUXER=asf ID_VIDEO_FORMAT=WMV3 ID_VIDEO_BITRATE=768000 ID_VIDEO_WIDTH=320 ID_VIDEO_HEIGHT=208 ID_VIDEO_FPS=1000.000 ID_VIDEO_ASPECT=0. ID_AUDIO_FORMAT=353 ID_AUDIO_BITRATE=0 ID_AUDIO_RATE=0 ID_AUDIO_NCH=0 ID_LENGTH=15.00 Opening video filter: [screenshot=yes] == Requested video codec family [wmv9dmo] (vfm=dmo) not available. Enable it at compilation. Requested video codec family [wmvdmo] (vfm=dmo) not available. Enable it at compilation. Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family [wmv3 @ 0x882b6f0]Extra data: 8 bits left, value: 0 Selected video codec: [ffwmv3] vfm: ffmpeg (FFmpeg M$ WMV3/WMV9) == ID_VIDEO_CODEC=ffwmv3 == Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 96.0 kbit/6.81% (ratio: 12005-176400) ID_AUDIO_BITRATE=96040 ID_AUDIO_RATE=44100 ID_AUDIO_NCH=2 Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg)) == AO: [oss] 44100Hz 2ch s16le (2 bytes per sample) ID_AUDIO_CODEC=ffwmav2 Starting playback... VDec: vo config request - 320 x 208 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. [swscaler @ 0x8827710]SwScaler: using unscaled yuv420p - bgr24 special converter VO: [xv] 320x208 = 320x208 Planar YV12 New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). subtitle font: load_sub_face failed. == What did you do? the man holding the flashlight asked. I put down a spider, he said, wondering why the man didn't see; in the beam of yellow light the spider bloated up larger than life. So it could get away. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On 1/16/2010 1:01 PM, Chad Perrin wrote: snip Best: check for conflicts early, error out early if there are conflicts so one doesn't waste hours compiling something and checking/installing dependencies and so on Middling: check for conflicts late Worst: don't check for conflicts at all Yeah, sounds about right. That does nothing for conflict resolution, though. That's a big concern for me because in the past, only one distribution of Linux (not having used any of the BSD's before, cannot comment on them except for what I'm seeing in this discussion) that I've used seems to handle not only package dependency with ease and grace, but also conflict resolution (in the sense that the only time I've had an issue with conflicts was when an updated package wasn't available or an older required package was discontinued). I like the fact that FreeBSD checks for conflicts early, but erroring out without anything really useful is a negative for me. Instead of erroring out, why not initiate some sort of conflict resolution (e.g. remove and or update an old port) when the conflict is first detected? Yes, it may very well mean increased time to install a package, especially if compiling from source, but I find that a more elegant solution then just erroring out and requiring yet another manual step. Of course there could be an option to opt-out of this sort of behavior too, for those who like the extra steps. -- PIT signature.asc Description: OpenPGP digital signature
Re: bsdar/netstat issue
Hello,
i just was able myself to find out why netstat was showing different output
on i386.
My i386 machine was updated on 28 November, netstat was modified on 25
November, so seems that
CVS server from which I have updated sources was a little bit outdated.
Thank you.
--
Maxim Ianoglo
On Tue, 12 Jan 2010 14:58:06 +0200
Maxim Ianoglo dot...@gmail.com wrote:
Hello,
Got an issue.
On FreBSD amd64 bsdsar dows not works properly because of netstat -b -i
-n
shows one extra column Idrop
$ uname -m
amd64
$ netstat -b -i -n
NameMtu Network Address Ipkts Ierrs Idrop Ibytes
Opkts Oerrs Obytes Coll
bge0 1500 Link#1 00:00:1a:19:3b:69 722511 0 0 413208866
447516 0 63777493 0
$ uname -imprs
FreeBSD 8.0-STABLE amd64 amd64 GENERIC
In i386 netstat output is as was before
$ uname -m
i386
$ netstat -b -i -n
NameMtu Network Address Ipkts Ierrs Ibytes
Opkts Oerrs Obytes Coll
wpi0* 2290 Link#1 00:1b:77:d3:75:5e0 0 0
0 0 0 0
$ uname -imprs
FreeBSD 8.0-STABLE i386 i386 NAFNOTE
To make bsdsar work properly I have modified it
here is the diff:
$ diff -u /usr/local/bin/bsdsar_gather /usr/local/bin/bsdsar_gather.new
--- /usr/local/bin/bsdsar_gather2010-01-12 14:19:09.0 +0200
+++ /usr/local/bin/bsdsar_gather.new2010-01-12 14:18:13.0 +0200
@@ -91,11 +91,11 @@
# now lets pull data from netstatlist
foreach $ifaceline (@netstatlist) {
chomp $ifaceline;
- ($ifacename, $Mtu, $Network, $Address, $inpkts, $inerrs,
$inbytes, $outpkts, $outerrs, $outbytes, $coll) = split/\s+/,$ifaceline;
+ ($ifacename, $Mtu, $Network, $Address, $inpkts, $inerrs,
$idrops, $inbytes, $outpkts, $outerrs, $outbytes, $coll) =
split/\s+/,$ifaceline;
if ( $coll eq ) {
# $coll is empty because of a blank column, assume
this is Address
# so try again wthout it
- ($ifacename, $Mtu, $Network, $inpkts, $inerrs,
$inbytes, $outpkts, $outerrs, $outbytes, $coll) = split/\s+/,$ifaceline;
+ ($ifacename, $Mtu, $Network, $inpkts, $inerrs,
$idrops, $inbytes, $outpkts, $outerrs, $outbytes, $coll) =
split/\s+/,$ifaceline;
}
$ifaceinfo .=
$ifacename,$inpkts,$inerrs,$inbytes,$outpkts,$outerrs,$outbytes,$coll\|;
Did anyone faced such issue before ? Or thie is not a bug with netstat/bsdsar.
Thank you.
--
Maxim Ianoglo a.k.a dotNox ( dot...@gmail.com )
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On Sat, 16 Jan 2010 13:18:15 -0600 Programmer In Training p...@joseph-a-nagy-jr.us articulated: That does nothing for conflict resolution, though. That's a big concern for me because in the past, only one distribution of Linux (not having used any of the BSD's before, cannot comment on them except for what I'm seeing in this discussion) that I've used seems to handle not only package dependency with ease and grace, but also conflict resolution (in the sense that the only time I've had an issue with conflicts was when an updated package wasn't available or an older required package was discontinued). I like the fact that FreeBSD checks for conflicts early, but erroring out without anything really useful is a negative for me. Instead of erroring out, why not initiate some sort of conflict resolution (e.g. remove and or update an old port) when the conflict is first detected? Yes, it may very well mean increased time to install a package, especially if compiling from source, but I find that a more elegant solution then just erroring out and requiring yet another manual step. Of course there could be an option to opt-out of this sort of behavior too, for those who like the extra steps. If I remember correctly, 'portmanager -y' removed conflicting ports prior to installing a new or updated port. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Children begin by loving their parents. After a time they judge them. Rarely, if ever, do they forgive them. Oscar Wilde ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Secure method for fetching freebsd sources ?
Angelin Lalev wrote: Greetings, Which is the *secure* way of fetching freebsd sources? Cvsup looks prone to MiM attacks, CTM looks promising, but only if I have been member of the appropriate ctm list since the release of 8.0. (it seems that the ctm deltas on the ftp are not signed.). Do FreeBSD cvs servers support ssh instead of rsh access as OpenBSD server do? Other alternatives? Please note that this is not a theoretical question. I really have a system which i'll put in a place I don't trust, so I'll try to encrypt everything from the disk to the connections which I will use for updating. You can use freebsd-update(8) to fetch system sources as well as binary updates. Updates are cryptographically secured -- whether this is enough for your application is a judgement call you will have to make. 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 signature.asc Description: OpenPGP digital signature
Re: Dislike the way port conflicts are handled now
Greg Larkin píše v so 16. 01. 2010 v 13:58 -0500: That's exactly what I proposed. The bsd.port.mk could be patched to support a new variable (EARLY_CONFLICT_CHECK=yes or somesuch) that shifts the check-conflict target from its old position (part of the install sequence) to its new position (fetch?). The default behavior (no mods to /etc/make.conf) would revert to the old conflict checking method. This may be something for portmgr@ to chime in on, and I'm cc'ing them now. There could be other reasons for this change that I'm unaware of. What is the particular scenario that the new conflicts handling broke for you? Often you really want to ignore locally installed packages and then it's better to override LOCALBASE to /nonex or something similar, instead of disabling conflict handling... -- Pav Lucistnik p...@oook.cz p...@freebsd.org It's the classic Microsoft security-bulletin formula: The vulnerability is important (never dangerous); you have nothing to fear and no reason to regret trusting us; we have no intention of apologizing for it or even explaining it adequately; now go get your patch, shut up, and be grateful nothing bad has happened. -- The Register signature.asc Description: Toto je digitálně podepsaná část zprávy
changing place of .core files
Normally when a program crashes, it places a .core file in the homefilesystem. Is there a way of changing the filesystem where FreeBSD places it's core dumps? Thanks in advance, Marco -- Rule #7: Silence is not acquiescence. Contrary to what you may have heard, silence of those present is not necessarily consent, even the reluctant variety. They simply may sit in stunned silence and figure ways of sabotaging the plan after they regain their composure. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On Sat, 16 Jan 2010 13:01:47 -0500 b. f. bf1...@googlemail.com wrote: Wait a minute; rewind. Isn't that what make -DDISABLE_CONFLICTS does? I believe that he is talking about changing _when_ the check for conflicts is made; whereas DISABLE_CONFLICTS ignores the check, regardless of when it is made. A late check is preferable to using DISABLE_CONFLICTS, because with that knob you can shoot yourself in the foot by mistakenly installing one port on top of another. I think the point is you can make -DDISABLE_CONFLICTS using targets other than install ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: changing place of .core files
On Sat, 16 Jan 2010 23:23:52 +0100 (CET) Marco Beishuizen mb...@xs4all.nl wrote: Normally when a program crashes, it places a .core file in the homefilesystem. Is there a way of changing the filesystem where FreeBSD places it's core dumps? cd to another directory before starting the program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pav Lucistnik wrote: Greg Larkin píše v so 16. 01. 2010 v 13:58 -0500: That's exactly what I proposed. The bsd.port.mk could be patched to support a new variable (EARLY_CONFLICT_CHECK=yes or somesuch) that shifts the check-conflict target from its old position (part of the install sequence) to its new position (fetch?). The default behavior (no mods to /etc/make.conf) would revert to the old conflict checking method. This may be something for portmgr@ to chime in on, and I'm cc'ing them now. There could be other reasons for this change that I'm unaware of. What is the particular scenario that the new conflicts handling broke for you? Often you really want to ignore locally installed packages and then it's better to override LOCALBASE to /nonex or something similar, instead of disabling conflict handling... Hi Pav, I'm not the one who posted the original message to the list, but I'm participating in the conversation with some of the folks who expressed a preference for checking conflicts later in the build process. Here is the original post: http://www.mail-archive.com/freebsd-questions@freebsd.org/msg227363.html I thought portmgr might have some insight into additional reasons for making the change, such as fixing a problem with pointyhat builds, etc. At the moment, I'm neutral on the change, since it hasn't caused me any grief, but I did some research for the folks who posted the original questions. What do you think of adding an entry to UPDATING to note a change like this in the build process? For instance, I wasn't aware of the LOCALBASE=/nonexistent idea that you mentioned, so the entry could include that and some other tips. Thank you, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLUkWE0sRouByUApARApVWAKCmof3lBaN+R58UkPm82KjNvt9RCACeMExc uQCKc9mU4ou9qJ95fz6sv5Y= =Eq2R -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: changing place of .core files
On Sun, 17 Jan 2010, RW wrote: On Sat, 16 Jan 2010 23:23:52 +0100 (CET) Marco Beishuizen mb...@xs4all.nl wrote: Normally when a program crashes, it places a .core file in the homefilesystem. Is there a way of changing the filesystem where FreeBSD places it's core dumps? cd to another directory before starting the program. This won't work most of the time because a lot of programs are not started by me as user. For example npviewer.bin core dumps a lot because of bad flash. But npviewer.bin is started by Firefox, not by me. -- Horngren's Observation: Among economists, the real world is often a special case. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On 1/16/10, Pav Lucistnik p...@freebsd.org wrote: Greg Larkin píše v so 16. 01. 2010 v 13:58 -0500: That's exactly what I proposed. The bsd.port.mk could be patched to support a new variable (EARLY_CONFLICT_CHECK=yes or somesuch) that shifts the check-conflict target from its old position (part of the install sequence) to its new position (fetch?). The default behavior (no mods to /etc/make.conf) would revert to the old conflict checking method. This may be something for portmgr@ to chime in on, and I'm cc'ing them now. There could be other reasons for this change that I'm unaware of. What is the particular scenario that the new conflicts handling broke for you? Often you really want to ignore locally installed packages and then it's better to override LOCALBASE to /nonex or something similar, instead of disabling conflict handling... Some people want to be able to fetch and build ports that conflict with installed ports, without going to the trouble of (1) re-installing all of the build dependencies in an alternate LOCALBASE; or (2) first de-installing, and then afterwards reinstalling the conflicting ports. And they want to do this without disabling the conflict check, so that they don't mistakenly corrupt an installed port. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: changing place of .core files
On Sat, Jan 16, 2010 at 11:23:52PM +0100, Marco Beishuizen wrote: Normally when a program crashes, it places a .core file in the homefilesystem. Is there a way of changing the filesystem where FreeBSD places it's core dumps? Thanks in advance, Marco -- Rule #7: Silence is not acquiescence. Contrary to what you may have heard, silence of those present is not necessarily consent, even the reluctant variety. They simply may sit in stunned silence and figure ways of sabotaging the plan after they regain their composure. Check core(5). HTH, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On Sat, 16 Jan 2010 21:26:28 +0100 Pav Lucistnik p...@freebsd.org wrote: Greg Larkin píše v so 16. 01. 2010 v 13:58 -0500: That's exactly what I proposed. The bsd.port.mk could be patched to support a new variable (EARLY_CONFLICT_CHECK=yes or somesuch) that shifts the check-conflict target from its old position (part of the install sequence) to its new position (fetch?). The default behavior (no mods to /etc/make.conf) would revert to the old conflict checking method. This may be something for portmgr@ to chime in on, and I'm cc'ing them now. There could be other reasons for this change that I'm unaware of. What is the particular scenario that the new conflicts handling broke for you? Often you really want to ignore locally installed packages and then it's better to override LOCALBASE to /nonex or something similar, instead of disabling conflict handling... I'd be very happy if I could: - fetch the distfiles, even if I have a conflicting port installed - be able to use portmaster -o to switch from one port to an other one that conflicts with it. - be able to at least compile a port (eg. for testing) without having to de-install the current one. I'm all in favor of restoring the old behavior with a switch available to turn on the new one. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Dislike the way port conflicts are handled now
On 01/16/2010 02:26 PM, Pav Lucistnik wrote: What is the particular scenario that the new conflicts handling broke for you? Often you really want to ignore locally installed packages and then it's better to override LOCALBASE to /nonex or something similar, instead of disabling conflict handling.. Pav, I'm the OP, and described the problem in the first post. To recap, though, say I want to upgrade from the databases/mysql50-client port to databases/mysql51-client. Without taking extra steps such as using -DDISABLE_CONFLICTS or removing the CONFLICTS definition from the Makefile, I can't even start downloading the distfiles (using make fetch) until I pkg_delete the old version. With the old system, I could do everything up through building the new port so that the time between running pkg_delete and make reinstall is minimized. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
To jail, or not to jail?
I've been having fun playing with jails on my home server. There's one for databases, one for a webserver, another for using as a play shell server, etc. We use jails heavily at work for encapsulating services, and I can make a pretty good argument there for doing so. In general, though, do you see jails as particularly important or useful when not in a hosting environment where you're giving root access to an untrusted party? How far do you go toward segregating services? Theoretically, you could have a jail per daemon, but it seems like down that path lies madness. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: changing place of .core files
On Sun, 17 Jan 2010, Yuri Pankov wrote: Check core(5). HTH, Yuri Thanks, this is what I was looking for. Regards, Marco -- Never argue with a woman when she's tired -- or rested. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Sound (micro-)interrupts with 8.0 stable/snd_hda/mplayer/vlc
On Saturday 16 January 2010 19:17:18 Thomas Hummel wrote: Hello, I'm not really sure what the right list is since I cannot isolate the part of the system which cause the problem : I could use a little help on a weird sound issue I'm struggling with : 1. Description : When playing audio files, the sound has from few to many micro-interrupts (less than 1/4 of a second), randomly but frequently (so this is not hard to reproduce). This seem to occur : . with any file (I can pick a random audio file to experience it) . with either mp3 or flaac encoded files . with mplayer (from the ports collection or hand compiled from svn), either with oss or sdl audio output (although sdl seems to have less interrupts) . with vlc but . not with ffplay . apparently not with xine . apparently not with amarok Amarok uses xine. All of the above ultimately use OSS to output the sound. - so I doubt this may be a harware or a driver issue. and on a almost idle 4GB RAM machine running only KDE-4 and firefox-3 no hints shows in /var/log/messages 2. Config : I'm running : . 8.0-STABLE FreeBSD amd64 . full zfs (no ufs) (files are on a slow disk pool (5400 rpm) but moving them to the fast system disk (7200 rpm) doesn't change anything . on a (bios up to date) P5Q3 ASUS motherboard . with snd_hda sound driver [snip] Try increasing the hw.snd.latency sysctl: hw.snd.latency Configure the buffering latency. Only affects applications that do not explicitly request blocksize / fragments. This tunable provides finer granularity than the hw.snd.latency_profile tun- able. Possible values range between 0 (lowest latency) and 10 (highest latency). Just thinking out loud here, but maybe you have some non-standard HZ configured or powerd configured to clock the CPU back by an extreme amount, both could theoretically cause buffer underruns. - Pieter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: need a Mencoder expert
On Saturday 16 January 2010 20:13:34 Neil Short wrote: I have a VOB file that I need to convert to something playable on a Sony Walkman NWZ-E344. The walkman wants an ASF container, resolution of 320x240 (or less), wmv9 codec, wma 2 codec, 30 frames per second, video bitrate of less than or equal to 768k. If it only accepts WMV3 (Windows Media Video 9) then you're out of luck. FFmpeg, and by extension, mencoder, do not support WMV3 encoding. There appears to be a patch floating around on the internet which adds WMV3 encoding support to ffmpeg, but it is at least 2 years old... You can try WMV2 or even WMV1 (Windows Media Video 8 and 7 respectively). Both are supported by ffmpeg: ffmpeg -i somevideo -vcodec wmv2 -acodec wmav2 -b 768k -s qvga test.asf - Pieter I cannot seem to get a mencoder (nor ffmpeg) encoding line to work. Here's some data on a video that works: $ ffmpeg -i Butterfly.wmv [wmv3 @ 0x29707c10]Extra data: 8 bits left, value: 0 Seems stream 1 codec frame rate differs from container frame rate: 1000.00 (1000/1) - 29.97 (3/1001) Input #0, asf, from 'Butterfly.wmv': Duration: 00:00:08.21, start: 5.00, bitrate: 1126 kb/s Stream #0.0: Audio: wmav2, 44100 Hz, stereo, s16, 96 kb/s Stream #0.1: Video: wmv3, yuv420p, 320x208, 768 kb/s, 29.97 tbr, 1k tbn, 1k tbc mplayer -identify Butterfly.wmv Playing Butterfly.wmv. ASF file format detected. ID_AUDIO_ID=1 [asfheader] Audio stream found, -aid 1 ID_VIDEO_ID=2 [asfheader] Video stream found, -vid 2 VIDEO: [WMV3] 320x208 24bpp 1000.000 fps 768.0 kbps (93.8 kbyte/s) ID_FILENAME=Butterfly.wmv ID_DEMUXER=asf ID_VIDEO_FORMAT=WMV3 ID_VIDEO_BITRATE=768000 ID_VIDEO_WIDTH=320 ID_VIDEO_HEIGHT=208 ID_VIDEO_FPS=1000.000 ID_VIDEO_ASPECT=0. ID_AUDIO_FORMAT=353 ID_AUDIO_BITRATE=0 ID_AUDIO_RATE=0 ID_AUDIO_NCH=0 ID_LENGTH=15.00 Opening video filter: [screenshot=yes] == Requested video codec family [wmv9dmo] (vfm=dmo) not available. Enable it at compilation. Requested video codec family [wmvdmo] (vfm=dmo) not available. Enable it at compilation. Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family [wmv3 @ 0x882b6f0]Extra data: 8 bits left, value: 0 Selected video codec: [ffwmv3] vfm: ffmpeg (FFmpeg M$ WMV3/WMV9) == ID_VIDEO_CODEC=ffwmv3 == Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 96.0 kbit/6.81% (ratio: 12005-176400) ID_AUDIO_BITRATE=96040 ID_AUDIO_RATE=44100 ID_AUDIO_NCH=2 Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg)) == AO: [oss] 44100Hz 2ch s16le (2 bytes per sample) ID_AUDIO_CODEC=ffwmav2 Starting playback... VDec: vo config request - 320 x 208 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. [swscaler @ 0x8827710]SwScaler: using unscaled yuv420p - bgr24 special converter VO: [xv] 320x208 = 320x208 Planar YV12 New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). subtitle font: load_sub_face failed. == What did you do? the man holding the flashlight asked. I put down a spider, he said, wondering why the man didn't see; in the beam of yellow light the spider bloated up larger than life. So it could get away. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Errors on UFS Partitions
Hi, I am sorry if I am asking a question that might have been brought up before I have attempted to research my issue but it has many angles it might be listed under so please bare with me. We have had ongoing problems with UFS Errors on our root partition (and any additional partition that did not have soft-updates enabled by default) and we recently had a problem with a secondary drive that housed home directories completely filled up and then everything locked up due-to huge CPU and Memory usage because nothing was able to write to the drive but when the server was rebooted it failed to bootup because of critical errors on the root partition. We have /etc and /usr on the root partition and our home/var partitions mistakenly do not have soft-updates flag set. ::dmesg:: http://the-irc.com/dmesg ::mount:: /dev/ad4s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/ad4s1d on /home (ufs, local, with quotas) /dev/ad4s1e on /tmp (ufs, local, noexec, nosuid, soft-updates) /dev/ad4s1f on /var (ufs, local) devfs on /var/named/dev (devfs, local, multilabel) procfs on /proc (procfs, local) /dev/ad0s1e on /Backups (ufs, local, soft-updates) /dev/ad0s1d on /root (ufs, local, soft-updates) ::fsck /:: ** /dev/ad4s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=361477 OWNER=root MODE=100666 SIZE=144464 MTIME=Jan 1 03:59 2010 CLEAR? no UNREF FILE I=966786 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 15 23:02 2010 CLEAR? no ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no 549534 files, 4784719 used, 2830920 free (47200 frags, 347965 blocks, 0.6% fragmentation) ::fsck /home:: ** /dev/ad4s1d (NO WRITE) ** Last Mounted on /home ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=1957573 (4 should be 0) CORRECT? no INCORRECT BLOCK COUNT I=10270973 (300 should be 0) CORRECT? no INCORRECT BLOCK COUNT I=10270976 (44 should be 0) CORRECT? no INCORRECT BLOCK COUNT I=10271040 (48 should be 0) CORRECT? no INCORRECT BLOCK COUNT I=11871624 (4 should be 0) CORRECT? no ** Phase 2 - Check Pathnames UNALLOCATED I=732010 OWNER=agrippas MODE=100600 SIZE=33868 MTIME=Jan 16 19:05 2010 FILE=/agrippas/services/lib/akill.db REMOVE? no UNALLOCATED I=4545818 OWNER=port1080 MODE=100600 SIZE=2052 MTIME=Jan 16 19:06 2010 FILE=/port1080/services/nick.db REMOVE? no ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=730879 OWNER=agrippas MODE=100664 SIZE=3020510 MTIME=Jan 16 18:54 2010 CLEAR? no LINK COUNT FILE I=732011 OWNER=agrippas MODE=0 SIZE=0 MTIME=Jan 16 19:05 2010 COUNT 0 SHOULD BE -1 ADJUST? no UNREF FILE I=2359889 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2359928 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2359930 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2359931 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2359932 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2359934 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360094 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360101 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360103 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360104 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360118 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360121 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360122 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360123 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 10 17:20 2010 CLEAR? no UNREF FILE I=2360124 OWNER=killjoyr MODE=100600 SIZE=0 MTIME=Jan 11 00:02 2010 CLEAR? no UNREF FILE I=2920477 OWNER=marianus MODE=100644 SIZE=6 MTIME=Jan 2 20:27 2010 CLEAR? no UNREF FILE I=2920480 OWNER=marianus MODE=100644 SIZE=6 MTIME=Jan 2 20:27 2010 CLEAR? no LINK COUNT FILE I=4545817 OWNER=port1080 MODE=0 SIZE=0 MTIME=Jan 16 19:06 2010 COUNT 0 SHOULD BE -1 ADJUST? no UNREF FILE I=6267525 OWNER=chijiru MODE=100644 SIZE=5 MTIME=Jan 2 10:05 2010 CLEAR? no UNREF FILE I=6760292 OWNER=jibbanet MODE=100644 SIZE=6 MTIME=Jan 10 20:21 2010 CLEAR? no UNREF FILE I=7089454 OWNER=talkingi MODE=100600 SIZE=0 MTIME=Jan 10 22:22 2010 CLEAR? no UNREF FILE I=8668793 OWNER=mutrcom MODE=100660 SIZE=1074 MTIME=Jan 8 14:32 2010 CLEAR? no UNREF FILE I=9752529 OWNER=gigircco MODE=100600 SIZE=0 MTIME=Jan 11 00:25 2010 CLEAR? no UNREF FILE I=9752883 OWNER=gigircco MODE=100600 SIZE=18 MTIME=Jan 12 00:04 2010 CLEAR?
Re: Server set up
Chad Perrin wrote: On Fri, Jan 15, 2010 at 04:34:17PM -0600, Kevin Kinsey wrote: NTFS comes with NT versions of Windows, that is, NT, Windows 2000, and everything since then. W95 and W98 used FAT filesystems. Fat32 was the default for Win98 IIRC. I know a lot of MS Windows users like to pretend WinME never existed, but I like to think those of us in the FreeBSD community take a more honest look at the world. Thus, for the sake of clarity: NTFS comes with NT versions of Windows -- that is, WinNT, Win2K, WinXP, and everything since then. Win95, Win98, and WinME used FAT filesystems. I wouldn't want anyone to make some kind of grave error involving the assumption that WinME used NTFS. . . . ROFL. I don't think I was being dishonest, certainly not intentionally. I did recently purchase a small notebook with Windows 7 installed. I may have had my head infected by the Marketroid virus as a result. :-D So, yes Virginia, there was one further release with the (DOS-based?) Windows kernel, named WinME. Now, to be real pedantic, there was Windows 3.1 before Windows95, and before that, Windows 3.0, 2.1, 2.0, 1.0, and Interface Manager. I'm feeling kinda sick now ... so, no more ROFL, maybe ROLF instead? Fi`ni. Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Errors on UFS Partitions
In the last episode (Jan 16), The-IRC FreeBSD said: I am sorry if I am asking a question that might have been brought up before I have attempted to research my issue but it has many angles it might be listed under so please bare with me. We have had ongoing problems with UFS Errors on our root partition (and any additional partition that did not have soft-updates enabled by default) and we recently had a problem with a secondary drive that housed home directories completely filled up and then everything locked up due-to huge CPU and Memory usage because nothing was able to write to the drive but when the server was rebooted it failed to bootup because of critical errors on the root partition. We have /etc and /usr on the root partition and our home/var partitions mistakenly do not have soft-updates flag set. ::dmesg:: http://the-irc.com/dmesg ::mount:: /dev/ad4s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/ad4s1d on /home (ufs, local, with quotas) /dev/ad4s1e on /tmp (ufs, local, noexec, nosuid, soft-updates) /dev/ad4s1f on /var (ufs, local) devfs on /var/named/dev (devfs, local, multilabel) procfs on /proc (procfs, local) /dev/ad0s1e on /Backups (ufs, local, soft-updates) /dev/ad0s1d on /root (ufs, local, soft-updates) ::fsck /:: ** /dev/ad4s1a (NO WRITE) fsck'ing a filesystem that is currently mounted read-write will always produce errors. Boot in single-user mode if you want to check the root filesystem or other fs'es that you can't dismount in multi-user mode. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Errors on UFS Partitions
The-IRC FreeBSD wrote: Hi, I am sorry if I am asking a question that might have been brought up before I have attempted to research my issue but it has many angles it might be listed under so please bare with me. We have had ongoing problems with UFS Errors on our root partition (and any additional partition that did not have soft-updates enabled by default) and we recently had a problem with a secondary drive that housed home directories completely filled up and then everything locked up due-to huge CPU and Memory usage because nothing was able to write to the drive but when the server was rebooted it failed to bootup because of critical errors on the root partition. A healthy system does not get UFS errors during normal operation. We have /etc and /usr on the root partition and our home/var partitions mistakenly do not have soft-updates flag set. ::dmesg:: http://the-irc.com/dmesg ::mount:: /dev/ad4s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/ad4s1d on /home (ufs, local, with quotas) /dev/ad4s1e on /tmp (ufs, local, noexec, nosuid, soft-updates) /dev/ad4s1f on /var (ufs, local) devfs on /var/named/dev (devfs, local, multilabel) procfs on /proc (procfs, local) /dev/ad0s1e on /Backups (ufs, local, soft-updates) /dev/ad0s1d on /root (ufs, local, soft-updates) [snip] To prevent letting these errors go out of control and not beable to fix the root partition errors without going into singleuser mode and the other partitions by mounting them with soft-updates flag, does anyone advise removing everything from the root partition and only leaving the bootloader and thus moving /etc and /usr (or most of all just /usr) to it's own partition or do you guys have a better solution. No. Proceeding in directions such as this is a waste of time. Every partition gets errors over time but if you are unable to correct them without downtime how are you to correct them before they get out of control? Probably by not looking for a software solution to a hardware problem. It is not normal for a file system to behave as you describe. Moving partitions around and other such avenues of approach are doomed to failure as they are not addressing the underlying problem. Real server hardware with sophisticated ECC subsystems usually have some BIOS counters which you can check for stats on memory errors. Hard drives fail the most often but either bad memory or drive controller can readily corrupt data. If you have a RAID controller with RAM cache the RAM could be defective. Hardware failure is going to mean downtime. But I'd be looking for a hardware problem, get it fixed, then worry about how to proceed. If you have decent backups from before the system was corrupted you can get back to where you need to be in relatively short order. Not fixing a hardware defect will result in you never getting your server back to normal operation. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dislike the way port conflicts are handled now
On Sat, 16 Jan 2010 18:08:30 -0600 Kirk Strauser k...@strauser.com wrote: On 01/16/2010 02:26 PM, Pav Lucistnik wrote: What is the particular scenario that the new conflicts handling broke for you? Often you really want to ignore locally installed packages and then it's better to override LOCALBASE to /nonex or something similar, instead of disabling conflict handling.. Pav, I'm the OP, and described the problem in the first post. To recap, though, say I want to upgrade from the databases/mysql50-client port to databases/mysql51-client. Without taking extra steps such as using -DDISABLE_CONFLICTS or removing the CONFLICTS definition from the Makefile, I can't even start downloading the distfiles (using make fetch) until I pkg_delete the old version. With the old system, I could do everything up through building the new port so that the time between running pkg_delete and make reinstall is minimized. Is it so hard to type make -DDISABLE_CONFLICTS fetch to, fetch and make -DDISABLE_CONFLICTS to build - given that this is something that's rarely needed. When I first read this it sounded bad, but the more I think about it the more I think the change is sensible. If it bothers you that much why don't you just alias make -DDISABLE_CONFLICTS to make-anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: OOo question.....
On Sat, Jan 16, 2010 at 10:27:59AM +, Mike Clarke wrote: On Saturday 16 January 2010, Gary Kline wrote: this may be offtopic but it does deal with our OO.org port. a friend sent me a very nice slideshow in powerpoint format. I've saved it (and the original) somewhere in the evolution directory so all the photos are safe. first question is: can I save an individial image using Openoffice? Select the slide then right click on the image and select Save as Picture near the bottom of the menu. If you're lucky this will work - I've tried this with 3 different MS Powerpoint files and it worked fine with two of them but didn't even give me the Save as Picture option with the other one :-( I found out that the save as picture is a right-click that sometimes works, and siometimes does NOT. [??] also that there is also sometimes the option in the dropdown or pop-up menu (with the right click) that lets you save as a bitmap. xxx.PNG. so, nutshell, I was albe to save three of the ones I liked most. it took me long enough. I did check OOoforum, but nothing there. your info plus my own messing around let me get the job done. [[well, mostly!]] Second q is howto use them for my desktop backgrounds in KDE since, upon rebuild and relaunch, everything is black. the first question is howto save a separate image? or are there other tools to do this? [neither xv nor gv work] Right click on a blank piece of the KDE desktop and select Configure Desktop. This should open with the Change the background settings icon highlighted. In the Background section click the Picture radio button and click the folder icon on the right to browse to your selected image. (Several hours later). I found the place and added three 'wallpapers'; they haven't appeared. Probably will after I've rebooted. ---I see that my newest KDE is 3.5.10. Sometime this year I'll try KDE4 again.-- Meanwhile, thanks for your help! -- Mike Clarke -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.79a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: To jail, or not to jail?
I've been having fun playing with jails on my home server. There's one for databases, one for a webserver, another for using as a play shell server, etc. We use jails heavily at work for encapsulating services, and I can make a pretty good argument there for doing so. In general, though, do you see jails as particularly important or useful when not in a hosting environment where you're giving root access to an untrusted party? How far do you go toward segregating services? Theoretically, you could have a jail per daemon, but it seems like down that path lies madness. -- Kirk Strauser For home machine, I don't use any jails. All services run on host system. Not in a hosting environment with zero untrusted users, I still use 'jail'. I can always build 'newjail' duplicate services on it, test, and very quick switch from 'oldjail' to 'newjail' when all tests come back clean. Gives me a lot more room to play around/break things without effecting running services. Try not to have any services on the host system to keep it completely clean, easy upgrade as I can wipe the OS out [or move HD to new server], reinstall, mount the jails/zfs and have a running system in minutes. ]Peter[ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Errors on UFS Partitions
Thanks everyone for their input it has helped greatly. Does anyone know a way to toggle soft-updates on a UFS non-root partition while the system is live or without having to recreate the partition? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Errors on UFS Partitions
On Sun, Jan 17, 2010 at 12:30:09AM -0500, The-IRC FreeBSD wrote: Thanks everyone for their input it has helped greatly. Does anyone know a way to toggle soft-updates on a UFS non-root partition while the system is live or without having to recreate the partition? Sure. Use the tunefs(8) utility for this. (Note that it cannot be used on a filesystem which is mounted read-write.) -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
