The difference is one and half workdays salary of a waiter or about one workday salary for other jobs in the rural area here. These people may have different opinion when you have to recommend them wireless for home.
I do not understand that. Sometimes one wants connectivity from some small mobile device and there has been no replacement yet for N900 - see also some other recent article about it.
Basically nVidia did what was best for their business, and best for their customers that want to get work done.
read as: Good enough for those not doing any own software development and/or bugreporting.
With closed source parts of your system you can never be sure where the rare crash came from. You cannot recompile the driver with safety barriers (_FORTIFY_SOURCE, mudflap, valgrind...), hardware watchpoints trap in binary code you cannot easily verify...
This results in unstable software commonly found on closed source platforms as nobody can provide reliable software there.
So I have to square root the billion pixels first and guess the painting size or guess the parameters of "an average digital camera"... Why they just cannot say the DPI? slashdot is a technical magazine or - ok, it is no longer.
Do you call GPLv3+ gnash plugin an extension or workaround? What is a proprietary Flash player else than an extension? And what 3rd-party player are you talking about?
Using $HOME in CVS since 2001, it works perfectly, it is public: cvs -d:pserver:pserver:@dyn.jankratochvil.net/cvs co nethome
Checking it out across the world on various machines. If I find I miss something on some host, I do `cvs update' by hand. Not a rocket science.
I have only one host I consider secure enough so there is no point in distributed mails.
I was using my Gecko bookmarks in $HOME but I had to create a small script to "normalize" them. Otherwise they contain a lot of useless info (timestamps, whether expanded etc.) making both history diffs useless and conflict merges difficult/impossible.
i686 is now for about 6 years a dead horse. GNU/Linux world keeps i686 ABI compatible, that means:
cdecl calling convention - the stack passed arguments - terribly slow, MS-Windows world is using their stdcall/fastcall mess which is faster but not compatible with former cdecl. x86_64 uses registers passed arguments by default.
PIC - position independent code. GNU/Linux requires all the shared libraries (=that is all the Firefox code) to be position independent which is very expensive on i686 and as it also costs even one register. Vs. MS-Windows relocate libraries at kernel so they do not use PIC. On x86_64 the new PC-relative addressing makes PIC the same cheap as normal code.
64bit data for free - 32bit code had to handle all 64bit values expensively in two registers
Probably other x86_64 arch improvements I forgot about. (guaranteed SSE/SSE2/SSE3/others? I do not remember.)
Other points making x86_64 the only choice at the same time making more favors to F/OSS / GNU/Linux:
address space - Applications today already face the 1GB/2GB limit of i686 32-bit addressing. x86_64 has no such limits in any way. There are no reasons to run F/OSS (GNU/Linux) code in 32-bit mode. Contrary to MS-Windows with everything distributed proprietary where no 64-bit alternatives commonly exist.
Compiler tools development concentrates on x86_64, as proprietary code has more financial investments in the past this advantage whould vanish with x86_64 as F/OSS code has enough financial backing nowadays.
dd can do much more than cat. Just the original post did not use any of the features dd can do more so why to bother with the more complicated syntax of dd in such case.
Use/dev/urandom as/dev/random will immediately exhaust your kernel entropy pool and hangs to get more (or it is at least unusably slow). urandom is more than enough for this purpose.
There are no reports anyone would be even able to restore data after rewriting them with simple/dev/zero. OTOH rewriting by/dev/urandom and/dev/zero costs mostly the same so why to care if/dev/zero is enough.
cat/dev/something >/dev/sda is enough/easier on any Linux kernel, dd had to be used on some old commercial Unices nobody has seen for 30 years now.
> If it was good enough, Linus would roll it into his distribution.
Unfortunately one of the community successes of the Linux kernel is based on Torvald's refusal of any sophisticated code. If he could not understand it most probably 90% of the Linux kernel community also would not understand it. It would make the learning curve for the community developers too steep.
You get more code running by 99% of unqualified developers than with 1% of the qualified ones, also due to the fact those 99% of them enjoys it as they are still learning it.
You cannot write anything in C using just its about 5 commands/statements. You need to use some C system (or other) libraries and these are the compatibility problem of C. It is about those POSIX, SystemV, ANSI, BSD, GNU etc. etc. standards conflicting each other, with incomplete specifications etc. Also you face architectural problems of different word size, endianity etc. (this remains true even for high level languages regarding binary network protocols).
Slashdot Mirror
The difference is one and half workdays salary of a waiter or about one workday salary for other jobs in the rural area here. These people may have different opinion when you have to recommend them wireless for home.
I do not understand that. Sometimes one wants connectivity from some small mobile device and there has been no replacement yet for N900 - see also some other recent article about it.
Nokia N900 cannot do 5GHz. Besides that cheapest 5GHz router is still 3x more expensive than cheapest 2.4GHz router.
And where is it compressed as VP9 WebM? What do they mean with H.264?
That is N9-01. Wikipedia
TFA has it wrong. N9-00 was never released, N900 was. I have/use N900.
http://www.aeromobil.com/
read as: Good enough for those not doing any own software development and/or bugreporting.
With closed source parts of your system you can never be sure where the rare crash came from. You cannot recompile the driver with safety barriers (_FORTIFY_SOURCE, mudflap, valgrind...), hardware watchpoints trap in binary code you cannot easily verify...
This results in unstable software commonly found on closed source platforms as nobody can provide reliable software there.
what needs "public" IPs? What /really/ needs them?
SIP (its STUN support works only with a luck).
Besides any service providing = servers which I run some for local stuff even on my notebook.
So I have to square root the billion pixels first and guess the painting size or guess the parameters of "an average digital camera"... Why they just cannot say the DPI? slashdot is a technical magazine or - ok, it is no longer.
Choose any two GNU packages on your system. That is still more than that one Linux kernel.
That you may get sued (=Fedora forbidden item).
Calling Fabrice Bellard "a French computer programmer"? Is it a joke?
Do you chase web hits? Who cares about Windows, moreover together with Apache httpd?
Do you call GPLv3+ gnash plugin an extension or workaround? What is a proprietary Flash player else than an extension? And what 3rd-party player are you talking about?
slashdot in recent years does not expect you would not run Windows as your host OS (to play with that Linux game as the guest OS).
Android uses *just* Linux. Applications depend primarily on userland libraries which together with the Linux kernel are called as whole GNU/Linux OS.
There are really _three_ different pinouts, all the possibilities have been exercised. :-)
Using $HOME in CVS since 2001, it works perfectly, it is public: :pserver:pserver:@dyn.jankratochvil.net/cvs co nethome
cvs -d
Checking it out across the world on various machines. If I find I miss something on some host, I do `cvs update' by hand. Not a rocket science.
I have only one host I consider secure enough so there is no point in distributed mails.
I was using my Gecko bookmarks in $HOME but I had to create a small script to "normalize" them. Otherwise they contain a lot of useless info (timestamps, whether expanded etc.) making both history diffs useless and conflict merges difficult/impossible.
Other points making x86_64 the only choice at the same time making more favors to F/OSS / GNU/Linux:
dd can do much more than cat. Just the original post did not use any of the features dd can do more so why to bother with the more complicated syntax of dd in such case.
OMG try to run it yourself first because you start throwing your shit around.
# cat /dev/random >/tmp/1 & sleep 10; ls -l /tmp/1 /tmp/1
-rw-r--r-- 1 root root 119 2009-05-15 15:47
(One can also use the pv command etc.)
Unfortunately one of the community successes of the Linux kernel is based on Torvald's refusal of any sophisticated code. If he could not understand it most probably 90% of the Linux kernel community also would not understand it. It would make the learning curve for the community developers too steep.
You get more code running by 99% of unqualified developers than with 1% of the qualified ones, also due to the fact those 99% of them enjoys it as they are still learning it.
You cannot write anything in C using just its about 5 commands/statements.
You need to use some C system (or other) libraries and these are the compatibility problem of C.
It is about those POSIX, SystemV, ANSI, BSD, GNU etc. etc. standards conflicting each other, with incomplete specifications etc. Also you face architectural problems of different word size, endianity etc. (this remains true even for high level languages regarding binary network protocols).