I'm surprised about the misuse of terminology here from someone so knowledgable about Open Source and Open Source related matters. Whether a project is a Open Source or closed source has no bearing on whether it is commercial. There are many commerical Open Source projects, and many non-commercial closed source projects.
If a closed source vendor can't do better than an Open Source vendor.
Its not a matter of the kernel being brittle. Its a matter of kernel developers ensuring your privacy is safeguarded from Intels poorly thought out CPUID feature.
Now that the world has shown its disdain for the CPUID feature [of which this act was a part] , and Intel has abandoned it, Linux kernels need to be updated slightly do they don't bother to imlement this feature [which NT, 2K, 9x, or Solaris never had] on new CPUs.
MainSoft MainWin, a Win32 layer for Linux based on Microsofts source code and developed by both MainSoft and Microsoft [who own and control a large chun of Mainsoft] already exists for Linux. Historically it was used to port IE to Solaris and HPUX.
Get a 30 day trial of Mainwin here. You can also download Microsoft Freecell for Linux on the same site.
I severely doubt that Saving Private Ryan is a film to triumph historical accuracy. Neither is U-571, The Patriot, or any of the other revisionist Hollywood cinema which either simply places Americans is the shoes of other allied nations during battle, or [in the case of the latter film] simply create tales about enemies to enliven the story [no, that particular British general did not kill all those children, and nor has anyone ever alleged those events occured].
It surprises me for a country that seems to concerned about race and sexual relations [the birthplace of `affirmative action', and where it seems socially forbidden to describe someone whose skin is dark or light in color as `black' or `white'], the US has a tendency to pretty much create history in any war film.
Actually, I think you'll find this actually prevents bugtraq from quoting Technet security releses in their entirety, word for word. Hence spin control will actually be lessened.
Bugtraq can still report MS bugs, and use the Technet site as a research tool, but they have to produce their own vulnerablity reports. Which I hope they should, rather than relying on MSs own work. If they perform the research themselves, they might find out the exploit is actually wider than what MS thinks it is.
This id good for Bugtraq and users. I don't like MS any better than the rest of you, but lets talk about what's really wrong with them, rather than this sort of paranoia.
This situation is better for users and Bugtraq, though might delay advisory publication by a few minutes now that Bugtraq must confirm and document the exploit themselves.
a) He means desktop environment when he says Window Managers
b) `KDE', the term, as used by the developers, includes KWM. They are not seperate, one is a subset of the other.
A post from Estanislao Martínez on kuro5hin pretty much sums up the attitude of some on Slashdot to rally against John Katz as if he was trying to infiltrate this geek paradice without claiming any sort of technical merit as his pulpit.
This goes to something I've talked about plenty already-- what somebody on that other site called once/. arrogance-- the belief that programming is the hardest human endeavour in existence, and thus, programmers are the smartest people, and if you know how to program, you can do anything any other professional can as well as they do, or even better.
Like, i.e., give legal advice ("IANAL, but B.S.]"), lecture experts about their own areas of expertise (e.g., go up to a linguist, condescendingly start explaining to them the most idiotic and trivial ideas from, say, Pinker's books, *and* then get them backwards). Or the numerous stories in/. or here in k5 about "g**k political organizing"-- the typical "if anybody is able to hack the political system, we g**ks are". The g**k's premise *is* self-superiority.
The attitude is basically, Katz, as a serious journalist who does not have [or claim to have, or see in advantage of having] wide technical skills, should be denied a voice. Surely `geeks' are entirely capable of evaluating and investigating their own culture? Surely someone without technical skills couldn't possibly understand?
Wrong. The third party view from Katz is the most eloquent and nonpartisan view in any story. And the reactions to the Hellmouth series are a testament to that.
Keep in mind I'm responding to a broad claim, and have provided a broad answer. Yes, the discussion of `geeks' as a single group is a generalization. but in order to draw a picture of scoiety, or any group within it, one must paint broad brush strokes.
The comapny was Iterated Systems. The technology is still being developed, and highly advanced - they even have a fractal moving image compressor that can, [according to a workmate who did a thesis on compression - take with a grain of salt if you like, because I can't back it up] fit eight minuted of better-than-VHS-quality film on a floppy disk. He saw it at a trade show, allegedy. But believe what you will.
The licensing fees for FIF and other iterated technologies are huge. And the weird thing is, if they were open source, Iterated would be in much better straights than they are now. We'd all be using infinitely zoomable, highly comrpessed images [both GIF, JPG, and PNG are web standards due to seeming freeness], and despiute the fact they'd loose the revenue, they'd be known as the number one player in town for fractal image creation tools. And people would but their software over the other utilities which use the same Open Source image format, because they had the fastest algorithms, extra features, or other competitive advantages.
Its more a document archiving format than a new web image format [although it happens to be viewable over the web] - as the article states although its non vectorized, it uses layered bitmaps to create more efficiently encodable data chunks.
And, actually, there is Linux support, and source code available. Just Lizardtech aren't going out of the way to tell anybody about it - see my above post:-)
DjVu has been around for 2 years, and isn't anything new. In fact, it wasn't actually designed by Lizardtech - it was developed as an Open Source technology in the Olivetti and Oracle Researtch labs in Camridge, UK, and was sold when US telco AT&T purcahsed the labs.
Hence the Open Source products generally only seem to be there to satisfy existing licensing requirements from prior to Lizardtech's purchase. It's doubtful Lizardtech tend to encorage that aspect of the technology, and they're only promoting the closed source stuff.
However, the compression is indeed very real and the cross platform nature makes it quite useful for archiving stuff that won't be modified frequently in the future - remeber, that text ain't vectorized, it's just another layered image, AFAICT.
* Alpha blending is being worked on by Keith Packard of SuSE inc. and the brilliant XFree86 team, and should be implemented in a future version of XFree86
* True type fonts have been around for over 2 years and are standard on all major distros. XFree 3 uses an external font server like xfstt, XFree 4 handles them natively.
* etc? True, X lacks color correction. But XFree 4s modular interface allows for a companys to sell closed source X modules AFAIK, so an Apple ColorSync module should be possible. Why not do something constructive and mail them about it?
Well, I'm arguing modern Unix-like philosophy is good, but the implementation doesn't always stick to that philosophy [which is poor]. There's many aspects on Unix that have evolved from 30 years ago.
Another thing you have to remember is that Linux isn't Unix, and doesn't have to be Unix-like down to the last details [especially an aging permission system]. DevFS, and the upcoming XFree86 X extensions, are improvements in Linux [and other XFree86 systems] which are not Unix compatible [or Unix-like is the sense that Unix does not hadle these functions in the same way]. But the trade off is more than worth it.
root doesn't log in. That's the point of the exercise! In an ACL based environment, all users [including administrators] log in with the permissions they need to get their work done, and nothing more. And no, you do not need to have full access to the system to administer it properly.
When Notes Domino is running, even ROOT (NT's "Administrator" account) cannot violate sharing on these files.
Wrong. NT's Adminsitrator account is exactly what Linux should have - a fairly capable priviledged account that still does not have full access to the system.
NTs equiv of root is SYSTEM. No, it doesn't have permission to log on locally:-).
Sorry, you're right and I'm wrong. There were some additional provisions in the SHBA [unrelated to the SHBA, and favouring publishing companies over artists], but I think I'm a little off about the details.
But I think he means color depth - AFAIK, there's no way X can do colordepth on the fly. Does anyone have any info on changing X colordepth without restarting the server?
I agree that Linux should most definitely support both rwxs and ACLs for quite some time, so to give those who prefer the existing system some time to .
But the specifics of NTs ACL implementation won't really be replicated on Linux, nor will the specifics of VMS implementation. NTs mix of ACL and share permissions is [although good security practice by gicing the user the least permission of the two] difficult to comprehend.
And I don't think ACLs would change Linux tradition of giving users limited default permissions. In fact, I'm quite sure they would do the opposite - most daemons and admoinistrators would definitely not use the root account for their day to day work, and their new accounts would have very little system permissions outside of their regular work. A very Unix like concept.:-)
Performance issues could be overcome with some smart engineers. Remember, journalling filesystems are supposed to be slower than non-journalling, yet everything depends on the specifics of the implementation. Thus ReiserFS is faster than Ext2.
I totally agree - let's keep things compatible and allow the improvemtns for those that need it. I think, as a rule, that in situations where rwxs compatibility isn't a concern [and if you coded it smartly, this would be the case], ACLs would be the preferable access control system.
The dangers of having someone log in as root to perform basic tasks [which goes against Unix philiosophy of giving users only the permission they need on the system] and the numbers of services which run as root [there's either soemthing wrong with rwxs, or the authors of quite a few Linux daemons, and I think the authors know what they're doing] would mean ACLs would probably been the default standard once compatibility issues had been ironed out.
Slashdot Mirror
Bruce,
I'm surprised about the misuse of terminology here from someone so knowledgable about Open Source and Open Source related matters. Whether a project is a Open Source or closed source has no bearing on whether it is commercial. There are many commerical Open Source projects, and many non-commercial closed source projects.
If a closed source vendor can't do better than an Open Source vendor.
Mike
that seems more appropriate to an industrial-strength OS with an approved hardware list, which Linux decidedly doesn't have.
Here's Red Hat's. Your Linux distributor is likely to have its own list.
Its not a matter of the kernel being brittle. Its a matter of kernel developers ensuring your privacy is safeguarded from Intels poorly thought out CPUID feature.
Now that the world has shown its disdain for the CPUID feature [of which this act was a part] , and Intel has abandoned it, Linux kernels need to be updated slightly do they don't bother to imlement this feature [which NT, 2K, 9x, or Solaris never had] on new CPUs.
CMOS = Complimentary Metal Oxide Semiconductor
CCS = Compilementary Copper Semiconductor
But the complementary thing is a bit abitrary, so
CS = Copper Semiconductor
is perhaps more appropriate
This shows a fundamental misunderstanding of the licenses which prohibit taking open source software and selling it as part of a commercial
product.
You mean closed source product. The Open Source product may be commercial already, but whether it is or it isn't has no bearing on the GPL.
MainSoft MainWin, a Win32 layer for Linux based on Microsofts source code and developed by both MainSoft and Microsoft [who own and control a large chun of Mainsoft] already exists for Linux. Historically it was used to port IE to Solaris and HPUX.
Get a 30 day trial of Mainwin here. You can also download Microsoft Freecell for Linux on the same site.
I severely doubt that Saving Private Ryan is a film to triumph historical accuracy. Neither is U-571, The Patriot, or any of the other revisionist Hollywood cinema which either simply places Americans is the shoes of other allied nations during battle, or [in the case of the latter film] simply create tales about enemies to enliven the story [no, that particular British general did not kill all those children, and nor has anyone ever alleged those events occured].
It surprises me for a country that seems to concerned about race and sexual relations [the birthplace of `affirmative action', and where it seems socially forbidden to describe someone whose skin is dark or light in color as `black' or `white'], the US has a tendency to pretty much create history in any war film.
Actually, I think you'll find this actually prevents bugtraq from quoting Technet security releses in their entirety, word for word. Hence spin control will actually be lessened.
Bugtraq can still report MS bugs, and use the Technet site as a research tool, but they have to produce their own vulnerablity reports. Which I hope they should, rather than relying on MSs own work. If they perform the research themselves, they might find out the exploit is actually wider than what MS thinks it is.
This id good for Bugtraq and users. I don't like MS any better than the rest of you, but lets talk about what's really wrong with them, rather than this sort of paranoia.
This situation is better for users and Bugtraq, though might delay advisory publication by a few minutes now that Bugtraq must confirm and document the exploit themselves.
The Axis 2120 is a digital still camera running an embedded version of Linux.
It is not designed to be portable, as its power supply and case are aimed at security and permanent webcam use, but you could modify it appropriately.
It's also got motion detection and inbuilt Apache.
Of course, Slashcode took out the parameters because they looked like bad HTML. Using curly
brackets...
(appname)-(version)-(package version and other bits).(platform).rpm
These are 2.0 packages. It seems the naming convention for RPM packages has you a little confused:
--..rpm
Eg,
'
kdebase-2.0-1mdk.i586.rpm
which you linked to, is actually the first *package* of 2.0
Your point is good, but could I point out...
a) He means desktop environment when he says Window Managers
b) `KDE', the term, as used by the developers, includes KWM. They are not seperate, one is a subset of the other.
A post from Estanislao Martínez on kuro5hin pretty much sums up the attitude of some on Slashdot to rally against John Katz as if he was trying to infiltrate this geek paradice without claiming any sort of technical merit as his pulpit.
/. arrogance-- the belief that programming is the hardest human endeavour in existence, and thus, programmers are the smartest people, and if you know how to program, you can do anything any other professional can as well as they do, or even better.
/. or here in k5 about "g**k political organizing"-- the typical "if anybody is able to hack the political system, we g**ks are". The g**k's premise *is* self-superiority.
Self-described g**ks *are* elitist bastards (4.09) (#82)
by Estanislao Martínez (emartinez*NOSPAM@quebecemail.com)
This goes to something I've talked about plenty already-- what somebody on that other site called once
Like, i.e., give legal advice ("IANAL, but B.S.]"), lecture experts about their own areas of expertise (e.g., go up to a linguist, condescendingly start explaining to them the most idiotic and trivial ideas from, say, Pinker's books, *and* then get them backwards). Or the numerous stories in
The attitude is basically, Katz, as a serious journalist who does not have [or claim to have, or see in advantage of having] wide technical skills, should be denied a voice. Surely `geeks' are entirely capable of evaluating and investigating their own culture? Surely someone without technical skills couldn't possibly understand?
Wrong. The third party view from Katz is the most eloquent and nonpartisan view in any story. And the reactions to the Hellmouth series are a testament to that.
Keep in mind I'm responding to a broad claim, and have provided a broad answer. Yes, the discussion of `geeks' as a single group is a generalization. but in order to draw a picture of scoiety, or any group within it, one must paint broad brush strokes.
You can also grap the current viewer and a FIF Plugin for Adobe Photoshop [Win16, Win32, and Macintosh only] from Altamira Group
The comapny was Iterated Systems. The technology is still being developed, and highly advanced - they even have a fractal moving image compressor that can, [according to a workmate who did a thesis on compression - take with a grain of salt if you like, because I can't back it up] fit eight minuted of better-than-VHS-quality film on a floppy disk. He saw it at a trade show, allegedy. But believe what you will.
The licensing fees for FIF and other iterated technologies are huge. And the weird thing is, if they were open source, Iterated would be in much better straights than they are now. We'd all be using infinitely zoomable, highly comrpessed images [both GIF, JPG, and PNG are web standards due to seeming freeness], and despiute the fact they'd loose the revenue, they'd be known as the number one player in town for fractal image creation tools. And people would but their software over the other utilities which use the same Open Source image format, because they had the fastest algorithms, extra features, or other competitive advantages.
Just a thought.
Its more a document archiving format than a new web image format [although it happens to be viewable over the web] - as the article states although its non vectorized, it uses layered bitmaps to create more efficiently encodable data chunks.
:-)
And, actually, there is Linux support, and source code available. Just Lizardtech aren't going out of the way to tell anybody about it - see my above post
DjVu has been around for 2 years, and isn't anything new. In fact, it wasn't actually designed by Lizardtech - it was developed as an Open Source technology in the Olivetti and Oracle Researtch labs in Camridge, UK, and was sold when US telco AT&T purcahsed the labs.
Hence the Open Source products generally only seem to be there to satisfy existing licensing requirements from prior to Lizardtech's purchase. It's doubtful Lizardtech tend to encorage that aspect of the technology, and they're only promoting the closed source stuff.
However, the compression is indeed very real and the cross platform nature makes it quite useful for archiving stuff that won't be modified frequently in the future - remeber, that text ain't vectorized, it's just another layered image, AFAICT.
Your a troll. I'm biting.
*
Alpha blending is being worked on by Keith Packard of SuSE inc. and the brilliant XFree86 team, and should be implemented in a future version of XFree86
* True type fonts have been around for over 2 years and are standard on all major distros. XFree 3 uses an external font server like xfstt, XFree 4 handles them natively.
* etc? True, X lacks color correction. But XFree 4s modular interface allows for a companys to sell closed source X modules AFAIK, so an Apple ColorSync module should be possible. Why not do something constructive and mail them about it?
Well, I'm arguing modern Unix-like philosophy is good, but the implementation doesn't always stick to that philosophy [which is poor]. There's many aspects on Unix that have evolved from 30 years ago.
Another thing you have to remember is that Linux isn't Unix, and doesn't have to be Unix-like down to the last details [especially an aging permission system]. DevFS, and the upcoming XFree86 X extensions, are improvements in Linux [and other XFree86 systems] which are not Unix compatible [or Unix-like is the sense that Unix does not hadle these functions in the same way]. But the trade off is more than worth it.
Youre a troll, but I'll bite.
root doesn't log in. That's the point of the exercise! In an ACL based environment, all users [including administrators] log in with the permissions they need to get their work done, and nothing more. And no, you do not need to have full access to the system to administer it properly.
When Notes Domino is running, even ROOT (NT's "Administrator" account) cannot violate sharing on these files.
:-).
Wrong. NT's Adminsitrator account is exactly what Linux should have - a fairly capable priviledged account that still does not have full access to the system.
NTs equiv of root is SYSTEM. No, it doesn't have permission to log on locally
Sorry, you're right and I'm wrong. There were some additional provisions in the SHBA [unrelated to the SHBA, and favouring publishing companies over artists], but I think I'm a little off about the details.
SeeCourtney Love's speech gives the correct details.
Correct. Or he could use [Crtl] [Alt] [+/-].
But I think he means color depth - AFAIK, there's no way X can do colordepth on the fly. Does anyone have any info on changing X colordepth without restarting the server?
I agree that Linux should most definitely support both rwxs and ACLs for quite some time, so to give those who prefer the existing system some time to .
:-)
But the specifics of NTs ACL implementation won't really be replicated on Linux, nor will the specifics of VMS implementation. NTs mix of ACL and share permissions is [although good security practice by gicing the user the least permission of the two] difficult to comprehend.
And I don't think ACLs would change Linux tradition of giving users limited default permissions. In fact, I'm quite sure they would do the opposite - most daemons and admoinistrators would definitely not use the root account for their day to day work, and their new accounts would have very little system permissions outside of their regular work. A very Unix like concept.
Performance issues could be overcome with some smart engineers. Remember, journalling filesystems are supposed to be slower than non-journalling, yet everything depends on the specifics of the implementation. Thus ReiserFS is faster than Ext2.
I totally agree - let's keep things compatible and allow the improvemtns for those that need it. I think, as a rule, that in situations where rwxs compatibility isn't a concern [and if you coded it smartly, this would be the case], ACLs would be the preferable access control system.
The dangers of having someone log in as root to perform basic tasks [which goes against Unix philiosophy of giving users only the permission they need on the system] and the numbers of services which run as root [there's either soemthing wrong with rwxs, or the authors of quite a few Linux daemons, and I think the authors know what they're doing] would mean ACLs would probably been the default standard once compatibility issues had been ironed out.
In my opinion anyway.