Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo]
Andrey Chernov wrote: On Sun, Jun 15, 2008 at 09:17:01PM +0200, K?vesd?n G?bor wrote: Yes, of course, I haven't forgotten about your suggestion. First, I'd like to process the trivial errors, which come up like this one and make some tests myself. Then I'll think about this idea and ask portmgr to do an exp-run with BSD grep. I think that would be very valuable. Please note that BSD grep is not localized (and can't be per design) and works only with standard C locale. It may not affect ports system processing but shurely affects real texts handling. That is very troubling. In this day and age localization is a requirement. I cannot imagine being supportive of adding something to the base that does not have this capability. I also found another gratuitous difference in behavior tonight, again from portmaster (which uses grep a LOT, which is why I thought to try it out in the first place). I do this type of thing in lots of places: pkg=/var/db/pkg/p5-Net-DNS-0.63 if grep -ql '[EMAIL PROTECTED] ' $pkg/+CONTENTS 2>/dev/null; then fi With gnu grep I get no output, and if there is a match the if statement just runs as I'd expect. With bsd grep I'm getting the name of the file as output. That's 3 strikes and you're out as far as I'm concerned. I think this project needs to come a lot closer to feature compatibility with gnu grep (including the ability to be localized) before it's ready for a wider audience. Of course, that's just my opinion. Doug -- This .signature sanitized for your protection ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo]
On Sun, Jun 15, 2008 at 2:26 PM, Andrey Chernov <[EMAIL PROTECTED]> wrote: > On Sun, Jun 15, 2008 at 09:17:01PM +0200, K?vesd?n G?bor wrote: >> >> Yes, of course, I haven't forgotten about your suggestion. First, I'd >> like to process the trivial errors, which come up like this one and make >> some tests myself. Then I'll think about this idea and ask portmgr to do >> an exp-run with BSD grep. > > Please note that BSD grep is not localized (and can't be per design) and > works only with standard C locale. It may not affect ports system > processing but shurely affects real texts handling. Kudos on the hard work Gabor. Now all we need to do is write / import a BSD compatible less(1) into FreeBSD =). -Garrett ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo]
On Sun, Jun 15, 2008 at 09:17:01PM +0200, K?vesd?n G?bor wrote: > > Yes, of course, I haven't forgotten about your suggestion. First, I'd > like to process the trivial errors, which come up like this one and make > some tests myself. Then I'll think about this idea and ask portmgr to do > an exp-run with BSD grep. Please note that BSD grep is not localized (and can't be per design) and works only with standard C locale. It may not affect ports system processing but shurely affects real texts handling. -- http://ache.pp.ru/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo]
Diomidis Spinellis escribió: Doug Barton wrote: I use the following construct in portmaster, where pdb=/var/db/pkg, origin is set to the origin of a given port, and ro_opd is usually empty, but can be another origin directory or the same one. To guarantee that you should get some kind of results you can test with origin=devel/gettext. egrep -l "DEPORIGIN:($origin|$ro_opd)$" $pdb/*/+CONTENTS Obviously this works in portmaster with the gnu grep, but if ro_opd is unset with the bsd grep I get: egrep: empty (sub)expression To avoid these problems I had proposed to instrument getopt to write options passed through argv in a file, build all our ports, and look at the options used. Yes, of course, I haven't forgotten about your suggestion. First, I'd like to process the trivial errors, which come up like this one and make some tests myself. Then I'll think about this idea and ask portmgr to do an exp-run with BSD grep. Regards, -- Gabor Kovesdan EMAIL: [EMAIL PROTECTED] WWW: http://www.kovesdan.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AMD Geode LX crypto accelerator (glxsb)
On Sat, 14 Jun 2008 19:03:51 +0200 Patrick Lamaizière <[EMAIL PROTECTED]> mentioned: > > Sources (7-STABLE): > http://user.lamaiziere.net/patrick/glxsb-140608.tar.gz > > (Yes this is the good version!) > > If you can test it and provide some review it would be nice. > Small note about the manpage: I think we don't need the netbsd porting information in AUTHORS section, also you missed a dot in the end of last sentence in HISTORY section. -- Stanislav Sedov ST4096-RIPE pgpJ6rr8tinjB.pgp Description: PGP signature
Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo]
Doug Barton escribió: I use the following construct in portmaster, where pdb=/var/db/pkg, origin is set to the origin of a given port, and ro_opd is usually empty, but can be another origin directory or the same one. To guarantee that you should get some kind of results you can test with origin=devel/gettext. egrep -l "DEPORIGIN:($origin|$ro_opd)$" $pdb/*/+CONTENTS Obviously this works in portmaster with the gnu grep, but if ro_opd is unset with the bsd grep I get: egrep: empty (sub)expression If I set ro_opd to something, it works. Hello Doug, thanks a lot for you response! I'll look at this issue. Regards, -- Gabor Kovesdan EMAIL: [EMAIL PROTECTED] WWW: http://www.kovesdan.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: UPS shutdown with `sysutils/nut': where should I place "power off" command to UPS?
Hello, Erik. You wrote 15 июня 2008 г., 20:22:47: > You need an UPS that can accept a signal that says 'shut down in 20 seconds > time' (the value 20 may have to be adjusted) and send that as the last thing > in the shutdown scripts, which should cause the UPS to shutdown shortly > after 'shutdown -p' has turned off the computer. It seems, that my Ippon Smart Power Pro/1000 understand such commands: it can turn off load after 2 minutes, and I'll try to change this value. Great. -- // Black Lion AKA Lev Serebryakov <[EMAIL PROTECTED]> ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UPS shutdown with `sysutils/nut': where should I place "power off" command to UPS?
On Sun, Jun 15, 2008 at 07:08:10PM +0400, Lev Serebryakov wrote: > Hello, freebsd-hackers. > > nut's documentation says[1], that UPS should be switched off from > shutdown scripts in point, when FSes are synced and re-mounted as R/O. Problem is, on FreeBSD the FSes are not re-mounted as R/O during shutdown. > > google shows thread[2], according to which, last line of > `/etc/rc.shutdown' is too early, and if power will be switched off at > this line, FSes will be dirty on boot. Correct. > > What is proper place for "power off" command on FreeBSD system? There isn't any. On FreeBSD the filesystems are synced and marked as clean by the kernel, *after* all the shutdown scripts have finished. (Unlike Linux where the shutdown scripts are responsible for syncing and umounting/re-mounting the file systems.) > > Please, note, that it is NOT `shutdown -p', but signal to UPS to > switch off EXTERNAL power when battarey is almost dead, and no > external power, and `shutdown -p' turns off only computer, not UPS. You need an UPS that can accept a signal that says 'shut down in 20 seconds time' (the value 20 may have to be adjusted) and send that as the last thing in the shutdown scripts, which should cause the UPS to shutdown shortly after 'shutdown -p' has turned off the computer. > > > [1] http://www.networkupstools.org/doc/2.2.0/shutdown.html > [2] http://lists.freebsd.org/pipermail/freebsd-questions/2006-May/122764.htm > -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
UPS shutdown with `sysutils/nut': where should I place "power off" command to UPS?
Hello, freebsd-hackers. nut's documentation says[1], that UPS should be switched off from shutdown scripts in point, when FSes are synced and re-mounted as R/O. google shows thread[2], according to which, last line of `/etc/rc.shutdown' is too early, and if power will be switched off at this line, FSes will be dirty on boot. What is proper place for "power off" command on FreeBSD system? Please, note, that it is NOT `shutdown -p', but signal to UPS to switch off EXTERNAL power when battarey is almost dead, and no external power, and `shutdown -p' turns off only computer, not UPS. [1] http://www.networkupstools.org/doc/2.2.0/shutdown.html [2] http://lists.freebsd.org/pipermail/freebsd-questions/2006-May/122764.htm -- // Black Lion AKA Lev Serebryakov <[EMAIL PROTECTED]> ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo]
Doug Barton wrote: I use the following construct in portmaster, where pdb=/var/db/pkg, origin is set to the origin of a given port, and ro_opd is usually empty, but can be another origin directory or the same one. To guarantee that you should get some kind of results you can test with origin=devel/gettext. egrep -l "DEPORIGIN:($origin|$ro_opd)$" $pdb/*/+CONTENTS Obviously this works in portmaster with the gnu grep, but if ro_opd is unset with the bsd grep I get: egrep: empty (sub)expression To avoid these problems I had proposed to instrument getopt to write options passed through argv in a file, build all our ports, and look at the options used. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo]
I use the following construct in portmaster, where pdb=/var/db/pkg, origin is set to the origin of a given port, and ro_opd is usually empty, but can be another origin directory or the same one. To guarantee that you should get some kind of results you can test with origin=devel/gettext. egrep -l "DEPORIGIN:($origin|$ro_opd)$" $pdb/*/+CONTENTS Obviously this works in portmaster with the gnu grep, but if ro_opd is unset with the bsd grep I get: egrep: empty (sub)expression If I set ro_opd to something, it works. hth, Doug -- This .signature sanitized for your protection ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
