A good, FOSS, real-time microkernel kernel would be a very good contribution to free and open source software.
I'd rather see a unified and open driver interface that multiple operating systems and architectures could use without the porting. Then you'd only have to implement the interface, and just nick the drivers from somewhere else.
(oh, OT: yeah my website is down for the moment. Working on it)
Well, the best thing I could do is delve into dutch politics, since I am dutch. There's a political party called "SP" which is a socialist party.
Sure it's modeled after Maoism, which is a good philosophy. Too bad that china didn't really do it in practice.
So you could say the meaning of socialism I'm after is more Maoist. Dunno what american socialism entails, but maoist socialism has plenty of room for free enterprise, but it encourages people to share.
I also wrote a bunch of hacks that I just gave away, but I never expected patches, or for people to actually use it.
Open Source is like socialism, you just help out where you can, and share what you got. If people don't take it, then it's their loss:) At least it was useful for myself, and it might be useful for others.
To assume that one writes a few hundred lines of code, and then get instant fame is of course ridiculous:)
They will be used, but not gratuitously. It's mostly to get our packaging system to go where we want to, without having to worry about the new VFS stuff yet. Variant symlinks solve about 90% of the problems at 10% of the cost, so that's why they were implemented. Also, it kinda depends on what the person that installed DFly on his machine is doing:)
When DFly's VFS subsystem is getting into shape, the need for varsyms will be less and less.
You are right of course. Eventually it will be virtually impossible to do a clean switchover. But the DragonFly community is doing as much as they can to make the upgrade path as uneventful as possible.
Even though it might not be possible in the future to 'upgrade' to DragonFly from a FreeBSD-STABLE machine, we'll try the hardest to keep the FreeBSD port system working until we have our package management sorted out. And boy, with the stuff that Matt has planned, that's going to be beautiful. Not the compilation of hacks that the package/port system is today. Not to blast the port system, it's serving us well at the moment, but there's always a better way:)
You are right of course. I don't use varsyms yet, but I had a look at the code and that confirms what you said. Not much documentation yet, but the varsym tool has a manual page. It works like you expect. One sets a variable with varsym, and then you can use that variable (with ${} notation) in symlinks. Example:
> cat > file-file1 this is file 1 ^D > cat > file-file2 this is file 2 ^D > ln -s 'file-${foo}' test > varsym foo=file1 > cat test this is file 1 > varsym foo=file2 > cat test this is file 2
Of course, varsym defaults to user context, which means that the var is only 'visible' to the user. With the -s flag, the var becomes system wide, and you can also restrict the view to the process.
There isn't much more to it. It's easy, clean and simple:)
Variant symlinks as found in Domain OS (nee Domainix, nee Apollo Aegis) are symlinks that refer to environment variables, e.g.
ln -s '/etc-$(HOSTNAME)'/etc
to help enable sharing the root file system. (I don't know the variable-reference syntax used in Dragonfly).
It's exactly the same. The variables for symlinks can be set with the varsym(1) tool, and of course the vfs.varsym_enable sysctl has to be set to '1'. You can set symlink variables in global, user and process context.
It's already very good (and stable). Well allright, sometimes it breaks (that's development for ya), but wait a few hours, and the system is stabilized again (patches are backed out, or bugfixes get in). It's not like CURRENT, where you can hose your system beyond recognition if your not careful.
Your Distributed.net client will Just Work Fine(tm). I'm still running that KDE 3.1.4 on my laptop that I compiled under 4.9-RCmumble, and that's still working quite spiffy.
Dragonfly is almost a drop-in replacement. You can just pull it over your existing 4.x-STABLE box, and all your apps should work fine (except for kernel modules). Oh, if you have an NVIDIA gfx card, I ported the binary kernel module to DFBSD, and it's sitting smugly in the override ports. (read dfly's UPDATING about dfports)
DragonFly as of current perfectly fills that niche where people want the latest and greatest, but don't want to run FreeBSD-CURRENT just yet. It's mostly production-safe. You can always revert back to your old FreeBSD-STABLE without much hassle.
q1) Will this mean that SUSE's groupware client is dead?
No idea, but wouldn't it be cool if there was a Groupware for Linux? (which would be cool anyways, since I can run that with the Linux ABI in FreeBSD)
q2) will this mean there will be a directory enabled printing method for linux clients?
Oh, I wish. That would be really cool. If Novell intends to focus on linux, it'd be smart to do so. I hope they use CUPS as a framework for this though.
Not that I like linux that much (since I'm more of a *BSD nut), there are plenty of end-user targeted distros out there. Lindows and Mandrake have quite a strong commercial backing.
I was always under the impression that a "bang" was a sound. By your standards, it should have been called the "Big Detonation", which does imply an explosive situation, without making any assumptions about sound.
Same goes for "crunch" as in "The Big Crunch". Also has distinct sonical implications.
In the end, my point of the grandparent post was that the whining about "you don't have sound in space, so this is ridiculous" is in fact ridiculous itself:)
Space, in fact, is a pretty noisy place. Take background radiation, the chatter on the radiowaves from celestial bodies, black holes, etc. If space was _really_ quiet, there would never be any need for radio-astronomy.
Slashdot Mirror
"External augmentation does not a cyborg make"
Or something of that ilk. You figure it out :)
Remember when ASCII porn was traded through Gopher?
Copy the WinNT SAM file to a usb drive, and l0phtcrack at home at your leisure.
H.G. Wells called. He wants his time machine back.
I dunno, but where I come from, we call that a 'mailing list'.
I'd rather see a unified and open driver interface that multiple operating systems and architectures could use without the porting. Then you'd only have to implement the interface, and just nick the drivers from somewhere else.
(oh, OT: yeah my website is down for the moment. Working on it)
It does?
*hic*
Sure it's modeled after Maoism, which is a good philosophy. Too bad that china didn't really do it in practice.
So you could say the meaning of socialism I'm after is more Maoist. Dunno what american socialism entails, but maoist socialism has plenty of room for free enterprise, but it encourages people to share.
But I do like your approach. It comes a lot closer.
I also wrote a bunch of hacks that I just gave away, but I never expected patches, or for people to actually use it.
Open Source is like socialism, you just help out where you can, and share what you got. If people don't take it, then it's their loss :) At least it was useful for myself, and it might be useful for others.
To assume that one writes a few hundred lines of code, and then get instant fame is of course ridiculous :)
Not true. From the ifconfig manpage in FreeBSD (actually DragonFly, but who cares. Dfly didn't change ifconfig):
When it gets cold in my room I just turn on some more computers and screens. Who needs a heater? :)
When DFly's VFS subsystem is getting into shape, the need for varsyms will be less and less.
Might I refer you to RFC 2100? It explains why some hosts have such weird names sometimes. :)
Even though it might not be possible in the future to 'upgrade' to DragonFly from a FreeBSD-STABLE machine, we'll try the hardest to keep the FreeBSD port system working until we have our package management sorted out. And boy, with the stuff that Matt has planned, that's going to be beautiful. Not the compilation of hacks that the package/port system is today. Not to blast the port system, it's serving us well at the moment, but there's always a better way :)
Of course, varsym defaults to user context, which means that the var is only 'visible' to the user. With the -s flag, the var becomes system wide, and you can also restrict the view to the process.
There isn't much more to it. It's easy, clean and simple :)
to help enable sharing the root file system. (I don't know the variable-reference syntax used in Dragonfly).
It's exactly the same. The variables for symlinks can be set with the varsym(1) tool, and of course the vfs.varsym_enable sysctl has to be set to '1'. You can set symlink variables in global, user and process context.
Your Distributed.net client will Just Work Fine(tm). I'm still running that KDE 3.1.4 on my laptop that I compiled under 4.9-RCmumble, and that's still working quite spiffy.
Dragonfly is almost a drop-in replacement. You can just pull it over your existing 4.x-STABLE box, and all your apps should work fine (except for kernel modules). Oh, if you have an NVIDIA gfx card, I ported the binary kernel module to DFBSD, and it's sitting smugly in the override ports. (read dfly's UPDATING about dfports)
DragonFly as of current perfectly fills that niche where people want the latest and greatest, but don't want to run FreeBSD-CURRENT just yet. It's mostly production-safe. You can always revert back to your old FreeBSD-STABLE without much hassle.
So, if you're really curious, just give it a go!
Errr.... s/Groupware/GroupWise/i
No idea, but wouldn't it be cool if there was a Groupware for Linux? (which would be cool anyways, since I can run that with the Linux ABI in FreeBSD)
q2) will this mean there will be a directory enabled printing method for linux clients?
Oh, I wish. That would be really cool. If Novell intends to focus on linux, it'd be smart to do so. I hope they use CUPS as a framework for this though.
- Lindows
- Mandrake
- Knoppix
- Vector
- (and many more
Not that I like linux that much (since I'm more of a *BSD nut), there are plenty of end-user targeted distros out there. Lindows and Mandrake have quite a strong commercial backing.You mean when Dee-dee (Dexter's sister) pressed the blinkey shiney red button that was labeled "Don't press zis buutton!".
Right?
Same goes for "crunch" as in "The Big Crunch". Also has distinct sonical implications.
In the end, my point of the grandparent post was that the whining about "you don't have sound in space, so this is ridiculous" is in fact ridiculous itself :)
Space, in fact, is a pretty noisy place. Take background radiation, the chatter on the radiowaves from celestial bodies, black holes, etc. If space was _really_ quiet, there would never be any need for radio-astronomy.
*shrug*