Use /usr/local/bin/itweb-javaws to open *.jnlp files
Dear folks, For a while I have been trying to fix an issue about opening *.jnlp files, i.e, itweb-javaws is not launching iced-tea web plugin :( I check test java installation and java is working correctly: I visit: https://www.java.com/en/download/testjava.jsp I see: Your Java configuration is as follows: Vendor: Sun Microsystems Inc. Version: Java SE 6 Update 32 Operating System: FreeBSD 9.2-RELEASE Java Architecture: 64-bit I launch *.jnlp file: I don't see anything, nothing works I want to launch gradebook application: $ /usr/local/bin/itweb-javaws --help Your custom JRE /usr/local/openjdk6 read from deployment.properties under key deployment.jre.dir as /usr/local/openjdk6 is not valid. Using default (/usr/local/openjdk6/jre/bin/java, /usr/local/openjdk6/jre/lib/rt.jar) in attempt to start. Please fix this. Error: could not find libjava.so Error: could not find Java 2 Runtime Environment. ___ 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: Re: # portmaster -r pixman fails with !#/bin/sh list too long
On 10/03/2013 20:28, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Is it vital to use the texlive ports you get via portshaker or could you switch to TEX_DEFAULT=texlive and use the texlive 2012 from official ports (which has a few huge instead of many tiny packages)? (If you want to switch, remove everything starting with texlive, check out a fresh ports tree without portshaker, since there is at least one port with the same name, and install print/texlive-full and maybe print/texlive-docs.) Cheers, Jan Henrik ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Thu, 3 Oct 2013, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Careful: -R has a different meaning with portmaster than it does with portupgrade. It does not mean recursive like lowercase -r. pkg_libchk from sysutils/bsdadminscripts can be used to detect installed ports that depend on missing libraries. From that, it may be possible to just give a list of all the ones that are missing pixman to portmaster. ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Fri, Oct 4, 2013 at 12:09 PM, Warren Block wbl...@wonkity.com wrote: On Thu, 3 Oct 2013, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Careful: -R has a different meaning with portmaster than it does with portupgrade. It does not mean recursive like lowercase -r. pkg_libchk from sysutils/bsdadminscripts can be used to detect installed ports that depend on missing libraries. From that, it may be possible to just give a list of all the ones that are missing pixman to portmaster. Dear all, It appears that using # portmaster -d -r pixman -x 'texlive-*-*' is doing the job :) I am keeping my fingers crossed and hope it comes through and succeeds! It stopped with libexo, but got that sorted out. Then stopped with mplayer*, but I am skipping it at this time. -x 'mplayer-*' and hope it succeeds, I'll then rebuild mplayer later if needed. Best Regards, Antonio ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Tue, Oct 1, 2013 at 8:46 AM, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
Antonio Olivares olivares14...@gmail.com writes:
I tried your advice with the -R option, it worked, but for only pixman
the other ports that depend on it don't get rebuilt :(
I try to use -x 'texlive-*' but it does not work :(
I get
Could not execute shell
/usr/ports/Mk/bsd.port.mk, line 1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry in /usr/src/UPDATING :(
Please advice me as to how to get the desktop working again on these
machines. I did not want to shoot myself in the foot but I did so :(
Try the '-R' again; it may get a bit farther each time.
You can always recover by removing some of the ports and reinstalling
them after the remaining ports are updated. You're going to have to
rebuild a huge number of ports anyway, so this is not very different
from using portmaster on everything.
Good luck.
Have tried that, but it rebuilds pixman, but then X bombs out blurting
out messages that libpixman.so is missing :(
I have tried to remove print/texlive-scheme-full; removed it, but then
run portmaster -R pixman, and portmaster -r pixman and the running of
it stops with message that !#/bin/sh .. argument too long and comes up
with texlive-?-?-_1 or similar. Have not been successful in
fixing this issue. I have 2 machines working and 2 not working
because of this. I am running out of ideas. Is there another way to
fix this issue manually, i.e, going to /usr/ports/x11/pixman and
rebuilding it there or have to go one by one?
Thanks for your advice and suggestions but I am not getting there :(
Best Regards,
Antonio
___
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: # portmaster -r pixman fails with !#/bin/sh list too long
Antonio Olivares olivares14...@gmail.com writes: Dear folks, In updating ports I encounter above issue and cannot proceed. 20130929: AFFECTS: users of x11/pixman AUTHOR: zeis...@freebsd.org The library version of x11/pixman has changed, and portrevision has been bumped in all dependent ports. If you have external software that depends on pixman, this software needs to be recompiled. To recompile all software dependent on pixman, run: # portmaster -r pixman or # portupgrade -rf pixman The messages are that a pkg texlive-ub* and that #!/bin/sh list too long. I try to run # portmaster -d -r pixman -x 'texlive-*' but it still fails in the same place :( I continued with portmaster's -R option and got a lot further. You could try either that or the command line that portmaster suggests when it bails out. I am using texlive-freebsd from Romain Tartiere's googlecode page in case it is important. Please advice me so I can succeed to fix these issue. I lost X because I failed to read the /usr/src/UPDATING advice and then I realized that I overlooked this :( I don't think that texlive is relevant; if you continue the process instead of starting from scratch, you'll probably get farther. I'd prefer to actually debug the problem at its root, but it's the middle of the night and I don't seem to have enough brain cells awake to figure anything out. Good luck. ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
Dear Sir,
I tried your advice with the -R option, it worked, but for only pixman
the other ports that depend on it don't get rebuilt :(
I try to use -x 'texlive-*' but it does not work :(
I get
Could not execute shell
/usr/ports/Mk/bsd.port.mk, line 1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry in /usr/src/UPDATING :(
Please advice me as to how to get the desktop working again on these
machines. I did not want to shoot myself in the foot but I did so :(
Best Regards,
Antonio
On Tue, Oct 1, 2013 at 1:27 AM, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
Antonio Olivares olivares14...@gmail.com writes:
Dear folks,
In updating ports I encounter above issue and cannot proceed.
20130929:
AFFECTS: users of x11/pixman
AUTHOR: zeis...@freebsd.org
The library version of x11/pixman has changed, and portrevision has
been bumped in all dependent ports. If you have external software that
depends on pixman, this software needs to be recompiled.
To recompile all software dependent on pixman, run:
# portmaster -r pixman
or
# portupgrade -rf pixman
The messages are that a pkg texlive-ub* and that #!/bin/sh list
too long. I try to run
# portmaster -d -r pixman -x 'texlive-*'
but it still fails in the same place :(
I continued with portmaster's -R option and got a lot further. You
could try either that or the command line that portmaster suggests
when it bails out.
I am using texlive-freebsd from Romain Tartiere's googlecode page in
case it is important. Please advice me so I can succeed to fix these
issue. I lost X because I failed to read the /usr/src/UPDATING advice
and then I realized that I overlooked this :(
I don't think that texlive is relevant; if you continue the process
instead of starting from scratch, you'll probably get farther.
I'd prefer to actually debug the problem at its root, but it's the
middle of the night and I don't seem to have enough brain cells awake
to figure anything out.
Good luck.
___
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: # portmaster -r pixman fails with !#/bin/sh list too long
Antonio Olivares olivares14...@gmail.com writes:
I tried your advice with the -R option, it worked, but for only pixman
the other ports that depend on it don't get rebuilt :(
I try to use -x 'texlive-*' but it does not work :(
I get
Could not execute shell
/usr/ports/Mk/bsd.port.mk, line 1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry in /usr/src/UPDATING :(
Please advice me as to how to get the desktop working again on these
machines. I did not want to shoot myself in the foot but I did so :(
Try the '-R' again; it may get a bit farther each time.
You can always recover by removing some of the ports and reinstalling
them after the remaining ports are updated. You're going to have to
rebuild a huge number of ports anyway, so this is not very different
from using portmaster on everything.
Good luck.
___
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
# portmaster -r pixman fails with !#/bin/sh list too long
Dear folks, In updating ports I encounter above issue and cannot proceed. 20130929: AFFECTS: users of x11/pixman AUTHOR: zeis...@freebsd.org The library version of x11/pixman has changed, and portrevision has been bumped in all dependent ports. If you have external software that depends on pixman, this software needs to be recompiled. To recompile all software dependent on pixman, run: # portmaster -r pixman or # portupgrade -rf pixman The messages are that a pkg texlive-ub* and that #!/bin/sh list too long. I try to run # portmaster -d -r pixman -x 'texlive-*' but it still fails in the same place :( I am using texlive-freebsd from Romain Tartiere's googlecode page in case it is important. Please advice me so I can succeed to fix these issue. I lost X because I failed to read the /usr/src/UPDATING advice and then I realized that I overlooked this :( Best Regards, Antonio ___ 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
/compat/linux/usr/bin/ldd always reports not a dynamic executable
I am on FreeBSD 9.1, and I'm trying to use /compat/linux/usr/bin/ldd to tell me what libraries are needed by libpython2.7.so, a library obtained from a linux system. But all I get is not a dynamic executable. In fact, the same thing happens if I run this ldd on a library in /compat/linux/lib: [ko@wiley /compat/linux/lib]$ /compat/linux/usr/bin/ldd -v libc-2.9.so not a dynamic executable [ko@wiley /compat/linux/lib]$ What is going on?Thanks for any help. Kostas ___ 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
Unusual file: /bin/[
Hi, I spotted what i'd call an unusual file in the basejail on a jail install, and have since seen this on other non jailed boxes. -r-xr-xr-x 2 root wheel 11488 Jun 10 12:19 [ man [ reveals test, [ -- condition evaluation utility just checking thats all ok, and i've not been rooted! -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA High Specification Dedicated Servers from £100.00pm ___ 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: Unusual file: /bin/[
On 07/29/13 15:25, Paul Macdonald wrote: Hi, I spotted what i'd call an unusual file in the basejail on a jail install, and have since seen this on other non jailed boxes. -r-xr-xr-x 2 root wheel 11488 Jun 10 12:19 [ That's a perfectly valid UNIX program used in (bourne) shell programming. It has been part of BSD Unix for ages. And I really mean AGES! just checking thats all ok, and i've not been rooted! Don't worry about it. It's perfectly legitimate. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: Unusual file: /bin/[
That's a real binary, also known as /bin/test ___ 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: Unusual file: /bin/[
On Mon, 29 Jul 2013 14:25:08 +0100, Paul Macdonald wrote:
Hi, I spotted what i'd call an unusual file in the basejail on a jail
install, and have since seen this on other non jailed boxes.
-r-xr-xr-x 2 root wheel 11488 Jun 10 12:19 [
man [ reveals
test, [ -- condition evaluation utility
just checking thats all ok, and i've not been rooted!
The [ program is the same as the test program. It's
a valid file name and it's often used in shell scripts
instead of test.
% ll /bin/test /bin/\[
-r-xr-xr-x 2 root wheel 8336 2011-08-21 20:23:20 /bin/[*
-r-xr-xr-x 2 root wheel 8336 2011-08-21 20:23:20 /bin/test*
Consider shell scripts. When you have a script with something like
if [ -f bla.txt ]; then
... some stuff ...
fi
it is the same as
if test -f bla.txt; then
... some stuff ...
fi
It's also often being used like
[ -x blah.sh ] do_something
which is identical to calling test and acting upon the value
of the return code.
Nothing to worry here.
YOu can _always_ counter-check by building /usr/src/bin/test
from source and compare the resulting binary. Both /bin/[
and /bin/test are usually installed as hardlinks (two file
names for one / for _the same_ file), as seen in the
corresponding Makefile:
LINKS= ${BINDIR}/test ${BINDIR}/[
So it's not _that_ unusual. ;-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: Unusual file: /bin/[
On Mon, 29 Jul 2013 14:25:08 +0100
Paul Macdonald wrote:
Hi, I spotted what i'd call an unusual file in the basejail on a jail
install, and have since seen this on other non jailed boxes.
-r-xr-xr-x 2 root wheel 11488 Jun 10 12:19 [
man [ reveals
test, [ -- condition evaluation utility
just checking thats all ok, and i've not been rooted!
The idea was to make shell scripts more readable as you can have
something like:
if [ ${x} -gt 1 ] ...
[ is a hard-link to /bin/test and the closing] ] is its last argument.
In most modern shells its a builtin feature and /bin/[ isn't used.
___
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: Unusual file: /bin/[
On Mon, 29 Jul 2013 15:45:10 +0200 cpghost cpgh...@cordula.ws wrote: On 07/29/13 15:25, Paul Macdonald wrote: Hi, I spotted what i'd call an unusual file in the basejail on a jail install, and have since seen this on other non jailed boxes. -r-xr-xr-x 2 root wheel 11488 Jun 10 12:19 [ That's a perfectly valid UNIX program used in (bourne) shell programming. It has been part of BSD Unix for ages. And I really mean AGES! grin I recall someone deciding that /bin/[ looked iffy and deleted it from a FreeBSD 1.1.5.1 box busy serving connections to a bunch of dial up users. An amazing number of things stopped working. -- Steve O'Hara-Smith st...@sohara.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
/usr/bin/ld: cannot find -liconv
Hi, I'm trying to compile FreePascal from sources, but it keeps complaining about cannot find -liconv: When I do gmake all on fpc src directory, I get this: Output of ldconfig -r|grep iconv: 19:-lkiconv.4 = /lib/libkiconv.so.4 112:-liconv.3 = /usr/local/lib/libiconv.so.3 433:-lbiconv.2 = /usr/local/lib/libbiconv.so.2 434:-lticonv.6 = /usr/local/lib/libticonv.so.6 Output of gmake all: ... /usr/bin/ld: cannot find -liconv fpdoc.pp(404,1) Error: Error while linking fpdoc.pp(404,1) Fatal: There were 1 errors compiling module, stopping Fatal: Compilation aborted gmake[3]: *** [fpdoc] Error 1 gmake[3]: Leaving directory `/usr/home/martin/fpc/utils/fpdoc' gmake[2]: *** [fpdoc_all] Error 2 gmake[2]: Leaving directory `/usr/home/martin/fpc/utils' gmake[1]: *** [utils_all] Error 2 gmake[1]: Leaving directory `/usr/home/martin/fpc' gmake: *** [build-stamp.x86_64-freebsd] Error 2 This is a FreeBsd 9.1 RELEASE x86-64 machine. What I'm doing wrong?. Leonardo M. Ramé http://leonardorame.blogspot.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: /usr/bin/ld: cannot find -liconv
- Original Message - From: Leonardo M. Ramé martinr...@yahoo.com To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Cc: Sent: Sunday, January 27, 2013 12:28 PM Subject: /usr/bin/ld: cannot find -liconv Hi, I'm trying to compile FreePascal from sources, but it keeps complaining about cannot find -liconv: When I do gmake all on fpc src directory, I get this: Output of ldconfig -r|grep iconv: 19:-lkiconv.4 = /lib/libkiconv.so.4 112:-liconv.3 = /usr/local/lib/libiconv.so.3 433:-lbiconv.2 = /usr/local/lib/libbiconv.so.2 434:-lticonv.6 = /usr/local/lib/libticonv.so.6 Output of gmake all: ... /usr/bin/ld: cannot find -liconv fpdoc.pp(404,1) Error: Error while linking fpdoc.pp(404,1) Fatal: There were 1 errors compiling module, stopping Fatal: Compilation aborted gmake[3]: *** [fpdoc] Error 1 gmake[3]: Leaving directory `/usr/home/martin/fpc/utils/fpdoc' gmake[2]: *** [fpdoc_all] Error 2 gmake[2]: Leaving directory `/usr/home/martin/fpc/utils' gmake[1]: *** [utils_all] Error 2 gmake[1]: Leaving directory `/usr/home/martin/fpc' gmake: *** [build-stamp.x86_64-freebsd] Error 2 This is a FreeBsd 9.1 RELEASE x86-64 machine. What I'm doing wrong?. The solution was doing: gmake all OPT=-Fl/usr/local/lib Leonardo M. Ramé http://leonardorame.blogspot.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
/usr/bin/lint - bitrot?
Is /usr/bin/lint still useful to anyone? Here, even the simplest of
C programs does not parse without errors:
$ cat null.c
int main(void) { return 0; }
$ lint null.c
null.c:
lint: cannot find llib-lc.ln
Lint pass2:
$ uname -r
9.1-RC2
I'm not sure how to generate llib-lc.ln. Evidently this issue has
existed for at least 12 years if I'm reading this PR correctly:
http://www.freebsd.org/cgi/query-pr.cgi?pr=18326
Regards
Andrew
___
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: /root/bin and /usr/local/i386-portbld-freebsd9.0
I've found the two directories below on my system. I don't remember creating them. So I'd like to be able to find out what package(s) has/have created them, if possible. # ls -ld /root/bin/ drwxr-xr-x 2 root wheel 512 Aug 29 22:52 /root/bin/ # ls -Rl /root/bin/ total 0 # ls -dl /usr/local/i386-portbld-freebsd9.0 drwxr-xr-x 4 root wheel 512 Jul 8 22:32 /usr/local/i386-portbld-freebsd9.0 # ls -Rl /usr/local/i386-portbld-freebsd9.0 total 8 drwxr-xr-x 2 root wheel 512 Jul 8 22:32 bin drwxr-xr-x 3 root wheel 512 Jul 8 22:32 lib /usr/local/i386-portbld-freebsd9.0/bin: total 10816 -r-xr-xr-x 2 root wheel 604172 Jul 8 22:32 ar -r-xr-xr-x 2 root wheel 1036440 Jul 8 22:32 as -r-xr-xr-x 4 root wheel 879860 Jul 8 22:32 ld -r-xr-xr-x 4 root wheel 879860 Jul 8 22:32 ld.bfd -r-xr-xr-x 2 root wheel 3463684 Jul 8 22:32 ld.gold -r-xr-xr-x 2 root wheel 587808 Jul 8 22:32 nm -r-xr-xr-x 2 root wheel 733004 Jul 8 22:32 objcopy -r-xr-xr-x 2 root wheel 1098644 Jul 8 22:32 objdump -r-xr-xr-x 2 root wheel 604172 Jul 8 22:32 ranlib -r-xr-xr-x 2 root wheel 733004 Jul 8 22:32 strip /usr/local/i386-portbld-freebsd9.0/lib: total 4 drwxr-xr-x 2 root wheel 1024 Jul 8 22:32 ldscripts /usr/local/i386-portbld-freebsd9.0/lib/ldscripts: total 228 -r--r--r-- 1 root wheel 7375 Jul 8 22:32 elf_i386.x -r--r--r-- 1 root wheel 7158 Jul 8 22:32 elf_i386.xbn -r--r--r-- 1 root wheel 7188 Jul 8 22:32 elf_i386.xc -r--r--r-- 1 root wheel 7303 Jul 8 22:32 elf_i386.xd -r--r--r-- 1 root wheel 7133 Jul 8 22:32 elf_i386.xdc -r--r--r-- 1 root wheel 7123 Jul 8 22:32 elf_i386.xdw -r--r--r-- 1 root wheel 7375 Jul 8 22:32 elf_i386.xn -r--r--r-- 1 root wheel 4658 Jul 8 22:32 elf_i386.xr -r--r--r-- 1 root wheel 6897 Jul 8 22:32 elf_i386.xs -r--r--r-- 1 root wheel 6727 Jul 8 22:32 elf_i386.xsc -r--r--r-- 1 root wheel 6717 Jul 8 22:32 elf_i386.xsw -r--r--r-- 1 root wheel 4704 Jul 8 22:32 elf_i386.xu -r--r--r-- 1 root wheel 7178 Jul 8 22:32 elf_i386.xw -r--r--r-- 1 root wheel 7476 Jul 8 22:32 elf_i386_fbsd.x -r--r--r-- 1 root wheel 7259 Jul 8 22:32 elf_i386_fbsd.xbn -r--r--r-- 1 root wheel 7289 Jul 8 22:32 elf_i386_fbsd.xc -r--r--r-- 1 root wheel 7404 Jul 8 22:32 elf_i386_fbsd.xd -r--r--r-- 1 root wheel 7234 Jul 8 22:32 elf_i386_fbsd.xdc -r--r--r-- 1 root wheel 7224 Jul 8 22:32 elf_i386_fbsd.xdw -r--r--r-- 1 root wheel 7476 Jul 8 22:32 elf_i386_fbsd.xn -r--r--r-- 1 root wheel 4682 Jul 8 22:32 elf_i386_fbsd.xr -r--r--r-- 1 root wheel 6998 Jul 8 22:32 elf_i386_fbsd.xs -r--r--r-- 1 root wheel 6828 Jul 8 22:32 elf_i386_fbsd.xsc -r--r--r-- 1 root wheel 6818 Jul 8 22:32 elf_i386_fbsd.xsw -r--r--r-- 1 root wheel 4728 Jul 8 22:32 elf_i386_fbsd.xu -r--r--r-- 1 root wheel 7279 Jul 8 22:32 elf_i386_fbsd.xw -r--r--r-- 1 root wheel 838 Jul 8 22:32 i386bsd.x -r--r--r-- 1 root wheel 849 Jul 8 22:32 i386bsd.xbn -r--r--r-- 1 root wheel 843 Jul 8 22:32 i386bsd.xn -r--r--r-- 1 root wheel 642 Jul 8 22:32 i386bsd.xr -r--r--r-- 1 root wheel 682 Jul 8 22:32 i386bsd.xu Any pointers would be much appreciated. Alexander Kapshuk. ___ 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: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 20:23, Alexander Kapshuk wrote: I've found the two directories below on my system. I don't remember creating them. So I'd like to be able to find out what package(s) has/have created them, if possible. # ls -ld /root/bin/ drwxr-xr-x 2 root wheel 512 Aug 29 22:52 /root/bin/ # ls -Rl /root/bin/ total 0 # ls -dl /usr/local/i386-portbld-freebsd9.0 drwxr-xr-x 4 root wheel 512 Jul 8 22:32 /usr/local/i386-portbld-freebsd9.0 # ls -Rl /usr/local/i386-portbld-freebsd9.0 total 8 Which program do you use to upgrade/ build ports? http://forums.freebsd.org/showthread.php?t=21088 ___ 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: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 22:26, lokada...@gmx.de wrote: Which program do you use to upgrade/ build ports? portupgrade. I had a look at the link you'd included in your previous email. I'm still unclear as to where the two directories came from. Thanks. ___ 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: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 21:32, Alexander Kapshuk wrote: On 08/31/12 22:26, lokada...@gmx.de wrote: Which program do you use to upgrade/ build ports? portupgrade. I had a look at the link you'd included in your previous email. I'm still unclear as to where the two directories came from. Thanks. I think it comes from portupgrade. I use portmaster, but when i look at google, i found some thinks with portupgrade and portbld. I think, portbld is building for some ports, but on different places. Kick it (or rename it), look that all ok and make a upgrade, if available. If one port need it, it will create it. greetings ___ 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: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 22:41, lokada...@gmx.de wrote: I think it comes from portupgrade. I use portmaster, but when i look at google, i found some thinks with portupgrade and portbld. I think, portbld is building for some ports, but on different places. Kick it (or rename it), look that all ok and make a upgrade, if available. If one port need it, it will create it. Understood. Thanks. Any ideas about /root/bin? ___ 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: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/12 21:43, Alexander Kapshuk wrote: On 08/31/12 22:41, lokada...@gmx.de wrote: I think it comes from portupgrade. I use portmaster, but when i look at google, i found some thinks with portupgrade and portbld. I think, portbld is building for some ports, but on different places. Kick it (or rename it), look that all ok and make a upgrade, if available. If one port need it, it will create it. Understood. Thanks. Any ideas about /root/bin? Not really. It looks like an error like my tool [. I get this after i would go to head (in february?) and get back this linking. No chance to get of it. Every new buildworld will look for it. :( ___ 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: /root/bin and /usr/local/i386-portbld-freebsd9.0
On 08/31/2012 11:10 PM, lokada...@gmx.de wrote: Not really. It looks like an error like my tool [. I get this after i would go to head (in february?) and get back this linking. No chance to get of it. Every new buildworld will look for it. :( No worries. I didn't think it was there when I first installed the system. So I thought I'd ask. /root/bin/ does seem to be defined in the $PATH environment variable for the root user account in both .cshrc and .profile. Thanks for your prompt response. ___ 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
for loops with /bin/sh on command line.
I'm sure I'm being dim, but why cant I do a for loop on the command line using /bin/sh ? am I suffering from too much use of bash and as such shouldnt expect it to work? banshee# for foo in 1 2 3 ; do echo $foo ; done for: Command not found. foo: Undefined variable. banshee# echo 'for foo in 1 2 3; do echo $foo ; done' bahh.sh banshee# sh bahh.sh 1 2 3 banshee# Vince ___ 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: for loops with /bin/sh on command line.
am I suffering from too much use of bash and as such shouldnt expect it to work? maybe. i actually use bash for script. banshee# for foo in 1 2 3 ; do echo $foo ; done for: Command not found. foo: Undefined variable. banshee# echo 'for foo in 1 2 3; do echo $foo ; done' bahh.sh banshee# sh bahh.sh 1 2 3 banshee# Vince ___ 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
Re: for loops with /bin/sh on command line.
banshee# for foo in 1 2 3 ; do echo $foo ; done for: Command not found. foo: Undefined variable. banshee# echo 'for foo in 1 2 3; do echo $foo ; done' bahh.sh banshee# sh bahh.sh 1 2 3 banshee# echo $SHELL is it /bin/sh really? ___ 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: for loops with /bin/sh on command line.
On 08/07/2012 17:51, Wojciech Puchar wrote: banshee# for foo in 1 2 3 ; do echo $foo ; done for: Command not found. foo: Undefined variable. banshee# echo 'for foo in 1 2 3; do echo $foo ; done' bahh.sh banshee# sh bahh.sh 1 2 3 banshee# echo $SHELL is it /bin/sh really? Doh, yes that was it. Cant believe I forgot to check. I was running csh for no good reason. Thanks, Vince ___ 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: for loops with /bin/sh on command line.
3 banshee# echo $SHELL is it /bin/sh really? Doh, yes that was it. Cant believe I forgot to check. I was running csh for no good reason. the reason is that it is default. ___ 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
bug in /usr/bin/calendar: Thu+1 doesn't match on 7th or December
Bug report for /usr/bin/calendar SUMMARY: calendar does not match Thu+1 or Mon+1 in some months. With one exception, it looks like calendar file dates such as Thu+1 and Mon+1 are failing to match in two cases: (1) the 7th of Jan-Nov, and (2) December. DETAILS/EXAMPLES: FreeBSD crystal 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 The bug occurs whether or not the command line options below are used. I first noticed it today (a Wednesday) because a Thu+1 event tomorrow was not in calendar's output. Example 1: Thu+1 ~/.calendar/calendar: Thu+1 foo (that's Thu+1\tfoo\n in C) foreach i ( 1 2 3 4 5 6 7 8 9 10 11 12 ) calendar -t 1.$i.2011 -W 9 end Jan 6* foo Feb 3* foo Mar 3* foo - Apr 7 absent May 5* foo Jun 2* foo - Jul 7 absent Aug 4* foo Sep 1* foo Oct 6* foo Nov 3* foo - Dec 1 absent foreach i ( 1 2 3 4 5 6 7 8 9 10 11 12 ) calendar -t 1.$i.2012 -W 9 end Jan 5* foo Feb 2* foo Mar 1* foo Apr 5* foo May 3* foo - Jun 7 absent Jul 5* foo Aug 2* foo Sep 6* foo Oct 4* foo Nov 1* foo - Dec 6 absent foreach i ( 1 2 3 4 5 6 7 8 9 10 11 12 ) calendar -t 1.$i.2013 -W 9 end Jan 3* foo - Feb 7 absent - Mar 7 absent Apr 4* foo May 2* foo Jun 6* foo Jul 4* foo Aug 1* foo Sep 5* foo Oct 3* foo - Nov 7 absent - Dec 5 absent Example 2: Mon+1 foo: Mon+1 foo (Mon+1\tfoo\n) foreach i ( 1 2 3 4 5 6 7 8 9 10 11 12 ) calendar -t 1.$i.2011 -W 9 -f foo end Jan 3* foo - Feb 7 absent - Mar 7 absent Apr 4* foo May 2* foo Jun 6* foo Jul 4* foo Aug 1* foo Sep 5* foo Oct 3* foo - Nov 7 absent - Dec 5 absent foreach i ( 1 2 3 4 5 6 7 8 9 10 11 12 ) calendar -t 1.$i.2012 -W 9 -f foo end Jan 2* foo Feb 6* foo Mar 5* foo Apr 2* foo - May 3 absent --- EXCEPTION! Jun 4* foo Jul 2* foo Aug 6* foo Sep 3* foo Oct 1* foo Nov 5* foo - Dec 3 absent foreach i ( 1 2 3 4 5 6 7 8 9 10 11 12 ) calendar -t 1.$i.2013 -W 9 -f foo end - Jan 7 absent Feb 4* foo Mar 4* foo Apr 1* foo May 6* foo Jun 3* foo Jul 1* foo Aug 5* foo Sep 2* foo - Oct 7 absent Nov 4* foo - Dec 2 absent HTH, -WBE ___ 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: bug in /usr/bin/calendar: Thu+1 doesn't match on 7th or December
Hi, Please report bugs with send-pr (cos bug reports to mail list get lost) See man send-pr If you can attach a patch to fix it, so much the better Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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
Possible /bin/sh Bug?
Given this script: #!/bin/sh foo= while read line do foo=$foo -e done echo $foo Say I respond 3 times, I'd expect to see: -e -e -e Instead, I get: -e -e Linux appears to do the right thing here, so this seems like it is a bug ... or am I missing something? -- --- Tim Daneliuk ___ 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: Possible /bin/sh Bug?
In the last episode (Jun 05), Tim Daneliuk said: Given this script: #!/bin/sh foo= while read line do foo=$foo -e done echo $foo Say I respond 3 times, I'd expect to see: -e -e -e Instead, I get: -e -e Linux appears to do the right thing here, so this seems like it is a bug ... or am I missing something? echo takes a -e flag, so it eats the first one. Bash does the same thing, so any Linux that uses bash as /bin/sh will also. You must be testing on a Linux that uses something else as /bin/sh. Better to use the printf command if you are worried about compatibility. echo [-e | -n] [string ...] Print a space-separated list of the arguments to the standard output and append a newline character. -n Suppress the output of the trailing newline. -e Process C-style backslash escape sequences. The echo command understands the following character escapes: -- 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: Possible /bin/sh Bug?
On 06/05/2012 11:35 AM, Dan Nelson wrote: In the last episode (Jun 05), Tim Daneliuk said: Given this script: #!/bin/sh foo= while read line do foo=$foo -e done echo $foo Say I respond 3 times, I'd expect to see: -e -e -e Instead, I get: -e -e Linux appears to do the right thing here, so this seems like it is a bug ... or am I missing something? echo takes a -e flag, so it eats the first one. Bash does the same thing, so any Linux that uses bash as /bin/sh will also. You must be testing on a Linux that uses something else as /bin/sh. Better to use the printf command if you are worried about compatibility. echo [-e | -n] [string ...] Print a space-separated list of the arguments to the standard output and append a newline character. -n Suppress the output of the trailing newline. -e Process C-style backslash escape sequences. The echo command understands the following character escapes: Ah, OK, that makes sense, thanks... -- --- Tim Daneliuk ___ 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: Possible /bin/sh Bug?
On Tue, 05 Jun 2012 10:40:45 -0500 Tim Daneliuk tun...@tundraware.com wrote: Given this script: #!/bin/sh foo= while read line do foo=$foo -e done echo $foo Say I respond 3 times, I'd expect to see: -e -e -e Instead, I get: -e -e The last line echo $foo is what is getting confused. At the end of 3 passes, $foo contains -e -e -e so when the last line is executed, it looks like: echo -e -e -e The first -e is probably being interperted by echo as a flag ( echo -e ) and then only prints the last two -e. Its easier to see if you execute the script with xtrace: sh -x /path/to/script I'd recommend that you write the last line with quotes: echo $foo and I think it'll produce the results you expect. HTH, Randy ___ 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: Possible /bin/sh Bug?
From: Tim Daneliuk tun...@tundraware.com Given this script: #!/bin/sh foo= while read line do foo=$foo -e done echo $foo Say I respond 3 times, I'd expect to see: -e -e -e Instead, I get: -e -e Linux appears to do the right thing here, so this seems like it is a bug ... or am I missing something? Yup. there are -multiple-, incompatible, standards for 'echo'. a SYS-V derived echo will behve diferently than UCB based one. varous shell-program 'built-in' implementtions may have yet different behavior. Recommendation -- use 'print' instead of 'echo', it is much more predictble in differnt environments. ALTERNATIVE: replace the last line of the script with: echo -- $foo ___ 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: /usr/bin/find - binary operands howto
A single find already had the needed selection and execution ops.
So I was trying it first, before writing an external parser, etc.
It's still not clear to me how find is compiling the arguments
internally, but using -vv on the utils helped a lot. After adding
-false after all the -exec's, it now works as desired up against
my array of inodes. I also worked in a pre-change, select, ls.
The arbitrary format of gfind is interesting. It can maybe be
approximated in find with -exec ls someargs {} \+.
___
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: /usr/bin/find - binary operands howto
On Sun, 3 Jun 2012 19:10:00 -0400, grarpamp grarp...@gmail.com said: G Given a fs with millions of inodes, multiple find runs is expensive. As G is performing the ch* on more than the minimum required inodes, which G also needlessly updates the inode ctime. So I want one find, doing the G ch* only if necessary. So how should I write this? Do I want to use G -true/-false somehow? It might be more efficient to keep find output in either a flat file or DB, so you can avoid multiple walks over the filetree. You'll need GNU find: #!/bin/sh export PATH=/usr/local/bin:/bin:/usr/bin test $1 || set . echo '#filetype|inode|links|uname|gname|mode|size|mtime|pathname' gfind $@ -printf '%y|%i|%n|%u|%g|%m|%s|%T@|%p\n' exit 0 Sample output: root# chown 1234 stuff root# chgrp 5678 stuff me% ls -l drwxr-sr-x 3 kev local512 04-Jun-2012 21:01:41 . drwxr-xr-x 2 kev local512 04-Jun-2012 21:38:47 mail -rw-r--r-x 1 kev local 47072 04-Jun-2012 19:34:26 mail/junk* -rw-r--r-- 1 1234 5678 85 19-May-2012 23:28:30 stuff -rw-r--r-- 1 kev local 8104 04-Jun-2012 19:43:44 testing me% [run script] #filetype|inode|links|uname|gname|mode|size|mtime|pathname d|873603|3|kev|local|2755|512|1338858101|. d|1188634|2|kev|local|2755|512|1338860327|./mail f|1188649|1|kev|local|645|47072|1338852866|./mail/junk f|955452|1|1234|5678|644|85|1337484510|./stuff f|873708|1|kev|local|644|8104|1338853424|./testing Run this first, then look for the conditions you want using awk or perl. Advantages: * Doesn't change ctime, no additional filetree-walking. * You can use this to create your locate DB, if you want to avoid a second pass through the filesystem. * Gives you a point-in-time picture of ownership, mode, etc. in case you need to back out your changes. -- Karl Vogel I don't speak for the USAF or my company When I read about the evils of drinking, I gave up reading. --Henny Youngman ___ 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
/usr/bin/find - binary operands howto
Given a fs with millions of inodes, multiple find runs is expensive.
As is performing the ch* on more than the minimum required inodes,
which also needlessly updates the inode ctime. So I want one find,
doing the ch* only if necessary.
I came up with this. But any true line short circuits the rest of
the -o's, which isn't desired. Using -a results similarly.
The man page says -exec returns true if util is true. ch* is usually
true unless the operation isn't permitted (file flags, read-only,
etc) or the node vanishes in a race.
The test[s] would keep -exec[s] from being always executed.
Then there is the problem of the full permutation of the initial
state of the owner and mode, say: 00, 01, 10, 11.
So how should I write this? Do I want to use -true/-false somehow?
# touch 1 ; chown 1:1 1 ; chmod 0666 1 ; ls -l 1
# find 1 \( \
\( \! \( -uid 0 -gid 0 \) -exec chown 0:0 {} \+ \) \
-o \
\(-perm +0222 -exec chmod ugo-w {} \+ \) \
-o \
...
-o \
...
\)
# ls -l 1
___
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: FreeBSD problem reports - bin/167156
On 25/04/2012 22:54, Taras Marusin wrote: Hello! How can I track the solution to this problem? T.Marusin -- Forwarded message -- From:freebsd-gnats-sub...@freebsd.org Date: 2012/4/21 Subject: Re: bin/167156: looping process mksnap_ffs when run in a chroot environment named. CPU 100% To: Taras Marusinmtv.l...@gmail.com Thank you very much for your problem report. It has the internal identification `bin/167156'. The individual assigned to look at your report is: freebsd-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=167156 First as the submitter you should get emailed copies of any follow ups added to the report. Second the link at the end there will show all responses submitted to the problem report. You can check that page any time you want. ___ 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 problem reports - bin/167156
Hello! How can I track the solution to this problem? T.Marusin -- Forwarded message -- From: freebsd-gnats-sub...@freebsd.org Date: 2012/4/21 Subject: Re: bin/167156: looping process mksnap_ffs when run in a chroot environment named. CPU 100% To: Taras Marusin mtv.l...@gmail.com Thank you very much for your problem report. It has the internal identification `bin/167156'. The individual assigned to look at your report is: freebsd-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=167156 Category: bin Responsible:freebsd-bugs Synopsis: looping process mksnap_ffs when run in a chroot environment named. CPU 100% Arrival-Date: Sat Apr 21 07:10:10 UTC 2012 ___ 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 license vs /usr/bin/true license
FreeBSD, as specified here [1] uses 2-clause BSD license, but /usr/bin/true [2] (as empty as it is) uses something like 3-clause BSD license, is that desired? [1] http://www.freebsd.org/copyright/freebsd-license.html [2] http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/usr.bin/true/true.c Regards, vermaden -- ... ___ 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: FreeBSD license vs /usr/bin/true license
On 01/31/12 12:55, vermaden wrote: FreeBSD, as specified here [1] uses 2-clause BSD license, but /usr/bin/true [2] (as empty as it is) uses something like 3-clause BSD license, is that desired? [1] http://www.freebsd.org/copyright/freebsd-license.html [2] http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/usr.bin/true/true.c By coincidence, this link turned up on Hacker News Daily this morning. It's about the copyright on the true command. http://trillian.mit.edu/~jc/humor/ATT_Copyright_true.html ___ 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: FreeBSD license vs /usr/bin/true license
You might have to re-write it from scratch. It's still copyrighted by the university. I'd say write it in c++ to dispel all doubt that you didn't copy. Then true and groff will be c++. There's still software in the tree that uses the four clause license. But because of the advertising clause, you can't really talk about it or else you have to list it. On 1/31/2012 8:29 AM, Arthur Chance wrote: On 01/31/12 12:55, vermaden wrote: FreeBSD, as specified here [1] uses 2-clause BSD license, but /usr/bin/true [2] (as empty as it is) uses something like 3-clause BSD license, is that desired? [1] http://www.freebsd.org/copyright/freebsd-license.html [2] http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/usr.bin/true/true.c By coincidence, this link turned up on Hacker News Daily this morning. It's about the copyright on the true command. http://trillian.mit.edu/~jc/humor/ATT_Copyright_true.html ___ 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
* Re: chroot error: /bin/csh: No such file or directory; trying to create customized livecd/dvd
Sent from my iPhone On Dec 23, 2011, at 8:28 PM, Antonio Olivares olivares14...@gmail.com wrote: Dear folks, I am trying to build a simple livecd to learn more. I have successfully run some commands found here: http://www.secure-computing.net/wiki/index.php/FreeBSD/LiveCD # cd /usr/src # make buildworld DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make installworld DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make buildkernel DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make installkernel DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make distribution DESTDIR=/usr/home/olivares/tmp/tmp/R/ all these commands are successful I mount devfs as instructed in command # mount -t devfs devfs /path/to/livecd/dev # chroot /path/to/livecd === tricorehome# mount -t devfs devfs /usr/home/olivares/tmp/tmp/R/ tricorehome# chroot /usr/home/olivares/tmp/tmp/R/ chroot: /bin/csh: No such file or directory === I have tried to use freesbie script(s) by installing freesbie port, but it failed and I asked questions but got few to no responses. I have tried to look for some scripts/SDK but not have been successful like frenzy's to create frenzy livecd. There are few to no FreeBSD LiveCDs, only one that has been working and updated is the GhostBSD one by Eric Turgeon. I see OpenBSD has several livecds/livedvds like jggimi, FuguITA, etc to showcase it. NetBSD has one as well called Jibbed. FreeBSD has specialized ones like PfSense, Monowall, FreeNAS, Mahesha, and GhostBSD. Frenzy was apparently going to be maintained but no newer releases. I have gotten feedback as to there exist mfsBSD by Martin Matruska, http://mfsbsd.vx.sk/, and druidbsd, http://sourceforge.net/projects/druidbsd/, but cannot do much with them :( I try to get my feet wet, but I get error and can't seem to get around it :( Any thoughts, ideas, comments, observations? I just want to create a livecd/livedvd with customized packages to take my desktop everywhere, That should be pretty easy with druidbsd as it gives you a convenient dumping-ground to throw extras. Note, however, that there is a very large code-drop around the corner that will bring about 1.5 years of enhancements in soon. So if it doesn't do quite what you want now, it may soon. That being said, one of the things I feel makes DruidBSD unique is an insanely-customized mfsroot designed to break you out into the larger (and more expansive) ISO-9660 structure so that you -- as a developer of your own custom LiveCD -- CAN expand the functionality simply by dumping binaries and libs into the ISO-9660 structure while the mfsroot stays nice and compact. If you wanted to, you could add X windows even. -- Devin I have tried several *BSD livecds out there, they are good, but I want to have the packages that I use and more newer than FreeSBIE 2.0, and roFreeSBIE 1.3. I have seen linux-live scripts [http://www.linux-live.org/] by Tomas M, and wonder if there exist such a utility in the *BSDs, a universal script to create a livecd/livedvd of a running BSD ? if there is not any utility, how can I get around the error about /bin/csh, if it is apparently there: tricorehome# which csh /bin/csh so I can chroot to it and add packages/ports to customize the livecd/dvd I want to create? Regards, Antonio ___ 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 _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: chroot error: /bin/csh: No such file or directory; trying to create customized livecd/dvd
On 12/24/11 22:57, Antonio Olivares wrote: I'll ask a stupid question, and you're more than welcome to give a stupid answer: Is /bin/csh actually _in_ your chroot? So csh should be this path: /usr/home/olivares/tmp/tmp/R/bin/csh HTH ___ 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 tricorehome# pwd /usr/home/olivares/tmp/tmp/R tricorehome# ls -l /bin/csh -r-xr-xr-x 2 root wheel 369288 Apr 2 2011 /bin/csh I am not sure if it is there now :( I think you may have missed something there- you do realise that even though you've changed directory, you haven't chrooted. So when you run ls -l /bin/csh it is still checking your system root- not the chroot. Sometimes a single typo can cause huge hassles, eh? :) Try: cd /usr/home/olivares/tmp/tmp/R ls -l bin/csh Watch the bin/csh- don't make it an absolute path by adding the root (/) at the beginning. ___ 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: chroot error: /bin/csh: No such file or directory; trying to create customized livecd/dvd
I'll ask a stupid question, and you're more than welcome to give a stupid answer: Is /bin/csh actually _in_ your chroot? So csh should be this path: /usr/home/olivares/tmp/tmp/R/bin/csh HTH ___ 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 tricorehome# pwd /usr/home/olivares/tmp/tmp/R tricorehome# ls -l /bin/csh -r-xr-xr-x 2 root wheel 369288 Apr 2 2011 /bin/csh I am not sure if it is there now :( Thanks, Antonio ___ 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: chroot error: /bin/csh: No such file or directory; trying to create customized livecd/dvd
On Sat, Dec 24, 2011 at 7:03 AM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 12/24/11 22:57, Antonio Olivares wrote: I'll ask a stupid question, and you're more than welcome to give a stupid answer: Is /bin/csh actually _in_ your chroot? So csh should be this path: /usr/home/olivares/tmp/tmp/R/bin/csh HTH ___ 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 tricorehome# pwd /usr/home/olivares/tmp/tmp/R tricorehome# ls -l /bin/csh -r-xr-xr-x 2 root wheel 369288 Apr 2 2011 /bin/csh I am not sure if it is there now :( I think you may have missed something there- you do realise that even though you've changed directory, you haven't chrooted. So when you run ls -l /bin/csh it is still checking your system root- not the chroot. Sometimes a single typo can cause huge hassles, eh? :) Try: cd /usr/home/olivares/tmp/tmp/R ls -l bin/csh Watch the bin/csh- don't make it an absolute path by adding the root (/) at the beginning. ___ 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 I am trying to do what you have suggested, it appears that /bin/csh is not present in the /usr/home/olivares/tmp/tmp/R directory :( tricorehome# ls /usr/home/olivares/tmp/tmp/ R tricorehome# ls -l /usr/home/olivares/tmp/tmp/ total 2 drwxr-xr-x 17 root wheel 512 Dec 23 21:56 R tricorehome# ls -l /usr/home/olivares/tmp/tmp/R/ total 46 -rw-r--r-- 2 root wheel 798 Dec 23 21:56 .cshrc -rw-r--r-- 2 root wheel 265 Dec 23 21:56 .profile -r--r--r-- 1 root wheel 6200 Dec 23 21:56 COPYRIGHT drwxr-xr-x 2 root wheel 1024 Dec 23 21:30 bin drwxr-xr-x 7 root wheel 512 Dec 23 21:56 boot dr-xr-xr-x 2 root wheel 512 Dec 23 21:30 dev drwxr-xr-x 20 root wheel 2048 Dec 23 21:56 etc drwxr-xr-x 3 root wheel 1536 Dec 23 21:30 lib drwxr-xr-x 2 root wheel 512 Dec 23 21:31 libexec drwxr-xr-x 2 root wheel 512 Dec 23 21:30 media drwxr-xr-x 2 root wheel 512 Dec 23 21:30 mnt dr-xr-xr-x 2 root wheel 512 Dec 23 21:30 proc drwxr-xr-x 2 root wheel 2560 Dec 23 21:30 rescue drwxr-xr-x 2 root wheel 512 Dec 23 21:56 root drwxr-xr-x 2 root wheel 2560 Dec 23 21:31 sbin lrwxr-xr-x 1 root wheel11 Dec 23 21:30 sys - usr/src/sys drwxrwxrwt 2 root wheel 512 Dec 23 21:30 tmp drwxr-xr-x 14 root wheel 512 Dec 23 21:31 usr drwxr-xr-x 22 root wheel 512 Dec 23 21:30 var tricorehome# ls -l /usr/home/olivares/tmp/tmp/R/bin/ total 1692 -r-xr-xr-x 2 root wheel 11472 Dec 23 21:30 [ -r-xr-xr-x 1 root wheel 11448 Dec 23 21:30 cat -r-xr-xr-x 1 root wheel7912 Dec 23 21:30 chflags -r-xr-xr-x 1 root wheel 17576 Dec 23 21:30 chio -r-xr-xr-x 1 root wheel8392 Dec 23 21:30 chmod -r-xr-xr-x 1 root wheel 21304 Dec 23 21:30 cp -r-xr-xr-x 2 root wheel 369288 Dec 23 21:30 csh -r-xr-xr-x 1 root wheel 18440 Dec 23 21:30 date -r-xr-xr-x 1 root wheel 22104 Dec 23 21:30 dd -r-xr-xr-x 1 root wheel 13920 Dec 23 21:30 df -r-xr-xr-x 1 root wheel5704 Dec 23 21:30 domainname -r-xr-xr-x 1 root wheel5592 Dec 23 21:30 echo -r-xr-xr-x 2 root wheel 56880 Dec 23 21:30 ed -r-xr-xr-x 1 root wheel 16408 Dec 23 21:30 expr -r-xr-xr-x 1 root wheel 10336 Dec 23 21:30 getfacl -r-xr-xr-x 1 root wheel5840 Dec 23 21:30 hostname -r-xr-xr-x 1 root wheel7128 Dec 23 21:30 kenv -r-xr-xr-x 1 root wheel7640 Dec 23 21:30 kill -r-xr-xr-x 2 root wheel 11368 Dec 23 21:30 link -r-xr-xr-x 2 root wheel 11368 Dec 23 21:30 ln -r-xr-xr-x 1 root wheel 30496 Dec 23 21:30 ls -r-xr-xr-x 1 root wheel7152 Dec 23 21:30 mkdir -r-xr-xr-x 1 root wheel 13576 Dec 23 21:30 mv -r-xr-xr-x 1 root wheel 95448 Dec 23 21:30 pax -r-xr-xr-x 2 root wheel 16520 Dec 23 21:30 pgrep -r-xr-xr-x 2 root wheel 16520 Dec 23 21:30 pkill -r-xr-xr-x 1 root wheel 43312 Dec 23 21:30 ps -r-xr-xr-x 1 root wheel7128 Dec 23 21:30 pwait -r-xr-xr-x 1 root wheel5696 Dec 23 21:30 pwd -r-sr-xr-x 1 root wheel 20416 Dec 23 21:30 rcp -r-xr-xr-x 1 root wheel5456 Dec 23 21:30 realpath -r-xr-xr-x 2 root wheel 56880 Dec 23 21:30 red -r-xr-xr-x 2 root wheel 15880 Dec 23 21:30 rm -r-xr-xr-x 1 root wheel 72744 Dec 23 21:30 rmail -r-xr-xr-x 1 root wheel5784 Dec 23 21:30 rmdir -r-xr-xr-x 1 root wheel 18832 Dec 23 21:30 setfacl -r-xr-xr-x 1 root wheel 136696 Dec 23 21:30 sh -r-xr-xr-x 1 root wheel5448 Dec 23 21:30 sleep -r-xr-xr-x 1 root wheel 22608 Dec 23 21:30 stty -r-xr-xr-x 1 root wheel4456 Dec 23 21:30 sync -r-xr-xr-x 2 root wheel 369288 Dec 23 21:30 tcsh -r-xr-xr-x 2 root wheel 11472 Dec 23 21:30 test -r-xr-xr-x 2 root wheel
Re: chroot error: /bin/csh: No such file or directory; trying to create customized livecd/dvd
On 12/24/11 14:28, Antonio Olivares wrote: Dear folks, I am trying to build a simple livecd to learn more. I have successfully run some commands found here: http://www.secure-computing.net/wiki/index.php/FreeBSD/LiveCD # cd /usr/src # make buildworld DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make installworld DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make buildkernel DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make installkernel DESTDIR=/usr/home/olivares/tmp/tmp/R/ # make distribution DESTDIR=/usr/home/olivares/tmp/tmp/R/ all these commands are successful I mount devfs as instructed in command # mount -t devfs devfs /path/to/livecd/dev # chroot /path/to/livecd === tricorehome# mount -t devfs devfs /usr/home/olivares/tmp/tmp/R/ tricorehome# chroot /usr/home/olivares/tmp/tmp/R/ chroot: /bin/csh: No such file or directory === I have tried to use freesbie script(s) by installing freesbie port, but it failed and I asked questions but got few to no responses. I have tried to look for some scripts/SDK but not have been successful like frenzy's to create frenzy livecd. There are few to no FreeBSD LiveCDs, only one that has been working and updated is the GhostBSD one by Eric Turgeon. I see OpenBSD has several livecds/livedvds like jggimi, FuguITA, etc to showcase it. NetBSD has one as well called Jibbed. FreeBSD has specialized ones like PfSense, Monowall, FreeNAS, Mahesha, and GhostBSD. Frenzy was apparently going to be maintained but no newer releases. I have gotten feedback as to there exist mfsBSD by Martin Matruska, http://mfsbsd.vx.sk/, and druidbsd, http://sourceforge.net/projects/druidbsd/, but cannot do much with them :( I try to get my feet wet, but I get error and can't seem to get around it :( Any thoughts, ideas, comments, observations? I just want to create a livecd/livedvd with customized packages to take my desktop everywhere, I have tried several *BSD livecds out there, they are good, but I want to have the packages that I use and more newer than FreeSBIE 2.0, and roFreeSBIE 1.3. I have seen linux-live scripts [http://www.linux-live.org/] by Tomas M, and wonder if there exist such a utility in the *BSDs, a universal script to create a livecd/livedvd of a running BSD ? if there is not any utility, how can I get around the error about /bin/csh, if it is apparently there: tricorehome# which csh /bin/csh so I can chroot to it and add packages/ports to customize the livecd/dvd I want to create? I'll ask a stupid question, and you're more than welcome to give a stupid answer: Is /bin/csh actually _in_ your chroot? So csh should be this path: /usr/home/olivares/tmp/tmp/R/bin/csh HTH ___ 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: bin/161927: bsdinstall(8): has no help describing what is happening
From-To: open-closed By: nwhitehorn When: Sun Oct 23 15:18:39 UTC 2011 Why: There is help throughout, in particular in the partition editor, which shows help in the bottom line of the screen. More verbose help (e.g. pressing F1 to open a help screen) will likely come later. http://www.freebsd.org/cgi/query-pr.cgi?pr=161927 If there is help throughout it sure is not in the 9.0 RC1 version. I object to the closing of this pr without any review by the current list. I can not understand how you can say there is help info provided in bsdinstall. The very first dialog box where users select (install) has no help. Every dialog box shown should have a help option. Saying it will come later is not the professional way software is released to the public. This is not the Freebsd standard. bsdinstall is the front door to FreeBSD and is the first thing installers see when trying to install it. Do you really want to show the public such a lack of pride in doing a complete job. In its current condition bsdinstall is not ready to be released. It gives the public the wrong impression (image) of what a great OS Freebsd is. Too many developers and other volunteers have invested tons of hours to have their united effort disrespected by a installer that is incomplete. This pr about adding help info is not the only outstanding pr on bsdinstall. ___ 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: autologin on default shell /bin/sh
On Mon, 26 Sep 2011 19:07:47 -0500, Antonio Olivares wrote: I had it working (autologin on 8.2 amd64) on two machines, but I wanted to test out/install nvidia driver and I used sysinstall to install kernel source from 8.2 dvd and then many things I had working, like printer, scanner were erased. Shell changed back to /bin/sh, I was using bash. For some reason or another, it was not working. I did the same thing and now it works again :) Your autologin configuration is a little bit different from mine. I'll share and accomodate it to your particular use. Step 1: In /etc/gettytab, autologin:\ :al=olivares:tc=Pc: is to be placed _after_ the default: entry. This step defines the getty profile for an automated login with the username olivares as associated to the al= parameter. Also note the tc= parameter which incorporates the default Pc settings (that you can encounter in the next step's working file). Step 2: In /etc/ttys, the line for ttyv0 is to be changed like this: ttyv0 /usr/libexec/getty autologin cons25l1 on secure This instructs the getty program to use the autologin profile at system startup and automatically log in the user olivares (see step 1). Attention: Maybe you need a different console configuration; cons25 is the system's default. In Germany, I have to use cons25l1 for the local magic. :-) There should not be any problem if you have xterm there. Maybe just some terminal capabilities don't work in text mode, but there should be no effect on autologin functionality. Make sure you _don't_ have a line calling xdm here - maybe this causes conflicts. Step 3: In /home/olivares (or where $HOME is located for that user), make ~/.login end in [ ! -f /tmp/.X0-lock ] startx For bash, this would go to ~/.bash_login. Other shells may have different startup files; see man sh, man csh, man bash and man yourshell for details. To become independent from the actual login shell, you can write this command into a script that is executable by the user, e. g. chmod +x /opt/bin/autostartx; if you have /opt/bin in $PATH, you just need to call autostartx in the correct startup file. Then _any_ shell startup script could contain the call that script, like this: #!/bin/sh [ ! -f /tmp/.X0-lock ] startx exec $0 You can also make this script local to your user in ~/bin, maybe you already have that in $PATH. Attention: This _might_ get you into an infinite loop if something is _really_ wrong. :-) You can even modify the script to _restart_ X if it should have crashed, so you don't fall back to the console in case of a severe error (and enter startx again). Step 4 (optional): In order to combine the use of xdm (if you want to) and the different system shells, for your user account there can be some additional settings. In ~/.xsession, put #!/bin/csh source ~/.cshrc exec ~/.xinitrc This file will be executed in case xdm is used. I am using the C shell as a dialog shell here, so this makes sure my shell settings get incorporated. Then control will be given to the .xinitrc file, usually executed when you run startx, but xdm _may_ have a different opinion. In ~/.xinitrc, put all your X startup stuff. #!/bin/sh [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc #xrandr --fb 1400x1050 #xrandr --size 1400x1050 intclock -geometry 186x65+151-0 xload -geometry 150x70+0+826 -bg white -fg black -hl gray \ -scale 5 -label System load -update 1 xmbmon -g 150x100+0+897 -tmin 20.0 -tmax 70.0 -cmtmb CPU \ -cltmb blue -cmtcpu CS -cltcpu cyan -cmtcs SYS \ -cltcs green -vmin 2.0 -vmax 3.0 -cmvc V -clvc red xclock -geometry 50x50+50+998 xbiff -geometry 50x50+0+998 xlogo -geometry 50x50+100+998 -render xcpufreq -geometry 183x167+151+826 -cpuscalecolor grey \ -freqscalecolor grey -scales 6 -update 1 -jumpscroll 1 xterm -geometry 80x25+0+465 -class NOCLOSE_TERMINAL -fg black \ -bg beige -title Terminal xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms exec wmaker The first line (#!) is optional. I'm not fully sure if those files have to be +x attributes (I _have_ those settings, no idea where they came from and why they are still here). But it works, so I don't question it. :-) Step 5: Profit. :-) In the beta 2 machine, the /dev/ttys has xterm instead of original cons25. Other than that, you are correct with the rest of the information. It was strange that someone/some folks have changed cons25 to xterm. Surprises me too, but maybe the console driver now uses this emulation for I/O... I'm not running 9-BETA here so I cannot check, sorry. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa
Re: autologin on default shell /bin/sh
On Sun, Sep 25, 2011 at 10:56 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 25/09/2011 16:16, Antonio Olivares wrote: I have a 9.0 BETA 2 amd64 machine and I am using /bin/sh shell or default shell when one installs FreeBSD. I want to be able to setup autologin and automatic startx as well like I have on the other machines I tried to edit ~/.cshrc and copied W Block's example, but it did not work https://freebsd-forums.liquidneon.com/showthread.php?t=22304 How can I get it without using bash? Do I need to create a ~/.csh_login file and add the code to startx? I have tried to add to ~/.cshrc the code: if [ `/usr/bin/tty` = '/dev/ttyv0' ]; then /usr/local/bin/startx fi and it does not work. If the shell on your auto-login account is /bin/sh, then you should put your X startup in .profile -- syntax is identical to the bash example you showed. If the shell on your auto-login account is /bin/csh or /bin/tcsh (which are really exactly the same thing on FreeBSD), then you should put your X startup in .login In this case the syntax is different, but you can copy wblock's example from the forum thread you referenced. Either of those shells should work. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW Thanks Dr Matthew, Warren others who have made suggestions. It works [FreeBSD 9.0 BETA 2] partially. $ uname -a FreeBSD e213-amd64-1.grullahighschool.org 9.0-BETA2 FreeBSD 9.0-BETA2 #0: Tue Sep 20 10:02:05 CDT 2011 root@e213-amd64-1:/usr/obj/usr/src/sys/GENERIC amd64 $ They have changed /etc/gettytab from cons25 to xterm, and even changing it to cons25 back has no effect. If I type my username and login, startx starts automatically, but after I have logged in by typing my username and password. This is an excerpt of /etc/ttys on FreeBSD 9.0 BETA 2 ttyv0 /usr/libexec/getty Pc xterm on secure # Virtual terminals ttyv1 /usr/libexec/getty Pc xterm on secure ttyv2 /usr/libexec/getty Pc xterm on secure ttyv3 /usr/libexec/getty Pc xterm on secure ttyv4 /usr/libexec/getty Pc xterm on secure ttyv5 /usr/libexec/getty Pc xterm on secure ttyv6 /usr/libexec/getty Pc xterm on secure Something is restricting the automatic login, but don't know how to troubleshoot this. Regards, Antonio ___ 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: autologin on default shell /bin/sh
On Mon, 26 Sep 2011, Antonio Olivares wrote: If I type my username and login, startx starts automatically, but after I have logged in by typing my username and password. That means the part that starts X is correct. This is an excerpt of /etc/ttys on FreeBSD 9.0 BETA 2 ttyv0 /usr/libexec/getty Pc xterm on secure # Virtual terminals ttyv1 /usr/libexec/getty Pc xterm on secure Don't use xterm, it won't be able to run before X has started. Pc is the standard login. The new entry in /etc/gettytab creates a new Al for autologin: A|Al|Autologin console:\ :ht:np:sp#115200:al=user The A, Al, and Autologin console are all names for that entry. When the system starts, it will start the ttys listed in /etc/ttys: ttyv0 /usr/libexec/getty Pc cons25 on secure ttyv1 /usr/libexec/getty Al cons25 on secure I leave ttyv0 alone for log messages and such, and put the autologin on ttyv1. An autologin system probably won't need the rest of the ttyv entries and they can be commented out. ___ 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: autologin on default shell /bin/sh
On Mon, Sep 26, 2011 at 10:53 AM, Warren Block wbl...@wonkity.com wrote: On Mon, 26 Sep 2011, Antonio Olivares wrote: If I type my username and login, startx starts automatically, but after I have logged in by typing my username and password. That means the part that starts X is correct. This is an excerpt of /etc/ttys on FreeBSD 9.0 BETA 2 ttyv0 /usr/libexec/getty Pc xterm on secure # Virtual terminals ttyv1 /usr/libexec/getty Pc xterm on secure Don't use xterm, it won't be able to run before X has started. Pc is the standard login. The new entry in /etc/gettytab creates a new Al for autologin: A|Al|Autologin console:\ :ht:np:sp#115200:al=user The A, Al, and Autologin console are all names for that entry. When the system starts, it will start the ttys listed in /etc/ttys: ttyv0 /usr/libexec/getty Pc cons25 on secure ttyv1 /usr/libexec/getty Al cons25 on secure I leave ttyv0 alone for log messages and such, and put the autologin on ttyv1. An autologin system probably won't need the rest of the ttyv entries and they can be commented out. I have done as you have instructed. Set up /etc/ttyv with ttyv1 /usr/libexec/getty Al cons25 on secure and in /etc/gettytab A|Al|Autologin console:\ :ht:np:sp#115200:al=olivares as my username is olivares. It is working on BETA 2 :) Now I hope to get it working again at home on an 8.2 amd machine. I will report back but return different machine and different information, hope only with a success report :) It was working before, and now it is not :( Regards, Antonio ___ 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: autologin on default shell /bin/sh
On 26/09/2011 22:37, Antonio Olivares wrote: in /etc/gettytab A|Al|Autologin console:\ :ht:np:sp#115200:al=olivares as my username is olivares. It is working on BETA 2 :) Now I hope to get it working again at home on an 8.2 amd machine. I will report back but return different machine and different information, hope only with a success report :) This functionality hasn't changed over many FreeBSD versions -- certainly since the days of FreeBSD 4.x, and probably not over the entire lifetime of the FreeBSD project. If you do the same thing on your 8.2 machine as you've done on your 9.0beta2 machine, then it should work exactly the same. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: autologin on default shell /bin/sh
On Mon, Sep 26, 2011 at 4:46 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 26/09/2011 22:37, Antonio Olivares wrote: in /etc/gettytab A|Al|Autologin console:\ :ht:np:sp#115200:al=olivares as my username is olivares. It is working on BETA 2 :) Now I hope to get it working again at home on an 8.2 amd machine. I had it working (autologin on 8.2 amd64) on two machines, but I wanted to test out/install nvidia driver and I used sysinstall to install kernel source from 8.2 dvd and then many things I had working, like printer, scanner were erased. Shell changed back to /bin/sh, I was using bash. For some reason or another, it was not working. I did the same thing and now it works again :) I will report back but return different machine and different information, hope only with a success report :) This functionality hasn't changed over many FreeBSD versions -- certainly since the days of FreeBSD 4.x, and probably not over the entire lifetime of the FreeBSD project. If you do the same thing on your 8.2 machine as you've done on your 9.0beta2 machine, then it should work exactly the same. In the beta 2 machine, the /dev/ttys has xterm instead of original cons25. Other than that, you are correct with the rest of the information. It was strange that someone/some folks have changed cons25 to xterm. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW Thanks to both yourself and Warren for your valuable input. I could not have gotten anywhere without your advice :) I appreciate your advice/comments suggestions. Also other folks like Polytropon have been tremendous in helping out with some issues I have encountered. Can't forget Anton either with TeTeX issues on ports as well. I hope not to have forgotten anyone :( Regards, Antonio ___ 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: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
ead...@freebsd.org wrote: Synopsis: 9.0 burncd error caused by change to cd0 from acd0 State-Changed-From-To: open-analyzed State-Changed-By: eadler State-Changed-When: Mon Sep 26 23:24:00 UTC 2011 State-Changed-Why: requires only a release notes entry; use cdrecord instead of burncd http://www.freebsd.org/cgi/query-pr.cgi?pr=160979 Your solution is very un-professional. What your solution purposes to do is do nothing. I think your judgment is flawed and a larger group of your peers need to review your judgment in this case. burncd has been part of the system utilities included in the basic release since release 4.0 and cdrecord is a port. The professional solution is to remove burncd from the 9.0 system release and add the cdrecord command to the basic release as the replacement for burncd. Then add release notes entry of the change. You do not knowingly leave a non-working utility in the system, period, or not provide a included replacement for a popular utility as this one. The alternative is to fix burncd or backout the acd0 to cd0 change from 9.0 which may be the most desired solution because its obvious that no one researched the impact this change may have. This change may impact many ports that access cd/dvd drives for read and write access. burncd may be a very small worm in a large can of big worms. ___ 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: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On 09/26/2011 17:59, Fbsd8 wrote: Your solution is very un-professional. Good thing we're all volunteers. :) What your solution purposes to do is do nothing. I think your judgment is flawed and a larger group of your peers need to review your judgment in this case. Ok, done. Eitan is right. burncd has been part of the system utilities included in the basic release since release 4.0 and cdrecord is a port. The professional solution is to remove burncd from the 9.0 system release and add the cdrecord command to the basic release as the replacement for burncd. Then add release notes entry of the change. I think you misunderstand the situation. So here are a few hopefully helpful facts: 1. The fact that something is in the base, or in the ports, has absolutely no bearing on whether one piece of software is fundamentally more useful or valuable than another. 2. burncd has only ever worked with a subset of the legacy ATA hardware. 3. ATA-CAM is on by default in FreeBSD 9 (which means that rather than acd0 as an ATA device you'll have cd0 as a SCSI device). 4. However, ATA-CAM is not mandatory, which means that leaving burncd in the base for those that want to continue using the legacy ATA interface is a perfectly reasonable course of action. 5. For those that wish to use the default ATA-CAM interface the cdrecord port provides a mature, full-featured solution. Even if it were possible to import it into the base, doing so would be a step in the wrong direction. You do not knowingly leave a non-working utility in the system, period, That makes sense, however see above. or not provide a included replacement for a popular utility as this one. The alternative already exists. The fact that it's not in the base has no relevance. I hope this clears up your confusion. If you have any further questions please direct them to freebsd-questions@FreeBSD.org only. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On 09/26/2011 18:43, Craig Rodrigues wrote: On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote: burncd has been part of the system utilities included in the basic release since release 4.0 and cdrecord is a port. The professional solution is to remove burncd from the 9.0 system release and add the cdrecord command to the basic release as the replacement for burncd. Then add release notes entry of the change. I think you misunderstand the situation. So here are a few hopefully helpful facts: 1. The fact that something is in the base, or in the ports, has absolutely no bearing on whether one piece of software is fundamentally more useful or valuable than another. Hi, I have used burncd on many releases of FreeBSD, on many machines without problem. I can see the fact that burncd suddenly failing to work on ATAPI hardware could annoy and confused end-users. It doesn't fail to work on ATAPI hardware. It fails to work on cd0 which is a SCSI device. The fact that it's emulated doesn't matter. Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out a more useful error message? Sure, as soon as someone volunteers to create that patch. No one is *trying* to annoy users, but things change around here because people are interested in changing them. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy and confused end-users.
It doesn't fail to work on ATAPI hardware. It fails to work on cd0 which
is a SCSI device. The fact that it's emulated doesn't matter.
True, but the subtlety of that distinction will be lost on a lot of end-users
not familiar with the implementation of the FreeBSD storage implementation.
To them burncd just doesn't work, when it used to.
Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out
a more useful error message?
Sure, as soon as someone volunteers to create that patch. No one is
*trying* to annoy users, but things change around here because people
are interested in changing them.
I am not familiar enough with the ATA_CAM work. Is there a a sysctl or ioctl
that can be queried from userspace to detect if ATA_CAM is configured
in the kernel?
I would suggest something like:
flag = query for hw.ata.ata_cam_enabled sysctl;
if (flag == 1) {
printf(ERROR: ATA_CAM enabled, etc., etc.)
exit(1);
}
I only see these sysctls on a system with ATA_CAM enabled:
hw.ata.setmax: 0
hw.ata.wc: 1
hw.ata.atapi_dma: 1
hw.ata.ata_dma_check_80pin: 1
hw.ata.ata_dma: 1
dev.atapci.0.%desc: Intel ATA controller
dev.atapci.0.%driver: atapci
dev.atapci.0.%location: slot=3 function=2
dev.atapci.0.%pnpinfo: vendor=0x8086 device=0x29b6 subvendor=0x1028
subdevice=0x0211 class=0x010185
dev.atapci.0.%parent: pci0
dev.ata.2.%desc: ATA channel 0
dev.ata.2.%driver: ata
dev.ata.2.%location: channel=0
dev.ata.2.%parent: atapci0
dev.ata.3.%desc: ATA channel 1
dev.ata.3.%driver: ata
dev.ata.3.%location: channel=1
dev.ata.3.%parent: atapci0
dev.ata.0.%driver: ata
dev.ata.0.%parent: isa0
dev.ata.1.%driver: ata
dev.ata.1.%parent: isa0
--
Craig Rodrigues
rodr...@crodrigues.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
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote: burncd has been part of the system utilities included in the basic release since release 4.0 and cdrecord is a port. The professional solution is to remove burncd from the 9.0 system release and add the cdrecord command to the basic release as the replacement for burncd. Then add release notes entry of the change. I think you misunderstand the situation. So here are a few hopefully helpful facts: 1. The fact that something is in the base, or in the ports, has absolutely no bearing on whether one piece of software is fundamentally more useful or valuable than another. Hi, I have used burncd on many releases of FreeBSD, on many machines without problem. I can see the fact that burncd suddenly failing to work on ATAPI hardware could annoy and confused end-users. Fbsd8 has a valid point. Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out a more useful error message? ERROR: burncd does not work when ATAPI-CAM driver enabled. Install the sysutils/cdrtools port and use cdrecord instead. Please refer to http://www.freebsd.org/doc/handbook/creating-cds.html#CDRECORD; While it is necessary to document all these things in release notes, documentation, etc., I don't always read every single last line of documentation or release notes when using a system, and I suspect many end-users are the same. :) I am a big fan of having the system issue diagnostic errors that give the user a clue how to remedy the problem, or pointers to relevant information. I even put Please in the error message to be nice. :) -- Craig Rodrigues rodr...@crodrigues.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
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy and confused end-users.
It doesn't fail to work on ATAPI hardware. It fails to work on cd0 which
is a SCSI device. The fact that it's emulated doesn't matter.
True, but the subtlety of that distinction will be lost on a lot of end-users
not familiar with the implementation of the FreeBSD storage implementation.
To them burncd just doesn't work, when it used to.
Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out
a more useful error message?
Sure, as soon as someone volunteers to create that patch. No one is
*trying* to annoy users, but things change around here because people
are interested in changing them.
I am not familiar enough with the ATA_CAM work. Is there a a sysctl or ioctl
that can be queried from userspace to detect if ATA_CAM is configured
in the kernel?
I would suggest something like:
...
Please fix it and move on.
Thanks,
-Garrett
$ usr.sbin/burncd/burncd -f /dev/cd0 blank
burncd: device provided not an acd(4) device: /dev/cd0.
Please verify that your kernel is built with acd(4) and the beforementioned
device is supported by acd(4).Index: usr.sbin/burncd/burncd.c
===
--- usr.sbin/burncd/burncd.c(revision 225704)
+++ usr.sbin/burncd/burncd.c(working copy)
@@ -159,8 +159,16 @@
if ((fd = open(dev, O_RDWR, 0)) 0)
err(EX_NOINPUT, open(%s), dev);
- if (ioctl(fd, CDRIOCGETBLOCKSIZE, saved_block_size) 0)
- err(EX_IOERR, ioctl(CDRIOCGETBLOCKSIZE));
+ if (ioctl(fd, CDRIOCGETBLOCKSIZE, saved_block_size) 0) {
+ if (errno == ENOTTY)
+ errx(EX_IOERR,
+ device provided not an acd(4) device: %s.\n\n
+ Please verify that your kernel is built with
+ acd(4) and the beforementioned device is
+ supported by acd(4)., dev);
+ else
+ err(EX_IOERR, ioctl(CDRIOCGETBLOCKSIZE));
+ }
if (ioctl(fd, CDRIOCWRITESPEED, speed) 0)
err(EX_IOERR, ioctl(CDRIOCWRITESPEED));
___
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: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote: ... Please fix it and move on. Thanks, -Garrett $ usr.sbin/burncd/burncd -f /dev/cd0 blank burncd: device provided not an acd(4) device: /dev/cd0. Please verify that your kernel is built with acd(4) and the beforementioned device is supported by acd(4). Hi, That patch is an improvement over the existing behavior. However, we may want to go a bit farther. Here are some possible scenarios: (1) User has a system with ATAPI CD-ROM only. (2) User has a system with ATAPI CD-ROM *and* USB CD-ROM. (3) User has a system with USB CD-ROM only. (4) User has a system with ATAPI CD-ROM and SCSI CD-ROM (5) User has a system with SCSI CD-ROM only I would guess that (1) is the most common scenario, and end-users will definitely encounter it and complain. In the case of (1), it would be nice if we could fail if we try to burn to /dev/cd0, as per your patch, but still check to see if ATA_CAM is enabled in the kernel, and print out a message with pointers for using cdrtools. With your patch, a user will see a message about acd(4), and try to get it to compile/kldload/whatever acd(4) on their system, and then not get it to work because ATA_CAM is enabled. Adding notes to the burncd man page that burncd will not work on ATAPI devices if ATA_CAM is enabled would be good to do also. If the long term plan is to get rid of the old ATA subsystem, and completely move to ATA_CAM, then we should put a deprecation warning in the burncd man page as well, to give users a further heads-up. -- Craig Rodrigues rodr...@crodrigues.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
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On Mon, 26 Sep 2011, Craig Rodrigues wrote: On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote: ... Please fix it and move on. Thanks, -Garrett $ usr.sbin/burncd/burncd -f /dev/cd0 blank burncd: device provided not an acd(4) device: /dev/cd0. Please verify that your kernel is built with acd(4) and the beforementioned device is supported by acd(4). Hi, That patch is an improvement over the existing behavior. However, we may want to go a bit farther. Here are some possible scenarios: (1) User has a system with ATAPI CD-ROM only. Covered. (2) User has a system with ATAPI CD-ROM *and* USB CD-ROM. First case covered. Second case requires cdrecord anyhow, so don't care. (3) User has a system with USB CD-ROM only. Second case requires cdrecord anyhow, so don't care. (4) User has a system with ATAPI CD-ROM and SCSI CD-ROM Same as (2). (5) User has a system with SCSI CD-ROM only Same as (3). I would guess that (1) is the most common scenario, and end-users will definitely encounter it and complain. In the case of (1), it would be nice if we could fail if we try to burn to /dev/cd0, as per your patch, but still check to see if ATA_CAM is enabled in the kernel, and print out a message with pointers for using cdrtools. With your patch, a user will see a message about acd(4), and try to get it to compile/kldload/whatever acd(4) on their system, and then not get it to work because ATA_CAM is enabled. Adding notes to the burncd man page that burncd will not work on ATAPI devices if ATA_CAM is enabled would be good to do also. If the long term plan is to get rid of the old ATA subsystem, and completely move to ATA_CAM, then we should put a deprecation warning in the burncd man page as well, to give users a further heads-up. Noting something in the documentation is fine. The point is that there's a lot of wasted electrons being tossed about about a fairly trivial issue: most of the apps that burn/use CDs were converted over to some logic long ago that matches cdrecord. The only apps that haven't really been (atacontrol, burncd) were abandoned because the developer isn't an active maintainer. Thanks, -Garrett___ 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: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
.. and if someone would like to contribute patches to burncd to update it, I think there'd be at least one committer here who would be happy to help you get your changes into the tree. :-) Adrian ___ 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
autologin on default shell /bin/sh
Dear folks, I have several FreeBSD boxes three 8.2 amd 64 with autologin working fine but with bash shell, /usr/local/bin/bash. I have used bits pieces from several places and thanks to kind folks like Polytropon and others(hope I don't offend anyone), I was able to login automatically and startx as well from ~/.bash_login file. quote FreeBSD autologin How to make some user login automatically? Add to the /etc/gettytab file the following strings: test:\ :al=test:ht:np:sp#115200: test:\ - entry name, autologin will use this username; al=test - autologin username; ht - terminal has real tabs; np - 8-bit chars; (optional) sp#115200 - line speed; Edit /etc/ttys file: ttyv0 /usr/libexec/getty test cons25 on secure Usual Pc changed with test. /quote http://keyhell.org/advices.html and a .bash_login file [olivares@quadcore ~]$ cat .bash_login # if test ! -f /tmp/.X0-lock; then /usr/local/bin/startx fi that runs startx automagically. I have a 9.0 BETA 2 amd64 machine and I am using /bin/sh shell or default shell when one installs FreeBSD. I want to be able to setup autologin and automatic startx as well like I have on the other machines I tried to edit ~/.cshrc and copied W Block's example, but it did not work https://freebsd-forums.liquidneon.com/showthread.php?t=22304 How can I get it without using bash? Do I need to create a ~/.csh_login file and add the code to startx? I have tried to add to ~/.cshrc the code: if [ `/usr/bin/tty` = '/dev/ttyv0' ]; then /usr/local/bin/startx fi and it does not work. As always, thanks for any pointers to solve this problem. I will get to the machine tomorrow at work, but I want to try some options and then report back which option/options helped solve the problem. Regards, Antonio ___ 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: autologin on default shell /bin/sh
On 25/09/2011 16:16, Antonio Olivares wrote: I have a 9.0 BETA 2 amd64 machine and I am using /bin/sh shell or default shell when one installs FreeBSD. I want to be able to setup autologin and automatic startx as well like I have on the other machines I tried to edit ~/.cshrc and copied W Block's example, but it did not work https://freebsd-forums.liquidneon.com/showthread.php?t=22304 How can I get it without using bash? Do I need to create a ~/.csh_login file and add the code to startx? I have tried to add to ~/.cshrc the code: if [ `/usr/bin/tty` = '/dev/ttyv0' ]; then /usr/local/bin/startx fi and it does not work. If the shell on your auto-login account is /bin/sh, then you should put your X startup in .profile -- syntax is identical to the bash example you showed. If the shell on your auto-login account is /bin/csh or /bin/tcsh (which are really exactly the same thing on FreeBSD), then you should put your X startup in .login In this case the syntax is different, but you can copy wblock's example from the forum thread you referenced. Either of those shells should work. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: autologin on default shell /bin/sh
On Sun, 25 Sep 2011, Antonio Olivares wrote: I tried to edit ~/.cshrc and copied W Block's example, but it did not work https://freebsd-forums.liquidneon.com/showthread.php?t=22304 Current link: http://forums.freebsd.org/showthread.php?t=22304 That example was copied from a specially-configured FreeBSD image that auto-starts in X. Try it exactly. If it doesn't work, please be specific about what it does. ___ 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: autologin on default shell /bin/sh
On Sun, Sep 25, 2011 at 12:44 PM, Warren Block wbl...@wonkity.com wrote: On Sun, 25 Sep 2011, Antonio Olivares wrote: I tried to edit ~/.cshrc and copied W Block's example, but it did not work https://freebsd-forums.liquidneon.com/showthread.php?t=22304 Current link: http://forums.freebsd.org/showthread.php?t=22304 That example was copied from a specially-configured FreeBSD image that auto-starts in X. Try it exactly. If it doesn't work, please be specific about what it does. I tried it and it worked as Matthew suggested for one time. I put it in .profile and it worked one time. Subsequent reboots, I have to login then startx runs automatically This is what I am seeing: Sep 25 13:00:04 quadcore sm-mta[1432]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon Daemon0: cannot bind: Can't assign requested address Sep 25 13:00:04 quadcore sm-mta[1432]: daemon Daemon0: problem creating SMTP socket Sep 25 13:00:04 quadcore sm-mta[1432]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon Daemon0: server SMTP socket wedged: exiting I decided to install nvidia driver and ran sysconfig to install kernel source to be able to install it, finally succeeded, but then it erased some settings the file /etc/devd.conf where scanner settings(HP Scanjet 3300C) were stored and I had to put it back and reconfigure the HP Deskjet 812 printer. I don't use sendmail and I get these errors. Thanks for any suggestions to fix this. Regards, Antonio ___ 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: autologin on default shell /bin/sh
On Sun, 25 Sep 2011, Antonio Olivares wrote: On Sun, Sep 25, 2011 at 12:44 PM, Warren Block wbl...@wonkity.com wrote: On Sun, 25 Sep 2011, Antonio Olivares wrote: I tried to edit ~/.cshrc and copied W Block's example, but it did not work https://freebsd-forums.liquidneon.com/showthread.php?t=22304 Current link: http://forums.freebsd.org/showthread.php?t=22304 That example was copied from a specially-configured FreeBSD image that auto-starts in X. Try it exactly. If it doesn't work, please be specific about what it does. I tried it and it worked as Matthew suggested for one time. I put it in .profile and it worked one time. That will depend on the user's shell; the code is written for csh and will have to be changed for sh or bash. Subsequent reboots, I have to login then startx runs automatically That would say the autologin entry isn't right. Incidentally, the built-in test(1) command can conflict with use of the word test, so it's best to use something else. At least for filenames, it might not be a problem here.___ 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 report bin/157732
On Sat, 18 Jun 2011 14:45:51 -0400 (EDT) Igor free...@str.komkon.org wrote: 1. I don't think that the proposed patch by itself would be reasonable. Some limit should be imposed. According to the RFC-1123 (2.1) (circa October 1989), Host software MUST handle host names of up to 63 characters and SHOULD handle host names of up to 255 characters. http://www.ietf.org/rfc/rfc1123.txt I am not sure if any subsequent RFC changed that. The wording is, interestingly, ambiguous, especially when comparing RFC1123 to earlier and later RFCs. It looks like one changed ones mind several times or was not particularly cautious with the wording: From _should_ I would derive that it is _recommended_ that sw supports up to 255 characters. RFC2181 (http://tools.ietf.org/html/rfc2181#section-11) _limits_ domain names to 255 octets, which sound like 254 characters to me (adding one for the implicit terminating '.'. That is also what RFC1035 specifies (§2.3.4, http://www.ietf.org/rfc/rfc1035.txt), so that Host software MUST handle host names of up to 63 characters and SHOULD handle host names of up to 255 characters. Thus, RFC 1123 should rather be read ... should handle host names of _at most_ 255 octets. This is also what Tanenbaum, Computer Networks, 5th ed, is stating when discussing DNS. Interestingly, wikipedia.org claims only 253 characters, which sounds to be like a superfluous double subtraction of the terminating dot. In some discussions on the net, I've seen people mentioning that any component (between the dots) of the host name should not exceed 63 characters. Upon a very quick search, I could find only one somewhat reliable source that supporting that: http://support.microsoft.com/?kbid=909264SD=tech The maximum length of the host name and of the fully qualified domain name (FQDN) is 63 octets per label and 255 bytes per FQDN. This maximum includes 254 bytes for the FQDN and one byte for the ending dot. see above I would assume that the length checks corresponding to these rules should be implemented. I can follow your argument up to here. What I do not understand is why anything bad should happen if you supply an argument of greater length to inet_addr(). Since more recent RFCs allowed non-ASCII hostnames, that factor should be taken into account as well. See, e.g. here, for the discussion of that: http://support.microsoft.com/kb/245809 You are probably right, but that is well over my head. Superficially looking at the relevant RFCs (i.e., 3492 and 5891), there does not seem an extension of domain record length to be issued there. 2. You are probably right in checking to make sure that bumping up that limit of the hostname length would not result in a buffer overflow somewhere downstream. You should probably check that inet_addr() and all other relevant functions define the variables of the type and length that can handle this longer input. I noticed that some Linux (2.6.26-2-686) I had access to, was capable of handling that long host name. So, you might want to pick at how it is handled by Linux. (Unless that might create some sort of copyright/license issues.) Looking over the fence, the Linux traceroute calls getaddr(), which does check against hostname length and also has a limit of 64. Calling traceroute with anything longer than 64 chars will result in a traceroute: hostname abcdefghi.abcdefghi.abcdefghi.ab... is too long error. Solaris, on the other hand, calls a getaddr() in getaddrinfo (http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libsocket/inet/getaddrinfo.c), which checks against a MAXHOSTNAMELENGTH=256 defined in netdb.h (http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libresolv/netdb.h). Anyway, it performs for the example from the PR. When supplying an arbitary string longer than 255 chars, traceroute from Solaris terminates with a memory allocation error as defined in EAI_MEMORY (also defined in netdb.h). TrustedBSD has the same 64 chars limit and is, I gather, not too dissimilar. As an aside, inet_addr() is, i gather, part of POSIX (http://pubs.opengroup.org/onlinepubs/009695399/functions/inet_addr.html), so I wonder, why so many do not implement inet_getaddr(), but have some home-brew called get_addr()? 3. In either case, I would assume that this number should not be hardcoded in the function, but instead defined in one of the header files (and properly documented) (e.g. HostNameMaxLength). Such as in Solaris, ... BTW, there is a MAXHOSTNAMELEN 64 defined in traceroute.c (http://fxr.aydogan.net/xref/src/contrib/traceroute/traceroute.c#267) ... it escapes me why it isn't used. 4. Yet another thought is that some folks involved into the TrustedBSD project may have very good expertise on this or related issues. Consider searching the source tree in TrustedBSD, in case something appears there that was not brought back to FreeBSD. You might also want to shoot a message with a
problem report bin/157732, patch included
Currently, I have issues mailing to *@freebsd.org, so please reply to
c...@cruwe.de.
I have started looking at FreeBSD bug reports recently to improve my
skills in C, to learn more about operating systems which I am
concentrating on at university and, at some point, contribute should my
abilities permit (tired of being consumer of other's work only).
I am not entirely sure I am addressing the right list, setting my issue
on the right track will be much appreciated, ;-)
I have analysed http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/157732
as an excercise and found a hard string limit to be encoded into
traceroute.c, checking whether the hostname passed to traceroute is
longer than 64 (traceroute line 1621, cf.
http://fxr.aydogan.net/xref/src/contrib/traceroute/traceroute.c#1621).
The same code can be found in NetBSD and probably some more programs,
as traceroute appears to be rather old code (Tue Dec 20 03:50:13 PST
1988 according to comment).
Reading futher, I noticed, that inet_addr() was used to get IP from the
hostname. I have not found any resources hinting that inet_addr() was
not able to deal with hostnames longer than 64. although there is a
report of a tracesroute (similar?) that could produce buffer overflows
with long hostnames.
Experimentally, I have removed the offending lines, compiled a world
and ran the new traceroute with the example Igor
free...@str.komkon.org provided, i.e.,
./playworld/usr/sbin/traceroute
hlfxns0188w-099192079201.pppoe-dynamic.high-speed.ns.bellaliant.net
traceroute to
hlfxns0188w-099192079201.pppoe-dynamic.high-speed.ns.bellaliant.net
(99.192.79.201), 64 hops max, 52 byte packets
1 speedport.ip (192.168.2.1) 0.419 ms 0.442 ms 0.442 ms
2 217.0.118.104 (217.0.118.104) 37.232 ms 37.396 ms 36.645 ms
3 87.186.244.186 (87.186.244.186) 38.319 ms 38.672 ms 37.741 ms
4 d-ec1-i.D.DE.NET.DTAG.DE (62.154.43.134) 38.376 ms 217.239.37.150
(217.239.37.150) 38.495 ms d-ec1-i.d.de.net.dtag.de (62.154.43.134)
38.839 ms
5 194.25.211.130 (194.25.211.130) 56.736 ms 38.338 ms 38.484 ms
6 xe-8-1-0.was10.ip4.tinet.net (89.149.183.154) 134.724 ms
xe-7-1-0.was10.ip4.tinet.net (89.149.183.150) 132.715 ms 133.687 ms
7 bell-aliant-regional-communications-gw.ip4.tinet.net
(77.67.71.210) 131.050 ms 130.681 ms 129.450 ms
8 xe-5-1-0.cr02.hlfx.ns.aliant.net (207.231.227.5) 149.687 ms 150.815
ms xe-5-0-1.cr02.hlfx.ns.aliant.net (207.231.227.9) 163.629 ms
9 lag-2-84.88w.ba16.hlfx.ns.aliant.net (142.176.53.57) 152.538 ms
150.338 ms te-4-0-0-83.88w.ba16.hlfx.ns.aliant.net (142.176.53.41)
151.741 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * *^C
after which, as you can see, I aborted. The hostname looks like some
dialup line host, which may or may not be online (and according to a
ping, isn't). It can be seen, that the function called after that
ominous 64 check, inet_addr(), returns what appears to be a valid ip.
I can imagine several reasons for forbidding any hostnames 64, among
others, limited resources on machines at the time of traceroute being
written (1988) or, more importantly, security considerations similar to
the buffer overflow issue I found on the net. I can find no issues
regarding hostname-lenght in inet_addr(), though.
As I am new to this kind of work, I still (and will probably for some
time) need help. Can somebody advise me on if and if, where, to conduct
further research on the nature of the ! 64 issue and if and if, how,
to analyse possible security considerations of that !64 issue?
Futhermore, should nobody have any ideas on my fix being dangerous or
not, how can I have my fix reviewed more thoroughly (and possibly
integrated)?
Thank you for our help, have a nice weekend, cheers
--
Christopher J. Ruwe
TZ GMT + 2
--
Christopher J. Ruwe
TZ GMT + 2--- /usr/src/contrib/traceroute/traceroute.c 2009-09-13 13:34:33.0 +0200
+++ /usr/home/chris/playsrc/contrib/traceroute/traceroute.c 2011-06-17 16:11:01.095616587 +0200
@@ -1625,11 +1625,11 @@
register char **p;
register u_int32_t addr, *ap;
- if (strlen(hostname) 64) {
+ /*if (strlen(hostname) 64) {
Fprintf(stderr, %s: hostname \%.32s...\ is too long\n,
prog, hostname);
exit(1);
- }
+ }*/
hi = calloc(1, sizeof(*hi));
if (hi == NULL) {
Fprintf(stderr, %s: calloc %s\n, prog, strerror(errno));
___
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 report bin/157732, patch included
1. I don't think that the proposed patch by itself would be reasonable. Some limit should be imposed. According to the RFC-1123 (2.1) (circa October 1989), Host software MUST handle host names of up to 63 characters and SHOULD handle host names of up to 255 characters. http://www.ietf.org/rfc/rfc1123.txt I am not sure if any subsequent RFC changed that. In some discussions on the net, I've seen people mentioning that any component (between the dots) of the host name should not exceed 63 characters. Upon a very quck search, I could find only one somewhat reliable source that supporting that: http://support.microsoft.com/?kbid=909264SD=tech The maximum length of the host name and of the fully qualified domain name (FQDN) is 63 octets per label and 255 bytes per FQDN. This maximum includes 254 bytes for the FQDN and one byte for the ending dot. I would assume that the length checks corresponding to these rules should be implemented. Since more recent RFCs allowed non-ascii hostnames, that factor should be taken into account as well. See, e.g. here, for the discussion of that: http://support.microsoft.com/kb/245809 2. You are probably right in checking to make sure that bumping up that limit of the hostname length would not result in a buffer overflow somewhere downstream. You should probably check that inet_addr() and all other relevant functions define the variables of the type and length that can handle this longer input. I noticed that some Linux (2.6.26-2-686) I had access to, was capable of handling that long host name. So, you might want to pick at how it is handled by Linux. (Unless that might create some sort of copyright/license issues.) 3. In either case, I would assume that this number should not be hardcoded in the function, but instead defined in one of the header files (and properly documented) (e.g. HostNameMaxLength). 4. Yet another thought is that some folks involved into the TrustedBSD project may have very good expertise on this or related issues. Consider searching the source tree in TrustedBSD, in case something appears there that was not brought back to FreeBSD. You might also want to shoot a message with a question to Robert Watson rwat...@freebsd.org or FreeBSD Security Team sect...@freebsd.org Good luck! Igor On Sat, 18 Jun 2011, Christopher J. Ruwe wrote: Currently, I have issues mailing to *@freebsd.org, so please reply to c...@cruwe.de. I have started looking at FreeBSD bug reports recently to improve my skills in C, to learn more about operating systems which I am concentrating on at university and, at some point, contribute should my abilities permit (tired of being consumer of other's work only). I am not entirely sure I am addressing the right list, setting my issue on the right track will be much appreciated, ;-) I have analysed http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/157732 as an excercise and found a hard string limit to be encoded into traceroute.c, checking whether the hostname passed to traceroute is longer than 64 (traceroute line 1621, cf. http://fxr.aydogan.net/xref/src/contrib/traceroute/traceroute.c#1621). The same code can be found in NetBSD and probably some more programs, as traceroute appears to be rather old code (Tue Dec 20 03:50:13 PST 1988 according to comment). Reading futher, I noticed, that inet_addr() was used to get IP from the hostname. I have not found any resources hinting that inet_addr() was not able to deal with hostnames longer than 64. although there is a report of a tracesroute (similar?) that could produce buffer overflows with long hostnames. Experimentally, I have removed the offending lines, compiled a world and ran the new traceroute with the example Igor free...@str.komkon.org provided, i.e., ./playworld/usr/sbin/traceroute hlfxns0188w-099192079201.pppoe-dynamic.high-speed.ns.bellaliant.net traceroute to hlfxns0188w-099192079201.pppoe-dynamic.high-speed.ns.bellaliant.net (99.192.79.201), 64 hops max, 52 byte packets 1 speedport.ip (192.168.2.1) 0.419 ms 0.442 ms 0.442 ms 2 217.0.118.104 (217.0.118.104) 37.232 ms 37.396 ms 36.645 ms 3 87.186.244.186 (87.186.244.186) 38.319 ms 38.672 ms 37.741 ms 4 d-ec1-i.D.DE.NET.DTAG.DE (62.154.43.134) 38.376 ms 217.239.37.150 (217.239.37.150) 38.495 ms d-ec1-i.d.de.net.dtag.de (62.154.43.134) 38.839 ms 5 194.25.211.130 (194.25.211.130) 56.736 ms 38.338 ms 38.484 ms 6 xe-8-1-0.was10.ip4.tinet.net (89.149.183.154) 134.724 ms xe-7-1-0.was10.ip4.tinet.net (89.149.183.150) 132.715 ms 133.687 ms 7 bell-aliant-regional-communications-gw.ip4.tinet.net (77.67.71.210) 131.050 ms 130.681 ms 129.450 ms 8 xe-5-1-0.cr02.hlfx.ns.aliant.net (207.231.227.5) 149.687 ms 150.815 ms xe-5-0-1.cr02.hlfx.ns.aliant.net (207.231.227.9) 163.629 ms 9 lag-2-84.88w.ba16.hlfx.ns.aliant.net (142.176.53.57) 152.538 ms 150.338 ms te-4-0-0-83.88w.ba16.hlfx.ns.aliant.net (142.176.53.41) 151.741 ms 10 * * * 11 * * * 12 * * * 13 * * * 14
Installing .bin file?
On one of my old servers I'm running FreeBSD 6.3 and I'm having some disk problems. The raid card is a Promise TX4310 and I'd like to install Webpam ( http://firstweb.promise.com/support/download/download2_eng.asp?productId=136category=utilityos=100go=GO) to swap + rebuild two broken disks and to have an overview via a webgui. So, I download *WebPAM for FreeBSD*http://firstweb.promise.com/upload/Support/Utility/freebsd_Webpam.rar, unrar it and find a .bin file inside. How do I install a .bin file on FreeBSD? I'm used to makefiles etc. Thanks for any help! Best, Andy ___ 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: Installing .bin file?
On Thu, 12 May 2011 13:10:55 +0200, Andy Wodfer wod...@gmail.com wrote: How do I install a .bin file on FreeBSD? I'm used to makefiles etc. First off all, check _what_ kind of file it is. % file filename If it's a Bourne shell script, run % sh filename If it's a binary that runs on FreeBSD, run % chmod +x filename % ./filename The .bin seems to indicate that it is a binary file, so the 3rd method mentioned should apply. If you need root privileges for the installation process, use su or sudo / super / ... according to your preferences. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Memory limit in xz (/usr/local/bin/xz)
I have the same problem when I want to upgrade libtool from 15 to 22, thanks. On Tue, Jun 15, 2010 at 10:57 AM, Olivier Nicole olivier.nic...@cs.ait.ac.th wrote: Hi, Since I upgraded that machine from 6.x to 7.3 I am hitting a memory limit with xz when trying to build/upgrade several ports. The error message looks like: /usr/local/bin/xz: /usr/ports/distfiles//libpng-1.4.1.tar.xz: Memory usage limit reached /usr/local/bin/xz: Limit was 46 MiB, but 65 MiB would have been needed Is there a config parameter to tell the make files in /usr/ports to desactivate xz memory limit? Best regards, Olivier ___ 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 -- Dsewnr Lu ___ 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: Memory limit in xz (/usr/local/bin/xz)
I have the same problem when I want to upgrade libtool from 15 to 22, thanks. True, libtool is among the several ports affected. For libtool I uncompressed by hand and so make accepted to complete, but it defeats the purpose of portupgrade if one has to do everything by hand. Since I upgraded that machine from 6.x to 7.3 I am hitting a memory limit with xz when trying to build/upgrade several ports. The error message looks like: /usr/local/bin/xz: /usr/ports/distfiles//libpng-1.4.1.tar.xz: Memory usage limit reached /usr/local/bin/xz: Limit was 46 MiB, but 65 MiB would have been needed Is there a config parameter to tell the make files in /usr/ports to desactivate xz memory limit? TIA, Olivier ___ 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: Memory limit in xz (/usr/local/bin/xz)
On Tuesday 15 June 2010 03:57:28 Olivier Nicole wrote: Hi, Since I upgraded that machine from 6.x to 7.3 I am hitting a memory limit with xz when trying to build/upgrade several ports. The error message looks like: /usr/local/bin/xz: /usr/ports/distfiles//libpng-1.4.1.tar.xz: Memory usage limit reached /usr/local/bin/xz: Limit was 46 MiB, but 65 MiB would have been needed Is there a config parameter to tell the make files in /usr/ports to desactivate xz memory limit? From xz(1): To prevent uncomfortable surprises caused by huge memory usage, xz has a built-in memory usage limiter. While some operating systems provide ways to limit the memory usage of processes, relying on it wasn't deemed to be flexible enough. The default limit depends on the total amount of physical RAM: [...] The default limit can be overridden with --memory=limit. and ENVIRONMENT XZ_OPT A space-separated list of options is parsed from XZ_OPT before parsing the options given on the command line. Note that only options are parsed from XZ_OPT; all non-options are silently ignored. Parsing is done with getopt_long(3) which is used also for the command line arguments. -- Bruce Cran ___ 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
Memory limit in xz (/usr/local/bin/xz)
Hi, Since I upgraded that machine from 6.x to 7.3 I am hitting a memory limit with xz when trying to build/upgrade several ports. The error message looks like: /usr/local/bin/xz: /usr/ports/distfiles//libpng-1.4.1.tar.xz: Memory usage limit reached /usr/local/bin/xz: Limit was 46 MiB, but 65 MiB would have been needed Is there a config parameter to tell the make files in /usr/ports to desactivate xz memory limit? Best regards, Olivier ___ 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: Memory limit in xz (/usr/local/bin/xz)
I have the same problem when I want to upgrade libtool from 15 to 22, thanks. On Tue, Jun 15, 2010 at 10:57 AM, Olivier Nicole olivier.nic...@cs.ait.ac.th wrote: Hi, Since I upgraded that machine from 6.x to 7.3 I am hitting a memory limit with xz when trying to build/upgrade several ports. The error message looks like: /usr/local/bin/xz: /usr/ports/distfiles//libpng-1.4.1.tar.xz: Memory usage limit reached /usr/local/bin/xz: Limit was 46 MiB, but 65 MiB would have been needed Is there a config parameter to tell the make files in /usr/ports to desactivate xz memory limit? Best regards, Olivier ___ 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 -- Dsewnr Lu ___ 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: usage of /usr/bin
Allow me an addition: On Wed, 7 Apr 2010 10:13:10 -0700, Charlie Kester corky1...@comcast.net wrote: On Wed 07 Apr 2010 at 00:24:51 PDT Fbsd1 wrote: Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. In many configurations, /bin and /usr/bin are not in the same slice. In some cases, they're not even on the same drive. I think you wanted to say that they often aren't on the same partition (not slice), but it is possible to have them on different slices, as well as disks, as you mentioned. Example: /dev/ad0s1a / - /bin, /sbin, /etc reside here /dev/ad0s1f /usr- /usr/bin, as well as /usr/local In this example, both are on the same disk and within the same slice, but on different partitions. In case of mount trouble, / would usually be available read-only, to provide a kind of reduced maintenance mode, and /usr wouldn't be mounted at all. Think about scenarios where /usr fails to mount for some reason. Then look at what's in /bin compared to what's in /usr/bin, and perhaps you'll understand the logic of it. The manpage man hier explains it very well. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: usage of /usr/bin
On Wed, 07 Apr 2010 20:21:57 -0400, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Fbsd1 fb...@a1poweruser.com writes: Your wrong. I installed the package of postfix and it installed it self into /usr/bin with out any help from me. Believe it or not, I checked before responding, so I'm *not* wrong. I said that the port populates into /usr/local like it should, and having it on several machines for nearly a decade now, I knew that to be the case. You then changed that to refer to a package rather than a port; I don't know where you got your packages from, but I checked the packages for 8-STABLE and for 8.0-RELEASE, and saw that they install into /usr/local as well. So it sounds like your packages didn't come from the FreeBSD project, if they are really installing anything into /usr/bin. Just as a sanity check: what, specifically, is installed into /usr/bin on your system? Most of the postfix executables go into sbin rather than bin anyway, so it's possible that something in the mailwrapper system is confusing you. If you don't have a /usr/local/sbin/postfix, but have a /usr/sbin/postfix instead, then this is not the case. A comfortable, maybe overcomplicated way to check what a package will install - without actually installing it - is to use the option -n for pkg_add (which obviously operates on packages, not on ports). So you could do: pkg_add -fKnrv postfix /tmp/postfix_add.txt This even works if postfix is already installed. The options, for a short reference, are: -f = force, -K = keep, -n = no install, -r = remote and -v = verbose. You can then search for lines that address specific locations in /usr/bin rather than /usr/local/bin. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: usage of /usr/bin
On Thu, Apr 8, 2010 at 1:06 AM, Fbsd1 fb...@a1poweruser.com wrote: Lowell Gilbert wrote: Fbsd1 fb...@a1poweruser.com writes: But that is not true. The postfix port populates /usr/bin. By default, it does not. You have to enable the Install into /usr and /etc/postfix configuration option for it to do so. I don't recommend that anyone do it without a *really* good reason. Turn that option back off and you'll be fine. Your wrong. I installed the package of postfix and it installed it self into /usr/bin with out any help from me. You're argument then is with the person who build that package as it was obviously build incorrectly. The supported manner to install postfix (at least from my understanding) is from ports and that by default installs withing the /usr/local subtree. -- Opportunity is most often missed by people because it is dressed in overalls and looks like work. Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ 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
usage of /usr/bin
Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. ___ 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: usage of /usr/bin
On Wed, 07 Apr 2010 15:24:51 +0800, Fbsd1 fb...@a1poweruser.com wrote: Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. No. The /usr/local subtree (LOCAL) is for local additions (ports and packages), while things outside this structure usually belong to the system itself; I'm excluding mounted filesystem and other things here for a moment. /usr/ contains the majority of user utilities and applications bin/ common utilities, programming tools, and applica- tions But: local/local executables, libraries, etc. Also used as the default destination for the FreeBSD ports framework. Within local/, the general layout sketched out by hier for /usr should be used. Exceptions are the man directory (directly under local/ rather than under local/share/), ports documentation (in share/doc/port/), and /usr/local/etc (mimics /etc). Because we are on FreeBSD, there's excellent documentation that shows how and why the system tree has a well intended layout. :-) The command % man hier will explain everything in detail. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: usage of /usr/bin
Because /usr/local is used to store binaries installed from ports or packages :) You should check the man pages or the handbook for this. Regards, Ivailo Tanusheff Deputy Head of IT Department ProCredit Bank (Bulgaria) AD Fbsd1 fb...@a1poweruser.com Sent by: owner-freebsd-questi...@freebsd.org 07.04.2010 10:25 To FreeBSD Questions freebsd-questions@freebsd.org cc Subject usage of /usr/bin Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. ___ 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: usage of /usr/bin
Polytropon wrote: On Wed, 07 Apr 2010 15:24:51 +0800, Fbsd1 fb...@a1poweruser.com wrote: Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. No. The /usr/local subtree (LOCAL) is for local additions (ports and packages), while things outside this structure usually belong to the system itself; I'm excluding mounted filesystem and other things here for a moment. /usr/ contains the majority of user utilities and applications bin/ common utilities, programming tools, and applica- tions But: local/local executables, libraries, etc. Also used as the default destination for the FreeBSD ports framework. Within local/, the general layout sketched out by hier for /usr should be used. Exceptions are the man directory (directly under local/ rather than under local/share/), ports documentation (in share/doc/port/), and /usr/local/etc (mimics /etc). Because we are on FreeBSD, there's excellent documentation that shows how and why the system tree has a well intended layout. :-) The command % man hier will explain everything in detail. But that is not true. The postfix port populates /usr/bin. And I am sure postfix is not the only port to do this also. This intermingling of RELEASE binaries and port binaries in /usr/bin is a really big problem when trying to build jails. Any past ports which have been included into the base release should not be in /usr period. Saying system user utilizes are in /user/bin then why is fdisk or sysinstall not there also. That don't make sense. It time to modernize the directory layout keeping all RELEASE binaries out of /usr. I would think moving the /usr RELEASE binaries by the RELEASE development team is a far smaller task then reviewing all 21,500 ports for the bad ones that don't target /usr/local/bin and then correcting their make files. Before jails this problem was not a problem, But with the growing usage of jails this is becoming a major incentive to not use jails at all. ___ 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: usage of /usr/bin
On Wednesday 07 April 2010 11:13:13 Fbsd1 wrote: Polytropon wrote: On Wed, 07 Apr 2010 15:24:51 +0800, Fbsd1 fb...@a1poweruser.com wrote: Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. No. The /usr/local subtree (LOCAL) is for local additions (ports and packages), while things outside this structure usually belong to the system itself; I'm excluding mounted filesystem and other things here for a moment. [snip] But that is not true. The postfix port populates /usr/bin. I haven't installed postfix, but is this possibly related to the recently (2010-03-22) added option to install postfix into the base? In which case the commit six days later claims to correct a problem with the default (non-base) install. Jonathan ___ 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: usage of /usr/bin
On Wed, 07 Apr 2010 17:13:13 +0800, Fbsd1 fb...@a1poweruser.com wrote: But that is not true. It is, and the example you're giving is one of the exceptions that secures the truth of the statement given in man hier. :-) The postfix port populates /usr/bin. And I am sure postfix is not the only port to do this also. Basically, there are ports that can be installed outside /usr/local, or are especially intended to be. For example postfix, a MTA that can replace the system one's (sendmail), so it takes its position. Other ports also allow the setting of a certain PREFIX variable that will override /usr/local, which is the default setting. Note that it isn't very often done, and if it is, it is intended (as the postfix example you've given, or the sometimes requested statically linked bash within the base system). This intermingling of RELEASE binaries and port binaries in /usr/bin is a really big problem when trying to build jails. Yes, understandable. Any past ports which have been included into the base release should not be in /usr period. It has been the system administrator who decides to install them there. If he insists on replacing some part of the base system with a port, or to add a port outside of /usr/local, it's his decision to do so. Of course, this can lead into problems. Saying system user utilizes are in /user/bin then why is fdisk or sysinstall not there also. Because the creators of FreeBSD have decided that those programs to belong to different classes of programs, and according to man hier: /usr/sbin/sysinstall /usr/ contains the majority of user utilities and applications sbin/ system daemons system utilities (executed by users) /sbin/fdisk /sbin/ system programs and administration utilities fundamental to both single-user and multi-user environments There are often decisions that aren't obvious (or even don't make sense) at first sight. That don't make sense. There are some historical reasons for that. Would you believe me if I told you that the mount binary historically was /etc/mount? Or /etc/fsck? Or how about /bin/adm? Other kinds of UNIX have different hierarchy concepts and naming conventions. And Linux has many more. It time to modernize the directory layout keeping all RELEASE binaries out of /usr. Hmmm... modernize... I know of some Linux that maps all the historical locations into Programs/ or Config/ subtrees... I'm not sure if I would be happy with FreeBSd going the same way, or even further, because I usually find things when I need to search from them, and I can mostly do it by brain - rather than /usr/bin/find. :-) I would think moving the /usr RELEASE binaries by the RELEASE development team is a far smaller task then reviewing all 21,500 ports for the bad ones that don't target /usr/local/bin and then correcting their make files. If should be relatively easy to spot them by variations of Makefile, especially the mentioned PREFIX setting which needs to be overridden in order to leave /usr/local. If I have that in mond correctly, LOCALBASE is the name of the variable that controls where things are put; there was another one called X11BASE, which is deprecated because /usr/X11R6 is now inside /usr/local. Before jails this problem was not a problem, But with the growing usage of jails this is becoming a major incentive to not use jails at all. On the other hand, if you encounter such a problem by the presence of a nonstandard - meaning not being part of the base system - mail transfer agent, then maybe its documentation should mention to pay attention when using it instead of what the system brings, so further problems with jails can be avoided, or at least cured (by a correct procedure given in the documentation). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: usage of /usr/bin
Fbsd1 fb...@a1poweruser.com writes: But that is not true. The postfix port populates /usr/bin. By default, it does not. You have to enable the Install into /usr and /etc/postfix configuration option for it to do so. I don't recommend that anyone do it without a *really* good reason. Turn that option back off and you'll be fine. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: usage of /usr/bin
On Wed 07 Apr 2010 at 00:24:51 PDT Fbsd1 wrote: Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. In many configurations, /bin and /usr/bin are not in the same slice. In some cases, they're not even on the same drive. Think about scenarios where /usr fails to mount for some reason. Then look at what's in /bin compared to what's in /usr/bin, and perhaps you'll understand the logic of it. ___ 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: usage of /usr/bin
On Wed 07 Apr 2010 at 10:13:10 PDT Charlie Kester wrote: Think about scenarios where /usr fails to mount for some reason. Then look at what's in /bin compared to what's in /usr/bin, and perhaps you'll understand the logic of it. I should add that comparing the contents of /usr/sbin and /sbin is also instructive. ___ 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: usage of /usr/bin
Lowell Gilbert wrote: Fbsd1 fb...@a1poweruser.com writes: But that is not true. The postfix port populates /usr/bin. By default, it does not. You have to enable the Install into /usr and /etc/postfix configuration option for it to do so. I don't recommend that anyone do it without a *really* good reason. Turn that option back off and you'll be fine. Your wrong. I installed the package of postfix and it installed it self into /usr/bin with out any help from me. ___ 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: usage of /usr/bin
Jonathan McKeown wrote: On Wednesday 07 April 2010 11:13:13 Fbsd1 wrote: Polytropon wrote: On Wed, 07 Apr 2010 15:24:51 +0800, Fbsd1 fb...@a1poweruser.com wrote: Why are there RELEASE base files in /usr/bin. I thought /usr was to only contain binaries installed from ports or packages. No. The /usr/local subtree (LOCAL) is for local additions (ports and packages), while things outside this structure usually belong to the system itself; I'm excluding mounted filesystem and other things here for a moment. [snip] But that is not true. The postfix port populates /usr/bin. I haven't installed postfix, but is this possibly related to the recently (2010-03-22) added option to install postfix into the base? In which case the commit six days later claims to correct a problem with the default (non-base) install. Jonathan I installed the package of postfix and it installed is self into /usr/bin with out any help from me. Packages are frozen some time before the RELEASE is distributed to the public. The change you question would have never made it into the RELEASE 8.0 package. ___ 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: usage of /usr/bin
On Apr 7, 2010, at 4:06 PM, Fbsd1 wrote: Your wrong. I installed the package of postfix and it installed it self into /usr/bin with out any help from me. Unless you or whoever built the package changed $PREFIX: % pkg_info -Lx postfix Information for postfix-2.7.0,1: Files: /usr/local/man/man1/postalias.1.gz /usr/local/man/man1/postcat.1.gz /usr/local/man/man1/postconf.1.gz /usr/local/man/man1/postdrop.1.gz [ ... ] /usr/local/share/doc/postfix/tlsmgr.8.html /usr/local/share/doc/postfix/generic.5.html /usr/local/etc/rc.d/postfix ...every file is under /usr/local. Perhaps you set INST_BASE option? [ ] INST_BASE Install into /usr and /etc/postfix Regards, -- -Chuck ___ 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: usage of /usr/bin
Chuck Swiger wrote: On Apr 7, 2010, at 4:06 PM, Fbsd1 wrote: Your wrong. I installed the package of postfix and it installed it self into /usr/bin with out any help from me. Unless you or whoever built the package changed $PREFIX: % pkg_info -Lx postfix Information for postfix-2.7.0,1: Files: /usr/local/man/man1/postalias.1.gz /usr/local/man/man1/postcat.1.gz /usr/local/man/man1/postconf.1.gz /usr/local/man/man1/postdrop.1.gz [ ... ] /usr/local/share/doc/postfix/tlsmgr.8.html /usr/local/share/doc/postfix/generic.5.html /usr/local/etc/rc.d/postfix ...every file is under /usr/local. Perhaps you set INST_BASE option? [ ] INST_BASE Install into /usr and /etc/postfix Regards, I installed the package of postfix and it installed is self into /usr/bin with out any help from me. This is now I know that. I swapped a empty drive with my live system drive. Installed the sysinstall kern developer option to get full binaries and sources. After the install I set chflags schg /dir/ and /dir/* for these dir. /bin /boot /lib /libexec /sbin /usr/bin /usr/include /usr/lib /usr/libexec /usr/sbin. This should have protected all those RELEASE base directors and all the files in then. With the dir also having schg on, no files should have been able to be added to it. I then did a ls -lo /dir file to save copy of their content. Then I did pkg_add -r postfix-current. After which i did another ls -lo /dir file and to my surprise i see all these new files have been added to /usr/bin. What am I to think? How else would you explain this? ___ 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: usage of /usr/bin
On Apr 7, 2010, at 4:41 PM, Fbsd1 wrote: I installed the package of postfix and it installed is self into /usr/bin with out any help from me. Hmm, a terrible surprise, I agree. Please ask for a refund of your purchase price from whomever sold you such a package. :-) Regards, -- -Chuck ___ 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: usage of /usr/bin
Fbsd1 fb...@a1poweruser.com writes: Lowell Gilbert wrote: Fbsd1 fb...@a1poweruser.com writes: But that is not true. The postfix port populates /usr/bin. By default, it does not. You have to enable the Install into /usr and /etc/postfix configuration option for it to do so. I don't recommend that anyone do it without a *really* good reason. Turn that option back off and you'll be fine. Your wrong. I installed the package of postfix and it installed it self into /usr/bin with out any help from me. Believe it or not, I checked before responding, so I'm *not* wrong. I said that the port populates into /usr/local like it should, and having it on several machines for nearly a decade now, I knew that to be the case. You then changed that to refer to a package rather than a port; I don't know where you got your packages from, but I checked the packages for 8-STABLE and for 8.0-RELEASE, and saw that they install into /usr/local as well. So it sounds like your packages didn't come from the FreeBSD project, if they are really installing anything into /usr/bin. Just as a sanity check: what, specifically, is installed into /usr/bin on your system? Most of the postfix executables go into sbin rather than bin anyway, so it's possible that something in the mailwrapper system is confusing you. If you don't have a /usr/local/sbin/postfix, but have a /usr/sbin/postfix instead, then this is not the case. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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
