This has always been the case for compiling programs for Novell: a DOS/Windows box with compilers. This is nothing new or special with regard to Perl.
You're correct, but that's my point; no other enterprise NOS that I know of requires a completly different platform in order to compile and link its binaries.
Just to share blame, why not address the issue that a large portion of Perl modules that use native code aren't portable outside of UNIX (and even then...).
Funny, I've never had that problem with the more simple perl modules. With NetWare I'm talking about simple things such as rsync for perl, or even most of the tools as implemented in the Perl Power Tools.
Perl for NetWare is poorly supported, and does not support basic things such as fork(), chown, syscall, chroot, alarm, and about 20 other functions... Ummm... Of course this is because NetWare itself doesn't have these functions.
Correct, NetWare does not have these functions. You made yet another point of mine. For example; NetWare has a cron binary (NLM) - it is not possible to run two cron jobs at the same time. For example: I have one job that starts at 8:55am, and takes about 5 hours to complete, and another that runs every hour on the hour. What happens is that the first job will start at 8:55, but the second job will be unable to run until the first one is complete. That's five hours later, not every hour on the hour...
Current operating systems? UNIX is *how* old? NetWare by your metric IS the current operating system.
Hmm, I must have confused you here. By current, I meant an OS that kept up with what EVERYONE else was doing (ie: implementing simple things such as fork()), not in regards to actual age.
As for network-wide security and administration, I'm sorry but Novell's offerings are superior and have been superior for years. NIS+? LDAP? Active Directory? Pshaw! NDS was already better than these years ago and eDirectory widens that margin.
Security, oh god you're one of those. I never mentioned security in my post, but all NetWare die-hards have to include this bit in their argument. Well, I bite: NetWare has a horrible track record for communicating with their customers regarding security issues. Novell needs to grow up, and stop acting like a two-year old when they have a security issue. Their security website (only a few months old I might add), is sketchy, and does not outline all of the security issues encountered with their products. For example, the buffer overflow in the GroupWise GWIA that was discovered back in June/July; Novell still has not noted the issue, or posted a specfic patch to the issue. This is not the only example, but I quite frankly dont want to dig up the others right now...
When I talk to Novell techs about when/why I should have to apply a patch, they basicaly tell me that they have poor change control and documentation procedures for their code, and many times, fixes for bugs and security issues get placed into production code, without it ever being documented. Oh great, now I, as the customer, have to guess when a security issue is going to bite me, and/or when a feature is changed - because Novell cant be bothered to tell me about them... The fact of the matter is, from an administrative standpoint, when you really take the time to look at it, NetWare is looking less and less secure.
Oh, and dont get me started on the security of NetWare itself - what idiot runs all of their processes at root-level on Unix systems. I sure dont, but with NetWare you dont get a choice, if an NLM crashes, it abends the server, if an NLM has a security issue (like the recent Apache one), youre server gets rooted. If the process crashes, the crash most likely shuts down the service that was running under the NLM, and very likely requires a reboot of the server in order to get that process/service back online (unlike Unix, where under 99.9% of the cases, you simply start the process again). I dont know about you, but I dont fully trust all of the software that comes from my software vendors, and I'd rather see it running at a level that is not likely to shutdown or takeover the entire server (ie: as "nobody", or a normal user with less-than root access to the server). On Unix this is dead simple to do, with NetWare I dont get that option...
While I'll agree that NDS is an excellent product, developers for it are as scarce as the products that integrate into it (ie: they are far and few between). Afterall, if Novell's GroupWise folks cant make GroupWise work with NDS natively, how can they expect anyone else to make their product work. The GroupWise folks have only been promising full NDS integration for around 4-6 years. Sure LDAP support is getting there, but it's not native NDS support, and not even the GroupWise folks have gotten LDAP support fully working yet.
Why does Novell need to update Perl? Because they bundle it? Why doesn't the Perl community maintain the port just like they do for every other operating system ? Or is Novell special on your shitlist? It's not like Novell controls the Perl source.
Yes, if they bundle it, they should update/maintain it, just like the other vendors do... I dont see Novell providing an enviroment where the perl developers can connect to a NetWare server and compile/update/patch/test the code (oops, you cant do that with NetWare, you need a seperate Windows/DOS system to do that...). Most of the other ports are written because the perl developers have access to a system they can test/develop on...
NetWare is an excellent file and print server. Novell is trying to make NetWare into an application server, something it has never done well at...
This is just a me-too tatic by Novell. Many of Novell's previous me-too's have fallen by the wayside as well. One exception at present is Perl.
NetWare ships with Perl 5.00307, an almost useless and stripped down old version (released October 1996 by the Perl folks, and released November 2000 by the NetWare folks) - where you cannot compile your own Modules without a Windows NT machine (95/98 will not be sufficent) Microsoft Visual C 4.2 or later, a CodeWarrior compiler and linker, the "NetWare SDK", "NLM & NetWare Libraries for C" and "NetWare Server Protocol Libraries for C".
To put it as breifly as possible; Perl for NetWare is poorly supported, and does not support basic things such as fork(), chown, syscall, chroot, alarm, and about 20 other functions that are standard with a real, and current Network Operating System (ie: Unix based systems, and to a lesser extent, Win32 systems).
MySQL users on NetWare will very likely fall into the same unsupported trap... History speaks for itself, beware!
So, how often do you create backups? Every 5 minutes, 10, 20, what? In the real world, where everyone makes mistakes (gasp! make a mistake!?!), the end-user most likely made a significant change to a document, only to overwrite the changes or delete the document by accident. The NetWare salvage tool is an excellent tool for "undoing" these kind of mistakes while not wasting time retyping the entire document, or restoring the document from backup, and then pulling together the changes that were overwritten from that point (plus, as the sysadmin, I dont have to spend time restoring the document)...
Dont be so quick to criticize, it makes you look like an idiot, and turns people off to asking these types of questions in a public forum.
It makes you wonder if technology like the Tesla Turbine, and the technology behind the air powered car could be combined to create something much more efficient...
USENET has been around for 20+ years, and covers topics far more vast than whats covered at Ask Slashdot. A good USENET search engine: groups.google.com
Yes, I am tired of proprietary systems, ones that change at the vendors whim without regard for what the customers are clearly requesting, and ones where I've had software written for - for the vendor to only make yet another undocumented change that breaks it. Or for the vendor to lock the system details up, so that I, as the owner of the data, cannot get to it without jumping though inefficient hoops that only give me a porthole to drag the mountain through. In-fact, I feel these types of issues are a core catalyst behind the upsurge in the open source movement.
I've worked with quite a few companies where more than just email worked for them, in-fact the calendaring is pretty useful in may cases. My concerns are with designs that lock my data up into proprietary systems, inaccessible to other systems without expensive third party tools, extensively written custom software or expensive and ad-hock consulting services - when open and well published standards exist that better facilitate interopability. I'm tired of systems that don't allow you to interoperate with others outside your organization, without jumping though yet more hoops, making the whole process inefficient and cumbersome.
Nature has told us, time and time again, that the simplest system is the one most likely to succeed (ala: Ockham's razor)... Which may just help to explain UNIX's still strong success after its incarnation 30+ years ago, where nearly every process/program/library still serves a specific purpose, KISS...
Training does help, but it does not resolve the issues completely. Systems must be easy to use, or over the long term, they will not be used. It really is just that simple, as humans are pretty lazy when it comes right down to it. There is that group that wants to learn, but then there is that much larger group that wants to stay they way they where.
In regards to the referred to paper, yes it does accurately reflect where we are now, but it was written 8 years ago, and based on papers mostly dating into the mid to late 80's. If you really think we can get past that, or that we are headed past that, why arent we clearly past it, or moving past it now... The fact is, existing groupware systems are far too complex for the average user to grasp. Anyone who expects the average user to grasp these proprietary concepts and methods is living a pipe dream, especially when these systems change so frequently...
Novell has done a good job these last few years communicating to the end-users with tools like CoolSolutions. In-fact I've been on the CoolSolutions mailing lists since they first started, but the fact is - not everybody shares the same passion into computers as most of us on Slashdot do. Most "...normal..." people (if you can call them that:-) feel they have better things to do with their time. Yes, I do have those users who are the local experts, and those that express a desire to learn more about the systems, but in reality, these valuable people are far and few between.
Why do I knock down GroupWise? It is a collective system that historically has not worked well for the environments I've seen and heard of it in. It's a system full of half-baked implementations, and broken and inefficient features, that Novell has acknowledged, and for years has promised to fix, but still has not followed through. Novell has allowed the development to stagnate over the last few years, and the excuses I'm hearing are that the development team feels that they don't need to listen to the customers. Now, from what I understand this developer issue may be changing, but many of Novell's other products are in the same situation, so I have to question how much if this is just another line of excuses.... Other than vendor supplied case studies, I know of nobody that has implemented an all-encompassing proprietary groupware system, in an normal business environment, where interopability with different systems was maintained, and was cost-effective to setup and deploy.
I'll second the recommendation for "The Practice of System and Network Administration". It's the only book of its kind; independent of specfic platforms or technologies, and it stresses the six key principles of systems design and support practices: simplicity, clarity, generality, automation, communication, and the basics.
The slashdot review is here, and the freshmeat.net review is here
Where this book falls short in details (ie: exact policy wording, exact technical details of an issue, etc...), it gives you solid references to goto to get the details.
This book should really be required reading for anyone thinking of going into (or already in) systems administration. I've got 7 years in the field, and this book is still teaching me a thing-or-two.
And no, I dont get any kickbacks for this recommendation...
This is the first step for him and Microsoft to admit that this is in-fact possible on a wide scale.
There is already a tool (IEradicator) that can remove IE from any version of Windows older than Win2Ksp2. Having Microsoft admit this is possible, is just another step forward,
I just bought a HandEra 330, after considering a Visor, one of the new Palm models and some of the WinCE devices. I didn't think the springboard "standard" was very viable, and I didn't like the bulkiness of the add-ons. The newest Palm models are not much of an improvement over my current PDA. The WinCE devices, well, I just winced when they kept crashing on me (nevermind the battery life and interopability issues as well).
The HandEra 330 is hands down the best, you get a CompactFlash slot, and a MMC/SD slot. I can add 64MB of memory to this thing, and still have room to plug in my GPS, 802.11 wireless NIC, cell modem, or landline modem (all based off of the miniature PCMCIA standard that CompactFlash uses) all while using the built-in microphone to record things. Plus I can use equipment that was originally designed to work with the Palm III line of products. I'm going to purchase the Lithium battery pack and charger, which will eliminate the need for the 4 AAAs it currently uses.
Also, the HandEra 330 screen is double the resolution of any greyscale Palm or Visor currently on the market. The HandEra 330 also has a "soft silkscreen", where the graffiti area can actually be minimized to free up screen real-estate.
Use Ghostscript (ps2pdf) for your ps to pdf conversions on Linux and Win32. On Win32, print to a file using the "Apple LaserWriter II NT" printer. This has taken care of 99% of my needs (the other 1%, I haven't had to deal with yet:-).
One thing I haven't been able to find yet, is the ablity to create FDF's (Acrobat Forms). Any ideas out there?
Now I cant access Word, or Excel at microsoft.net
on
Microsoft's DNS Down
·
· Score: 1
Well, if I was stupid enough to license my software through MS.net, I would have to go home now. As, I wouldnt be able to access any applications through their hosted services... Remember microsoft.net...
Actually I live in Portland OR. Not a small city, but not the largest either. We are also not the ideal city for solar powered anything, our sunshine is more in the form or what we call "liquid sunshine" (ie: Rain).
Yes, you are right on the parking garages, I thought of that as soon as I hit the submit button. Hey! Maybe solar panels on the top of the garages, just a thought...
It's simple. Peak usage for the power to recharge the car is at night, wheras peak usage for things like air conditioning are during the day.
Another idea is that you usally have 8-10 hours before you need to use your car again. So on those hot days when the AC is running, you have a solar panel on the roof of your car charging the batteries.
To really make this happen, the hardware to make it work will have to be inexpensive. Maybe something like this would help move things along (it's even based on Linux too)?
Try MRTG, a nice tool for obtaining SNMP info. I use it for reporting utilization on my routers, others use it for modem usage, processor utilization, memory usage, uptime, basicly whatever you can get a MIB on. Also, freshmeat.net returns about 17 hits on a search for "SNMP". Google returns about 6206 hits on a search for SNMP from their www.google.com/linux page. Some of it looks very usefull, of-course I have yet to do a search on Google that does not return good results.
Thats great for Linux, but what is the best digital camera out there anyway (price, Hi res, good color..)? I would love to see some of them get Linux support too. But this is a step in the right direction.
Slashdot Mirror
This has always been the case for compiling programs for Novell: a DOS/Windows box with compilers. This is nothing new or special with regard to Perl.
You're correct, but that's my point; no other enterprise NOS that I know of requires a completly different platform in order to compile and link its binaries.
Just to share blame, why not address the issue that a large portion of Perl modules that use native code aren't portable outside of UNIX (and even then...).
Funny, I've never had that problem with the more simple perl modules. With NetWare I'm talking about simple things such as rsync for perl, or even most of the tools as implemented in the Perl Power Tools.
Perl for NetWare is poorly supported, and does not support basic things such as fork(), chown, syscall, chroot, alarm, and about 20 other functions...
Ummm... Of course this is because NetWare itself doesn't have these functions.
Correct, NetWare does not have these functions. You made yet another point of mine. For example; NetWare has a cron binary (NLM) - it is not possible to run two cron jobs at the same time. For example: I have one job that starts at 8:55am, and takes about 5 hours to complete, and another that runs every hour on the hour. What happens is that the first job will start at 8:55, but the second job will be unable to run until the first one is complete. That's five hours later, not every hour on the hour...
Current operating systems? UNIX is *how* old? NetWare by your metric IS the current operating system.
Hmm, I must have confused you here. By current, I meant an OS that kept up with what EVERYONE else was doing (ie: implementing simple things such as fork()), not in regards to actual age.
As for network-wide security and administration, I'm sorry but Novell's offerings are superior and have been superior for years. NIS+? LDAP? Active Directory? Pshaw! NDS was already better than these years ago and eDirectory widens that margin.
Security, oh god you're one of those. I never mentioned security in my post, but all NetWare die-hards have to include this bit in their argument. Well, I bite: NetWare has a horrible track record for communicating with their customers regarding security issues. Novell needs to grow up, and stop acting like a two-year old when they have a security issue. Their security website (only a few months old I might add), is sketchy, and does not outline all of the security issues encountered with their products. For example, the buffer overflow in the GroupWise GWIA that was discovered back in June/July; Novell still has not noted the issue, or posted a specfic patch to the issue. This is not the only example, but I quite frankly dont want to dig up the others right now...
When I talk to Novell techs about when/why I should have to apply a patch, they basicaly tell me that they have poor change control and documentation procedures for their code, and many times, fixes for bugs and security issues get placed into production code, without it ever being documented. Oh great, now I, as the customer, have to guess when a security issue is going to bite me, and/or when a feature is changed - because Novell cant be bothered to tell me about them... The fact of the matter is, from an administrative standpoint, when you really take the time to look at it, NetWare is looking less and less secure.
Oh, and dont get me started on the security of NetWare itself - what idiot runs all of their processes at root-level on Unix systems. I sure dont, but with NetWare you dont get a choice, if an NLM crashes, it abends the server, if an NLM has a security issue (like the recent Apache one), youre server gets rooted. If the process crashes, the crash most likely shuts down the service that was running under the NLM, and very likely requires a reboot of the server in order to get that process/service back online (unlike Unix, where under 99.9% of the cases, you simply start the process again). I dont know about you, but I dont fully trust all of the software that comes from my software vendors, and I'd rather see it running at a level that is not likely to shutdown or takeover the entire server (ie: as "nobody", or a normal user with less-than root access to the server). On Unix this is dead simple to do, with NetWare I dont get that option...
While I'll agree that NDS is an excellent product, developers for it are as scarce as the products that integrate into it (ie: they are far and few between). Afterall, if Novell's GroupWise folks cant make GroupWise work with NDS natively, how can they expect anyone else to make their product work. The GroupWise folks have only been promising full NDS integration for around 4-6 years. Sure LDAP support is getting there, but it's not native NDS support, and not even the GroupWise folks have gotten LDAP support fully working yet.
Why does Novell need to update Perl? Because they bundle it? Why doesn't the Perl community maintain the port just like they do for every other operating system ? Or is Novell special on your shitlist? It's not like Novell controls the Perl source.
Yes, if they bundle it, they should update/maintain it, just like the other vendors do... I dont see Novell providing an enviroment where the perl developers can connect to a NetWare server and compile/update/patch/test the code (oops, you cant do that with NetWare, you need a seperate Windows/DOS system to do that...). Most of the other ports are written because the perl developers have access to a system they can test/develop on...
NetWare is an excellent file and print server. Novell is trying to make NetWare into an application server, something it has never done well at...
This is just a me-too tatic by Novell. Many of Novell's previous me-too's have fallen by the wayside as well. One exception at present is Perl.
NetWare ships with Perl 5.00307, an almost useless and stripped down old version (released October 1996 by the Perl folks, and released November 2000 by the NetWare folks) - where you cannot compile your own Modules without a Windows NT machine (95/98 will not be sufficent) Microsoft Visual C 4.2 or later, a CodeWarrior compiler and linker, the "NetWare SDK", "NLM & NetWare Libraries for C" and "NetWare Server Protocol Libraries for C".
To put it as breifly as possible; Perl for NetWare is poorly supported, and does not support basic things such as fork(), chown, syscall, chroot, alarm, and about 20 other functions that are standard with a real, and current Network Operating System (ie: Unix based systems, and to a lesser extent, Win32 systems).
MySQL users on NetWare will very likely fall into the same unsupported trap... History speaks for itself, beware!
So, how often do you create backups? Every 5 minutes, 10, 20, what? In the real world, where everyone makes mistakes (gasp! make a mistake!?!), the end-user most likely made a significant change to a document, only to overwrite the changes or delete the document by accident. The NetWare salvage tool is an excellent tool for "undoing" these kind of mistakes while not wasting time retyping the entire document, or restoring the document from backup, and then pulling together the changes that were overwritten from that point (plus, as the sysadmin, I dont have to spend time restoring the document)...
Dont be so quick to criticize, it makes you look like an idiot, and turns people off to asking these types of questions in a public forum.
It makes you wonder if technology like the Tesla Turbine, and the technology behind the air powered car could be combined to create something much more efficient...
USENET has been around for 20+ years, and covers topics far more vast than whats covered at Ask Slashdot. A good USENET search engine: groups.google.com
Yes, I am tired of proprietary systems, ones that change at the vendors whim without regard for what the customers are clearly requesting, and ones where I've had software written for - for the vendor to only make yet another undocumented change that breaks it. Or for the vendor to lock the system details up, so that I, as the owner of the data, cannot get to it without jumping though inefficient hoops that only give me a porthole to drag the mountain through. In-fact, I feel these types of issues are a core catalyst behind the upsurge in the open source movement.
:-) feel they have better things to do with their time. Yes, I do have those users who are the local experts, and those that express a desire to learn more about the systems, but in reality, these valuable people are far and few between.
I've worked with quite a few companies where more than just email worked for them, in-fact the calendaring is pretty useful in may cases. My concerns are with designs that lock my data up into proprietary systems, inaccessible to other systems without expensive third party tools, extensively written custom software or expensive and ad-hock consulting services - when open and well published standards exist that better facilitate interopability. I'm tired of systems that don't allow you to interoperate with others outside your organization, without jumping though yet more hoops, making the whole process inefficient and cumbersome.
Nature has told us, time and time again, that the simplest system is the one most likely to succeed (ala: Ockham's razor)... Which may just help to explain UNIX's still strong success after its incarnation 30+ years ago, where nearly every process/program/library still serves a specific purpose, KISS...
Training does help, but it does not resolve the issues completely. Systems must be easy to use, or over the long term, they will not be used. It really is just that simple, as humans are pretty lazy when it comes right down to it. There is that group that wants to learn, but then there is that much larger group that wants to stay they way they where.
In regards to the referred to paper, yes it does accurately reflect where we are now, but it was written 8 years ago, and based on papers mostly dating into the mid to late 80's. If you really think we can get past that, or that we are headed past that, why arent we clearly past it, or moving past it now... The fact is, existing groupware systems are far too complex for the average user to grasp. Anyone who expects the average user to grasp these proprietary concepts and methods is living a pipe dream, especially when these systems change so frequently...
Novell has done a good job these last few years communicating to the end-users with tools like CoolSolutions. In-fact I've been on the CoolSolutions mailing lists since they first started, but the fact is - not everybody shares the same passion into computers as most of us on Slashdot do. Most "...normal..." people (if you can call them that
Why do I knock down GroupWise? It is a collective system that historically has not worked well for the environments I've seen and heard of it in. It's a system full of half-baked implementations, and broken and inefficient features, that Novell has acknowledged, and for years has promised to fix, but still has not followed through. Novell has allowed the development to stagnate over the last few years, and the excuses I'm hearing are that the development team feels that they don't need to listen to the customers. Now, from what I understand this developer issue may be changing, but many of Novell's other products are in the same situation, so I have to question how much if this is just another line of excuses.... Other than vendor supplied case studies, I know of nobody that has implemented an all-encompassing proprietary groupware system, in an normal business environment, where interopability with different systems was maintained, and was cost-effective to setup and deploy.
I'll second the recommendation for "The Practice of System and Network Administration". It's the only book of its kind; independent of specfic platforms or technologies, and it stresses the six key principles of systems design and support practices: simplicity, clarity, generality, automation, communication, and the basics.
The slashdot review is here, and the freshmeat.net review is here
Where this book falls short in details (ie: exact policy wording, exact technical details of an issue, etc...), it gives you solid references to goto to get the details.
This book should really be required reading for anyone thinking of going into (or already in) systems administration. I've got 7 years in the field, and this book is still teaching me a thing-or-two.
And no, I dont get any kickbacks for this recommendation...
This is the first step for him and Microsoft to admit that this is in-fact possible on a wide scale.
There is already a tool (IEradicator) that can remove IE from any version of Windows older than Win2Ksp2. Having Microsoft admit this is possible, is just another step forward,
I just bought a HandEra 330, after considering a Visor, one of the new Palm models and some of the WinCE devices. I didn't think the springboard "standard" was very viable, and I didn't like the bulkiness of the add-ons. The newest Palm models are not much of an improvement over my current PDA. The WinCE devices, well, I just winced when they kept crashing on me (nevermind the battery life and interopability issues as well).
The HandEra 330 is hands down the best, you get a CompactFlash slot, and a MMC/SD slot. I can add 64MB of memory to this thing, and still have room to plug in my GPS, 802.11 wireless NIC, cell modem, or landline modem (all based off of the miniature PCMCIA standard that CompactFlash uses) all while using the built-in microphone to record things. Plus I can use equipment that was originally designed to work with the Palm III line of products. I'm going to purchase the Lithium battery pack and charger, which will eliminate the need for the 4 AAAs it currently uses.
Also, the HandEra 330 screen is double the resolution of any greyscale Palm or Visor currently on the market. The HandEra 330 also has a "soft silkscreen", where the graffiti area can actually be minimized to free up screen real-estate.
I'm in PDA heaven...
And no, I dont work for them...
Use Ghostscript (ps2pdf) for your ps to pdf conversions on Linux and Win32. On Win32, print to a file using the "Apple LaserWriter II NT" printer. This has taken care of 99% of my needs (the other 1%, I haven't had to deal with yet :-).
If you don't want to or can't install Ghostscript, take a look here: http://www.babinszki.com/distiller/
One thing I haven't been able to find yet, is the ablity to create FDF's (Acrobat Forms). Any ideas out there?
Well, if I was stupid enough to license my software through MS.net, I would have to go home now. As, I wouldnt be able to access any applications through their hosted services... Remember microsoft.net...
Checkout the Debian sponsored project: www.linuxforkids.com
Actually I live in Portland OR. Not a small city, but not the largest either. We are also not the ideal city for solar powered anything, our sunshine is more in the form or what we call "liquid sunshine" (ie: Rain).
Yes, you are right on the parking garages, I thought of that as soon as I hit the submit button. Hey! Maybe solar panels on the top of the garages, just a thought...
It's simple. Peak usage for the power to recharge the car is at night, wheras peak usage for things like air conditioning are during the day.
Another idea is that you usally have 8-10 hours before you need to use your car again. So on those hot days when the AC is running, you have a solar panel on the roof of your car charging the batteries.
To really make this happen, the hardware to make it work will have to be inexpensive. Maybe something like this would help move things along (it's even based on Linux too)?
Try MRTG, a nice tool for obtaining SNMP info. I use it for reporting utilization on my routers, others use it for modem usage, processor utilization, memory usage, uptime, basicly whatever you can get a MIB on. Also, freshmeat.net returns about 17 hits on a search for "SNMP". Google returns about 6206 hits on a search for SNMP from their www.google.com/linux page.
Some of it looks very usefull, of-course I have yet to do a search on Google that does not return good results.
Thats great for Linux, but what is the best digital camera out there anyway (price, Hi res, good color..)? I would love to see some of them get Linux support too.
But this is a step in the right direction.