I have to agree about using the command line. I the GNU screen application in an 80x24 terminal. All and I mean _ALL_ work is done in this text based command line terminal (screen provides multiple virtual terminals), with the only exceptions being a GUI browser, which can be any local client web browser and a local realmedia player. It's not taken any real adapting by me as I've been using UNIX for years, email/Usenet/writing/coding/computer support via ssh are all covered by tools that have been around since before there even was windows. Despite the common opinion of this being legacy many of these are in revisions that were updated this month! I can also work extremely quickly using clever shell expansion BNC form {a,b}{1,2}* for file matches, being a wiz at vi etc makes me more proficient than anyone I know where I work who uses a GUI system. Then we get to the clintcher. I'm able to use this system _ANYWHERE_ because _EVERYTHING_ can do a text 80x24 terminal even shite like windows has a telnet application. So from anywhere I can ssh/telnet in reattach to my screen terminal on my desktop and it's the same as being at work. It's hardly any different even if the baud rate is 9,600 baud compared to ADSL/LAN. In fact as I use a Nokia 9210 with an ssh client I can detach from my X session on a Sun at work, use the 9210 on the train in to london, then ssh in from a desktop and always use the same session.
Anyway if you insist on relying on windows GUI kak then you might want to see a linux solution to that: http://www.lpbn.org:8080/ramgen/w3.rm?usehostname
I bought a copy and liked it so much I got one for my dad for his Birthday too. It's really cheap costing me about £6 (6 quid - if that pound symbol doesn't make it). I suspect that the 0.01% of people who don't use Windows to browse the web and visit sites using Qt/WM, don't bother the site owners. Even if every one of us complained it's such a piddly amount of complaints it still won't help. However with crossover allowing linux to see pretty much any site it'll encourage those on x86 systems to use Linux, which in turn might have the affect you're after at a future date.
Now we can use ICQ?
on
New Nokia Phone
·
· Score: 2, Informative
Over 4 years ago Nokia released the 9000 phone with a telnet client. At 9600 baud (which is pretty good) you could sit on a shell account using whatever UNIX clients you wanted to. IRC or a free ICQ client. You could also get VNC for it. so you had 640x200 res 8grayscale connection to any graphical unix client. Since then the 9110 provided 14,400 connectivity, 16greyscale and MUCH smaller size (roughly normal phone size and weight). Then earlier this year Nokia released the 9210 which has a 12bit colour 640x200 display (note that VGA is only 640x480 and that's pretty good). Battery life like 6 hours talk time and 80hours standby. EPOC6 (god knows what the reviewer of the linked article is on about boasting about first use of EPOC?) and 8meg SDRAM.
Yes Nokia arsed up by making it have Word Compatibility instead of a telnet client, but in the last few months a company has written a good ssh client making this (at last) almost as good as the 9110 and basically THE device for admins to use in a pub in a country village. In the UK we have almost 100% coverage all over the place, be it in the middle of fields and lakes or right in the middle of a City. ICQ? That's **cked up too. It's just a combination of about 5 other 20year old standards, like mixing talk, finger, ping, email, wall/write together.. all things that already existed. Why do I feel like nothing is progressing?
I don't think the PS2 is fast enough to play
"DivX;-)" natively, if the native version is
even finished/useful yet. If you mean in the
same way as 'normal' linux "DivX;-)" support
then the PS2 can't do it as that uses x86 binary
specific code with thunking wrappers. The
PS2 is a MIPS cpu and won't be able to do anything
with these.
The Agenda has a full IR output along with it's
2nd IrDA led that it can use for communication.
This means that you can not only use linux to
control it, it IS linux in the remote you are
using. The screen might get a little too
fingerprinty, but It is capable of working as the
remote for any device.
Yes, I suspect Patrick has been viewing the ftp
logs to wait until the most amount of people had
just downloaded the latest release before going
live. Some kind of humour I guess!
That's why we at the BBC searched for a forum
system based on Usenet. We couldn't find one
so we wrote one. The current main forum system
in use now for the BBC Online forums is backed
by INN, and frontended with mod_perl on apache
I can attach in tin and read threads at ease.
Our Lusers can use a webbrowser for the same.
Slashdot Mirror
coo, it's good for me in the uk it' being nearly 3
Why do people put 9/11? That only makes sense
with a year prepended 2001-09-11 otherwise it's
assumed to be 9th of 11 (November)
I have to agree about using the command line. I the GNU screen application in an 80x24 terminal. All and I mean _ALL_ work is done in this text based command line terminal (screen provides multiple virtual terminals), with the only exceptions being a GUI browser, which can be any local client web browser and a local realmedia player. It's not taken any real adapting by me as I've been using UNIX for years, email/Usenet/writing/coding/computer support via ssh are all covered by tools that have been around since before there even was windows. Despite the common opinion of this being legacy many of these are in revisions that were updated this month! I can also work extremely quickly using clever shell expansion BNC form {a,b}{1,2}* for file matches, being a wiz at vi etc makes me more proficient than anyone I know where I work who uses a GUI system. Then we get to the clintcher. I'm able to use this system _ANYWHERE_ because _EVERYTHING_ can do a text 80x24 terminal even shite like windows has a telnet application. So from anywhere I can ssh/telnet in reattach to my screen terminal on my desktop and it's the same as being at work. It's hardly any different even if the baud rate is 9,600 baud compared to ADSL/LAN. In fact as I use a Nokia 9210 with an ssh client I can detach from my X session on a Sun at work, use the 9210 on the train in to london, then ssh in from a desktop and always use the same session.
Anyway if you insist on relying on windows GUI kak then you might want to see a linux solution to that: http://www.lpbn.org:8080/ramgen/w3.rm?usehostname
I bought a copy and liked it so much I got one for my dad for his Birthday too. It's really cheap costing me about £6 (6 quid - if that pound symbol doesn't make it). I suspect that the 0.01% of people who don't use Windows to browse the web and visit sites using Qt/WM, don't bother the site owners. Even if every one of us complained it's such a piddly amount of complaints it still won't help. However with crossover allowing linux to see pretty much any site it'll encourage those on x86 systems to use Linux, which in turn might have the affect you're after at a future date.
Over 4 years ago Nokia released the 9000 phone with a telnet client. At 9600 baud (which is pretty good) you could sit on a shell account using whatever UNIX clients you wanted to. IRC or a free ICQ client. You could also get VNC for it. so you had 640x200 res 8grayscale connection to any graphical unix client. Since then the 9110 provided 14,400 connectivity, 16greyscale and MUCH smaller size (roughly normal phone size and weight). Then earlier this year Nokia released the 9210 which has a 12bit colour 640x200 display (note that VGA is only 640x480 and that's pretty good). Battery life like 6 hours talk time and 80hours standby. EPOC6 (god knows what the reviewer of the linked article is on about boasting about first use of EPOC?) and 8meg SDRAM.
Yes Nokia arsed up by making it have Word Compatibility instead of a telnet client, but in the last few months a company has written a good ssh client making this (at last) almost as good as the 9110 and basically THE device for admins to use in a pub in a country village. In the UK we have almost 100% coverage all over the place, be it in the middle of fields and lakes or right in the middle of a City. ICQ? That's **cked up too. It's just a combination of about 5 other 20year old standards, like mixing talk, finger, ping, email, wall/write together.. all things that already existed. Why do I feel like nothing is progressing?
Isn't this like the BDSs jail() syscall?
I don't think the PS2 is fast enough to play "DivX ;-)" natively, if the native version is
even finished/useful yet. If you mean in the
same way as 'normal' linux "DivX ;-)" support
then the PS2 can't do it as that uses x86 binary
specific code with thunking wrappers. The
PS2 is a MIPS cpu and won't be able to do anything
with these.
The Agenda has a full IR output along with it's
2nd IrDA led that it can use for communication.
This means that you can not only use linux to
control it, it IS linux in the remote you are
using. The screen might get a little too
fingerprinty, but It is capable of working as the
remote for any device.
Unimpressive, we just turned this box off shortly after recording it's uptime, because the hardware is now obsolete, so it's wasting rackspace!
4:47pm up 1026 days, 21:07, 2 users, load average: 0.01, 0.00, 0.00
Yes, I suspect Patrick has been viewing the ftp logs to wait until the most amount of people had just downloaded the latest release before going live. Some kind of humour I guess!
That's why we at the BBC searched for a forum system based on Usenet. We couldn't find one so we wrote one. The current main forum system in use now for the BBC Online forums is backed by INN, and frontended with mod_perl on apache I can attach in tin and read threads at ease. Our Lusers can use a webbrowser for the same.
Oh yeah, they left it a bit late asking us to encode it, it should be available live streamed and then on-demand on the same .ram
once I set this up.