Re: FreeBSD has serious problems with focus, longevity, and lifecycle
On 18/01/12 10:07 +1300, Atom Smasher wrote: On Tue, 17 Jan 2012, Mark Felder wrote: To be fair, it could be worse -- OpenBSD secretly wants you to run snapshots and CURRENT as the RELEASEs are mostly unmaintained outside of the most extreme security concerns. Even the packages are kept at the exact version of the time of release. = and how many corps are running openBSD? talk about an OS that seems to exist only as a playground for its developers... This is more or less like Debian in regards to their packaging. Admittedly, OpenBSD is way up there on the paranoia scale, but I know of plenty of big companies running OpenBSD on large scale routing infrastructure. -- richo || Today's excuse: Your Pentium has a heating problem - try cooling it with ice cold water.(Do not turn off your computer, you do not want to cool down the Pentium Chip while he isn't working, do you?) http://blog.psych0tik.net signature.asc Description: Digital signature
Re: FreeBSD has serious problems with focus, longevity, and lifecycle
On 16/01/12 16:13 -0800, John Kozubik wrote: Julian, On Mon, 16 Jan 2012, Julian Elischer wrote: It pretty much boils down to one thing.. man power.. Wouldn't there be more manpower available for more frequent minor releases if the project were not undertaking two simultaneous production releases ? Specifically, wouldn't it have been feasible to be at 8.4 right now if much of 2011 had not been spent breaking ground on 9.0 ? Further, isn't the lack of focus, or polish of the current release also impacted by these decisions ? Of course there is a limited amount of manpower, but for the points I raised that was a symptom, not a cause... This would be a different argument if all the devs were paid a salary. In many instances the devs in question wouldn't have the motivation to work on the maintenence release, in others the work is sponsored but is moving in a direction that is fundamentally incompatible with the 8.x release. I'm not trying to refute your input, just offering some insight about how it may not be strictly accurate. -- richo || Today's excuse: Please excuse me, I have to circuit an AC line through my head to get this database working. http://blog.psych0tik.net signature.asc Description: Digital signature
Re: FreeBSD has serious problems with focus, longevity, and lifecycle
On 17/01/12 02:21 +, Igor Mozolevsky wrote: On 17 January 2012 01:02, richo ri...@psych0tik.net wrote: This would be a different argument if all the devs were paid a salary. Isn't this a bit of a cyclical argument: developers don't work because they are not paid a salary, the end-user base shrinks, BigCo doesn't want to pay for someone to put extra work in getting fBSD to do something that it can get elsewhere (eg Linux), fewer still developers work on fBSD, end-user base shrinks, BigCo is even more reluctant, even fewer Potentially, but it doesn't invalidate it, imo. I'm very aware that the code I produce for $WORK is very different to code I write in my own time. Code for $WORK is wrapped in test cases, clean, neat and well documented. code I write in my own time tends to be hackish, incomplete totally undocumented and ludicrously easy to break because I'm intrigued by implementing a single interesting figure that has my attention, or to see whether or not a concept is technically feasible. This is a shortcoming of mine that I should work to overcome, but I feel that the same thing would likely extend to other developers, though in most cases to a lesser degree. Without some other motivation most people naturally gravitate towards newer cool features, rather than doing the relatively boring maintenence and backporting. Note though, that recognising this highlights my respect for the people who take the time to do it, even though it may not be as cool as working on the latest and greatest new feature. -- richo || Today's excuse: emissions from GSM-phones http://blog.psych0tik.net signature.asc Description: Digital signature
Re: Porting FreeBSD to Raspberry Pi
On 03/11/11 10:22 +0100, Lars Engels wrote: Hi Hackers, maybe you've heard of the upcoming Raspberry Pi, a credit card sized ARM computer which is about to get sold for 25$ - 35$ from december on. http://www.raspberrypi.org/archives/302 Hardware details: http://elinux.org/RaspberryPiBoard#Hardware_Details The first charge will be 10,000 pieces, so there's a fair chance that one can actually buy a board. If someone is willing to port FreeBSD to the Raspberry, I'd try to get one of the boards and send it to the porter. Cheers Lars I am planning to attempt a port, however I'm very new to kernel development/FreeBSD and would not feel right about accepting hardware for a project I'm not sure I have the skills to finish. To that end I'll be buying boards on release date, but would be interested in working with anyone else who is attempting it. cheers richo -- richo || Today's excuse: static from plastic slide rules signature.asc Description: Digital signature
Re: getting a list of open files versus PID nos.?
On 08/12/10 17:18 -0500, Chuck Robey wrote: What I want to see is a list of all Pids and how many open files there are associated with each Pid? And maybe a ps ax list, so I can associate an application with a pid. I would set things up so it would do this every 15 minutes, and it might just point me at my real Any idea what would be the best way to get a list of all openfiles versus each open pid? I would be happy to write up a python script to give me application versus count of open files list, if I could start with that files versus pids thing. lsof is what you're looking for. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
