Hey, some very good programming can be found on cable-access. Many old horror shows came out of local broadcast, and when those channels had to go to networks, the cable access took over. MST3k got its start on local access, and anyone over 40 can remember the local shows featuring clowns showing cartoons on Saturday mornings, and personalities such as the Ghoul or Zacherly, which graced only local markets.
Re:the code of conduct for free software distribut
on
Drafting GPL3
·
· Score: 0
IP Tables? Bahh, we call that Netfilter, and we've had it for years! You don't need IP addresses on that firewall! BSD will run that software faster! We've been ported to your toaster before linux was a twinkle in Torvalds' eye!... Ad Nauseam.
Re:the code of conduct for free software distribut
on
Drafting GPL3
·
· Score: 0
Yeah, but the BSD folks have something to say about everything.
You mean they won't be able to contol the desire for everyone to have this machine, instead of buying their competitors product? They won't have to worry about people poking around their bios and reverse engineering it, because there would only be one reason to do that? They won't be able to handle the heaps of praise placed upon them from the open source community?
Why do they keep trying to hide this stuff from us? The same goes for the Canon Digital Rebel, and everything else that has an artificial ceiling put on performance.
Yes, and I've even compiled KDE to use PAM and just installed the dropline pam-relevant stuff. The main problem is the lack of coordination between the two camps. --current has been known to break things, as right now there is a new GCC with NPTL threads in current, and dropline is not compiled against it, and won't be until we get slack 10.2 or 11.0, whatever the next version is.
I am hoping that Pat realizes that slackware is going to be left behind, stuck in single-server installations, pushed to the network fringe, unless he breaks down and accept PAM, and with Novell's network logon and Fedora's newly gpl-ed directory server both out there now, I hope he breaks down and goes with PAM.
Not to start a flame war, but if I liked debian, I'd use debian.
I use slackware, because I like slackware. I can use Debian if I have to, but it's my choice to use slack. Anything that apt can do I can do with ldd and a tgz package. That's my choice. I don't want a debian system, any more than I want an Ubuntu system, anymore than I want a mandrake system. And once I can coerce Pat Voldekerg to include PAM, I won't have to roll my own slack packages.
When so many shops went from Novell 3 and 4 to NT, keeping one of your customers, especially one this large, and proving that your technology is scalable, manageable, and affordable for 30K desktops, I would say that it IS something to get excited about.
I don't think that Novell is going to be providing level one tech support to 30,000 users. I imagine that it will be primarily server support, integration support, etc. available to the tech support staff on-site.
I imagine that there's also a big training portion for their support staff. Novell has always had a certification structure in place that I have found to be more relevant and targetted than Cisco's CCNA and CCNP programs. Hopefully Novell's going to crank out some Novell Certified Professionals within the organization by the time this changeover is completed. It'd be worth it in the long run, for all parties involved.
That's the question. The big problem with answering the question is that we haven't really stated the question properly. What is everyone looking for?
This is what I need, and I hope that developers are listening.
1) A definitive login startegy. I don't want well you could use radius, openldap and pam, or NIS, I want a strategy that is flexible, secure, works across platforms, and is auto configuring, auto discovering. When I plug in my linux laptop, I should at the very least have the option to log onto domains/realms that I know about, but it would be nicer if the network told me what services were available.
2) For Document management, I want the ability to save to a subversion-like repository for documents. This has to be available in the software that I'm using, or integrated into the filesystem so that when I save to a location, it does the work. Sure it can prompt me for document info, titles, notes, etc. but it should pull my user info from the network. I should also be able to open up old revisions, control who has access to my files, and let me know if someone else is working on it, allow merged changes from different sources, etc. It should have the ability to encrypt documents, and keep a version history. Also, it should be easy to back up, be able to restore either the whole shot or parts, and be managed by an administrator. Come to think of it, this might be better incorporated into the filesystem. Sounds a little like Reiser4, with some AFS thrown in. SVNFS anyone?
3) Enterprise grade CRM and Accounting for linux. Although, I think that ACCPAC is working on this, we need something. I'm not aware of any linux programs that break past the SME marktet for linux. Support for cheque stocks, micr strips, the whole works, is a must.
You have these three things, and you could turn quite a few companies to linux in their next upgrade cycle. #3 is going to be difficult to pull off in the FOSS style, as it is a lot more than just programming that goes into it, it needs to be updated for new tax tables, and thouroughly tested, and commercial entities have a hard time doing all that, let alone people who aren't going to be paid for it.
Anyways, that's what I want. Hopefully wilt Red Hat open sourcing the Netscape Directory, we can get something that fits the bill for #1, all packaged up nicely, and in one single project, not a collaboration of many different ones.
If anyone decides to make #1 and #2 a reality, let me know where to send the cheque.
you have a rock solid (Yes, solid) platform for group work, communication and management that OSS can't even touch.
Which, imho, is one of the two problems with the OSS business desktop. Gnome and KDE are great desktops, Linux has a long pedigree of network interoperatiblity, but it is really nothing more than a chain of islands, each doing its own thing. There is not a large network collaboration software for linux that takes care of all of the needs of business users. You can cobble the parts together, but if developers don't control all aspects of the equation, it makes things difficult.
Microsoft is in a unique position where it can tie in parts of its operating system and application software together for a 'just works' solution. People can cobble together a 'works' solution, and even a 'works better than MS' solution, but there is a lot of issues with setting these solutions up. To date (and I have been looking) there is no single definitive solution for something as simple as network logon, and the preferred solution (Ldap, pam and Kerberos) is not the easiest thing to deploy.
Even if you were to create a ldap-pam-kerberos network, with a document management system that used the kerberos authentication, e-mail that used kerberos authentication, and a plugin that allowed you to check out and check in documents into the dms for OpenOffice,without using a third party middleware that added twenty extra steps into it, you would need a huge company or dedicated group to do it, do it right, and do it seamlessly.
Novell's working on it, but because it's new, it isn't mature enough for business to see it as a viable solution. Novell still has its fanboys, and their stuff does warrant it, but they are not seen as a competitive threat to MS.
Hey, e-machine's are standards compliant, they just have low standards.
Every e-machine I've seen is commodity hardware, but usually bargain basement winmodem crap components that I'd never think of using in a production machine.
My big fear is that home users currently need nat to hook more computers to the Internet. If we take that away, can you imagine how many botnets can be out there? Sure it's easier to track to the actual computer, but if the large ISP's aren't helping, what does it matter? My blocklist is going to end up being 6.2e^29 lines long.
Ahh, I never checked out the e-server line. I thought that they were just the xeon processor machines. They are a tad expensive, I thought they wanted their 4-way machines under the $4000 mark.
Guess I'll have to hold out for the Dragon/Godson processors. I'd get killed if I spend more on a computer than on my wedding.
IBM had also planned on releasing multi-power5 processor computers, although I haven't heard anything as of late. Hopefully IBM updates the roadmap for multi-cell computers, or blades, or something that I can fit in my home office.
Slashdot Mirror
I just use mplayer and run the sub files through babelfish a few times. English->German-French->English usually does the trick.
I wonder how much latency we can expect. Could you do a live call-in show using this and skype/asterix?
Hey, some very good programming can be found on cable-access. Many old horror shows came out of local broadcast, and when those channels had to go to networks, the cable access took over. MST3k got its start on local access, and anyone over 40 can remember the local shows featuring clowns showing cartoons on Saturday mornings, and personalities such as the Ghoul or Zacherly, which graced only local markets.
IP Tables? Bahh, we call that Netfilter, and we've had it for years! You don't need IP addresses on that firewall! BSD will run that software faster! We've been ported to your toaster before linux was a twinkle in Torvalds' eye! ...
Ad Nauseam.
Yeah, but the BSD folks have something to say about everything.
You mean they won't be able to contol the desire for everyone to have this machine, instead of buying their competitors product? They won't have to worry about people poking around their bios and reverse engineering it, because there would only be one reason to do that? They won't be able to handle the heaps of praise placed upon them from the open source community?
Damn, this looks like a bad move on their part.
I think that the people over at The Pirate Baywould have to disagree with you.
So with Communism, you have slaves working to become free, and with Captialism you have free men working to become slaves?
What's the third choice?
Why do they keep trying to hide this stuff from us?
The same goes for the Canon Digital Rebel, and everything else that has an artificial ceiling put on performance.
pick a software component that the OSS doesn't have an alternative to, and buy it.
Yes, and I've even compiled KDE to use PAM and just installed the dropline pam-relevant stuff. The main problem is the lack of coordination between the two camps. --current has been known to break things, as right now there is a new GCC with NPTL threads in current, and dropline is not compiled against it, and won't be until we get slack 10.2 or 11.0, whatever the next version is.
I am hoping that Pat realizes that slackware is going to be left behind, stuck in single-server installations, pushed to the network fringe, unless he breaks down and accept PAM, and with Novell's network logon and Fedora's newly gpl-ed directory server both out there now, I hope he breaks down and goes with PAM.
Not to start a flame war, but if I liked debian, I'd use debian.
I use slackware, because I like slackware. I can use Debian if I have to, but it's my choice to use slack. Anything that apt can do I can do with ldd and a tgz package. That's my choice. I don't want a debian system, any more than I want an Ubuntu system, anymore than I want a mandrake system. And once I can coerce Pat Voldekerg to include PAM, I won't have to roll my own slack packages.
Fedora Directory Server, for one.
When so many shops went from Novell 3 and 4 to NT, keeping one of your customers, especially one this large, and proving that your technology is scalable, manageable, and affordable for 30K desktops, I would say that it IS something to get excited about.
I don't think that Novell is going to be providing level one tech support to 30,000 users. I imagine that it will be primarily server support, integration support, etc. available to the tech support staff on-site.
I imagine that there's also a big training portion for their support staff. Novell has always had a certification structure in place that I have found to be more relevant and targetted than Cisco's CCNA and CCNP programs. Hopefully Novell's going to crank out some Novell Certified Professionals within the organization by the time this changeover is completed. It'd be worth it in the long run, for all parties involved.
Some strategic marketing, and porting of code, Novell becomes relevant again, and in a big way.
Go Novell!
That's the question. The big problem with answering the question is that we haven't really stated the question properly. What is everyone looking for?
This is what I need, and I hope that developers are listening.
1) A definitive login startegy. I don't want well you could use radius, openldap and pam, or NIS, I want a strategy that is flexible, secure, works across platforms, and is auto configuring, auto discovering. When I plug in my linux laptop, I should at the very least have the option to log onto domains/realms that I know about, but it would be nicer if the network told me what services were available.
2) For Document management, I want the ability to save to a subversion-like repository for documents. This has to be available in the software that I'm using, or integrated into the filesystem so that when I save to a location, it does the work. Sure it can prompt me for document info, titles, notes, etc. but it should pull my user info from the network. I should also be able to open up old revisions, control who has access to my files, and let me know if someone else is working on it, allow merged changes from different sources, etc. It should have the ability to encrypt documents, and keep a version history. Also, it should be easy to back up, be able to restore either the whole shot or parts, and be managed by an administrator. Come to think of it, this might be better incorporated into the filesystem. Sounds a little like Reiser4, with some AFS thrown in. SVNFS anyone?
3) Enterprise grade CRM and Accounting for linux. Although, I think that ACCPAC is working on this, we need something. I'm not aware of any linux programs that break past the SME marktet for linux. Support for cheque stocks, micr strips, the whole works, is a must.
You have these three things, and you could turn quite a few companies to linux in their next upgrade cycle. #3 is going to be difficult to pull off in the FOSS style, as it is a lot more than just programming that goes into it, it needs to be updated for new tax tables, and thouroughly tested, and commercial entities have a hard time doing all that, let alone people who aren't going to be paid for it.
Anyways, that's what I want. Hopefully wilt Red Hat open sourcing the Netscape Directory, we can get something that fits the bill for #1, all packaged up nicely, and in one single project, not a collaboration of many different ones.
If anyone decides to make #1 and #2 a reality, let me know where to send the cheque.
It'll never make it out of beta.
you have a rock solid (Yes, solid) platform for group work, communication and management that OSS can't even touch.
Which, imho, is one of the two problems with the OSS business desktop. Gnome and KDE are great desktops, Linux has a long pedigree of network interoperatiblity, but it is really nothing more than a chain of islands, each doing its own thing. There is not a large network collaboration software for linux that takes care of all of the needs of business users. You can cobble the parts together, but if developers don't control all aspects of the equation, it makes things difficult.
Microsoft is in a unique position where it can tie in parts of its operating system and application software together for a 'just works' solution. People can cobble together a 'works' solution, and even a 'works better than MS' solution, but there is a lot of issues with setting these solutions up. To date (and I have been looking) there is no single definitive solution for something as simple as network logon, and the preferred solution (Ldap, pam and Kerberos) is not the easiest thing to deploy.
Even if you were to create a ldap-pam-kerberos network, with a document management system that used the kerberos authentication, e-mail that used kerberos authentication, and a plugin that allowed you to check out and check in documents into the dms for OpenOffice,without using a third party middleware that added twenty extra steps into it, you would need a huge company or dedicated group to do it, do it right, and do it seamlessly.
Novell's working on it, but because it's new, it isn't mature enough for business to see it as a viable solution. Novell still has its fanboys, and their stuff does warrant it, but they are not seen as a competitive threat to MS.
Hey, e-machine's are standards compliant, they just have low standards.
Every e-machine I've seen is commodity hardware, but usually bargain basement winmodem crap components that I'd never think of using in a production machine.
My big fear is that home users currently need nat to hook more computers to the Internet. If we take that away, can you imagine how many botnets can be out there? Sure it's easier to track to the actual computer, but if the large ISP's aren't helping, what does it matter? My blocklist is going to end up being 6.2e^29 lines long.
-1, bandicoot.
Ahh, I never checked out the e-server line. I thought that they were just the xeon processor machines. They are a tad expensive, I thought they wanted their 4-way machines under the $4000 mark.
Guess I'll have to hold out for the Dragon/Godson processors. I'd get killed if I spend more on a computer than on my wedding.
IBM had also planned on releasing multi-power5 processor computers, although I haven't heard anything as of late. Hopefully IBM updates the roadmap for multi-cell computers, or blades, or something that I can fit in my home office.
And with yesterday's article about Cuban shooting off his mouth, I don't know what to believe. I thought it was a dupe.