Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
- It breaks expectations of experienced Unix/Linux users. Where somebody was accustomed to interact with the system a certain way, e.g. having console logging and log files available to cat/grep/etc, systemD changes that. Programs should be designed for human usage - if it breaks already established human interfaces, it drives up the learning curve, and that is bad. We are overstressed with too much information as it is.
- Non-deterministic. If reordering the startup daemons breaks the system, systemD is at fault. You're saying that it's my fault for having broken systemD configuration. I want to remind you that a program should help me out, not raise barriers for me. If I write a configuration, test it, verifies that it works, and then two weeks later it refuses to work, nothing changed, this is horrible design - how was I even supposed to know it will break ? When I test a program, get to run through inputs and verify the results, I don't want unexpected surprises with the program changing behaviour without me telling it to do so.
I'm not going into technical merits here. I am talking as a human interacting with a machine - the behaviour of the systemD-driven machine is horrible.
Would you even drive a car that randomly speeds up a bit before breaking when you hit the breaks, because it thought it would get me a bit faster to my destination ? KISS is a principle because experience shows that simpler things work better.
and, I could bet that it will run something like wine, or CrossOver, to have limited support for windows application - it will even be advertised as such: " Runs Microsoft Office** ! ". Google invested quite a bunch in Wine, and the number one of reasons the Linux netbooks are returned is that Win apps are not supported - so it would be an obvious move from the part of Google to embed wine in the OS.
For the interface, it will probably run a modified version of Chrome with hooks added to control the hardware (D-Bus, much like Nokia did with maemo), and will have some kind of AIR environment to support webish application development.
** somewhat poorly, better try this nice online suite here, mmmkay ?
Can you guide me to a proper solution, both hardware and software-wise ? I run Linux, and I could hack together some cron'd scripts to get automated backups, but I don't know what medium would offer long-term storage, while having big capacity; I'd like to know the pictures and videos would last enough in backups for the viewing pleasure of generations to be."
Is there any ready-made device close to what I want, or should I start looking into building my own custom PC ? I already have a MythTV box for personal use, but I find it hard to use and control. The power consumption and noise of a full-blown PC are an issue, so I'd prefer something smaller (like a set-top box) with SSD storage."