NetBSD Summer of Code Summary 20
UltimaGuy writes "The NetBSD Project is pleased to announce the results of its participation in Google's "Summer of Code". After Google announced this program to introduce students to the world of open source software development at the beginning of June, the NetBSD Project was happy to join the approximately 40 other open source groups as a mentoring organization and compiled a list of suggested projects. I personally think the Project tmpfs: Efficient memory file-system as the most successful one."
So.... (Score:3, Funny)
Re:So.... (Score:3, Funny)
As long as it's not followed by a Winter of Discontent.
Re:So.... (Score:2)
Userfs (Score:5, Interesting)
Re:Userfs (Score:2)
SysV-type (init.d) subsystem control? (Score:2, Interesting)
Being a big-Unix person, I find the SysV approach to subsystem control through "init.d/blahblah {stop/start}" very sysadmin-friendly, so Linux has always got a big pat on the back from me for that. In contrast, the old *BSD approach has always seemed less helpful when you need to bring subsystems up and down regularly. One manages, but it's a pain.
I guess I was hoping to see SysV-type subsystem control a
Re:SysV-type (init.d) subsystem control? (Score:4, Informative)
Re:SysV-type (init.d) subsystem control? (Score:2, Interesting)
Indeed. I actually find the rc.d system much easier to use then the sysv-init thing. I tend to get confused by 6 directories with symlinks which have to be kept up to date instead of 1 configuration file.
And frankly, i never use the different runlevels like you're supposed to anyways. I only ever start or stop single services, and reboot the system. I don't start different sets of services.
Re:SysV-type (init.d) subsystem control? (Score:3, Insightful)
I don't think anyone else does either. It's far more complex than the "problem" it was trying to solve. Somewhere deep within the bowels of Sun is a sysadmin who truly uses the SysV init system, but everyone else can get by with a far simpler system... like rc.d.
Re:SysV-type (init.d) subsystem control? (Score:1)
UserFs Completion (Score:2, Interesting)
# still bare-bones
# simple filesystem with some hardcoded files (which are modifiable) written
# "The framework coughs but manages to avoid complete and utter defeat."
# code not yet imported
However, in the end: all SoC goals met ?
That just seems...... off to me.
Re:UserFs Completion (Score:2, Informative)
That's because you didn't read the goals. They were behind a link, so I'm not sure if they qualify as TFA.
I think I speak for the entire open source... (Score:2)
tmpfs documentation (Score:2, Interesting)
I once wrote a ramdisk driver from scratch on MacOS 7; it would have been nice to have enough documentation to actually write a new filesystem to use on it instead of HFS.
Is it coding season already? (Score:2)
The Fall of programming progress...
The Winter of endless loop hibernation -- a bitter code spell, indeed...
And the Spring of 1000 bugs! (looks like time to gear up for another Summer of Code, eh?)
--
Minimalist barebones computer, motherboard, and CPU reviews [baremetalbits.com].
SOC was good, I wish for more summaries (Score:1)
It would be cool if more would tell the world how things turned out. I noticed that some of the NetBSD projects didn't get completed in time. I suspect that some organizations might be afraid to summarize because they would show that the projects didn't get completed, but I say that's OK. In business some projects get