No, ARM don't make processors. They design processor cores, instruction sets and so on, and license them to other companies to make them - hence, for example, Intel and TI both have pretty successful ARM-based chips for PDAs and phones...
So what, I'm supposed to invent a bug and then solve it?
I certainly can't speak for XFree86, but this is normal practice within the engineering group at my employer, and AFAIK at other commercial development houses. Raising a bug for a feature means that it can be tracked as a commit, means people can make comments on it, means you have a common format for all commits, be they bugfixes or new features, and so on. No, I don't really like it either, but it makes a lot of sense.
Sun has proceeded to demostrate how it is NOT serious about the OSS thingy by never following through on that promise. The university still has not seen line one of source code from the vapor-OSS project known as Sun GridWare under popular OSS license.
Well the University obviously hasn't looked very hard. Following the standard Sun method, there's the 'commercial' product, and an Open Source 'project' standing behind it. The Grid Engine Project does, of course, have downloadable and browsable source code under the SISL.
An excellent speaker (don't miss him if you get the chance), a fascinating dinner guest, and generous with his hip-flask. And all this on my birthday...
An internet debut announced around the world, yet only available to those living on the island.
Um... I've seen this advertised/discussed in exactly 3 places now: the BBC (yes, the British Broadcasting Corporation), the GLLUG mailing list (that's the Greater London LUG) and here. Of them, I would only consider the BBC one to be an 'official' announcement and they are a British corporation, aiming at a British audience, paid for by the British tax-payer.
The amount of content on this site which is only available or in any way relevent to residents of the US is phenomenal. And that's largely okay, since this is effectively a US site. But you and others who are complaining that this is only available in the UK are only seeing a small example of what we see all the time.
In a more practical sense, I can think of at least three major reasons for the limitation:
Another US/UK inbalance thing - we pay for bandwidth both ways because we have to pay for the privilege of talking to you guys. Streaming a movie could get really expensive really fast.
This is an experiment - they are hoping to generate enough noise and support from this to get a US distribution deal.
Um... forgot the third one. Argh. There was something to go in here. Really.
Re:What would make the ultimate player...
on
MPlayer 1.0Pre1 Is Here
·
· Score: 4, Informative
Taint, in this case, is a technical term. The kernel keeps a flag showing if all the code in it or loaded into it (i.e. modules) is open source, and if a module containing closed source code is loaded, the taint flag is set.
The point, of course, is that when you post on the lkml saying "Wah wah my kernel's dead", they can come back and say "Sorry - we can't fix that because you're running code in your kernel which we don't have access to". Or possibly something less polite:-) But anyway, that's why the taint flag exists.
I've been playing with the same thing for my iPAQ for a while - effectively the same hardware... Any chance of posting your script (or at least your settings) here, or directly to me by e-mail? Much appreciated:-)
Okay, so you sound like you have what I need... the problem is that I'm not a qmail guru, and I have absolutely no interest in becoming one. So how do I do this? To be honest, I'd just prefer to go over to exim - not for any specific reason, apart from not having enjoyed my experience with qmail, and having met Phil Hazel a couple of times and heard him speak on exim - and him sounding sane and, frankly, being a nice bloke:-)
So tell me, what do I need in which of the various config files - I'm talking system-wide, on a real multi-user system with lots of virtual domains - to get SpamAssissin run with per-user settings while mail is delivered. It should hopefully go without saying that changing individual.qmail files is unacceptable, since there are already over 100 of them on the system.
I do have the QMAILQUEUE patch applied... To be honest - if you've got all this working, I'd really appreciate it if you'd drop me a line (I'd mail you, but you've not published your address) and let me know in detail what you had to do to get this stuff working...
Answer me this then - how do I get all mail going through my qmail system (not setup by me, but I'm one of the admins) to go through SpamAssassin, but with per-user settings - i.e. after the decision has been made on who to deliver the mail to - without losing the ability to use.qmail files? Oh, and ideally without lots and lots more patching - there's a lot to be said for a stable system, but it's a real problem when the author doesn't seem to be planning any more releases, but the license forbids people from distributing patched releases...
Or to put it another way: qmail may be better for security, but I've had a lot of trouble working out how to hell to administer it, since it seems to ignore most of the tradition UNIX rules on 'how stuff works' in favour of newer, cooler, but random-seeming rules...
For those of us who - for whatever reason - aren't going to go help people ourselves, you could do a lot worse than helping one of our own who asks - very politely.
Bram Moolenaar, the author/maintainer of the amazing vim visited a school/community center/development center in Uganda a few years back, and when he returned to Europe, he, along with others, setup a charity in the Netherlands to support the center. Those who use and enjoy vim (and those who don't!) "are
encouraged to make a donation for needy children in Uganda." Go to the International Child Care Fund and make a donation, or at least click through their Amazon affiliation links next time you buy something from there. That way, it doesn't even cost you anything...
Wouldn't it be nice to Slashdot a charity with donations?:-)
Wouldn't you know it... I had mod points until a couple of hours ago. These are exactly the same points that I make to 'but isn't a TiVo just a VCR with a hard drive?' people. Ain't TiVo grand?:-)
What or who determines the "evilness" or "goodness" of the packet? If a security admin or OS can determine or flag bits as good, what keeps the hacker from spoofing this process by setting the bit to "good"? Does the bit change based on behavior? Or maybe a database with signatures of "bad" bits?
(name deleted)
Microsoft Corporation
Not to worry, good sir - there is a simple and easy answer to your question. All Microsoft software and systems should automatically set the bit to evil! On the off-chance of the packet passing through a clean system, the bit could be set to good, but all data originating from a Microsoft system are, by definition, evil.
I thought XMMS was going to be the default media player for Linux (and UNIX). I love it for listening to music, but video development has been ignored.
I actually use mplayer as my music player of choice now. I like the keyboard control, the doesn't-need-X-ness, the choice of output method (I use esd for local streaming - I know it sucks, but it works) and the support for many codecs...:-)
UNIX and Unix aren't the same thing:-) Unix is a style and/or a family of operating systems, including the commercial Unixes, the BSDs and (at least possibly) the Linuxes. UNIX is a trademark and a brand name, owned by the Open Group, and operating systems which pass the branding process - in effect, which are provably compatible with the published POSIX/Unix standards - are granted the right to use the brand. So NT with the right layered stuff may be UNIX, but it certainly isn't Unix, while Linux is Unix, but no Linux distro (and it would have to be a distro) is UNIX.
Slashdot Mirror
You know the answer to that just as well as I do... I hope :-)
:-(
No, ARM don't make processors. They design processor cores, instruction sets and so on, and license them to other companies to make them - hence, for example, Intel and TI both have pretty successful ARM-based chips for PDAs and phones...
Yep, 45 minutes of groove without so much as a wiggle in it.
And the BBC are broadcasting a live performance of the single version, this evening!
Seriously :-)
Sorry, just can't resist a chance to waste some karma :-)
Got it from DVDSoon, got the confirmation mail last night... Oh, and Hi! I used to be u5rmc@csc in a previous life...
I think you'll find that would actually make it a 'de jure' sim :-)
It does, if it's done in the same way as the FOTR extended edition. The film itself comes on two disks :-)
I certainly can't speak for XFree86, but this is normal practice within the engineering group at my employer, and AFAIK at other commercial development houses. Raising a bug for a feature means that it can be tracked as a commit, means people can make comments on it, means you have a common format for all commits, be they bugfixes or new features, and so on. No, I don't really like it either, but it makes a lot of sense.
Well the University obviously hasn't looked very hard. Following the standard Sun method, there's the 'commercial' product, and an Open Source 'project' standing behind it. The Grid Engine Project does, of course, have downloadable and browsable source code under the SISL.
What more could one want? :-)
Um... I've seen this advertised/discussed in exactly 3 places now: the BBC (yes, the British Broadcasting Corporation), the GLLUG mailing list (that's the Greater London LUG) and here. Of them, I would only consider the BBC one to be an 'official' announcement and they are a British corporation, aiming at a British audience, paid for by the British tax-payer.
The amount of content on this site which is only available or in any way relevent to residents of the US is phenomenal. And that's largely okay, since this is effectively a US site. But you and others who are complaining that this is only available in the UK are only seeing a small example of what we see all the time.
In a more practical sense, I can think of at least three major reasons for the limitation:
You mean something like this?.
Well, maybe... but on my systems (x86 and UltraSPARC), it looks like 32 bits to me... so that's either one word or half a word.
Sorry - had to do that :-)
The point, of course, is that when you post on the lkml saying "Wah wah my kernel's dead", they can come back and say "Sorry - we can't fix that because you're running code in your kernel which we don't have access to". Or possibly something less polite :-) But anyway, that's why the taint flag exists.
Except that it apparently contravenes naming rules. :-(
I've been playing with the same thing for my iPAQ for a while - effectively the same hardware... Any chance of posting your script (or at least your settings) here, or directly to me by e-mail? Much appreciated :-)
So tell me, what do I need in which of the various config files - I'm talking system-wide, on a real multi-user system with lots of virtual domains - to get SpamAssissin run with per-user settings while mail is delivered. It should hopefully go without saying that changing individual .qmail files is unacceptable, since there are already over 100 of them on the system.
I do have the QMAILQUEUE patch applied... To be honest - if you've got all this working, I'd really appreciate it if you'd drop me a line (I'd mail you, but you've not published your address) and let me know in detail what you had to do to get this stuff working...
Answer me this then - how do I get all mail going through my qmail system (not setup by me, but I'm one of the admins) to go through SpamAssassin, but with per-user settings - i.e. after the decision has been made on who to deliver the mail to - without losing the ability to use .qmail files? Oh, and ideally without lots and lots more patching - there's a lot to be said for a stable system, but it's a real problem when the author doesn't seem to be planning any more releases, but the license forbids people from distributing patched releases...
Or to put it another way: qmail may be better for security, but I've had a lot of trouble working out how to hell to administer it, since it seems to ignore most of the tradition UNIX rules on 'how stuff works' in favour of newer, cooler, but random-seeming rules...
Bram Moolenaar, the author/maintainer of the amazing vim visited a school/community center/development center in Uganda a few years back, and when he returned to Europe, he, along with others, setup a charity in the Netherlands to support the center. Those who use and enjoy vim (and those who don't!) "are encouraged to make a donation for needy children in Uganda." Go to the International Child Care Fund and make a donation, or at least click through their Amazon affiliation links next time you buy something from there. That way, it doesn't even cost you anything...
Wouldn't it be nice to Slashdot a charity with donations? :-)
Wouldn't you know it... I had mod points until a couple of hours ago. These are exactly the same points that I make to 'but isn't a TiVo just a VCR with a hard drive?' people. Ain't TiVo grand? :-)
What or who determines the "evilness" or "goodness" of the packet? If a security admin or OS can determine or flag bits as good, what keeps the hacker from spoofing this process by setting the bit to "good"? Does the bit change based on behavior? Or maybe a database with signatures of "bad" bits?
(name deleted)
Microsoft Corporation
Not to worry, good sir - there is a simple and easy answer to your question. All Microsoft software and systems should automatically set the bit to evil! On the off-chance of the packet passing through a clean system, the bit could be set to good, but all data originating from a Microsoft system are, by definition, evil.
HTH, HAND...
I actually use mplayer as my music player of choice now. I like the keyboard control, the doesn't-need-X-ness, the choice of output method (I use esd for local streaming - I know it sucks, but it works) and the support for many codecs... :-)
Oh, and I like the developers' style...
UNIX and Unix aren't the same thing :-) Unix is a style and/or a family of operating systems, including the commercial Unixes, the BSDs and (at least possibly) the Linuxes. UNIX is a trademark and a brand name, owned by the Open Group, and operating systems which pass the branding process - in effect, which are provably compatible with the published POSIX/Unix standards - are granted the right to use the brand. So NT with the right layered stuff may be UNIX, but it certainly isn't Unix, while Linux is Unix, but no Linux distro (and it would have to be a distro) is UNIX.
At least, that's how I see things :-)