Re: problem to kill -KILL process
On Fri, Jan 20, 2012 at 11:24:21PM +0200, ??? ??? 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
How to kill process without reboot?
Doesn't radius have a script in /usr/local/etc/rc.d?
If so use that to stop it rather than KILLing it. E.g:
# /usr/local/etc/rc.d/radiusd stop
or something like that.
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
pgpdWOgpOyFjB.pgp
Description: PGP signature
Re: Horrible installer
On Saturday 21 January 2012 12:52:31 am Damien Fleuriot wrote: On 21 Jan 2012, at 05:47, Michael Sierchio ku...@tenebras.com wrote: I've been using FreeBSD since 2.2.1, and IMHO, the 9.0 installer SUX! It blow chunks. It's a POS. It's crap. It is a joke. I hope I made myself clear. ;-) - M Just because you see things a certain way doesn't make them a fact. It's your personal opinion and other people's mileage may vary. Since you're a fbsd user from 2.x, certainly you're WAY beyond needing the installer and just unpack the base system + kern + src + ports and install them manually. Well, because that's work, and anyone who simply says something sucks like that, probably doesn't like doing that lol ;) Refer my earlier post on the subject. Perhaps if you're unhappy with the new installer you should have submitted feedback about it before -RELEASE hit the road. I too wonder about this. I mean, 9.0 was supposed to be out BEFORE it was actually released, and it was released a little late, so there was actually MORE time to talk about this with someone than what I'm guessing is normal. Last but not least I find your calling the new installer a pos highly disrespectful towards the people that invested time, energy and money in it. I agree. Someone saying anything free is a POS is kind of like... You know? I bet that's Meg griffin! lol. I'm not the best person for sales because I speak my mind, so I can easily say simply If you don't like it, you have choices; You can either write a new installer yourself, find another one that works with it, use a different version, a different OS period, or, of course, shut up and like it since you didn't exactly pay through the nose for it. It's totally free, and you can install it on any number of machines. Complaining about free stuff is perfectly fine I think, but at least give examples of how you think it could be better, or, fix it! Note pad comes for free on Windows, and it blows like Windows does, but I'm not a programmer so even if you COULD get the source, I couldn't fix it. But, I don't sit there telling Microsoft's terrible tech supportpeople who failed at sellingused cars that it sucks... If I wanted to try that out I'd tell Richard Stallman where he could stick Emacs and every bit of the source code lol..Anyone who thinks ITS is better than Unix. Yea... Right... An OS entirely in Assembler, 6 characters no exceptions no passwords and hey I have a Hack! use Enter for your password! Luckly ITS was crappy enough no one in their right mind would WANT to break in to steal CPU cycles lol. That's like breaking into a VMS machine; I'd rather dip my balls in honey and tea bag a jar full of Bullet Ants. (And if you didn't laugh enough at that; look up Bullet Ants; They have one of the most painful stings of anything, and, as such, you aren't considered a man by most tribes until you stick your hands in a special glove set with them in there) lol :) -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: kgzip(8) regression in RELENG_9 GENERIC
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. It's manpage indicates that it is unsuitable for loader(8) use, and that just running gzip(1) on the kernel file is sufficient; a fact to which I can attest, since I compress everything in /boot/kernel to save space on my flashcard installs, and the loader has no problem decompressing it on the fly. kldload(8), on the other hand, still seems to be incapable of handling gzipped klds. -- 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
freebsd-update and archs
Hi! I've just finished installing FreeBSD on my new Mac mini G4, and when I ran freebsd-update on it I found out that freebsd-update only supports i386 and amd64 architectures. How come? -- 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: freebsd-update and archs
On 21/01/2012 10:25, Christer Solskogen wrote: I've just finished installing FreeBSD on my new Mac mini G4, and when I ran freebsd-update on it I found out that freebsd-update only supports i386 and amd64 architectures. How come? If that's not an Intel based Mac, then your definition of new is, well, contrary to all accepted usage. Tier-2 architectures aren't supported by freebsd-update for two reasons: * Lack of available hardware for build systems for freebsd-update to use. Not entirely sure what the status of cross-compilation is at the moment, but I believe the best results are still obtained by compiling natively. * Also, quite frankly, lack of demand. There simply aren't that many consumer or server grade systems available using PowerPC at the moment. (Not the case for embedded systems, but they are unlikely to be using the public freebsd-update servers.) 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
Calxeda processors
I just stumbled on these new ARM based chipsets. Apparently one the FreeBSD folk was onboard with the company as a software engineer as well. 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 :) 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: freebsd-update and archs
On 01/21/12 02:25, Christer Solskogen wrote: I've just finished installing FreeBSD on my new Mac mini G4, and when I ran freebsd-update on it I found out that freebsd-update only supports i386 and amd64 architectures. How come? We don't have suitable build hardware for other architectures, and there are some problems with release cross-building which aren't fixed yet. -- 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: freebsd-update and archs
On Sat, Jan 21, 2012 at 11:52 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 21/01/2012 10:25, Christer Solskogen wrote: I've just finished installing FreeBSD on my new Mac mini G4, and when I ran freebsd-update on it I found out that freebsd-update only supports i386 and amd64 architectures. How come? If that's not an Intel based Mac, then your definition of new is, well, contrary to all accepted usage. That's why I said new and not new :-) Tier-2 architectures aren't supported by freebsd-update for two reasons: * Lack of available hardware for build systems for freebsd-update to use. Not entirely sure what the status of cross-compilation is at the moment, but I believe the best results are still obtained by compiling natively. Perhaps. But building 9.0-RELEASE with TARGET= worked perfectly :) -- 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: freebsd-update and archs
On Sat, Jan 21, 2012 at 12:42 PM, Colin Percival cperc...@freebsd.org wrote: We don't have suitable build hardware for other architectures, and there are some problems with release cross-building which aren't fixed yet. I found out that building ppc with TARGET= worked nicely on 9.0-RELEASE. Do you know what problems? Maybe I can help. -- 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: Horrible installer
On Sat, 21 Jan 2012, Damien Fleuriot wrote: On 21 Jan 2012, at 05:47, Michael Sierchio ku...@tenebras.com wrote: I've been using FreeBSD since 2.2.1, and IMHO, the 9.0 installer SUX! It blow chunks. It's a POS. It's crap. It is a joke. I hope I made myself clear. ;-) - M Just because you see things a certain way doesn't make them a fact. It's your personal opinion and other people's mileage may vary. Since you're a fbsd user from 2.x, certainly you're WAY beyond needing the installer and just unpack the base system + kern + src + ports and install them manually. Refer my earlier post on the subject. Perhaps if you're unhappy with the new installer you should have submitted feedback about it before -RELEASE hit the road. I have not yet encountered the new installer, but I recall the traditional installer still came with 9.0 Beta3 (which I have used), so I am wondering how much time for discussion of the new installer there really was. Nevertheless, the problem with the old installer was the menu system's departure from convention, which did take quite a while to get used to. I recall that the author of the old installer said he regretted picking that menu package for this reason. Could someone enumerate what advanced hooks are now buried? If they are configuration items that can be changed post-install, then there is probably little reason to offer them during the install. Partitioning, RAID setup and encryption are things that do need to be established during setup, and I regret that no installer (for FreeBSD or Linux) notices that I have two empty drives, and defaults to a RAID 1. Daniel Feenberg Last but not least I find your calling the new installer a pos highly disrespectful towards the people that invested time, energy and money in 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 ___ 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/21/12 04:15, Christer Solskogen wrote: On Sat, Jan 21, 2012 at 12:42 PM, Colin Percival cperc...@freebsd.org wrote: We don't have suitable build hardware for other architectures, and there are some problems with release cross-building which aren't fixed yet. I found out that building ppc with TARGET= worked nicely on 9.0-RELEASE. Do you know what problems? Maybe I can help. IIRC there were some data files (fortunes? magic? something like that...) which had platform-specific formats (presumably pointer size and endianness issues) and didn't have properly crossing build tools. It's possible that these have been fixed by now, though. 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. -- 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
Clang - what is the story?
I've been seeing a lot of hoorays and pats on the back and a general feeling satisfaction in being able to use clang to compile FreeBSD and ports. The only reason I can see from searching is a need to get away from gcc (which is tried and tested since the beginning of time) which is now apparently GPLv3. Can someone offer some clarity as to the importance of this? I'm guessing the that stepping away from GPL is generally a good thing, especially if there is something similar with similar license structure to BSD; I just can't understand the rush of it. Even under GPL anything built using gcc can be licensed as you like, so I doubt it could be that. I'm not skeptical, just curious- trying to get my head around some of the dev side of things :) ___ 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[2]: problem to kill -KILL process
Здравствуйте, Frank.
Вы писали 21 января 2012 г., 11:24:59:
FS On Fri, Jan 20, 2012 at 11:24:21PM +0200, ??? ??? 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
How to kill process without reboot?
FS Doesn't radius have a script in /usr/local/etc/rc.d?
FS If so use that to stop it rather than KILLing it. E.g:
FS # /usr/local/etc/rc.d/radiusd stop
despite on it uses standart rc.subr, which says:
# stopif ${pidfile}
# rc_pid=$(check_pidfile $pidfile $command)
# else
# rc_pid=$(check_process $command)
# kill $sig_stop $rc_pid
# wait_for_pids $rc_pid
# ($sig_stop defaults to TERM.)
in other words: kill -TERM 45471 in my case
FS or something like that.
man kill
..
Some of the more commonly used signals:
..
9 KILL (non-catchable, non-ignorable kill)
Standart tool do not do its job. It can not stop/kill processes.
--
С уважением,
Коньков mailto:kes-...@yandex.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
Re: Clang - what is the story?
On 21/01/2012 12:11, Da Rock wrote: I've been seeing a lot of hoorays and pats on the back and a general feeling satisfaction in being able to use clang to compile FreeBSD and ports. The only reason I can see from searching is a need to get away from gcc (which is tried and tested since the beginning of time) which is now apparently GPLv3. Can someone offer some clarity as to the importance of this? I'm guessing the that stepping away from GPL is generally a good thing, especially if there is something similar with similar license structure to BSD; I just can't understand the rush of it. The problem is exactly the GPLv3. The version of gcc in the base system is gcc-4.2, the last version licensed under the old GPLv2 terms, but now looking quite elderly and not resulting in the best performance. Even under GPL anything built using gcc can be licensed as you like, so I doubt it could be that. I'm not skeptical, just curious- trying to get my head around some of the dev side of things :) Unfortunately, no -- you can't necessarily license anything compiled with a GPLv3 compiler using whatever license you prefer. For instance, one problem is that executables will be linked against libraries which are part of the compiler -- and the viral nature of GPLv3 means that the resulting programs have in their turn to be licensed under GPLv3. That's not acceptable for FreeBSD, hence the decision to switch to a BSD licensed toolchain using clang. 9.0 is really an intermediate step in the changeover -- gcc and clang are both provided in the base system and its a matter of administrative choice which one is chosen for compiling the system. One consequence of the change is that it will become more common to install a recent version of gcc from ports to facilitate compiling gcc-only software, with the rest of ports typically compiled with either that ports-gcc or the base clang. This is fairly new at the moment, and there still needs to be a deal of debugging effort put into making the ports work well with compilers other than the base gcc-4.2. 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: Clang - what is the story?
On Sat, 21 Jan 2012 22:11:18 +1000 Da Rock wrote: I've been seeing a lot of hoorays and pats on the back and a general feeling satisfaction in being able to use clang to compile FreeBSD and ports. The only reason I can see from searching is a need to get away from gcc (which is tried and tested since the beginning of time) which is now apparently GPLv3. Can someone offer some clarity as to the importance of this? I'm guessing the that stepping away from GPL is generally a good thing, especially if there is something similar with similar license structure to BSD; I just can't understand the rush of it. Even under GPL anything built using gcc can be licensed as you like, so I doubt it could be that. It is that. I don't know the details, but GPLv3 is sufficiently more viral that recent gcc versions can't be used as the base system compiler. We're currently stuck with a version from 2007. ___ 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
Clang - what is the story?
Da Rock writes: The only reason I can see from searching is a need to get away from gcc (which is tried and tested since the beginning of time) which is now apparently GPLv3. I believe the GPLv3 issue is correct. Two other reasons I have heard mentioned in various discussions: 1) clang has better diagnostics, both for users and compiler developers/ 2) over the years, extensions have crept into GCC. Many were/are there for a reason; many can be ignored or turned off. However, doing so breaks various programs (either when building or running), Why? is above my pay grade. _As I understand it_, clang has few such extensions and those it does have are less necessary. Robert Huff ___ 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
help
where can I register a free shell account, which shell was able to make psybnc and eggdrop? ___ 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 Sat, 21 Jan 2012 13:35:06 + RW wrote: On Sat, 21 Jan 2012 22:11:18 +1000 Da Rock wrote: Even under GPL anything built using gcc can be licensed as you like, so I doubt it could be that. It is that. I don't know the details, but GPLv3 is sufficiently more viral that recent gcc versions can't be used as the base system compiler. We're currently stuck with a version from 2007. I was just wondering what would have happened if Apple hadn't backed clang/LLVM as BSD licensed projects. Was there a plan B (other than gcc 4.2.1) or did Apple save the *BSD world? ___ 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
Network traffic human readable?!
Hi, how can I display my network traffic (netstat output) human readable? Is there a function of the netstat that can do this? Thanks... -- Mit freundlichen Grüßen / Yours sincerely Tobias Pulm -- Tobias Pulm Sperberweg 8 58644 Iserlohn Germany t...@facility5.org | http://www.facility5.org t...@tobias-pulm.de| http://www.tobias-pulm.de OpenPGP| 0xF652F1A5 XMPP / Jabber | t...@xmpp.facility5.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: Network traffic human readable?!
2012/1/21 Tobias Pulm t...@facility5.org Hi, how can I display my network traffic (netstat output) human readable? Is there a function of the netstat that can do this? Thanks... Is this what you need : netstat -i And then filter out the interfaces you need (netstat -i | grep device) -- Beni Brinckman. ___ 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 Sat, Jan 21, 2012 at 7:11 AM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: I've been seeing a lot of hoorays and pats on the back and a general feeling satisfaction in being able to use clang to compile FreeBSD and ports. The only reason I can see from searching is a need to get away from gcc (which is tried and tested since the beginning of time) which is now apparently GPLv3. Can someone offer some clarity as to the importance of this? I'm guessing the that stepping away from GPL is generally a good thing, especially if there is something similar with similar license structure to BSD; I just can't understand the rush of it. Even under GPL anything built using gcc can be licensed as you like, so I doubt it could be that. I'm not skeptical, just curious- trying to get my head around some of the dev side of things :) __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org The reasons for Clang are not just for the GPLv3 issue, but Clang is architecturally superior in many ways over GCC, Clang was designed from the ground up to learn from GCCs mistakes and to be a better C compiler. One of the Clang's features is better debugging and a more modular architecture that is easier to develop and extend. GCC has often been criticised for its monolithic and inflexible structure that has often hindered implementing new features and functionality. One of the advantages of Clang is that it can be more easily plugged into IDEs for integrated debugging. You can read all about the many advantages and innovations of clang and how it exceeds GCC here: http://clang.llvm.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: * Re: Horrible installer
On Fri, Jan 20, 2012 at 11:13 PM, Chad Perrin per...@apotheon.com wrote: ... On the other hand, bsdinstall does get the job done, at least for my purposes. It just does so in a way that feels a bit more straightjacketed, and it rubs me personally a bit the wrong way. ... From my perspective, it replaces something that clearly had at least a decimal order of magnitude more time and effort put into it, and it again makes FreeBSD look like a hobbyist's OS. As you point out, once installed, it has its merits. ;-) - M ___ 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 01/21/12 14:35, RW wrote: [...] It is that. I don't know the details, but GPLv3 is sufficiently more viral that recent gcc versions can't be used as the base system compiler. We're currently stuck with a version from 2007. Sorry if this has been asked before, but it makes me wonder, what are the plans for SPARC and PowerPC? Raimund -- Worringer Str 31 Duesseldorf 40211 Germany +49-179-2981632 icq 16845346 ___ 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: How to destroy a zombie zpool
--As of January 17, 2012 5:19:15 AM +0100, Fritz Wuehler is alleged to have said: zfs is famous for fucking itself like this. the only totally safe way is to dd the drive since nailing the label doesn't clear out stuff at the far end of the filesystem that can really ruin your day. don't ask me how i know.. it will take a few hours dd'ing from /dev/zero to your devices but it is well worth it when you do any major surgery on drives that had zfs at one point and you want to use them over again with zfs --As for the rest, it is mine. Thanks; I finally had some more time to play with this box again, and that did the trick. Took less than 2 hours, to do two drives. ;) (Simultainously, and one's a SSD.) (Well, I still can't figure out why I can't *boot* into ZFS, but at least I've eliminated one variable.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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 21/01/2012 17:47, Raimund Steger wrote: On 01/21/12 14:35, RW wrote: [...] It is that. I don't know the details, but GPLv3 is sufficiently more viral that recent gcc versions can't be used as the base system compiler. We're currently stuck with a version from 2007. Sorry if this has been asked before, but it makes me wonder, what are the plans for SPARC and PowerPC? PowerPC is apparently supported by clang, so ultimately it should just switch over like i386 and amd64. Clang doesn't compile on sparc64 at the moment. I assume this is just a temporary state of affairs and sparc64 support will be forthcoming eventually. Until then sparc64 will have to make do with the current gcc 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: mplayer fails to compile on amd64 machine
From: Antonio Olivares olivares14...@gmail.com To: FreeBSD Questions freebsd-questions@freebsd.org Sent: Thursday, January 19, 2012 9:07 PM Subject: mplayer fails to compile on amd64 machine Dear kind folks, Running Amd64 FreeBSD 8.0 updated l/live/groupsock/libgroupsock.a -lm -rpath=/usr/lib:/usr/local/lib -Wl,-rpath=/usr/local/lib/gcc46 -liconv /usr/lib/libncurses.so -lpng -lz -ljpeg -lungif -L/usr/local/lib -lfreetype -lz -lbz2 -lfontconfig -lz /usr/lib/libbz2.so -llzo2 -lmad -lspeex -L/usr/local/lib -ltheora -logg -lstdc++ -L/usr/local/lib -lrtmp -lz -lssl -lcrypto -ldv -pthread -rdynamic -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib -lv4l1 -lv4l2 -lrtmp -lXext -lX11 -pthread -lXss -lXv -lvdpau -lXinerama -lXxf86vm -lXxf86dga -laa -lcaca -lvga -lSDL -lGL -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangocairo-1.0 -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lgdk_pixbuf-2.0 -lpangoft2-1.0 -lgio-2.0 -lXfixes -lcairo -lX11 -lpango-1.0 -lm -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lglib-2.0 ffmpeg/libavcodec/libavcodec.a(ffv1.o): In function `find_best_state': /usr/ports/multimedia/mplayer/work/mplayer-export-2011-12-18/ffmpeg/libavcodec/ffv1.c:243: undefined reference to `log2' ffmpeg/libavcodec/libavcodec.a(aacsbr.o): In function `sbr_make_f_master': /usr/ports/multimedia/mplayer/work/mplayer-export-2011-12-18/ffmpeg/libavcodec/aacsbr.c:428: undefined reference to `log2f' /usr/ports/multimedia/mplayer/work/mplayer-export-2011-12-18/ffmpeg/libavcodec/aacsbr.c:456: undefined reference to `log2f' ffmpeg/libavcodec/libavcodec.a(aacsbr.o): In function `sbr_make_f_derived': /usr/ports/multimedia/mplayer/work/mplayer-export-2011-12-18/ffmpeg/libavcodec/aacsbr.c:580: undefined reference to `log2f' /usr/ports/multimedia/mplayer/work/mplayer-export-2011-12-18/ffmpeg/libavcodec/aacsbr.c:580: undefined reference to `log2f' collect2: ld returned 1 exit status gmake: *** [mplayer] Error 1 *** Error code 1 Stop in /usr/ports/multimedia/mplayer. *** Error code 1 Stop in /usr/ports/multimedia/mplayer. === make failed for multimedia/mplayer === Aborting update === Update for multimedia/mplayer failed === Aborting update Terminated /usr/src/UPDATING shows nothing relevant. ideas/suggestions/advice/comments are welcome and appreciated. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org The mplayer port has been broken before. Now doubt it's in need of fixing again. I have found over the years that once you get a working version of it in place, don't try to reinstall it. I'm sure the port maintainer does their best, afterall this is a Linux program ported to run on FreeBSD and all the subtle changes can never be thought completely through. Send an e-mail to the port maintainer, they'll get it fixed in the next round. ___ 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 01/22/12 02:39, David Jackson wrote: On Sat, Jan 21, 2012 at 7:11 AM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: I've been seeing a lot of hoorays and pats on the back and a general feeling satisfaction in being able to use clang to compile FreeBSD and ports. The only reason I can see from searching is a need to get away from gcc (which is tried and tested since the beginning of time) which is now apparently GPLv3. Can someone offer some clarity as to the importance of this? I'm guessing the that stepping away from GPL is generally a good thing, especially if there is something similar with similar license structure to BSD; I just can't understand the rush of it. Even under GPL anything built using gcc can be licensed as you like, so I doubt it could be that. I'm not skeptical, just curious- trying to get my head around some of the dev side of things :) __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.orgfreebsd-questions-unsubscr...@freebsd.org The reasons for Clang are not just for the GPLv3 issue, but Clang is architecturally superior in many ways over GCC, Clang was designed from the ground up to learn from GCCs mistakes and to be a better C compiler. One of the Clang's features is better debugging and a more modular architecture that is easier to develop and extend. GCC has often been criticised for its monolithic and inflexible structure that has often hindered implementing new features and functionality. One of the advantages of Clang is that it can be more easily plugged into IDEs for integrated debugging. You can read all about the many advantages and innovations of clang and how it exceeds GCC here: http://clang.llvm.org/ That was the first place I looked to see if anything stood out as the reason why, and I couldn't quite see apart from license. Apparently I had missed some aspects in the license Thanks for the answers guys. Legal issues can be real tricky sometimes can't they? I definitely would have missed that about the libraries- its obvious now :) That also explains the issues with other compilers (especially ones on other platforms). 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
Fwd: wrong MD5 and SHA256 ?!? OK!!!!!!!
It's OK, You've already changed the FreeBSD-9.0-RELEASE-i386-memstick.im on site, the checksums are the same as I calculate. Thanks. Best regards, Ruben Original Message Subject:wrong MD5 and SHA256 ?!? Date: Sun, 22 Jan 2012 02:29:08 +0400 From: Ruben R. Shkhikyan shkhik...@gmail.com To: freebsd-questions@FreeBSD.org Hi, why the MD5 and SHA256 of FreeBSD-9.0-RELEASE-i386-memstick.img are wrong? (MD5: FreeBSD-9.0-RELEASE-i386-memstick.img = 79ddd8f3422e209ae9bd11fee4e399eb) - Your Calculation (MD5: FreeBSD-9.0-RELEASE-i386-memstick.img = F9DDF26894FCF7EA5813D7D9099FF6A4) - My Calculation (with WinHex) (SHA256 (FreeBSD-9.0-RELEASE-i386-memstick.img = 99193a7895109d415936ba89e4f2c24227af48f064073dee7c4b49722c3656f8) - Your Calculation (SHA256 (FreeBSD-9.0-RELEASE-i386-memstick.img = 3A325895F4D9E14F0F60F9A7ADF50C73DB71C7BA833D2E5A27A34985B6F88523) - My Calculation (with WinHex) Best regards, Ruben. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Network traffic human readable?!
On 01/21/12 07:47, Tobias Pulm wrote: Hi, how can I display my network traffic (netstat output) human readable? Is there a function of the netstat that can do this? Rather than netstat, perhaps you want 'tcpdump' or 'nc'. Regards, Jason C. Wells ___ 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: mplayer fails to compile on amd64 machine
/usr/ports/multimedia/mplayer/work/mplayer-export-2011-12-18/ffmpeg/libavcodec/aacsbr.c:580: undefined reference to `log2f' collect2: ld returned 1 exit status gmake: *** [mplayer] Error 1 *** Error code 1 Stop in /usr/ports/multimedia/mplayer. *** Error code 1 Stop in /usr/ports/multimedia/mplayer. === make failed for multimedia/mplayer === Aborting update === Update for multimedia/mplayer failed === Aborting update Terminated /usr/src/UPDATING shows nothing relevant. ideas/suggestions/advice/comments are welcome and appreciated. Regards, Antonio ___ The mplayer port has been broken before. Now doubt it's in need of fixing again. I have found over the years that once you get a working version of it in place, don't try to reinstall it. I'm sure the port maintainer does their best, afterall this is a Linux program ported to run on FreeBSD and all the subtle changes can never be thought completely through. Send an e-mail to the port maintainer, they'll get it fixed in the next round. ___ Thank you Bill, I have three machines two running 8.2 amd64 and one running 9.0-STABLE and only one had this problem. I have installed svn version of mplayer on this machine and it is working fine. Guess, I will just run # portmaster -a -x mplayer and skip mplayer updates via ports. Maintainer of mplayer port advised me to update src to latest, either 8.2 or move up to 9.0, but I am hesistant to do so at this time :( Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
wrong MD5 and SHA256 ?!?
Hi, why the MD5 and SHA256 of FreeBSD-9.0-RELEASE-i386-memstick.img are wrong? (MD5: FreeBSD-9.0-RELEASE-i386-memstick.img = 79ddd8f3422e209ae9bd11fee4e399eb) - Your Calculation (MD5: FreeBSD-9.0-RELEASE-i386-memstick.img = F9DDF26894FCF7EA5813D7D9099FF6A4) - My Calculation (with WinHex) (SHA256 (FreeBSD-9.0-RELEASE-i386-memstick.img = 99193a7895109d415936ba89e4f2c24227af48f064073dee7c4b49722c3656f8) - Your Calculation (SHA256 (FreeBSD-9.0-RELEASE-i386-memstick.img = 3A325895F4D9E14F0F60F9A7ADF50C73DB71C7BA833D2E5A27A34985B6F88523) - My Calculation (with WinHex) Best regards, Ruben. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: wrong MD5 and SHA256 ?!?
On Sat, Jan 21, 2012 at 4:29 PM, Ruben R. Shkhikyan shkhik...@gmail.com wrote: Hi, why the MD5 and SHA256 of FreeBSD-9.0-RELEASE-i386-memstick.img are wrong? (MD5: FreeBSD-9.0-RELEASE-i386-memstick.img = 79ddd8f3422e209ae9bd11fee4e399eb) - Your Calculation (MD5: FreeBSD-9.0-RELEASE-i386-memstick.img = F9DDF26894FCF7EA5813D7D9099FF6A4) - My Calculation (with WinHex) (SHA256 (FreeBSD-9.0-RELEASE-i386-memstick.img = 99193a7895109d415936ba89e4f2c24227af48f064073dee7c4b49722c3656f8) - Your Calculation (SHA256 (FreeBSD-9.0-RELEASE-i386-memstick.img = 3A325895F4D9E14F0F60F9A7ADF50C73DB71C7BA833D2E5A27A34985B6F88523) - My Calculation (with WinHex) Best regards, Ruben. ___ Maybe you downloaded before official release? The isos were made available but were not complete, then they were reuploaded since there was a file added? This could be one possibility? See: http://www.freebsd.org/releases/9.0R/announce.html quote NOTE: A problem was discovered with the DVD images for amd64 and i386 architectures shortly after they were loaded on the FTP distribution server. Those images have since been replaced and we have allowed enough time that the newer images should have distributed to all the FTP servers that carry the release. If you downloaded the amd64 or i386 DVD images prior to this announcement it would be a good idea to verify the checksums of the image you downloaded with the checksums provided as part of this Release Announcement. The only thing wrong with the images that were replaced is that sysinstall(8) can not be used to install the pre-built packages on the DVD. Other than that there is nothing different on the updated images. The bad DVD images were never available on BitTorrent. /quote Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Clang - what is the story?
On Sat, Jan 21, 2012 at 03:43:13PM +, RW wrote: I was just wondering what would have happened if Apple hadn't backed clang/LLVM as BSD licensed projects. Was there a plan B (other than gcc 4.2.1) or did Apple save the *BSD world? The backup plan was probably PCC. -- 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: Clang - what is the story?
On 01/22/12 17:02, Chad Perrin wrote: On Sat, Jan 21, 2012 at 03:43:13PM +, RW wrote: I was just wondering what would have happened if Apple hadn't backed clang/LLVM as BSD licensed projects. Was there a plan B (other than gcc 4.2.1) or did Apple save the *BSD world? The backup plan was probably PCC. Whats actually surprising is that it wasn't used as plan A (I just looked it up); It then would have come full circle ;) ___ 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 Sun, Jan 22, 2012 at 05:09:52PM +1000, Da Rock wrote: On 01/22/12 17:02, Chad Perrin wrote: On Sat, Jan 21, 2012 at 03:43:13PM +, RW wrote: I was just wondering what would have happened if Apple hadn't backed clang/LLVM as BSD licensed projects. Was there a plan B (other than gcc 4.2.1) or did Apple save the *BSD world? The backup plan was probably PCC. Whats actually surprising is that it wasn't used as plan A (I just looked it up); It then would have come full circle ;) A couple years ago, it looked like a race between PCC and TenDRA, but Clang seemed to just come out of nowhere and steal all the attention. All three of them had a lot to recommend them, but then the TenDRA modernization project evaporated and everybody jumped on the Clang wagon. At least, that's how it looked to me. -- 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
