The zaurus has a serial port in the bottom, and an IR port on the side. You can use either of these to do serial I/O.
When you put the zaurus in the cradle the I/O port on the bottom connects into the cradle. The cradle plugs into the USB port on your computer allowing you do to I/O over USB to the zaurus when it's in the cradle (The zaurus does ethernet over usb for this). The cradle has another I/O port in the back, so you can still plugin serial devices while it's in the cradle.
Re:here are the facts (Qt/Embedded vs. X11)
on
Zaurus 5600 Announced
·
· Score: 3, Interesting
* For the resident set size of Qt/Embedded, we get: qpe process, 6.7Mbytes, embeddedconsole, 3.8Mbytes, addressbook, 3.9Mbytes, etc.
Yes but how much of the RSS is shared? Most of the ram usage you list is probably due to shared libraries that all three apps are using. To work out their memory usage (for simplicities sake ignoring other apps sharing the same libraries) you go (qpe RSS-qpe shared)+(qtmail RSS - qtmail shared) + (console RSS - console shared) + shared ram usage. If you just add up those three apps RSS you get 14.4Mb. Obviously that can't be the way things work cause that would mean just those 3 apps exhaust all the available ram of the SL5000 here.
For instance, running qtmail here it uses 4.2Mb RSS, but 3.6Mb of that is shared! So the amount of extra ram now consumed is 400K.
Looking at the QPE process here it is 6.7Mb RSS and 5Mb shared.
I'm not familiar with the Agenda, what functionality does the window manager provide?
In the case of the Zaurus here, the QPE process gets me a window manager, several on screen keyboards, wireless lan monitor, battery monitor, clock, volume control, application launcher, taskbar, document tab, desktop sync server, and probably more i have forgotten.
I suspect the Agenda 75Kbyte window manager doesn't provide all those features. How much ram is used on the agenda once you start up all the extra processes to provide that funcionality?
Also, there is no KDE flab in Qtopia AFAIK, it's just QT based.
If a lot more people become vegetarians, then you'd need to grow more vegetables. That means you need more pesticides, and possibly some genetic modifications as well.
Actually, if a lot more people become vegetarians, then you'd need to grow less vegetables!
See before you can eat meat, you need to grow plants for the cow to eat. To make enough meat to feed 1 human, the cow eats enough vegetables that could directly have fed 5 humans.
So a vegetarian requires 1/5th the vegetable production that a meat eater does.
more vegetarians == Less vegetables == less fertilisers and pestisides etc != not more
the kernel.src.rpm is the stock kernel.org kernel with the 200+ patches a modern distributor applies to the kernel before deciding it is ready for general use.
When you install a kernel.src.rpm you get the stock kernel and all the patches under/usr/src/RPM. Usefull if you want to play with one of the patches. Not sure what the output of a build is.
The kernel-source.i386.rpm i assume is provided as a convenience. It's got the prepatched kernel source and the actuall.config used the build the kernel.
Come on Nvidia, can't we have an automated driver? Please? Pretty please?
Aside from providing a different download for every distribution on the planet, and for every kernel update for every distribution, which would be a complete nightmare, i think they have made it about as automatic as they can.
Just run "rpm --rebuild nvidia-kernel-xxx.rpm"
As for needing the kernel source, either you are running a custom kernel in which case you already have the source tree from which you built said kernel, or you are running a stock kernel in which case just install the kernel-source-xxx.rpm. Note it is kernel-source-xxx-i386.rpm, not kernel-xxx-src.rpm that you want to install, to get a prepatched preconfigured source tree in/usr/src
There's absolutly no need to configure and compile a kernel before building the nvidia kernel module.
America is rich enough to look after a few overpaid IT workers who lose their job.
Moving these jobs to equally talented humans who were born into poorer nations is a great idea.
Hell, maybe if india gets richer, then it will increase trade with other nations in the region.
Hell, maybe if other nations in the region get an economic boost, from supplyings goods and services to rich indians, they might actually be able to feed their citizens instead of leaving them to die of starvation.
So in conclusion, moving IT jobs offshore is a good thing for humanity.
It has killer package management (Portage! -- what other package manager lets you specify compile-time options?)
Dunno if you've heard of it, but there is a package manager called RPM that lets you set compile time options when you are building from source packages.
Try plugging your 7200RPM 120Gb IDE drive into a 386 era IDE controller and see what sort of performance you get. You'll probably only be able to access 8Gb of its capacity also.
IDE hasn't "just been there" it has been constantly evolving.
"Ironically, SCSI stands for Small Computer Standard Interface, but SCSI is most frequently found in Servers (large, not small computers), in large RAID arrays. And more ironically, the SCSI drives usually used in RAID (Redundant Array of Inexpensive Disks) usually are not that inexpensive at 3x the cost of IDE. "
You have to look at when these terms where invented.
The following definitions applied back then: Small Computer = a computer that did not require an entire building to house it. Inexpensive = cheaper than solid state.
Using KDEs SMB browser you can not browse all the machines on the network
smb:// does not work, it tries to connect to a web site called smb.
You need to know the name of each machine beforehand and do smb://machinename/ to browse the shares.
KDE also has another 'network neigbourhood' protocol lan:// but this is totally specific to KDE and requires that a special server (lisa) be installed on all the machines
I agree though that this can be fixed easily within the existing KDE framework. However i was replying to the second part of the statement "KDE can do everything Windows can do - and much more. " which is totally false.
Slashdot Mirror
The zaurus has a serial port in the bottom, and an IR port on the side. You can use either of these to do serial I/O.
When you put the zaurus in the cradle the I/O port on the bottom connects into the cradle. The cradle plugs into the USB port on your computer allowing you do to I/O over USB to the zaurus when it's in the cradle (The zaurus does ethernet over usb for this). The cradle has another I/O port in the back, so you can still plugin serial devices while it's in the cradle.
* For the resident set size of Qt/Embedded, we get: qpe process, 6.7Mbytes, embeddedconsole, 3.8Mbytes, addressbook, 3.9Mbytes, etc.
Yes but how much of the RSS is shared? Most of the ram usage you list is probably due to shared libraries that all three apps are using. To work out their memory usage (for simplicities sake ignoring other apps sharing the same libraries) you go (qpe RSS-qpe shared)+(qtmail RSS - qtmail shared) + (console RSS - console shared) + shared ram usage. If you just add up those three apps RSS you get 14.4Mb. Obviously that can't be the way things work cause that would mean just those 3 apps exhaust all the available ram of the SL5000 here.
For instance, running qtmail here it uses 4.2Mb RSS, but 3.6Mb of that is shared! So the amount of extra ram now consumed is 400K.
Looking at the QPE process here it is 6.7Mb RSS and 5Mb shared.
I'm not familiar with the Agenda, what functionality does the window manager provide?
In the case of the Zaurus here, the QPE process gets me a window manager, several on screen keyboards, wireless lan monitor, battery monitor, clock, volume control, application launcher, taskbar, document tab, desktop sync server, and probably more i have forgotten.
I suspect the Agenda 75Kbyte window manager doesn't provide all those features. How much ram is used on the agenda once you start up all the extra processes to provide that funcionality?
Also, there is no KDE flab in Qtopia AFAIK, it's just QT based.
95% of 802.11b CF cards work in the zaurus
The zaurus has a backup battery also.
It's keeps the ram chips warm until you can recharge the main battery. I don't think the backup lasts for months though...
Eh, nope. Multisync monitors still have an upper resolution limit.
Or are you saying your 15 inch CRT monitor does do 128000000x1024000000 abeit at 0.0005Hz refresh?
All the monitors i've used just switch off if you try going past their highest resolution.
It's need to be as fast it can, I want to play a 6 hours movie compressed
If battery life is your main concern, then "as slow as it can" seems to be the best approach.
Also, how could I go about getting an ethernet adaptor for one?
You walk into your favourite electronics/computer store and say "Please sell me a CompactFlash ethernet adaptor"
If a lot more people become vegetarians, then you'd need to grow more vegetables. That means you need more pesticides, and possibly some genetic modifications as well.
Actually, if a lot more people become vegetarians, then you'd need to grow less vegetables!
See before you can eat meat, you need to grow plants for the cow to eat. To make enough meat to feed 1 human, the cow eats enough vegetables that could directly have fed 5 humans.
So a vegetarian requires 1/5th the vegetable production that a meat eater does.
more vegetarians == Less vegetables == less fertilisers and pestisides etc != not more
the kernel.src.rpm is the stock kernel.org kernel with the 200+ patches a modern distributor applies to the kernel before deciding it is ready for general use.
/usr/src/RPM. Usefull if you want to play with one of the patches. Not sure what the output of a build is.
.config used the build the kernel.
When you install a kernel.src.rpm you get the stock kernel and all the patches under
The kernel-source.i386.rpm i assume is provided as a convenience. It's got the prepatched kernel source and the actuall
Is it just me, or does everyone here suspect apple is paying OSDN to run OSX stories?
It crapped out after only 186K miles?
That's not much geeze, and for a '90 too. Modern cars should do 240K no worries. My '85 subaru is getting there
Come on Nvidia, can't we have an automated driver? Please? Pretty please?
/usr/src
Aside from providing a different download for every distribution on the planet, and for every kernel update for every distribution, which would be a complete nightmare, i think they have made it about as automatic as they can.
Just run "rpm --rebuild nvidia-kernel-xxx.rpm"
As for needing the kernel source, either you are running a custom kernel in which case you already have the source tree from which you built said kernel, or you are running a stock kernel in which case just install the kernel-source-xxx.rpm.
Note it is kernel-source-xxx-i386.rpm, not kernel-xxx-src.rpm that you want to install, to get a prepatched preconfigured source tree in
There's absolutly no need to configure and compile a kernel before building the nvidia kernel module.
Do they really have 12 executives earning $2M?
Last i heard their CEO received 100 cents renumeration for the year.
America is rich enough to look after a few overpaid IT workers who lose their job.
Moving these jobs to equally talented humans who were born into poorer nations is a great idea.
Hell, maybe if india gets richer, then it will increase trade with other nations in the region.
Hell, maybe if other nations in the region get an economic boost, from supplyings goods and services to rich indians, they might actually be able to feed their citizens instead of leaving them to die of starvation.
So in conclusion, moving IT jobs offshore is a good thing for humanity.
i am an ignorant fool?
He is the one that suggested that Gentoo is the only OS that has a package system that allows you to specify compile time options.
How was my correction ignorant?
It has killer package management (Portage! -- what other package manager lets you specify compile-time options?)
Dunno if you've heard of it, but there is a package manager called RPM that lets you set compile time options when you are building from source packages.
It has ALSA built in.
Compiling your own kernel additions is for experimental stuff, not stuff that has been working for years like ALSA
GonzoJohn is the person that submitted the story not the moderator!
Hemos is the one that posted it to slashdot
IDE also becomes outdated very quickly.
Try plugging your 7200RPM 120Gb IDE drive into a 386 era IDE controller and see what sort of performance you get. You'll probably only be able to access 8Gb of its capacity also.
IDE hasn't "just been there" it has been constantly evolving.
"Ironically, SCSI stands for Small Computer Standard Interface, but SCSI is most frequently found in Servers (large, not small computers), in large RAID arrays. And more ironically, the SCSI drives usually used in RAID (Redundant Array of Inexpensive Disks) usually are not that inexpensive at 3x the cost of IDE. "
You have to look at when these terms where invented.
The following definitions applied back then:
Small Computer = a computer that did not require an entire building to house it.
Inexpensive = cheaper than solid state.
Why not install linux on it instead?
I think you a dreaming if you expect people to run OpenOffice and mozilla on old machines.
Mozilla is just bearable on my K6-200 with 96Mb of ram. OpenOffice just crawls.
As much as i hate to use MS products, on p100 class machines win95+IE5.5+Office95 really is considerably more usable than the linux alternatives.
Newer versions of MS Office might be OK too, i dunno i haven't used windows much for many years.
Mandrake doesn't have perl in it's base either.
It's minimum install is 60Mb.
I am using mandrake 9.0
/tmp/resLisa-dcarter"
When i type rlan:/ i get a dialog that says:
"Could not read
When i type lan:/ it changes to lan://localhost and displays a blank page.
Using KDEs SMB browser you can not browse all the machines on the network
smb:// does not work, it tries to connect to a web site called smb.
You need to know the name of each machine beforehand and do smb://machinename/ to browse the shares.
KDE also has another 'network neigbourhood' protocol lan:// but this is totally specific to KDE and requires that a special server (lisa) be installed on all the machines
I agree though that this can be fixed easily within the existing KDE framework. However i was replying to the second part of the statement "KDE can do everything Windows can do - and much more. " which is totally false.