That is difficult to believe. All modern *nix systems use a journaling file system and we don't "lose" files. Most *nix users also backup data.
Now if it were Micro$oft then I'd believe it...
When Micro$oft abandoned Win98 it had over 7,000 recognized, unfixed, bugs.
No modern journaling file system "loses" files. Even earlier file systems didn't "lose" files due to RAM. All operating systems since Win95 have used virtual memory where files were swapped to disk if more RAM is needed.
Agreed. The only "manufacturer" who has faulty operating systems is Micro $oft. If you run any flavor of Windows then you should expect corrupted files, flawed operation, poor support, and to be regularly obsoleted without option.
Owning a computer carries the same responsibilities as any appliance, tool or vehicle. If you don't educate yourself on proper selection and operation then it's solely your fault. Don't bitch when Bill Gates abortions f*ck up your life.
Hell, yes... Their little venture into the clouds with Danger managed to lose most of the data for 1 million T-Mobile subscribers. It wasn't exactly a good advertisement for cloud computing.
Modern offices do not "word process" any longer but do desktop publishing. 8-bits is sufficient for rudimentary tasks and machine control but not for serious applications. Just try doing a least squared matrix inversion with 8-bit words...
Not true. .ods is the default OpenOffice document format and meets a IEEE standard. Micro$oft is trying to develop and have their own open "standard" accepted.
OpenOffice not only uses an open document format but is written largely in Python or Perl I seem to remember. That explains both OO's lethargy and robustness. M$ products are written largely in C and C++ which also explains it's crappy history.
No big deal on any system I administer. In fact _I_ am the only user who can do that. I have copies of all my various passwords and the passwords of all my users on a 4096-bit RSA encrypted thumbdrive as well as copies of all password files on their respective hard drives.
Any sysop of moderate intelligence keeps that, and much more, redundantly backed up.
Only to idiots. Idiots get what they deserve.
For example on most machines I have an hourly cron event rsyncing most users /home/ directories over ssh _behind_ the firewall. In fact no machine on our network is open or has a usable port in its traditional location. Ports 22, 25, 80, and a few others are in random locations even behind the firewall.
I've never been hacked and get sniffed about every 7.5 seconds. My situation isn't unique either, only one example of simple precautions.
You mean "kernel"? There are protections there too and you'd have to hack/corrupt the kernel to f*ck that up. You do not need what is commonly called an "operating system" to speak with the file system. You can boot directly into the kernel without *nix and talk to the disk directly. Google "grub".
Forth _is_ an operating system. It is also a threaded, meta-compiled, interpretative machine control language. Smalltalk evolved out of Forth but there is no "windows like shell" in forth.
That depends on the Operating System. The most common non-M$ operating system is Linux. If you have access to the keyboard and CD then you can overcome that problem easily.
Boot off the CD, mount the root directory, copy /etc/shadow/ from your backup, unmount, reboot, remove the CD before the reboot and you'll have a a working, secure, system again.
If you don't have a backup then copy /etc/shadow/ from a working system then use that user/root login to gain control and edit the passwords. You can also fabricate a /etc/shadow/ by deleting the root line but a secure linux system doesn't allow root login, you have to use "sudo root".
If you have access to the keyboard then you can break any computer. That's why all my machines have encrypted /home/ directories and shutdown wipes /tmp/.
Much more important than passwords is your home directories. Encrypt them heavily, the overhead is slight. Even on a non-internet connected computer you should encrypt /home/ to keep busybodies out.
I can also take the hard drive and mount it in another box and do the same as well as copy all personal information without password. Unless / home/ is encrypted. Memorize your randomly generated RSA passphrase, do not put it even on paper.
My sister ported forth to an 8080 and was able to write a control kernel for Kit Peak - many years ago naturally.
I had it and was able to use it - it would learn from what you do and did and next time it would still have the ability. Those were interesting days for me late 70's.
Mart> >
That rings a bell. If I remember right there was quite an outcry about M $ pushing a second "standard" when one already exists but that is a standard M$ ploy, just like they tried with Java and a few others. Start with a simple, semi-standard, product then evolve it into a proprietary piece of shit that only they can support.
Heh, an inch. My question would be whether M$ can _write_ .odt/.ods formats that OO can recognize...
I accept without looking but am pleasantly surprised. Any OO would be superior to C.
This is not MicroSoft. Obscurity is just another layer on top of an exceedingly robust operating system. Remember, I'm running OpenBSD on my firewall...
Well, not immdiately but yeah you can scan a series of ports _if_ the firewall permits it. "pf" can be smart enough to recognize a port scan and dynamically filter that ip in real time.
Even if you know the port of ssh, for instance, you still couldn't hack into a protected system. Again, after a few failed pw attempts your ip would be filtered out.
Different genesis. BSD is a direct descendant of Bell Labs UNIX while Linux was a clean room design by Linux Torvalds in order to break the chain of intellectual property rights. "Linux" is only the kernel.
Wrong linux was writen by Linus Torvalds as a hobby.
Hello everybody out there using minix -
I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. This has been brewing since april, and is starting to get ready. I'd like any feedback on things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things).
I've currently ported bash(1.08) and gcc(1.40), and things seem to work. This implies that I'll get something practical within a few months, and I'd like to know what features most people would want. Any suggestions are welcome, but I won't promise I'll implement them :-)
PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.