Re: Clang - what is the story?
On 22/01/2012 22:53, Da Rock wrote: What part is that? I thought it had to be all c... Not at all. clang and llvm are themselves written in C++. However, it's groff that Roland mentioned as the canonical example of C++ in base. 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: kgzip(8) regression in RELENG_9 GENERIC
On 01/23/2012 12:30 AM, Devin Teske wrote: On Jan 21, 2012, at 1:41 AM, CyberLeo Kitsana wrote: On 01/20/2012 09:02 PM, Devin Teske wrote: Taking a GENERIC 9.0-RELEASE kernel and running kgzip(8) on it produces an unusable kernel which causes immediate BTX halt in loader(8). ... 4. Say: kgzip kernel Curious, it doesn't even look like that binary is hooked into the build process at all on 9.0-RELEASE. Can you clarify what you mean by the above? On a brand new GENERIC box running 9.0-RELEASE with no special knobs: 8 (4b18d544)[cyberleo@jenga ~]$ which kgzip (4b18d544)[cyberleo@jenga ~]$ apropos kgzip (4b18d544)[cyberleo@jenga ~]$ cd /usr/src/usr.sbin (4b18d544)[cyberleo@jenga /usr/src/usr.sbin]$ ls | grep kgzip kgzip (4b18d544)[cyberleo@jenga /usr/src/usr.sbin]$ grep kgzip Makefile (4b18d544)[cyberleo@jenga /usr/src/usr.sbin]$ 8 So it's there, but the SUBDIR entry in the usr.sbin Makefile that hooks it into the build process seems to be missing, whereas things that do exist (freebsd-update, c) are present. It's manpage indicates that it is unsuitable for loader(8) use, Likewise, can you clarify the above? From kgzip.8 in the aforementioned directory: 8 BUGS As symbols are lost, the usefulness of this utility for compressing ker- nels is limited to situations where loader(8) cannot be used; otherwise the preferred method of compressing a kernel is simply to gzip(1) it. 8 and that just running gzip(1) on the kernel file is sufficient; I'm getting an error when loading a gzip(1)'d kernel... don't know how to load module '/kernels/GENERIC-i386-9.0.gz' So I figure, maybe it doesn't like the '.gz' suffix. No go, same error. I think we'll need more information on how your system is set up to boot: partition layout, what boot blocks and loaders are in use, etc. How are you instructing it to load that particular kernel, for example? -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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: php5 port seems broken
Tim Kellers wrote: On 1/22/12 5:35 PM, Tim Dunphy wrote: Hello list, I'm attempting to install php5 from my ports tree. I've attempted the latest version ( 5.3.9 located in /usr/ports/lang/php5) and the 'latest stable' (5.2.17 located in /usr/ports/lang/php52). The result is pretty much the same: [snip] = php-5.3.9.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://dk.php.net/distributions/php-5.3.9.tar.bz2 fetch: http://dk.php.net/distributions/php-5.3.9.tar.bz2: Requested Range Not Satisfiable = Attempting to fetch http://de.php.net/distributions/php-5.3.9.tar.bz2 fetch: http://de.php.net/distributions/php-5.3.9.tar.bz2: Requested Range Not Satisfiable = Attempting to fetch http://es.php.net/distributions/php-5.3.9.tar.bz2 fetch: http://es.php.net/distributions/php-5.3.9.tar.bz2: Requested Range Not Satisfiable = Attempting to fetch http://fi.php.net/distributions/php-5.3.9.tar.bz2 fetch: http://fi.php.net/distributions/php-5.3.9.tar.bz2: Requested Range Not Satisfiable = Attempting to fetch http://fr.php.net/distributions/php-5.3.9.tar.bz2 [snip] When I went to portupgrade mine on 16 Jan I experienced exactly the same. I ended up locating the tarball somewhere, downloaded it, and placed it in distfiles manually. Then the portupgrade went without hitch. I was just wondering if anyone might have a guess as to why this wasn't working? My bet is bad links pointing at a bad tarball. [snip] I just portupgraded my php5 this morning and I was able to fetch the distfile without trouble. It might just be a partially dled file and a checksum mismatch. Sounds like the situation was discovered fairly quick and corrected. [snip] -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Clang - what is the story?
kpn...@pobox.com wrote: Lattice C Later bought out by Microsoft IIRC ___ 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 best practices
Hello portmaster users, If portaudit shows that some installed packages have vulnerabilities, what do you usually do? Do you upgrade only the vulnerable packages, or vulnerable packages and dependent packages (portmaster -r), or perhaps all packages (portmaster -a)? Or do you pkg_delete -a all packages first and then reinstall from scratch (from `portmaster --list-origins` perhaps)? I am a bit uneasy about portmaster -a because, for example, in the output below it intends to install a package which is already installed: pg01-sibptus# portmaster -n -a === Gathering distinfo list for installed ports [dd] Upgrade php5-ldap-5.3.5_1 to php5-ldap-5.3.9 Install net/openldap24-sasl-client Upgrade postgresql-server-9.0.1 to postgresql-server-9.0.6_3 Upgrade tcl-8.5.9 to tcl-8.5.11 Upgrade vim-7.3.81 to vim-7.3.121 Install devel/gettext === Proceed? y/n [y] n === If you would like to upgrade or install some, but not all of the above try adding '-i' to the command line. pg01-sibptus# pg01-sibptus# pg01-sibptus# pkg_info -xo openldap Information for openldap-sasl-client-2.4.24: Origin: net/openldap24-client -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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
kqueue and filenames
Hi, I'm using kqueue for detecting file-events; for additional information I add a struct to udata, when registering an event with kevent. When I delete an event, will be udata deleted too, or do I have to manage the memory for the structs with an own implementation? kevent is triggered when a file is renamed. How do I get the new name? Is there an extra function? In the moment, I see only the possibility by searching the filesystem(folder) for a new name. Thanks for every hint. Matthias Moenchengladbach, Germany ___ 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
SV: php5 port seems broken
-Oprindelig meddelelse- Fra: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] På vegne af Tim Kellers Sendt: den 23 januari 2012 02:04 Til: freebsd-questions@freebsd.org Emne: Re: php5 port seems broken On 1/22/12 7:50 PM, Tim Dunphy wrote: Hello again, Thanks for your input. Before attempting to install php on this machine I updated my ports tree with csvsup. But following the steps in this article helped me to get past this point. http://icesquare.com/wordpress/freebsdproblem-to-update-php-port/ Which was basically: #sudo rm -Rf /var/db/portsnap/* #sudo portsnap fetch extract #sudo portsnap fetch update #cd /usr/ports/distfiles/ #sudo wget http://fi.php.net/distributions/php-5.3.9.tar.bz2 #cd /usr/ports/lang/php5 #sudo make That was all I had to do. :) However I'm onto a new stumbling block, so if you're still tuned in I hope you don't mind if I bounce this off the list. It seems that Apache 2.2 is not recognizing PHP now that it's installed. If I go to a php test page in a web browser this is all I see: ?php // Show all information, defaults to INFO_ALL phpinfo(); // Show just the module information. // phpinfo(8) yields identical results. phpinfo(INFO_MODULES); ? These are the contents of the file I am hitting: ?php // Show all information, defaults to INFO_ALL phpinfo(); // Show just the module information. // phpinfo(8) yields identical results. phpinfo(INFO_MODULES); ? I checked to see that in my main apache config file (httpd.conf) I have this line: LoadModule php5_modulelibexec/apache22/libphp5.so And of course I've restarted apache after installing the php5 port. :) And since apache isn't even recognizing php at this point hitting the test page does not generate any errors in the error logs. Any thoughts/hits/suggestions from here? thanks tim - Original Message - From: RWrwmailli...@googlemail.com To: freebsd-questions@freebsd.org Sent: Sunday, January 22, 2012 7:07:21 PM Subject: Re: php5 port seems broken On Sun, 22 Jan 2012 18:01:29 -0500 Tim Kellers wrote: On 1/22/12 5:35 PM, Tim Dunphy wrote: Hello list, I'm attempting to install php5 from my ports tree. I've attempted the latest version ( 5.3.9 located in /usr/ports/lang/php5) and the 'latest stable' (5.2.17 located in /usr/ports/lang/php52). The result is pretty much the same: suhosin-patch-5.3.9-0.9.10.patch.gz. ===Giving up on fetching files: php-5.3.9.tar.bz2 Make sure the Makefile and distinfo file (/usr/ports/lang/php5/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 I just portupgraded my php5 this morning and I was able to fetch the distfile without trouble. It might just be a partially dled file and a checksum mismatch. if you do a make checksum it will download the file or resume a partial download before checking the hash. You can try (as root) rm -rf /usr/ports/distfiles/php-5.3.9.tar.bz2 and cd /usr/ports/lang/php5 make clean make install clean or make distclean If that gets you past the checksum error, you should be able to build it successfully. Probably the ports tree needs to be updated to pick-up an updated hash value. ___ 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 Did you out this in httpd.conf? from pkg-message.mod: *** Make sure index.php is part of your DirectoryIndex. You should add the following to your Apache configuration file: AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps *** Tim Kellers ___ 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 [] - And have a look at /usr/ports/lang/php5-extentions An easy to follow step by step tutorial http://www.unixmen.com/how-to-install-apache-mysql-php-phpmyadmin-in-freebsd/ G'luck Hasse ___ 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
TAB not jumping to OK in options screen
I installed a new FreeBSD-8.2 system and installed a few ports, no problem Then I do want to install Xorg # cd /usr/ports/x11/xorg # make install clean At the package libxslt 1.1.26_3 it gives me an options screen. I hit TAB to go to the OK button, but it just moves the cursor 8 postions to the right on the same line. I can't get to the OK prommpt With the several packages I installed before I had no problem with the usage of TAB in the options screen. What can be the cause and how to fix 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: freebsd-update and archs
On 01/22/12 03:45, Christer Solskogen wrote: On Sat, Jan 21, 2012 at 1:21 PM, Colin Percival cperc...@freebsd.org wrote: Try doing a release cross-build and compare it against a non-crossed release build; extract the built tarballs and send me a list of which ones aren't identical. I know which files normally build differently so I can look over the list and tell you if there's something which shouldn't be there. I just did, and the file list is the same. Or do you want me to do a md5 of every file? Yes, I meant to compare the contents of files (or their hashes of course). -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ 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: TAB not jumping to OK in options screen
Hi, I've never experienced anything similar but one workaround is to edit the Makefile: and change the Off to On for the options you need, and the other way around for the options you don;t need. Still, the real problem eludes me and that;s the one that needs fixing. -- Best regards, Claudiu Vasadi ___ 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: Horrible installer (was: Re: FreeBSD 9)
All of these complaints can go directly to /dev/null Just as you don't get to express your opinion about the government if you don't vote, you don't get to express your opinion about -RELEASE changes when you didn't run the STABLE/RC/BETAs. You had your chance to help improve FreeBSD for everyone, assuming your concerns really are valid and far-reaching. You opted out. No longer the core team's problem. Closed: WORKSFORME ___ 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: Clang - what is the story?
On Mon, Jan 23, 2012 at 12:01 PM, per...@pluto.rain.com wrote: kpn...@pobox.com wrote: Lattice C Later bought out by Microsoft IIRC ___ 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 Adam David Alan Martin did a very nice intro to CLANG at NYC*BUG in October, in particular the comparison of ease of use with gcc is very nice here: October 5, 2011. ADAM David Alan Martin on Clang on FreeBSD.http://www.fetissov.org/public/nycbug/nycbug-10-05-11.mp3 http://www.fetissov.org/public/nycbug/nycbug-10-05-11.mp3can't seem to find the slides for the talk, maybe someone from admin@nycbug has a link they can share. -- regards, matt ___ 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-update and archs
On Mon, Jan 23, 2012 at 3:03 PM, Colin Percival cperc...@freebsd.org wrote: On 01/22/12 03:45, Christer Solskogen wrote: I just did, and the file list is the same. Or do you want me to do a md5 of every file? Yes, I meant to compare the contents of files (or their hashes of course). Here you go: http://antarctica.no/~solskogen/temp/cross.txt.bz2 http://antarctica.no/~solskogen/temp/native.txt.bz2 http://antarctica.no/~solskogen/temp/diff.txt.bz2 -- chs, ___ 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
Makeopts DEBUG=-g kernel option
Hi there I'm experiencing the following problem: All is we= ll when I boot the standard FreeBSD 8.2 GENERIC kernel. The moment howeve= r when I comment out the line the line below, the kernel hangs upon boot after detecting the em0 device (the motherboard has 2 Intel 8257x dual Gigabit Eth= ernet cards). makeopts = ; DEBUG=-g I'm using FreeBSD 8.2 on a WADE-8020 motherboard= with an Intel QM57 chipset and Intel Core i5 CPU. The reason I'm trying to remove debugging options= from the kernel is that I am trying to make the kernel footprint smaller. This leaves me with a few questions: 1)nb= sp; What are the risks/drawbacks/advantages of leaving debugging symbols in the kernel? 2)nb= sp; Why would debug symbols (of all things!) make the difference between a working and non-working kernel? 3)nb= sp; Does this point in the direction of some other (more serious problem perhaps?) with the hardware and/or other kernel drivers? Thanks so much for any assistance. Regards, Dirk= Kotze Devel= oper 3DNTQ [DEL: :DEL] nb= sp;Tel: +27 12 672 7281 F ax: +27 12 665 1343 P ostal: P.O. Box 7991, Centurion, 0046 P hysical: 1 Pieter street, Highveld Park, Centurion Important Notice: = = This e-mail and its contents are subject to the Nanoteq (Pty) Ltd e-mail leg= al notice available at: http://www.nanoteq.com/corp_profile/disclaimer.asp Important Notice: This e-mail and its contents are subject to the Nanoteq (Pty) Ltd e-mail legal notice available at: http://www.nanoteq.com/corp_profile/disclaimer.asp The message does not contain any threats AVG for MS Exchange Server (10.0.1416 - 2109/4756)___ 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 best practices
Victor Sudakov wrote: Hello portmaster users, If portaudit shows that some installed packages have vulnerabilities, what do you usually do? Greatly depend on where am I. All my systems are staying up-to-date whereas when I'm visiting someones system I prefer to update only required pieces of software. Anyway if you tell portmaster to update port x it would try to update all ports it depends on. Do you upgrade only the vulnerable packages, or vulnerable packages and dependent packages (portmaster -r), or perhaps all packages (portmaster -a)? Or do you pkg_delete -a all packages first and then reinstall from scratch (from `portmaster --list-origins` perhaps)? I am a bit uneasy about portmaster -a because, for example, in the output below it intends to install a package which is already installed: pg01-sibptus# portmaster -n -a === Gathering distinfo list for installed ports [dd] Upgrade php5-ldap-5.3.5_1 to php5-ldap-5.3.9 Install net/openldap24-sasl-client Upgrade postgresql-server-9.0.1 to postgresql-server-9.0.6_3 Upgrade tcl-8.5.9 to tcl-8.5.11 Upgrade vim-7.3.81 to vim-7.3.121 Install devel/gettext === Proceed? y/n [y] n === If you would like to upgrade or install some, but not all of the above try adding '-i' to the command line. pg01-sibptus# pg01-sibptus# pg01-sibptus# pkg_info -xo openldap Information for openldap-sasl-client-2.4.24: Origin: net/openldap24-client As far as I recall there was some glitches with correct detection of openldap24-client presence (some symbols moving around or so). Generally I never pay attention to this glitches and when (or if) update process fails I try to recompile mentioned port with portmaster. Then update process can be continued with `portmaster -a`. The better way of debugging such problems for me is pkg_libchk from sysutils/bsdadminscripts. -- Sphinx of black quartz judge my vow. ___ 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-update and archs
On 01/23/12 06:59, Christer Solskogen wrote: On Mon, Jan 23, 2012 at 3:03 PM, Colin Percival cperc...@freebsd.org wrote: On 01/22/12 03:45, Christer Solskogen wrote: I just did, and the file list is the same. Or do you want me to do a md5 of every file? Yes, I meant to compare the contents of files (or their hashes of course). Here you go: http://antarctica.no/~solskogen/temp/cross.txt.bz2 http://antarctica.no/~solskogen/temp/native.txt.bz2 http://antarctica.no/~solskogen/temp/diff.txt.bz2 Hmm, you've got almost everything being different there. Did you use the same src tree as the release? If you checked out the tree via CVS it won't match. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ 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 to kill -KILL process
Коньков Евгений wrote:
Hi
# ps ax|grep rad
45471 ?? TLs 263:35.44 /usr/local/sbin/radiusd
26473 1 S+ 0:00.00 grep rad
flux# date
Fri Jan 20 23:20:28 UTC 2012
flux# kill -KILL 45471
flux# date
Fri Jan 20 23:20:41 UTC 2012
flux# kill -KILL 45471
flux# date
Fri Jan 20 23:20:54 UTC 2012
flux# kill -KILL 45471
top
9 root16- 0K 8K syncer 2 7:12 0.00% syncer
45471 freeradius 20 -20 311M 283M STOP0 3:38 0.00% {radiusd}
49114 root210 10460K 4240K select 0 2:43 0.00% zebra
Looks like some bad things happen. Try kill -19 45471 to continue
radiusd execution, maybe that helps.
--
Sphinx of black quartz judge my vow.
___
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: kgzip(8) regression in RELENG_9 GENERIC
On Jan 23, 2012, at 12:56 AM, CyberLeo Kitsana wrote: On 01/23/2012 12:30 AM, Devin Teske wrote: On Jan 21, 2012, at 1:41 AM, CyberLeo Kitsana wrote: On 01/20/2012 09:02 PM, Devin Teske wrote: Taking a GENERIC 9.0-RELEASE kernel and running kgzip(8) on it produces an unusable kernel which causes immediate BTX halt in loader(8). ... 4. Say: kgzip kernel Curious, it doesn't even look like that binary is hooked into the build process at all on 9.0-RELEASE. Can you clarify what you mean by the above? On a brand new GENERIC box running 9.0-RELEASE with no special knobs: 8 (4b18d544)[cyberleo@jenga ~]$ which kgzip On my box: push900# uname -a FreeBSD push900.vicor.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 push900# which kgzip /usr/sbin/kgzip (4b18d544)[cyberleo@jenga ~]$ apropos kgzip push900# whereis kgzip kgzip: /usr/sbin/kgzip /usr/share/man/man8/kgzip.8.gz /usr/src/usr.sbin/kgzip (4b18d544)[cyberleo@jenga ~]$ cd /usr/src/usr.sbin (4b18d544)[cyberleo@jenga /usr/src/usr.sbin]$ ls | grep kgzip kgzip (4b18d544)[cyberleo@jenga /usr/src/usr.sbin]$ grep kgzip Makefile (4b18d544)[cyberleo@jenga /usr/src/usr.sbin]$ 8 push900# grep kgzip Makefile # $FreeBSD: release/9.0.0/usr.sbin/kgzip/Makefile 116221 2003-06-11 21:36:06Z obrien $ PROG= kgzip MAN=kgzip.8 SRCS= kgzip.c aouthdr.c elfhdr.c kgzcmp.c kgzld.c xio.c So it's there, Yes, there it is. How is it that my GENERIC 9.0-RELEASE build has it, source included, manual included, Makefile included, binary included,... but yours does not? but the SUBDIR entry in the usr.sbin Makefile that hooks it into the build process seems to be missing, whereas things that do exist (freebsd-update, c) are present. It's manpage indicates that it is unsuitable for loader(8) use, Likewise, can you clarify the above? From kgzip.8 in the aforementioned directory: 8 BUGS As symbols are lost, the usefulness of this utility for compressing ker- nels is limited to situations where loader(8) cannot be used; otherwise the preferred method of compressing a kernel is simply to gzip(1) it. 8 That's an odd sort of message. I've been using kgzip(1) since the days of RELENG_4 ... with loader(8) mind you, and have never had a problem until now with RELENG_9. and that just running gzip(1) on the kernel file is sufficient; I'm getting an error when loading a gzip(1)'d kernel... don't know how to load module '/kernels/GENERIC-i386-9.0.gz' So I figure, maybe it doesn't like the '.gz' suffix. No go, same error. I think we'll need more information on how your system is set up to boot: First, it's not my system, it's my installer. I'm taking on the task of creating a dual-installer (pictures linked-to below): http://www.twitpic.com/89l2ub/full http://www.twitpic.com/89l4n6/full I usually use kgzip'd kernels on my installer. It's always worked in the past (period). The reason for doing so is that it takes a 14MB GENERIC kernel and reduces it to 4.6MB (pretty obvious incentive there). partition layout, None to speak of. All I'm really doing to replicate the BTX halt is loading up an ISO with the following contents: 1. loader(8) from unmodified RELENG_9 2. kgzip(1)'d kernel -- again, unmodified RELENG_9 (GENERIC) 3. load kernel with FICL ``load'' 4. boot 5. BTX halted immediately what boot blocks and loaders are in use, etc. All from 9.0-RELEASE How are you instructing it to load that particular kernel, for example? Here's the FICL syntax used which replicates the BTX halt: load /kernels/GENERIC-i386-9.0.kgz load -t mfs_root /boot/fis_mfsroot9.gz set vfs.root.mountfrom=ufs:/dev/md0 set vfs.root.mountfrom.options=rw boot This leads to BTX halt. Simply going in and swapping kgzip(1)'d kernel for non-kgzip(1)'d kernel fixes the problem. -- 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-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: Horrible installer (was: Re: FreeBSD 9)
On Mon, 23 Jan 2012 08:27:32 -0600 Mark Felder articulated: Just as you don't get to express your opinion about the government if you don't vote, Excuse me, but are you just trying to look naive? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Remember to always be yourself. Unless you suck. -- Joss Whedon. ___ 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: TAB not jumping to OK in options screen
Well, I wanted the output to be logged, so in fact I did # make install clean | tee /tmp/xorg-install.txt Now, I tried again without the | tee ... and there wasn't a problem now ... But the | tee shouldn't be a problem, since in my script I run every week for a number of years already to do portupgrades, I have also a line portupgrade ...(my options)... | tee /tmp/portupgrade-mail this regularly offers me an options screen ... and I never had a problem Weird... 2012/1/23 claudiu vasadi claudiu.vas...@gmail.com Hi, I've never experienced anything similar but one workaround is to edit the Makefile: and change the Off to On for the options you need, and the other way around for the options you don;t need. Still, the real problem eludes me and that;s the one that needs fixing. -- Best regards, Claudiu Vasadi ___ 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: Horrible installer (was: Re: FreeBSD 9)
On Mon, 23 Jan 2012 09:40:42 -0600, je...@seibercom.net wrote: On Mon, 23 Jan 2012 08:27:32 -0600 Mark Felder articulated: Just as you don't get to express your opinion about the government if you don't vote, Excuse me, but are you just trying to look naive? The wording wasn't exactly as clear as it should have been, and I don't feel like seeing this thread degrade into politics and conspiracy theories. I should have known better. To clarify: Don't complain about major changes in -RELEASE if you refused to participate in the release process. (and bsdinstaller was HIGHLY publicized for a solid year before 9.0-RELEASE.) ___ 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: Horrible installer (was: Re: FreeBSD 9)
I've recently been presented with new information: namely that RC3 had sysinstall as an option (I did not know this, and I've been reading the lists) and that it was taken away for -RELEASE even though it was agreed upon that would not happen for 9.x. I'll crawl under this rock now. ___ 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: kgzip(8) regression in RELENG_9 GENERIC
Devin Teske devin.te...@fisglobal.com writes: On Jan 23, 2012, at 12:56 AM, CyberLeo Kitsana wrote: On 01/23/2012 12:30 AM, Devin Teske wrote: On Jan 21, 2012, at 1:41 AM, CyberLeo Kitsana wrote: On 01/20/2012 09:02 PM, Devin Teske wrote: Taking a GENERIC 9.0-RELEASE kernel and running kgzip(8) on it produces an unusable kernel which causes immediate BTX halt in loader(8). ... 4. Say: kgzip kernel Curious, it doesn't even look like that binary is hooked into the build process at all on 9.0-RELEASE. Can you clarify what you mean by the above? On a brand new GENERIC box running 9.0-RELEASE with no special knobs: 8 (4b18d544)[cyberleo@jenga ~]$ which kgzip On my box: push900# uname -a FreeBSD push900.vicor.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 push900# which kgzip /usr/sbin/kgzip On my system: $ uname -a FreeBSD birch.localnet 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 $ whereis kgzip kgzip: /usr/src/usr.sbin/kgzip $ grep kgzip /usr/src/usr.sbin/Makefile* Makefile.amd64:# kgzip: builds, but missing support files Makefile.i386:SUBDIR+= kgzip So it appears to be i386 only. -- Carl Johnsonca...@peak.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: kgzip(8) regression in RELENG_9 GENERIC
On 01/23/2012 11:26 AM, Carl Johnson wrote: On my system: $ uname -a FreeBSD birch.localnet 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 $ whereis kgzip kgzip: /usr/src/usr.sbin/kgzip $ grep kgzip /usr/src/usr.sbin/Makefile* Makefile.amd64:# kgzip: builds, but missing support files Makefile.i386:SUBDIR+= kgzip So it appears to be i386 only. Good catch. This build system of mine is amd64 as well. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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 best practices
On 23 January 2012 05:32, Victor Sudakov v...@mpeks.tomsk.su wrote: Hello portmaster users, If portaudit shows that some installed packages have vulnerabilities, what do you usually do? Do you upgrade only the vulnerable packages, or vulnerable packages and dependent packages (portmaster -r), or perhaps all packages (portmaster -a)? Or do you pkg_delete -a all packages first and then reinstall from scratch (from `portmaster --list-origins` perhaps)? I am a bit uneasy about portmaster -a because, for example, in the output below it intends to install a package which is already installed: pg01-sibptus# portmaster -n -a === Gathering distinfo list for installed ports [dd] Upgrade php5-ldap-5.3.5_1 to php5-ldap-5.3.9 Install net/openldap24-sasl-client Upgrade postgresql-server-9.0.1 to postgresql-server-9.0.6_3 Upgrade tcl-8.5.9 to tcl-8.5.11 Upgrade vim-7.3.81 to vim-7.3.121 Install devel/gettext === Proceed? y/n [y] n === If you would like to upgrade or install some, but not all of the above try adding '-i' to the command line. pg01-sibptus# pg01-sibptus# pg01-sibptus# pkg_info -xo openldap Information for openldap-sasl-client-2.4.24: Origin: net/openldap24-client As I general rule, I don't run portmaster -a Variations on -r usually succeed (-R -r is quite useful), though if it pulls in too many very large dependencies (firefox, chrome, open- or libre-office, most anything KDE/QT), I'll sometimes remove those before starting a portmaster -R -r type of run. It does require more typing to hand-specify the ports to be upgraded, but I end up with far fewer Whoops! moments. -- -- ___ 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
Applying local patches after updating FreeBSD source
Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make variable in /usr/local/etc/ports.conf (when using portconf), and the patch will be automatically applied whenever that port is built. Is there equivalent functionality for building FreeBSD world and kernel? When I run 'make update' in /usr/src, csup overwrites all local changes. There is a LOCAL_PATCHES variable, but it seems to apply only to 'make release'. If possible, I would like to avoid writing custom scripts for updating and building world, because at some point I will forget to use the script and build everything without the patches. How can I preserve the current behavior of running 'make update make buildworld buildkernel' while automatically applying custom patches in between? - Max ___ 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: Horrible installer (was: Re: FreeBSD 9)
Allan ___ Erm, you have to realize the new installer was discussed at length here, when 9.0 was still under development/beta/prerelease. Alternatively, you could do like me and install entirely by hand: - boot an MFSBSD image (thanks mm@ ) - partition your disks from there (see http://my.gd/bsd.htm for a rough sketch on how to use gpart) - fetch the 9.0 archives in .txz (tar.xz) format - unpack archives with xz -d - untar archived to the mountpoint with your new filesystems (eg: tar xf base.tar -C /mnt) - customize configuration files (rc.conf, fstab, root's password or SSH key, sshd_config to allow root login temporarily) and almost like me installing previous release (FreeBSD 8) everywhere. i just made once bootable pendrive with system, lots of tools and whole system as .tar.gz files (made my own compiling from cvs) actually i add WITHOUT_SYSINSTALL=yes to make.conf so i don't build it at all. And IMHO sysinstall should not exist, while good documentation about installing BY HAND should be there. Someone that cannot install it him/herself will not be able to ever manage it after so why waste time. Do not forget that FreeBSD is for unix users, contrary to linux which is for windoze haters. Again i propose removing sysinstall altogether. ___ 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: Applying local patches after updating FreeBSD source
On 23/01/2012 18:03, Maxim Khitrov wrote: Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make variable in /usr/local/etc/ports.conf (when using portconf), and the patch will be automatically applied whenever that port is built. Is there equivalent functionality for building FreeBSD world and kernel? When I run 'make update' in /usr/src, csup overwrites all local changes. There is a LOCAL_PATCHES variable, but it seems to apply only to 'make release'. If possible, I would like to avoid writing custom scripts for updating and building world, because at some point I will forget to use the script and build everything without the patches. How can I preserve the current behavior of running 'make update make buildworld buildkernel' while automatically applying custom patches in between? Check the system sources out of svn? This way, you can apply your patches and the result is automatically merged when you update the sources by 'svn up' -- unless there has been a conflicting commit to the same file, when you may be required to intervene manually. 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: Horrible installer
because, well, I LOVE FreeBSD. Basically, I've tried out NetBSD ONCE, actually i used NetBSD BEFORE switching to FreeBSD, short time after they released 2.0 and following versions. Got slower, unstable and bloated. Switched to FreeBSD, which in every version is getting BETTER not worse. I also don't think much, or care, about taking BSD, shutting everything off, and calling it the most secure thing ever. (Yes, I'm over FreeBSD by default is secure too ;) favorite OSs period. I also LOVE how awesome the Core Team are; Grey too. Kirk McKusick do the forward made me happy, he's one of my personal heros. I also got to speak with him recently and I was almost speechless I LOVE that guy, and he's so funny! The DVD 25 years of Bereley Unix is something I'd recommend you ALL buy. I also loved how nice he was. Marshal Kirk McKusick is one of the nicest, friendliest and made the most stable, dependable and high performance filesystem ever, which - after some improvements - is still used by most FreeBSD users. ___ 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: Horrible installer
I first touched FreeBSD around 2005. The current insteller is much more appealing and useful. All the people displaying elitist attitude toward the arcaic installer which infact DID push people away from FreeBSD, I don't understand you. so may i explain you: Those who cannot install things without fancy interfaces are not ever able to manage that system afterwards. This is not a toy but best performing unix system. ___ 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: Calxeda processors
http://www.calxeda.com Anyone know what the status would be of running our fav OS on these quadcore, blade based server processors? Running a server at 5W would be reeaal nice, you know :) not really 5W. you have to connect some hard drive anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Horrible installer (was: Re: FreeBSD 9)
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Wojciech Puchar Sent: Monday, January 23, 2012 10:25 AM To: Damien Fleuriot Cc: freebsd-questions@freebsd.org Subject: Re: Horrible installer (was: Re: FreeBSD 9) Allan ___ Erm, you have to realize the new installer was discussed at length here, when 9.0 was still under development/beta/prerelease. Alternatively, you could do like me and install entirely by hand: - boot an MFSBSD image (thanks mm@ ) - partition your disks from there (see http://my.gd/bsd.htm for a rough sketch on how to use gpart) - fetch the 9.0 archives in .txz (tar.xz) format - unpack archives with xz -d - untar archived to the mountpoint with your new filesystems (eg: tar xf base.tar -C /mnt) - customize configuration files (rc.conf, fstab, root's password or SSH key, sshd_config to allow root login temporarily) and almost like me installing previous release (FreeBSD 8) everywhere. i just made once bootable pendrive with system, lots of tools and whole system as .tar.gz files (made my own compiling from cvs) actually i add WITHOUT_SYSINSTALL=yes to make.conf so i don't build it at all. And IMHO sysinstall should not exist, while good documentation about installing BY HAND should be there. Someone that cannot install it him/herself will not be able to ever manage it after so why waste time. Disagree. For example, field engineers which may not be expected to know how to manage FreeBSD _ARE_ expected to know how to install it. A manual install process is more prone to errors than one that is guided by something/anything. Do not forget that FreeBSD is for unix users, Not all users are people. A corporation can be considered a unix user which changes the perspective quite a bit. contrary to linux which is for windoze haters. Again i propose removing sysinstall altogether. And you'll have your wish... over time! The community has agreed to phase out sysinstall(8) gradually over the next 2 or three releases (producing either a 10.0 or 11.0 that is free of sysinstall depending on how things progress with respect to replacement utilities such as bsdinstall and the proposed bsdconfig). -- 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-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: Which Common Lisp port for FreeBSD/sparc64?
On Wed, Jan 18, 2012 at 11:01 PM, Roland Smith rsm...@xs4all.nl wrote: On Wed, Jan 18, 2012 at 09:50:54PM +0100, Michel Talon wrote: You can find various cmucl snapshots here: http://common-lisp.net/project/cmucl/downloads/snapshots/2012/01/ i think one of the authors has a sparc machine, and also runs maxima, so i would be confident that cmucl works OK on the sparc, but it is here apparently under solaris. Looking into cmucl-2012-01-sparcv9-solaris10.tar.bz2, it seems that the lisp itself is 32-bit: file bin/lisp bin/lisp: ELF 32-bit MSB executable, SPARC32PLUS, V8+ Required, version 1 (SYSV), dynamically linked (uses shared libs), not stripped Looking at http://www.cons.org/cmucl/platforms.html, only x86 and amd64 (using the x86 32-bit binaries) are supported on FreeBSD. Only solaris is supported on sparc hardware. And according to http://sbcl.sourceforge.net/platform-table.html, sbcl doesn't run on FreeBSD/sparc. It seems that the latest release only supports x86 and amd64, irrespective of OS. Thank you guys for all the suggestions. I'll look into this. Kind regards, -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: Applying local patches after updating FreeBSD source
On Mon, Jan 23, 2012 at 1:25 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 23/01/2012 18:03, Maxim Khitrov wrote: Hi all, When I need to apply a custom patch to a port, I can set EXTRA_PATCHES make variable in /usr/local/etc/ports.conf (when using portconf), and the patch will be automatically applied whenever that port is built. Is there equivalent functionality for building FreeBSD world and kernel? When I run 'make update' in /usr/src, csup overwrites all local changes. There is a LOCAL_PATCHES variable, but it seems to apply only to 'make release'. If possible, I would like to avoid writing custom scripts for updating and building world, because at some point I will forget to use the script and build everything without the patches. How can I preserve the current behavior of running 'make update make buildworld buildkernel' while automatically applying custom patches in between? Check the system sources out of svn? This way, you can apply your patches and the result is automatically merged when you update the sources by 'svn up' -- unless there has been a conflicting commit to the same file, when you may be required to intervene manually. I don't have subversion installed on any of my servers and that's a dependency that I would prefer to do without. Are there any changes I could make to /etc/make.conf that would allow me to execute an arbitrary command after the 'update' task is finished? - Max ___ 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: kqueue and filenames
On 23-1-2012 11:52, Info wrote: I'm using kqueue for detecting file-events; for additional information I add a struct to udata, when registering an event with kevent. When I delete an event, will be udata deleted too, or do I have to manage the memory for the structs with an own implementation? It is up to you to free udata. kevent is triggered when a file is renamed. How do I get the new name? Is there an extra function? In the moment, I see only the possibility by searching the filesystem(folder) for a new name. A good question to which I unfortunately do not have the answer to. I think in principle it is impossible to get the file name by file descriptor alone (it could have multiple names). In practice I would just treat NOTE_RENAME as a sequence of unlink/link. I believe tools like lsof use the system name cache to map fds to names, but that is not very reliable. If you need more help with kqueue you might try the hackers@ mailing list, more technical people read that list. Regards, Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update and archs
On Mon, Jan 23, 2012 at 4:08 PM, Colin Percival cperc...@freebsd.org wrote: Hmm, you've got almost everything being different there. Did you use the same src tree as the release? If you checked out the tree via CVS it won't match. Hang on. I cheated a little. I used the base.txz from the release and compared that to my cross compile which was created using the releng/9.0 tree in subversion. I'll fire up my G4 to compile this instead (but it's probably going to take a while ;-) I'll get back to you! -- chs, ___ 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: Clang - what is the story?
On Mon, Jan 23, 2012 at 08:54:32AM +, Matthew Seaman wrote: On 22/01/2012 22:53, Da Rock wrote: What part is that? I thought it had to be all c... Not at all. clang and llvm are themselves written in C++. However, it's groff that Roland mentioned as the canonical example of C++ in base. And people have been grumbling about that for years, up to the point that a viable and indeed much smaller replacement (mandoc, in the textproc/mdocml port) has been written in C. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp0FYk1gfxHU.pgp Description: PGP signature
Wine-fbsd64 updated to 1.3.37 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.37 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.37,1.tbz) = 5e1db52bca7de4e5b6db2705eeff21f3 MD5 (freebsd9/wine-fbsd64-1.3.37,1.txz) = e9ebe02bda0b5d81667df69c23c1dc3f [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: Clang - what is the story?
On Mon, Jan 23, 2012 at 08:53:36AM +1000, Da Rock wrote: On 01/23/12 07:26, Chad Perrin wrote: On Sun, Jan 22, 2012 at 09:33:02PM +0100, Roland Smith wrote: PCC is only a C compiler, and there is some C++ code (e.g. groff) in the base system. The FreeBSD port is marked as i386 and amd64 only, even though other architectures seem to be there in the PCC source. I had somehow forgotten there was anything in the base system written in C++. That would probably account for the choice of Clang over PCC. What part is that? I thought it had to be all c... To the best of my knowledge the restriction to C only applies to the kernel and libraries, not to the utilities in the base system. And it is for a technical reason. C++ mangles function names to e.g. include argument types and class names. See [http://en.wikipedia.org/wiki/Name_mangling#Name_mangling_in_C.2B.2B]. This practically means that you can use a C library from a C++ program, but not the other way around. Then again, the kernel has more restrictions. Like no floating point allowed and no libc available. And presumably many more w.r.t. locking of data structures and practical limits on interrupt handlers. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpnUWoFLdT0T.pgp Description: PGP signature
Re: Horrible installer
On Mon, Jan 23, 2012 at 07:30:57PM +0100, Wojciech Puchar wrote: I first touched FreeBSD around 2005. The current insteller is much more appealing and useful. All the people displaying elitist attitude toward the arcaic installer which infact DID push people away from FreeBSD, I don't understand you. so may i explain you: Those who cannot install things without fancy interfaces are not ever able to manage that system afterwards. This is not a toy but best performing unix system. Thank you for (inadvertently?) making people with a legitimate need for the functionality of sysinstall look like intolerant elitists by association with you in the minds of those who don't understand their needs, just because you seem to agree with them. I miss your silence. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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: Horrible installer (was: Re: FreeBSD 9)
On Mon, Jan 23, 2012 at 07:25:03PM +0100, Wojciech Puchar wrote: And IMHO sysinstall should not exist, while good documentation about installing BY HAND should be there. I agree with the part of that sentence following the comma. That is all. Someone that cannot install it him/herself will not be able to ever manage it after so why waste time. Do not forget that FreeBSD is for unix users, contrary to linux which is for windoze haters. Again i propose removing sysinstall altogether. Automation is good, provided it does not eliminate useful options and flexibility. You seem unaware of this fact in the general case, for some reason. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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: portmaster best practices
On Mon, Jan 23, 2012 at 05:32:33PM +0700, Victor Sudakov wrote: Hello portmaster users, If portaudit shows that some installed packages have vulnerabilities, what do you usually do? It depends on the vulnerability and what the package does. I will de-install it if I think that the vulnerability is critical for me and there is no workaround. Look at freshports [http://www.freshports.org/commits.php] regularly to see if updates for vulnerable packages are available. Generally I like to run 'portsnap fetch update' followed by 'portmaster -ai' (after reading /usr/ports/UPDATING) every week. This keeps the number of huge compilefests (like gettext updates :-() to a minimum. For efficiency, I tend to keep one machine up-to-date in that way, and use rsync to then distribute the changes in /usr/local to my other machines. This only works for machines that are on the same major FreeBSD version and architecture, of course. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpWzSSkojAqm.pgp Description: PGP signature
Problems uppgrading x11/sessreg port
FreeBSD odin.thorshammare.org 9.0-STABLE FreeBSD 9.0-STABLE #0 r230424: Sun Jan 22 00:13:50 CET 2012 ad...@odin.thorshammare.org:/usr/obj/usr/src/sys/GENERIC i386 I've got some problem with the port sessreg, part of x11/xorg suite, when running portupgrade. === Building for sessreg-1.0.7 make all-recursive Making all in man GENfilenames.sed GENsessreg.1 CC sessreg.o sessreg.c: In function 'main': sessreg.c:281: warning: implicit declaration of function 'ttyslot' sessreg.c:281: warning: nested extern declaration of 'ttyslot' CCLD sessreg sessreg.o: In function `main': sessreg.c:(.text+0xcc1): undefined reference to `ttyslot' *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120123-9573-548d6g-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=sessreg-1.0.5_1 UPGRADE_PORT_VER=1.0.5_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! x11/sessreg (sessreg-1.0.5_1) (linker error) Preciate all help. /Hasse ___ 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
Hello
I want to create MySQL localhost. ___ 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: Problems uppgrading x11/sessreg port
On Mon, Jan 23, 2012 at 09:51:51PM +0100, Hasse Hansson wrote: FreeBSD odin.thorshammare.org 9.0-STABLE FreeBSD 9.0-STABLE #0 r230424: Sun Jan 22 00:13:50 CET 2012 ad...@odin.thorshammare.org:/usr/obj/usr/src/sys/GENERIC i386 I've got some problem with the port sessreg, part of x11/xorg suite, when running portupgrade. === Building for sessreg-1.0.7 make all-recursive Making all in man GENfilenames.sed GENsessreg.1 CC sessreg.o sessreg.c: In function 'main': sessreg.c:281: warning: implicit declaration of function 'ttyslot' sessreg.c:281: warning: nested extern declaration of 'ttyslot' CCLD sessreg sessreg.o: In function `main': sessreg.c:(.text+0xcc1): undefined reference to `ttyslot' *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120123-9573-548d6g-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=sessreg-1.0.5_1 UPGRADE_PORT_VER=1.0.5_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! x11/sessreg (sessreg-1.0.5_1) (linker error) Preciate all help. Check To rebuild everything and install it on the current system. in /usr/src/UPDATING (you are missing the 'make delete-old' step). Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Horrible installer
I first touched FreeBSD around 2005. The current insteller is much more appealing and useful. All the people displaying elitist attitude toward the arcaic installer which infact DID push people away from FreeBSD, I don't understand you. so may i explain you: Those who cannot install things without fancy interfaces are not ever able to manage that system afterwards. This is not a toy but best performing unix system. So for that matter GNU/Linux and Solaris both are toys because they also present a GUI installer alongside?? I was talking about text and gui being available, not just one or the other. Not everyone is using FreeBSD for rackmounts with a terminal and no monitor. -- Lyubomir Grigorov (bgalakazam) signature.asc Description: This is a digitally signed message part.
Using non-gcc linker?
Hi, I just made world and kernel using clang, but I noticed that ld is still using the GNU ld. The page http://wiki.freebsd.org/BuildingFreeBSDWithClangmentions using a different linker that supports LTO optimisation. Is that non-GNU linker part of FreeBSD 9? 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: Horrible installer
From my point of view, I would like to see 2 major things in bsdinstall: 1) ZFS support 2) an option, to use GUI or text mode installer (similar to RHEL, CentOS, Solaris) Other than that, I can use it just as I was using sysinstall, because we always have ZFS on root (need to drop to shell to run a script) or UFS (built-in). -- Best regards, Claudiu Vasadi ___ 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: Horrible installer
PS: would like to see option 2 in PC-BSD too (maybe I'm just melancholic to have a non-GUI installer :) ) -- Best regards, Claudiu Vasadi ___ 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: Horrible installer (was: Re: FreeBSD 9)
On Mon, Jan 23, 2012 at 09:52:17AM -0600, Mark Felder wrote: On Mon, 23 Jan 2012 09:40:42 -0600, je...@seibercom.net wrote: On Mon, 23 Jan 2012 08:27:32 -0600 Mark Felder articulated: Just as you don't get to express your opinion about the government if you don't vote, Excuse me, but are you just trying to look naive? The wording wasn't exactly as clear as it should have been, and I don't feel like seeing this thread degrade into politics and conspiracy theories. I should have known better. To clarify: Don't complain about major changes in -RELEASE if you refused to participate in the release process. (and bsdinstaller was HIGHLY publicized for a solid year before 9.0-RELEASE.) I understand the theory, but in reality, not everyone has the resources to frequently try out CURRENT or even STABLE as sort of Beta tests. It is good for those who can. In spite of that, it is good - a part of the development process - that people do post their complaints and concerns. Of course, the sendpr process is the canonical method, but really, many of these comments need some discussion before they are ready for prime time - eg to be posted by sendpr. Frankly, many of the comments are rather half baked and many are really just personal preferences that are not actually technical failings. That does not make them unvaluable. It ends up being sort of an Email BOF session like one might get into in a FreeBSD or USENIX conference. That hashing out is where many new ideas and features start and get vetted and may eventually get worked on by people able to do it. The one failing I frequently see in the complaint posts and the responses by other complainers is too frequently a lack of civility and respect for people who are doing the work of creating and maintaining this system and for those who are making complaints and stating personal preferences (true on other similar lists such as CentOS, etc too). It is not necessary or helpful to ascribe all sorts of negative attributes and motives to those doing the work or to those making comments and complaints. Just state your bit, then shut your digital mouth. jerry ___ 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: Horrible installer (was: Re: FreeBSD 9)
I'm very new to FreeBSD but it seems to me that the installer is pretty much ok. My only wish is that there might be a little more info upfront somewhere, preferably in the installer somewhere, about setting up for a dual boot. I couldn't find in the handbook, (that may be my fault, don't know, but i finally googled the info i needed, after thinking that I had inadvertently committed my Windows slice into the abyss. maybe that was a good thing, but IMO though, the installer should be as lightweight and spare as possible, that is, if the engineering dudes are writing it. I would rather see them doing their fantastic work on the OS, not on the installer anyway. Seems to me that a full-featured GUI installer would be a good project for the community? (ok, yeah they could have left sysinstall alone, but so what???) If you had to depend on sysinstall on a daily basis, i could see having issues with the change, but then again, if you are using it that often a custom install scriptsomething... would be better anyway. from my point of view, I would rather learn how to do this by hand, because then i would come out learning a lot more, and knowing more about my own system. Probably be next on my agenda. since this is my first contact with the community, I would like to thank the development folks properly for the awesome work that they do, and to those who contribute to this list. Kyle Adkins Sent from my iPad On Jan 23, 2012, at 9:27 AM, Mark Felder f...@feld.me wrote: All of these complaints can go directly to /dev/null Just as you don't get to express your opinion about the government if you don't vote, you don't get to express your opinion about -RELEASE changes when you didn't run the STABLE/RC/BETAs. You had your chance to help improve FreeBSD for everyone, assuming your concerns really are valid and far-reaching. You opted out. No longer the core team's problem. Closed: WORKSFORME ___ 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
SV: Problems uppgrading x11/sessreg port
-Oprindelig meddelelse- Fra: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] På vegne af Yuri Pankov Sendt: den 23 januari 2012 22:25 Til: Hasse Hansson Cc: freebsd-questions@freebsd.org Emne: Re: Problems uppgrading x11/sessreg port On Mon, Jan 23, 2012 at 09:51:51PM +0100, Hasse Hansson wrote: FreeBSD odin.thorshammare.org 9.0-STABLE FreeBSD 9.0-STABLE #0 r230424: Sun Jan 22 00:13:50 CET 2012 ad...@odin.thorshammare.org:/usr/obj/usr/src/sys/GENERIC i386 I've got some problem with the port sessreg, part of x11/xorg suite, when running portupgrade. === Building for sessreg-1.0.7 make all-recursive Making all in man GENfilenames.sed GENsessreg.1 CC sessreg.o sessreg.c: In function 'main': sessreg.c:281: warning: implicit declaration of function 'ttyslot' sessreg.c:281: warning: nested extern declaration of 'ttyslot' CCLD sessreg sessreg.o: In function `main': sessreg.c:(.text+0xcc1): undefined reference to `ttyslot' *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.7. *** Error code 1 Stop in /usr/ports/x11/sessreg. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120123-9573-548d6g-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=sessreg-1.0.5_1 UPGRADE_PORT_VER=1.0.5_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! x11/sessreg (sessreg-1.0.5_1) (linker error) Preciate all help. Check To rebuild everything and install it on the current system. in /usr/src/UPDATING (you are missing the 'make delete-old' step). Yuri [] Absolutely correct. Thnk you very much ! /Hasse ___ 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
lang/lua fails to build on 9.0-STABLE amd64 - bug or config issue?
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with
FreeBSD 9.0-STABLE, and I'm not sure whether it's a bug or incorrect
configuration on my part. The lang/lua port throws a linker error,
claiming to need -fPIC, which is odd because the port Makefile seems to
have logic to add that in, but somehow the logic seems not to have any
effect, at least in my case. Making the port Makefile put ${CFLAGS}
directly into lua's Makefile (patch at the end of this mail) fixes
matters for me, but I don't understand the port infrastructure well
enough to understand whether this patch represents a bugfix or a
workaround of some local configuration issue. Has anyone run into this
issue before? If this is a config issue, any hints on what might be
going on or how to dope it out?
Thanks for your help,
Lee Thomas
The details:
#date
Mon Jan 23 18:01:30 EST 2012
#uname -a
FreeBSD Anon 9.0-STABLE FreeBSD 9.0-STABLE #0: Sat Jan 21 10:39:05 EST
2012 anon@Anon:/usr/obj/usr/src/sys/GENERIC amd64
#cat /etc/make.conf
CPUTYPE?=nocona
CFLAGS= -O2 -fno-strict-aliasing -pipe
COPTFLAGS= -O -pipe
#csup ports-supfile
Connected to 216.165.129.134
Updating collection ports-all/cvs
Finished successfully
#cd /usr/ports/lang/lua make clean build
=== Cleaning for lua-5.1.4_6
=== Vulnerability check disabled, database not found
=== License check disabled, port has not defined LICENSE
=== Extracting for lua-5.1.4_6
= SHA256 Checksum OK for lua-5.1.4.tar.gz.
= SHA256 Checksum OK for patch-lua-5.1.4-3.
=== Patching for lua-5.1.4_6
=== Applying distribution patches for lua-5.1.4_6
=== Applying FreeBSD patches for lua-5.1.4_6
=== lua-5.1.4_6 depends on executable: pkg-config - found
=== Configuring for lua-5.1.4_6
=== Building for lua-5.1.4_6
cd src make freebsd
make all MYCFLAGS=-DLUA_USE_LINUX MYLIBS=-Wl,-E -lreadline
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lapi.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lcode.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c ldebug.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c ldo.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c ldump.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lfunc.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c llex.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lgc.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lmem.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lobject.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lopcodes.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lparser.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lstate.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lstring.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c ltable.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c ltm.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lundump.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lvm.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lzio.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lauxlib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lbaselib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c ldblib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c liolib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c loslib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lmathlib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c ltablib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lstrlib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c loadlib.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c linit.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c lua.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c luac.c
cc -O2 -fno-strict-aliasing -pipe -march=nocona -Wall -DLUA_USE_LINUX
-c print.c
cc -o liblua.so -O2 -fno-strict-aliasing -pipe -march=nocona -Wall
-DLUA_USE_LINUX -shared -Wl,-soname=liblua-5.1.so.1 lapi.o lcode.o
ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o
lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o
lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o
lstrlib.o loadlib.o linit.o
ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o
llex.o lmem.o lobject.o
Re: Horrible installer (was: Re: FreeBSD 9)
On Monday 23 January 2012 05:18:01 pm B. Kyle Adkins wrote: I'm very new to FreeBSD but it seems to me that the installer is pretty much ok. My only wish is that there might be a little more info upfront somewhere, preferably in the installer somewhere, about setting up for a dual boot. I couldn't find in the handbook, (that may be my fault, don't know, but i finally googled the info i needed, after thinking that I had inadvertently committed my Windows slice into the abyss. maybe that was a good thing, but Heh, I remember back in the day when I FIRST got to use FreeBSD for the very first time; I bought the BSD PowerPak, complete with FreeBSD 4.0, the 4 CD-ROM set, and a 6 CD toolkit, and The Complete FreeBSD book 3rd edition, Which is one of the best books ever written on BSD, or any OS period. Back then, I was running my Computer, it had Windows 98 SE, dual booting with a Linux distro (I used a few and formatted a lot to try new things so it could have been any of them) and then I decided to tri-boot Windows 98 SE, Linux, and FreeBSD... To put it mildly; The BSD installer overwrote my MBR even though I said not to, and wouldn't boot Windows. So it only booted Linux and FreeBSD. I was TOTALLY new to Computers in general still, but even back then, I knew I'd stumbled upon something special. I've also had installs go bad and I couldn't boot Windows anymore either, so I know how you feel. Right now, My Wife and I have 11 computers, and all of mine are running some form of BSD (ONLY FreeBSD and PC-BSD, which is FreeBSD with a pretty pain job and some custom apps that I like) and then a Slackware 12.0 FTP Server which is just my first Computer I ever bought because it still works, and then, I have my main desktop dual booting Windows 7 and Slackware as well. Every other machine is now running some form of FreeBSD. I like that. BSD has come a long way in terms of desktop usability over the years. I mean you could use FreeBSD as a Desktop or Workstation easily, but it COULD be a little but of a pain in the butt now and then for that, as it really is aimed at Servers. These days; It's much easier I think. And I LOVE FreeBSD. I have downloaded and tried out NetBSD but I didn't ever like it. I refuse to try OpenBSD, because I hate that damned talking turnip Theo, and, if anyone remembers unixpunx back in the day, I still have the Live CD they made based on FreeBSD :) IMO though, the installer should be as lightweight and spare as possible, that is, if the engineering dudes are writing it. I would rather see them doing their fantastic work on the OS, not on the installer anyway. Seems to me that a full-featured GUI installer would be a good project for the community? Actually, you could try out PC-BSD :) I'm installing 9.0 on my Laptop right now. I predict in the near future, with the rate at which PC-BSD is going, it's going to become MAJOR MAJOR COMPETITION to Linux, and even the Idiotic Ubuntu. I don't like Ubuntu... I do like Slackware and SUSE, but Ubuntu just. I like Debian, and it's retarded cousin Ubuntu is NOT for me. I use the installation media I have for it, for the SAME purpose I use my Windows NT and Windows Server 2003 Enterprise Edition CDs; Coffee Coasters. from my point of view, I would rather learn how to do this by hand, because then i would come out learning a lot more, and knowing more about my own system. Probably be next on my agenda. I personally would like to learn that part too. However, I don't think it should EVER be a requirement. I mean, when it comes down to it, I think we could all admit, FreeBSD is the most popular BSD because it was the first one to actually try and get something out there that was installable without being a guru. NetBSD and OpenBSD are barely catching up, and I don't care; FreeBSD and PC-BSD, are becoming very quickly my main OSs these days. I used to use SUSE Debian and Slackware for most of my stuff, but anymore, I don't. BSD has, FINALLY, got something called PC-BSD where I can use the stability of FreeBSD, but, with then fast and easy set up of something like RedHat. I hate RedHat so I'm VERY happy Pc-BSD has come along so far. I've got versions of it going back pretty far heh. I actually have a CD / DVD case that is dedicated JUST to BSD. and it's LOADED. FreeBSD going back to 4.0, and other BSD stuff I have. All in there. And For Christmas, I got a new FreeBSD tee, hoody, and a FreeBSD CD/DVD Case. I LOVE it. I also got stickers and stuff, and ANOTHER FreeBSD PC Case thingy, and I love it. since this is my first contact with the community, I would like to thank the development folks properly for the awesome work that they do, and to those who contribute to this list. If you want to thank them properly, I'd HIGHLY recommend buying some of the books! Look into The FreeBSD Mall and on the left hand side, you'll see a section called Books and Magazines. Look
Re: MySQL Localhost install - Was: Hello
On 01/24/12 07:06, Crow wrote: I want to create MySQL localhost. Can you provide some more information? Like which version of FreeBSD you are using (or other OS if you happen to be needing other support), what you have completed so far, other parameters that you are able to tell us which may have a bearing on your situation. Generally you can install from ports: If you haven't already installed ports (try cd /usr/ports), then as root run portsnap fetch extract. If you have installed ports, then cd /usr/ports/databases/mysql55-server, and then make make install make clean. Then in /etc/rc.conf you will need mysql_enable=YES and you can look at the file /usr/local/etc/rc.d/mysql for how to set any flags you need. Usually you just have to set mysql_flags=your flags here in rc.conf. Hope that helps you get started, but if you need more then you'll have to supply more info. Cheers ___ 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: Horrible installer (was: Re: FreeBSD 9)
On Monday 23 January 2012 12:17:33 pm Mark Felder wrote: I've recently been presented with new information: namely that RC3 had sysinstall as an option (I did not know this, and I've been reading the lists) and that it was taken away for -RELEASE even though it was agreed upon that would not happen for 9.x. I'll crawl under this rock now. Instead of crawling under a Rock, how about everyone here, ALL of the people I've seen in this thread trashing each other; ALL of you, just take 60 seconds, take a DEEP breath, and realize we ARE a Community, which is a lot like a family in some ways. That means we aren't always going to agree with each other, and that we may even want to punch one another in the head from time to time, but, at the least, can all of you who ARE getting pissed off like that, at LEAST be respectfulof one another? God, it's like being on an Ubuntu mailing list with this thread and I WILL NOT stand for that! If I wanted to use shoddy shitty software that some asshole Billionaire ripped off from another OS I'd go buy Windows and pretend I was being bent over. I don't personally care if everyone here gets along or anything, but I DO care when you start insulting each other over OPINIONS. I'm not going to say that stupid cliche about how everyone has one, because I think it's cheezy, but damn it this is FreeBSD! The most Stable OS on Earth. (If you take into account that you don't need a 40 millon dollar cluster to run it and all that). I've been watching this thread from the start, and I've replied to a few posts myself, but it's like, seriously? You have to insult EVERY person you don't agree with? I don't have an issue with insulting morons. I'd make it a sport if I could and I LOVE being a condescending jerk sometimes. But, on a list such as this, it's making us ALL look bad! So, to all of you taking part in this thread; Can we turn the bashing off for a while? We're FreeBSD users, and I sort of expect... No, I EXPECT that we all can act professional! So, PLEASE, if you have an issue with someone on here, and you want to bash them for it... Why not just reply to their email address instead of the list itself? work it out! Man up! If your pooter hurts; the Vagisil is in the same isle as the Depends. Suck it up! (Yes, I'm trying to add humor I'm one of those people who can't deal with certain high stress situations so I try and crack jokes and stuff. But yea, I'm a playful person right now because the Oxy kicked in, but yea, can we not bash each other over opinions?). Anyway, I fully understand BOTH sides of what everyone is saying. I really do for the most part. I know that bsdinstall has it's issues, but don't you think that the FreeBSD team is watching this? You know they WILL get it going and fix it up, so just be professional. Make a list of EVERYTHING that EVERYONE doesn't like about bsdinstall, and get the list to the right people who can do something about it. I mean come on You HAVE the source Write something better, or, at least, get the stuff that bugs you to the people in charge. It will be OK! I've been working with BSD since 4.0, do you really think this is the first time something happened where people were upset? Jeez guys They'll work it out and we'll be fine, OK? -Allen -- BSD user ___ 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: Horrible installer
On Monday 23 January 2012 01:29:23 pm Wojciech Puchar wrote: because, well, I LOVE FreeBSD. Basically, I've tried out NetBSD ONCE, actually i used NetBSD BEFORE switching to FreeBSD, short time after they released 2.0 and following versions. Got slower, unstable and bloated. Switched to FreeBSD, which in every version is getting BETTER not worse. Yea I ust never really got into the NetBSD thing. In mean, I don't HATE NetBSD, I just don't care about it. I also don't think much, or care, about taking BSD, shutting everything off, and calling it the most secure thing ever. (Yes, I'm over FreeBSD by default is secure too ;) Agree :) I like how FreeBSD managed to make a system that was actually USABLE and ALSO secure. I mean, if you're not sure, you can look something up and learn how to do it in a very short time due to the great docs, and the great books. Kirk McKusick do the forward made me happy, he's one of my personal heros. I also got to speak with him recently and I was almost speechless I LOVE that guy, and he's so funny! The DVD 25 years of Bereley Unix is something I'd recommend you ALL buy. I also loved how nice he was. Marshal Kirk McKusick is one of the nicest, friendliest and made the most stable, dependable and high performance filesystem ever, which - after some improvements - is still used by most FreeBSD users. Oh I know! It amazes me just how Talented he is. And of course being very friendly. I was actually nervous about meeting him because, you know, when you meet a hero, you worry about people who talk about Glenn Danzig being a Jerk sometimes and it ruins it for you, but he's a really nice guy. I didn't have a whole conversation or anything, but he was very nice to me, and I was glad he wasn't pissed about the long ass email I sent so it was nice :) -Allen -- BSD user ___ 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: Horrible installer
On 01/24/12 11:33, gore wrote: On Monday 23 January 2012 12:17:33 pm Mark Felder wrote: I've recently been presented with new information: namely that RC3 had sysinstall as an option (I did not know this, and I've been reading the lists) and that it was taken away for -RELEASE even though it was agreed upon that would not happen for 9.x. I'll crawl under this rock now. Instead of crawling under a Rock, how about everyone here, ALL of the people I've seen in this thread trashing each other; ALL of you, just take 60 seconds, take a DEEP breath, and realize we ARE a Community, which is a lot like a family in some ways. That means we aren't always going to agree with each other, and that we may even want to punch one another in the head from time to time, but, at the least, can all of you who ARE getting pissed off like that, at LEAST be respectfulof one another? God, it's like being on an Ubuntu mailing list with this thread and I WILL NOT stand for that! If I wanted to use shoddy shitty software that some asshole Billionaire ripped off from another OS I'd go buy Windows and pretend I was being bent over. ROFL... I cant imagine what happened on the ubuntu lists, maybe they were throwing foam balls at each other or something... This thread to me seems pretty tame though as opposed to some - maybe a Nerf match? You should see some of the other linux lists - they almost get to the point of using real guns! I don't personally care if everyone here gets along or anything, but I DO care when you start insulting each other over OPINIONS. I'm not going to say that stupid cliche about how everyone has one, because I think it's cheezy, but damn it this is FreeBSD! The most Stable OS on Earth. (If you take into account that you don't need a 40 millon dollar cluster to run it and all that). I've been watching this thread from the start, and I've replied to a few posts myself, but it's like, seriously? You have to insult EVERY person you don't agree with? I don't have an issue with insulting morons. I'd make it a sport if I could and I LOVE being a condescending jerk sometimes. But, on a list such as this, it's making us ALL look bad! So, to all of you taking part in this thread; Can we turn the bashing off for a while? We're FreeBSD users, and I sort of expect... No, I EXPECT that we all can act professional! So, PLEASE, if you have an issue with someone on here, and you want to bash them for it... Why not just reply to their email address instead of the list itself? work it out! Man up! If your pooter hurts; the Vagisil is in the same isle as the Depends. Suck it up! ROFL _and_ pissing myself... :) (Yes, I'm trying to add humor I'm one of those people who can't deal with certain high stress situations so I try and crack jokes and stuff. But yea, I'm a playful person right now because the Oxy kicked in, but yea, can we not bash each other over opinions?). Anyway, I fully understand BOTH sides of what everyone is saying. I really do for the most part. I know that bsdinstall has it's issues, but don't you think that the FreeBSD team is watching this? You know they WILL get it going and fix it up, so just be professional. Make a list of EVERYTHING that EVERYONE doesn't like about bsdinstall, and get the list to the right people who can do something about it. I mean come on You HAVE the source Write something better, or, at least, get the stuff that bugs you to the people in charge. It will be OK! I've been working with BSD since 4.0, do you really think this is the first time something happened where people were upset? Jeez guys They'll work it out and we'll be fine, OK? You have a point though, and some dignity and tact need to remain; and I agree - if you don't like something try and find a way to fix it, offer helpful advice/criticism, work with beta versions of the installer (or whatever bothers 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: Horrible installer
On Monday 23 January 2012 08:45:21 pm Da Rock wrote: *snip* Instead of crawling under a Rock, how about everyone here, ALL of the people I've seen in this thread trashing each other; ALL of you, just take 60 seconds, take a DEEP breath, and realize we ARE a Community, which is a lot like a family in some ways. That means we aren't always going to agree with each other, and that we may even want to punch one another in the head from time to time, but, at the least, can all of you who ARE getting pissed off like that, at LEAST be respectfulof one another? God, it's like being on an Ubuntu mailing list with this thread and I WILL NOT stand for that! If I wanted to use shoddy shitty software that some asshole Billionaire ripped off from another OS I'd go buy Windows and pretend I was being bent over. ROFL... I cant imagine what happened on the ubuntu lists, maybe they were throwing foam balls at each other or something... This thread to me seems pretty tame though as opposed to some - maybe a Nerf match? You should see some of the other linux lists - they almost get to the point of using real guns! Hahaha yea. I've seen a few of those ones. God they get mad. I watched a few where I was basically waiting for one to tell the other This is where I live, come over here and kick my nerdy ass! lol. I don't personally care if everyone here gets along or anything, but I DO care when you start insulting each other over OPINIONS. I'm not going to say that stupid cliche about how everyone has one, because I think it's cheezy, but damn it this is FreeBSD! The most Stable OS on Earth. (If you take into account that you don't need a 40 millon dollar cluster to run it and all that). I've been watching this thread from the start, and I've replied to a few posts myself, but it's like, seriously? You have to insult EVERY person you don't agree with? I don't have an issue with insulting morons. I'd make it a sport if I could and I LOVE being a condescending jerk sometimes. But, on a list such as this, it's making us ALL look bad! So, to all of you taking part in this thread; Can we turn the bashing off for a while? We're FreeBSD users, and I sort of expect... No, I EXPECT that we all can act professional! So, PLEASE, if you have an issue with someone on here, and you want to bash them for it... Why not just reply to their email address instead of the list itself? work it out! Man up! If your pooter hurts; the Vagisil is in the same isle as the Depends. Suck it up! ROFL _and_ pissing myself... :) Oh thank you for getting that :) I was kind of wondering how that would get taken and if everyone would get it but thanks lol. I thought it was funny. (Yes, I'm trying to add humor I'm one of those people who can't deal with certain high stress situations so I try and crack jokes and stuff. But yea, I'm a playful person right now because the Oxy kicked in, but yea, can we not bash each other over opinions?). Anyway, I fully understand BOTH sides of what everyone is saying. I really do for the most part. I know that bsdinstall has it's issues, but don't you think that the FreeBSD team is watching this? You know they WILL get it going and fix it up, so just be professional. Make a list of EVERYTHING that EVERYONE doesn't like about bsdinstall, and get the list to the right people who can do something about it. I mean come on You HAVE the source Write something better, or, at least, get the stuff that bugs you to the people in charge. It will be OK! I've been working with BSD since 4.0, do you really think this is the first time something happened where people were upset? Jeez guys They'll work it out and we'll be fine, OK? You have a point though, and some dignity and tact need to remain; and I agree - if you don't like something try and find a way to fix it, offer helpful advice/criticism, work with beta versions of the installer (or whatever bothers you). Thank you! :) -Allen -- BSD user ___ 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: lang/lua fails to build on 9.0-STABLE amd64 - bug or config issue?
On Mon, Jan 23, 2012 at 04:22:30PM -0700, Lee Thomas wrote: Hello fellow FreeBSD users, I ran across an odd issue compiling lua from ports on amd64 with FreeBSD 9.0-STABLE, and I'm not sure whether it's a bug or incorrect configuration on my part. The lang/lua port throws a linker error, The same port builds fine on my machine (9.0-RELEASE, amd64, also CPUTYPE=nocona, otherwise standard settings in make.conf). #uname -a FreeBSD Anon 9.0-STABLE FreeBSD 9.0-STABLE #0: Sat Jan 21 10:39:05 EST 2012 anon@Anon:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD slackbox.erewhon.net 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 #cat /etc/make.conf CPUTYPE?=nocona CFLAGS= -O2 -fno-strict-aliasing -pipe COPTFLAGS= -O -pipe - # file: /etc/make.conf # host: slackbox.erewhon.net # Time-stamp: 2012-01-15 18:27:45 rsmith # $Id: a7a5c36f9b8474b6139154d7d7b8aa595415be86 $ # Type of CPU the system is built for. CPUTYPE=nocona # Compiler flags # Use standard settings. - #csup ports-supfile Connected to 216.165.129.134 Updating collection ports-all/cvs Finished successfully I tend to use portmaster, but I've got the same port version; lua-5.1.4_6. #cd /usr/ports/lang/lua make clean build === Cleaning for lua-5.1.4_6 === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for lua-5.1.4_6 = SHA256 Checksum OK for lua-5.1.4.tar.gz. = SHA256 Checksum OK for patch-lua-5.1.4-3. === Patching for lua-5.1.4_6 === Applying distribution patches for lua-5.1.4_6 === Applying FreeBSD patches for lua-5.1.4_6 === lua-5.1.4_6 depends on executable: pkg-config - found === Configuring for lua-5.1.4_6 === Building for lua-5.1.4_6 After builing, I get the following for lapi.*: # sha256 work/lua-5.1.4/src/lapi.* SHA256 (work/lua-5.1.4/src/lapi.c) = 6aa0d9fdd88b13fe46568ad6722ecf44164fb84476cfdf6480cf05b5704935f8 SHA256 (work/lua-5.1.4/src/lapi.h) = 4aea4c1b975d43184f4f1fd1a42c79cf11d74d2801315740cec07fe9abebb56d SHA256 (work/lua-5.1.4/src/lapi.o) = 08de497fe95c4afacd941f6aeede3d07db9fb08db7260efeffd5a4c0194bcb7e # cc --version cc (GCC) 4.2.1 20070831 patched [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You could try building with clang, that works here as well; # make CC=clang and gives: # sha256 work/lua-5.1.4/src/lapi.o SHA256 (work/lua-5.1.4/src/lapi.o) = d96c0ae288387d9030e1228eaa03f9997b62e433b16ad7b9df959f99901bc301 Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpE2zganLIZb.pgp Description: PGP signature
Re: freebsd-update and archs
On Mon, Jan 23, 2012 at 8:50 PM, Christer Solskogen christer.solsko...@gmail.com wrote: On Mon, Jan 23, 2012 at 4:08 PM, Colin Percival cperc...@freebsd.org wrote: Hmm, you've got almost everything being different there. Did you use the same src tree as the release? If you checked out the tree via CVS it won't match. Hang on. I cheated a little. I used the base.txz from the release and compared that to my cross compile which was created using the releng/9.0 tree in subversion. I'll fire up my G4 to compile this instead (but it's probably going to take a while ;-) I'll get back to you! http://antarctica.no/~solskogen/temp/cross.txt.bz2 http://antarctica.no/~solskogen/temp/native.txt.bz2 http://antarctica.no/~solskogen/temp/diff.txt.bz2 But there is still a lot of files which don't match. -- chs, ___ 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: lang/lua fails to build on 9.0-STABLE amd64 - bug or config issue?
On Tue, Jan 24, 2012 at 12:22 AM, Lee Thomas lthomas_li...@lthomas.net wrote:
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with FreeBSD
9.0-STABLE, and I'm not sure whether it's a bug or incorrect configuration
on my part. The lang/lua port throws a linker error, claiming to need -fPIC,
which is odd because the port Makefile seems to have logic to add that in,
but somehow the logic seems not to have any effect, at least in my case.
Making the port Makefile put ${CFLAGS} directly into lua's Makefile (patch
at the end of this mail) fixes matters for me, but I don't understand the
port infrastructure well enough to understand whether this patch represents
a bugfix or a workaround of some local configuration issue. Has anyone run
into this issue before? If this is a config issue, any hints on what might
be going on or how to dope it out?
I think I had the same problem about a moth ago. The problem was my
CFLAGS in make.conf.
You probably have CFLAGS=something, try setting it to CFLAGS?=something.
--
chs,
___
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: Using non-gcc linker?
On 1/23/2012 3:47 PM, Pierre-Luc Drouin wrote: Hi, I just made world and kernel using clang, but I noticed that ld is still using the GNU ld. The page http://wiki.freebsd.org/BuildingFreeBSDWithClangmentions using a different linker that supports LTO optimisation. Is that non-GNU linker part of FreeBSD 9? 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 It's a newer gnu ld that supports plugins. The plugin handles the LTO. It might be possible to compile to bytecode, link and optimize with llvm-ld. It might still need gnu ld to create a final binary. ___ 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: kqueue and filenames
Thanks for your reply! Am 23.01.2012 20:12, schrieb Pieter de Goeje: kevent is triggered when a file is renamed. How do I get the new name? Is there an extra function? In the moment, I see only the possibility by searching the filesystem(folder) for a new name. A good question to which I unfortunately do not have the answer to. I think in principle it is impossible to get the file name by file descriptor alone (it could have multiple names). In practice I would just treat NOTE_RENAME as a sequence of unlink/link. I believe tools like lsof use the system name cache to map fds to names, but that is not very reliable. Ok, then it's a new challenge! I was hoping, that there's a more comfortable way to obtain the new filename. Matthias ___ 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: Horrible installer
On Mon, Jan 23, 2012 at 11:24:20PM +0100, claudiu vasadi wrote: From my point of view, I would like to see 2 major things in bsdinstall: 1) ZFS support 2) an option, to use GUI or text mode installer (similar to RHEL, CentOS, Solaris) 3) GELI disk encryption pgpWKcdL5irSY.pgp Description: PGP signature
