Comment Re:Just bite the bullet (Score 1) 111
Call the police every time as well as your bank.
Duh.
Call the police every time as well as your bank.
Duh.
Come on up to Canada, we're all chip&pin ready and mostly tap&pay as well.
Why would you want to run an insecure OS like XP instead of an easily secured one like Unixware or PCDOS?
Being pretty doesn't make it an upgrade.
Yes, they've robbed the users of their hardware from the ability to use self-compiled BSD on *that* hardware in *that* way because any changes made by Apple are secret and the user is stuck not having them except in compiled form.
When a user has a problem with the OS they're robbed of the ability to fix it themselves by looking at the source code that would've otherwise been available and they're robbed of the ability to expand the abilities of the system without Apple's consent as well.
Funny, I'm pretty sure you just made a pun.
Yes. He endorses workers, users, and owners all having equal rights to their means of production. Ownership is still held by the Copyright holder of free software, and that person allows others certain rights. There is no communism here.
The problem is that you can never assure yourself that closed source software is secure. You can trust or insure but you can't assure.
Assurance requires access to the source code.
Any user can change their own password without root. Just fyi.
SUID? Which programs are running setuid by default on a Linux box? Most Linux systems also ship by default with SELinux enabled.
My only complaint on a modern Linux distro is that SSHD often allows remote root logins by default.
Its just miseducation on your part to think that OpenSSL is part of Linux. It may ship with a given Linux distribution, or it may not. Its a library used by third party software, some of which may or may not be part of the problem.
Most vulnerable systems have disabled SELinux, disabled other security features and are running fast and loose with their user permissions.
The source has nothing to do with it, but yes, any one unpatched OS can be at risk just like any other
I'm quite certain with a properly configured SELinux configuration even unpatched Apache would survive however.
Google supports his argument. "systemd sucks" has over 35 thousand results right now.
He wrote another blog post, another in a long line of blog posts by people who are annoyed by or don't want or actually hate systemd for one reason or another. Ignoring them all doesn't make it not true -- there are a lot of users who are unhappy with systemd.
More importantly, there are a *lot* of users who wouldn't know the difference and who haven't had a reason to notice the change at all. Those people can't be cited as 'supporters' because they couldn't care less if its rc.d or systemd or djb's svscan.
I'm still installing CentOS 5 on almost all systems right now, I can't believe the mess that systemd causes me in testing...
Imagine if you ran "cp -ar stuff
The default behaviour should be to return whether the service started or not when you start a service.
No you don't, you just need to install the X application you want to run and the xorg-x11-xauth package so you can run 'ssh -X remote command-name'
That's all.
Your GUI point aside though, I agree that systemd is way too big for a PID 1 process.
Business is a good game -- lots of competition and minimum of rules. You keep score with money. -- Nolan Bushnell, founder of Atari