Oh My God! This will make Perl code look really crazy. I'm managing 15 kSLOC Perl SW an 50 kSLOC PHP SW. Making changes to Perl code is at least twice as hard and requires much more time to re-study the code (and that both SW are written by myself with trying to keep the "code style" like no $tmp vars etc.).
Perl is usefull for 1-100 lines "maintenance" scripts but writting some reall SW in it just sucks...
Connection - how about reverse it? Print PCB on board/paper with pre-installed connectors? And PCB itself is also nothing - you need to mount SMT resistors, CPUs etc.
Depends... my experiences are if there are "few bad blocks" that means that there is something VERY bad with HDD and it should be IMMEDIATLY removed. Or are you talking about S.M.A.R.T. value "Reallocated event count"?
Jesus christ - if 2 disks TOTALY fails, your TOTALY done. But most (90%) of the time fails ONLY several blocks (few kB) and if it's not something critical (superblock etc.) you can recover your data EXCEPT the files which are locaten on failed blocks. And if disk TOTALY fails, usually it's only the electronic board, which you can "borrow" from same-but-working drive, recover you data and trash the bad disk.
As someone who built and installed ~400 systems with about 50 TB of storage capacity and ALL on Linux SW RAID5 I can only recommend it. I have bad experiences with HW RAID - when 2 or more disks fails, you can't get your data. Linux SW RAID is easy (OK, not SO easy) to be convinced to recover most of your data except the really bad ones. Also performance is really superb (with P4/Xeon/Opteron CPUs it's much higher then any HW IDE RAID can do).
Sorry, but using P266 you shouldn't expect any good "interactivity" using OOo. Use some other tools (which are "profiled" as single usage small footprint - like Gnumeric, Abiword etc.)
Never put RMS & Alan Cox & Linus in the very same car/plane or even building (just for sure;-))). If you are paranoid it doesn't mean they aren't after you.
Just notice that if you look "close enough", nothing is "special new" (e.g. relativity theory, iMac, Linux etc. etc.) - evolution is done in small steps. What I found great on this is the vision - let's throw away thin/fat client idea and just think about separating "operating system" and "user data".
Wow - this is really HUGE project. I mean - it spreads from kernel, through init scritps, through X managers & enviroments to easy to use administration tools. If they suceed this could be really "Linux killer application".
And please all the "NFS root is enough" posts - read the article!
Can somebody explain me WHY should we put things like database, indexing/previewing etc. into the filesystem => KERNEL SPACE!!!! What advantage does it bring?
Any good (XFS, JFS, ext3) filesystem now has nice feature called Extended Attributes which is intented for STORING such a data (like previews etc.). And using user-space server it's much more easier to add plug-ins for various file-formats, "search" plugins etc.
Slashdot Mirror
Oh My God! This will make Perl code look really crazy. I'm managing 15 kSLOC Perl SW an 50 kSLOC PHP SW. Making changes to Perl code is at least twice as hard and requires much more time to re-study the code (and that both SW are written by myself with trying to keep the "code style" like no $tmp vars etc.).
Perl is usefull for 1-100 lines "maintenance" scripts but writting some reall SW in it just sucks...
Connection - how about reverse it? Print PCB on board/paper with pre-installed connectors? And PCB itself is also nothing - you need to mount SMT resistors, CPUs etc.
Depends... my experiences are if there are "few bad blocks" that means that there is something VERY bad with HDD and it should be IMMEDIATLY removed. Or are you talking about S.M.A.R.T. value "Reallocated event count"?
SW RAID howto.
Jesus christ - if 2 disks TOTALY fails, your TOTALY done. But most (90%) of the time fails ONLY several blocks (few kB) and if it's not something critical (superblock etc.) you can recover your data EXCEPT the files which are locaten on failed blocks. And if disk TOTALY fails, usually it's only the electronic board, which you can "borrow" from same-but-working drive, recover you data and trash the bad disk.
As someone who built and installed ~400 systems with about 50 TB of storage capacity and ALL on Linux SW RAID5 I can only recommend it. I have bad experiences with HW RAID - when 2 or more disks fails, you can't get your data. Linux SW RAID is easy (OK, not SO easy) to be convinced to recover most of your data except the really bad ones. Also performance is really superb (with P4/Xeon/Opteron CPUs it's much higher then any HW IDE RAID can do).
One single word - "politics".
When you have to buy 100$ computer you aren't expect to have any really-sensitive data on it...
This is very easy to defeat! Just imagine - imitate "master" behaviour and then (after recognized by opponent) just abuse it...
What's "lot of logistical factors" when all you need it Torrent file? .-)
Sorry, but using P266 you shouldn't expect any good "interactivity" using OOo. Use some other tools (which are "profiled" as single usage small footprint - like Gnumeric, Abiword etc.)
I just looked out from window and sky is black ;-)
...in other news was sky reported to be mostly blue and sun is expected to rise tommorow morning.
Never put RMS & Alan Cox & Linus in the very same car/plane or even building (just for sure ;-))). If you are paranoid it doesn't mean they aren't after you.
P.S.
Deepest condolences...
Who cares about cracking some slow print server when there are myriads of unsecured Win98 ADSL computers ;-)
Just notice that if you look "close enough", nothing is "special new" (e.g. relativity theory, iMac, Linux etc. etc.) - evolution is done in small steps. What I found great on this is the vision - let's throw away thin/fat client idea and just think about separating "operating system" and "user data".
Posts like:
NFS read-only & shared root is enough
+
LTSP
+
Thin clients
=> please read the article
Wow - this is really HUGE project. I mean - it spreads from kernel, through init scritps, through X managers & enviroments to easy to use administration tools. If they suceed this could be really "Linux killer application".
And please all the "NFS root is enough" posts - read the article!
Shareware strikes OSS back!
Probably they needed to test it before they launched it to be sure they'll be able to catch it ;-)
Now just imagine a beowulf cluster of... damned!
He doesn't want to be contactable all the time but he wants to be able to contact others at any time.
Am I the only who finds this...hm... selfish? paradox?
1, Manage to transfer your data at 6.63Gbps
2, ???
3, Profit!
Heh :-) I think that XFS is everything you need (incl. ACLs, EAs, guaranteed I/O rate, quatas and it has got 6.5 MB (in 2.6 kernel)...
Can somebody explain me WHY should we put things like database, indexing/previewing etc. into the filesystem => KERNEL SPACE!!!! What advantage does it bring?
Any good (XFS, JFS, ext3) filesystem now has nice feature called Extended Attributes which is intented for STORING such a data (like previews etc.). And using user-space server it's much more easier to add plug-ins for various file-formats, "search" plugins etc.