Installing packages from 9.2 Release DVD
Dear All , In sysinstall , there are menu items to install packages from release DVD . In bsdinstall , there is NO such package installation menu items . Another problem is there is no any available information about this subject in the Handbook installation pages ( at least I could not find any one one ) . Is there any such available information link , and is there any possibility to include such information into Handbook pages and Release Notes templates ? When there is no such information , people will use pkg_add -r ... statement although many packages are already in the release DVD which means a large waste of band width . ( Please consider less experienced people : Each year , many persons are entering into an age to try FreeBSD without prior experience about FreeBSD . Lack of necessary information about install is an important obstacle for such new entries . ) Thank you very much . Mehmet Erol Sanliturk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Installing packages from 9.2 Release DVD
On Oct 7, 2013, at 11:35 PM, Mehmet Erol Sanliturk wrote: Dear All , In sysinstall , there are menu items to install packages from release DVD . In bsdinstall , there is NO such package installation menu items . You've got the wrong tool. s/bsdinstall/bsdconfig/ Another problem is there is no any available information about this subject in the Handbook installation pages ( at least I could not find any one one ) . bsdconfig was just born in 9.2-R. Nobody has gotten around to documenting it. I'll be doing the first presentation on it at the vBSDcon [un]Conference coming up in a couple weeks (Oct 25-27th in Reston, VA; hosted by Verisign). Is there any such available information link , and is there any possibility to include such information into Handbook pages and Release Notes templates ? bsdconfig(8) was announced in the quarterly announcements and release highlights for FreeBSD 9.2-R. As for the handbook... it will take time for doc folks to assimilate it. When there is no such information , people will use pkg_add -r ... statement although many packages are already in the release DVD which means a large waste of band width . Only media type that bsdconfig(8) doesn't support is TAPE. However, bsdconfig supports a couple new types of media for accessing packages. Other than that, your old friends of CD/DVD, FTP, HTTP, FTP via Proxy, NFS, and some new ones are all there. ( Please consider less experienced people : Each year , many persons are entering into an age to try FreeBSD without prior experience about FreeBSD . Lack of necessary information about install is an important obstacle for such new entries . ) I appreciate your feedback. Rest assured, less experienced peoples *were* considered. That's why I started work on bsdconfig(8) 3 years ago shortly after the deprecation of sysinstall in base. The curses-UI-loving folks were not forgotten (less experienced or otherwise; a fancy TUI/GUI doesn't necessarily mean it has to be only usable to less skilled folks... take bsdconfig startup for example -- something not normally possible with any other tool regardless of your skill level). -- Devin _ 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
after freebsd-update: /lib/libc.so.7: unsupported file layout
Hi, i have a box with FreeBSD-9.1-Release. I did freebsd-update and since then i get: root@6:/root # jexec 1 /bin/csh /lib/libc.so.7: unsupported file layout root@6:/root # i see /lib/libc.so.7 was updated as i read in some forums, i did: root@6:/root # ldconfig /lib /usr/lib /usr/local/lib root@6:/root # any hints to fix that? i did once again freebsd-update fetch install, and that didn't help. maybe i can rollback? Thanksin advance, -- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert Network Admin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: after freebsd-update: /lib/libc.so.7: unsupported file layout
Hi, heads up: i did freebsd-update rollback on the specific jail and its working again.. it uninstalled the libc.so.7. whats strange is that this jail almost a clean jail nothing is running but cron, sshd and some shoutcat processes, in parallel i have 2 jails that have sshd/crond and much more processes (apache, dns, mysql) that work after the update without a problem. Sami On Tue, Oct 8, 2013 at 2:32 PM, Sami Halabi sodyn...@gmail.com wrote: Hi, i have a box with FreeBSD-9.1-Release. I did freebsd-update and since then i get: root@6:/root # jexec 1 /bin/csh /lib/libc.so.7: unsupported file layout root@6:/root # i see /lib/libc.so.7 was updated as i read in some forums, i did: root@6:/root # ldconfig /lib /usr/lib /usr/local/lib root@6:/root # any hints to fix that? i did once again freebsd-update fetch install, and that didn't help. maybe i can rollback? Thanksin advance, -- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert Network Admin -- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Overrated if_obytes accounting in 8.4-STABLE
Hi! Right now outgoint network interface accounting is broken in stable/8 due to incomplete MFC (r247430) of r241037. That MFC was meant to move if_obytes computation from drbr to distinct drivers. In fact, it did not remove if_obytes computation drom drbr so it is overrated. The patch for stable/8 is presented here: http://www.freebsd.org/cgi/query-pr.cgi?pr=182828 Please fix. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Running a script via PHP
and just to be safe wrap it all up in a VIMAGE jail On 1 October 2013 14:39, Ronald Klop ronald-freeb...@klop.yi.org wrote: On Fri, 27 Sep 2013 23:50:02 +0200, Charles Swiger cswi...@mac.com wrote: Hi-- On Sep 27, 2013, at 2:18 AM, Michael BlackHeart amdm...@gmail.com wrote: Hello there, It's quite off-topic, but I'm using freebsd-stable,so The priblem is - running a script that requires root privileges via PHP (or probably CGI - I do not care, just want it to be secure and working). Unfortunately the combination of PHP, doing something which needs root, and security are inherently contradictory. The least risky approach would be to invoke the needed command via sudo, or possibly a small setuid-root C wrapper program which launches only the needed script with root permissions. Use sudo unless your C wrapper is careful enough to use exec() and not system(), sanitizes $PATH and other env variables, and guards against games with $IFS, shell metachars, and such. Regards, Use sudo, because your home grown C wrapper will make all the mistakes which are already solved in sudo. Or will be spotted in the future in sudo and will never be spotted in your program. Chances are high that future requirements of your C wrapper will turn it in a little sudo. Ronald. __**_ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**stablehttp://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscribe@**freebsd.orgfreebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Who hacked the FreeBSD website?
Greetings, I was performing a ports search, and noticed that all the links providing more information about each port goes to the FreeBSD 404 page. For example, autotrace-0.31.1_23; The link to it is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace the Long description link is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace/pkg-descr?revision=HEAD Both of which return: Page not found. Oh no. :( Any chance FreeBSD has a backup of the web site? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
No, the FreeBSD website was not hacked.... (Re: Who hacked the FreeBSD website?)
Please don't use subject lines like that for broken links... On Tue, Oct 08, 2013 at 08:00:14AM -0700, Chris H wrote: Greetings, I was performing a ports search, and noticed that all the links providing more information about each port goes to the FreeBSD 404 page. For example, autotrace-0.31.1_23; The link to it is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace the Long description link is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace/pkg-descr?revision=HEAD It looks like the paths are messed up somehow. I'll take a look asap. Glen Both of which return: Page not found. Oh no. :( Any chance FreeBSD has a backup of the web site? ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-www To unsubscribe, send any mail to freebsd-www-unsubscr...@freebsd.org pgp_ncvE9IUTw.pgp Description: PGP signature
Re: No, the FreeBSD website was not hacked.... (Re: Who hacked the FreeBSD website?)
Please don't use subject lines like that for broken links... Sorry. I was sure that the ports page was rendered as an automated process. Making it unlikely that such a dramatic change in pathing would be highly unlikely, if not impossible. On Tue, Oct 08, 2013 at 08:00:14AM -0700, Chris H wrote: Greetings, I was performing a ports search, and noticed that all the links providing more information about each port goes to the FreeBSD 404 page. For example, autotrace-0.31.1_23; The link to it is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace the Long description link is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace/pkg-descr?revision=HEAD It looks like the paths are messed up somehow. I'll take a look asap. Aren't changes like this verified before roll out? --Chris Glen Both of which return: Page not found. Oh no. :( Any chance FreeBSD has a backup of the web site? ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-www To unsubscribe, send any mail to freebsd-www-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Who hacked the FreeBSD website?
On Tue, Oct 8, 2013, at 10:00, Chris H wrote: Greetings, I was performing a ports search, and noticed that all the links providing more information about each port goes to the FreeBSD 404 page. For example, autotrace-0.31.1_23; The link to it is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace the Long description link is: http://www.freebsd.org/home/indexbuild/tindex/ports/graphics/autotrace/pkg-descr?revision=HEAD Both of which return: Page not found. Oh no. :( Any chance FreeBSD has a backup of the web site? Not sure what's going on with that, but you can use freshports.org as a backup ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: after freebsd-update: /lib/libc.so.7: unsupported file layout
On Tue, Oct 8, 2013 at 7:32 AM, Sami Halabi sodyn...@gmail.com wrote: Hi, i have a box with FreeBSD-9.1-Release. I did freebsd-update and since then i get: root@6:/root # jexec 1 /bin/csh /lib/libc.so.7: unsupported file layout root@6:/root # i see /lib/libc.so.7 was updated as i read in some forums, i did: root@6:/root # ldconfig /lib /usr/lib /usr/local/lib root@6:/root # any hints to fix that? i did once again freebsd-update fetch install, and that didn't help. maybe i can rollback? Thanksin advance, Does the jail host have a 32-bit (i386) kernel and userland? You would get that error if you tried to run 64-bit software on a 32-bit host. Perhaps you accidentally upgraded your jail to an amd64 image? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Trouble building/upgrading 9-stable
Hi, I'm having trouble upgrading a system running 9-stable to a new revision. buildworld always dies with an internal compiler error during lib/clang/libllvminstcombine. The machine is currently running: FreeBSD fred 9.1-STABLE FreeBSD 9.1-STABLE #0 r251914: Tue Jun 18 20:30:07 BST 2013 root@fred:/usr/obj/usr/src/sys/FRED amd64 I'm trying to upgrade to svn stable/9 r256049. I tried switching off compiler optimisations in make.conf but that didn't work. The very same error happens since August, different revisions. Bits from the script(1)-ed output are: === lib/clang/libllvminstcombine (all) c++ -O -fno-strict-aliasing -pipe -mtune=native -march=native -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine -I. -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd9.2\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd9.2\ -DDEFAULT_SYSROOT=\\ -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine/InstCombineAddSub.cpp -o InstCombineAddSub.o c++ -O -fno-strict-aliasing -pipe -mtune=native -march=native -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine -I. -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd9.2\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd9.2\ -DDEFAULT_SYSROOT=\\ -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine/InstCombineAndOrXor.cpp -o InstCombineAndOrXor.o c++ -O -fno-strict-aliasing -pipe -mtune=native -march=native -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine -I. -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd9.2\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd9.2\ -DDEFAULT_SYSROOT=\\ -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine/InstCombineCalls.cpp -o InstCombineCalls.o c++ -O -fno-strict-aliasing -pipe -mtune=native -march=native -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine -I. -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd9.2\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd9.2\ -DDEFAULT_SYSROOT=\\ -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine/InstCombineCasts.cpp -o InstCombineCasts.o c++ -O -fno-strict-aliasing -pipe -mtune=native -march=native -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/lib/Transforms/InstCombine -I. -I/usr/src/lib/clang/libllvminstcombine/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd9.2\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd9.2\ -DDEFAULT_SYSROOT=\\ -fstack-protector -fno-exceptions -fno-rtti -c
Re: after freebsd-update: /lib/libc.so.7: unsupported file layout
Hi, Your right... Chee. Forgot about it totally... This is my only 32 bit jail used for shoutcast v1. Apparently freebsd-update from host(with -b) grabbed amd64 binarries... Any way to safly update the 32bit jail.. The host is64 however... Sami בתאריך 8 באוק 2013 23:50, Ryan Stone ryst...@gmail.com כתב: On Tue, Oct 8, 2013 at 7:32 AM, Sami Halabi sodyn...@gmail.com wrote: Hi, i have a box with FreeBSD-9.1-Release. I did freebsd-update and since then i get: root@6:/root # jexec 1 /bin/csh /lib/libc.so.7: unsupported file layout root@6:/root # i see /lib/libc.so.7 was updated as i read in some forums, i did: root@6:/root # ldconfig /lib /usr/lib /usr/local/lib root@6:/root # any hints to fix that? i did once again freebsd-update fetch install, and that didn't help. maybe i can rollback? Thanksin advance, Does the jail host have a 32-bit (i386) kernel and userland? You would get that error if you tried to run 64-bit software on a 32-bit host. Perhaps you accidentally upgraded your jail to an amd64 image? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
