serve multiple SliMP3s, either in concert or independently.
This sounds interesting. When you say "in concert", do you mean that the music output is perfectly synchronized on each device? So I can have several of these things around the house, and not get nasty echoing effects when I play the same tunes out of all of them at once? I had assumed that the various buffering at different stages along the way would make this impossible.
But then "nobody" is the only user who can log in remotely. Some part of the OpenSSH code needs to run as root so that it can setuid() to the user who is logging in. The privilege separation this article's about minimizes that part of the code.
Since Steve Jobs decided to close source FreeBSD, I don't understand why anyone would carry on following its sorry demise. It seems to me that Linux is the only credible alternative?
We should all keep in mind this simple truth:
America's laser of death is dying. You
don't need to be Kreskin to predict
America's laser of death's future. The hand writing
is on the wall:
America's laser of death faces a bleak future. In fact there won't be any future at all for
America's laser of death because America's laser of death is dying. Things are looking very bad for America's laser of death.
Unfortunately for the community, just as mozilla was becoming usable for everyday use, AOL TW have decided to close the source for the product once again. While this is certainly the best commercial decision they could make, it does leave the free software community with the rather daunting prospect of lacking a credible browser rendering engine. khtml is all very well and good, but I for one am not looking forward to the return to the dark old days of using a desktop which depends forever on proprietary libraries. Unfortunately, it looks like this problem will never be resolved, despite large efforts of persuasion on my part. It seems that some people just won't be told.
Oh dear you seem to have your facts in a terrible muddle. Goodness knows where you are getting this bogus information from, but I think you should consider something of more fundamental importance: Debian is not Free Software. Ever since they announced their intention to go completely closed source, developers have been flocking away in droves. Alas, it is now time to start building a new community-developed distribution that is truly open and not dominated by vested commercial interests.
Unfortunately I can't continue this conversation right now. But I will just say: next time you write an improvised diatribe from a position of total ignorance, you will not be let off the hook so lightly.
Re:apache is dying
on
High-End Apache
·
· Score: -1, Flamebait
It's a shame I suppose. This article is just a nail in the coffin showing that apache unfortunately can't keep up with the big boys. Now that the apache foundation has decided not to release Apache 2.0, I suppose we'll just have to stand aside and watch while IIS relentlessly gains market share at apache's expense. With the current apache codebase going closed-source, we'd better start trying to implement a new free web server.
Andrew Morton is a well known troll on lkml. It's a well known fact that he is always spouting off with ill-informed opinions without anything positive to add in terms of code. Why doesn't this man just step back and let the big boys like
ESR get on with their work?
Listen sweetheart, bang on all you want about the other branches. There's not one debian, but there *is* one stable Debian. The fact is Debian 2.2 was released in August 2000. For the last year and a half there have only been security updates. Debian 3.0 is still not released. A year and a half later. That is too long. I think they can do better.
Oh, and comparing Debian security to OpenBSD's in such a fatuous manner is really daft. There is no project within Debian to audit their code. Debian has comparable security problems to any other linux distribution.
No what I actually did was install Red Hat. That's something I thought I'd never do, but I don't regret it. When debian adopts a sensible release cycle I will come back to it.
The new Debian release manager wants to make the releases more frequent but I really can't see this happening.
For
the next cycle (assuming this freeze actually turns out to be relatively
short and controlled), I think it would be interesting to see if we can
do the same thing again, with a short (2 or 3 month) development cycle,
for a 5 to 7 month release cycle.
It looks like the first part of his plan failed dismally. He sent that mail 7 months ago, and part of it says
My overriding goal for this release was to manage to
get a short, controllable freeze; one that we can get over and done with
in a few months, rather than letting it drag on for seven months with no
end in sight
It would be nice to use Debian again but to be frank why bother when there are such more responsive and up to date distributions?
Oh well, maybe someday I'll figure out the keycodes and write a little hack to make the buttons work.
Use xev to find out the keycodes. Then use xmodmap to give them keysyms (choose names from/usr/X11R6/include/X11/keysymdef.h). There are applications to assign arbitrary commands to keysyms. Some window managers (eg sawfish) have this built in.
Those of you who can see through the usual slashdot editorializing will realise that BT are a veritable innovation machine. Not only did their visionary engineers invent the concept of hyperlinking, their lawyers are not afraid to defend their intellectual property against scoundrels and freeloaders such as Prodigy.
In any case I don't believe you that TBL didn't intend users to see URLs. What did he want them to see, RealNames? Or maybe you're after what's described here as
Another year, another dumb attempt to create a totally new
namespace instead of trying to make more intelligent use of
the existing one... JINI SEARCH, the revolutionary IE
plugin where you "just type the brand, company or product name
directly into the address line of your Internet Explorer
browser and go straight to the specific page
The question remains, can you justify saying "it's the law, get over it" to back up your earlier point. I still assert: Nowhere is there any law which states that domain names must be qualified by a unique legal jurisdiction
I am constantly typing in fully qualified domain names as a user in every application. Whether it's mail, the web, ssh, telnet, rsync, ping, host, nmap blah blah blah. You aren't going to get me to encode a load of extra legal information every time I type a fully qualified domain name. Forget it.
Slashdot Mirror
This sounds interesting. When you say "in concert", do you mean
that the music output is perfectly synchronized on each device?
So I can have several of these things around the house, and not
get nasty echoing effects when I play the same tunes out of all of them at once? I had assumed that the various buffering at different stages along the way would make this impossible.
But then "nobody" is the only user who can log in remotely. Some part of the OpenSSH code needs to run as root so that it can setuid() to the user who is logging in. The privilege separation this article's about minimizes that part of the code.
I think you can still call something illegal if it only breaches civil law. You can't call it criminal, of course.
Apache is dying
I look forward to your reply.
Since Steve Jobs decided to close source FreeBSD, I don't understand why anyone would carry on following its sorry demise. It seems to me that Linux is the only credible alternative?
We should all keep in mind this simple truth: America's laser of death is dying. You don't need to be Kreskin to predict America's laser of death's future. The hand writing is on the wall: America's laser of death faces a bleak future. In fact there won't be any future at all for America's laser of death because America's laser of death is dying. Things are looking very bad for America's laser of death.
Unfortunately for the community, just as mozilla was becoming usable for everyday use, AOL TW have decided to close the source for the product once again. While this is certainly the best commercial decision they could make, it does leave the free software community with the rather daunting prospect of lacking a credible browser rendering engine. khtml is all very well and good, but I for one am not looking forward to the return to the dark old days of using a desktop which depends forever on proprietary libraries. Unfortunately, it looks like this problem will never be resolved, despite large efforts of persuasion on my part. It seems that some people just won't be told.
Oh dear you seem to have your facts in a terrible muddle. Goodness knows where you are getting this bogus information from, but I think you should consider something of more fundamental importance: Debian is not Free Software. Ever since they announced their intention to go completely closed source, developers have been flocking away in droves. Alas, it is now time to start building a new community-developed distribution that is truly open and not dominated by vested commercial interests.
Unfortunately I can't continue this conversation right now. But I will just say: next time you write an improvised diatribe from a position of total ignorance, you will not be let off the hook so lightly.
Apache *is* dying
You might as well face it. Pringle canning is dying.
It's a shame I suppose. This article is just a nail in the coffin showing that apache unfortunately can't keep up with the big boys. Now that the apache foundation has decided not to release Apache 2.0, I suppose we'll just have to stand aside and watch while IIS relentlessly gains market share at apache's expense. With the current apache codebase going closed-source, we'd better start trying to implement a new free web server.
Cheers, tho' it is rather worrying how many people took it so seriously.
Andrew Morton is a well known troll on lkml. It's a well known fact that he is always spouting off with ill-informed opinions without anything positive to add in terms of code. Why doesn't this man just step back and let the big boys like ESR get on with their work?
Sorry, I don't mean responsiveness of the developers to bug reports. I mean the responsiveness of the whole system to advances in software technology.
Oh, and comparing Debian security to OpenBSD's in such a fatuous manner is really daft. There is no project within Debian to audit their code. Debian has comparable security problems to any other linux distribution.
No what I actually did was install Red Hat. That's something I thought I'd never do, but I don't regret it. When debian adopts a sensible release cycle I will come back to it.
Read the whole mail at the list archives
It looks like the first part of his plan failed dismally. He sent that mail 7 months ago, and part of it says
It would be nice to use Debian again but to be frank why bother when there are such more responsive and up to date distributions?
No, I meant Debian 2.2
I'm hoping they're serious about changing to a much shorter development cycle. 2.2 was out of date enough when I installed it over a year ago.
Use xev to find out the keycodes. Then use xmodmap to give them keysyms (choose names from /usr/X11R6/include/X11/keysymdef.h). There are applications to assign arbitrary commands to keysyms. Some window managers (eg sawfish) have this built in.
You misunderstand. The data doesn't need to leave the SCSI bus.
Actually HTTPS is an application protocol. The secure socket is the transport.
Those of you who can see through the usual slashdot editorializing will realise that BT are a veritable innovation machine. Not only did their visionary engineers invent the concept of hyperlinking, their lawyers are not afraid to defend their intellectual property against scoundrels and freeloaders such as Prodigy.
The question remains, can you justify saying "it's the law, get over it" to back up your earlier point. I still assert: Nowhere is there any law which states that domain names must be qualified by a unique legal jurisdiction
I am constantly typing in fully qualified domain names as a user in every application. Whether it's mail, the web, ssh, telnet, rsync, ping, host, nmap blah blah blah. You aren't going to get me to encode a load of extra legal information every time I type a fully qualified domain name. Forget it.