Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re: Ah yes the secret to simplicity (Score 1) 751

For instance, often systemctl reports a daemon as failed while it's not, or suddenly decides that it didn't start because of some mysterious arbitrary timeout while the daemon just needs some time to run a maintenance tasks at startup time.

If you don't write your systemd unit files correctly, you can't blame systemd.

Comment Re:Systemd is a bitch (Score 0) 751

but I've been doing sysadmin work as an aside (unavoidable in small companies) more or less continuously for the last 30 years.

So, you've been doing sysadmin work for 30 years and decided that a major change to the init system was something you could just upgrade without a second thought? Without reading some docs? Or taking some time to learn how these things would change how you manage the system? Or learn the failure modes of the boot process and the debug utilities available?

Good thing this wasn't a production server. Sheesh.

Comment Re:I have no problem with systemd (Score 1, Informative) 751

The problem with systemd is that although it does init systems *better* than everything else*, it's also trying to take over half a dozen more responsibilities that are none of its damn business.

The only thing it "takes over" that some people seem to take exception to is the system log, and it does it for its own purposes. Yes, it can be argued that it would have been better to work with the generic syslog interface, but that just wasn't going to work. They would have had to rewrite large portions of it anyway that would have broken backwards-compatibility, so they just went with their own logging daemon instead, and they did their best to maintain backwards-compatibility by forwarding the log messages to the standard interface. Seems like a pretty reasonable decision to me. The other stuff--NFS, DNS, NTP, etc--is optional, and actually NOT recommended for general use. The standard system utilities are used unless you explicitly override them.

Comment Re:I have no problem with systemd (Score 1) 751

systemd fails silently if something is wrong in /etc/fstab. It just doesn't finish booting. Which is moderately annoying if you have access to the system console and you can guess that an unchanged /etc/fstab from before systemd that worked for a while with systemd is now suddenly toxic

It retries for a bit, but it DOES eventually fail and kick you out to a recovery shell. It just doesn't do it immediately because it assumes that the device may just need some time to come up.

Thanks to the binary log files you cannot even boot something random and read the logs,

What do you mean "boot something random"? I don't see why a generic recovery disk can't have journalctl installed. How about a Debian install disk?

but at least you aren't missing anything, because nothing pertinent to the error is logged anyway.

Not true at all. If you don't know how to use journalctl, that's on you.

Comment Re:This is what makes PHP so powerful. (Score 1) 94

There are plenty of people using Perl on shared hosts, so it really shouldn't be a problem. As far as modules go, I can't imagine what would be available in a default PHP that wouldn't be provided for Perl on a shared host, but there are plenty of ways to install local modules if need be. Heck, you can even install a full Perl distribution locally and avoid the system Perl entirely, which is something you cannot do with PHP. Also, Perl had CGI::Application (http://search.cpan.org/~markstos/CGI-Application-4.50/lib/CGI/Application.pm) long before PHP had CakePHP or Zend. A decade ago MVC frameworks were the new hotness, and Perl had Catalyst, which was quite comparable to CakePHP.

Comment Re:Perl6, brought to you by PHP (Score 1) 38

Perhaps. I haven't had time to mess around with it yet, but I've been meaning to. The problem is Perl6 is a clean break from Perl5, so it is only useful for new projects. If you are working with legacy code, you have to stick with Perl5. And there are also a ton of useful packages that are not yet available for Perl6.

Also, while Larry did screw around a bit, the delay wasn't entirely his fault. There were a few groups writing competing specs/implementations, and rewriting them, before they finally settled on Larry's spec and the Rakudo implementation.

Comment Re: Am i missing something here? (Score 1) 237

Although giving the root account an invalid shell will also break single user mode and various system functions, possibly even preventing the system from booting.

Are you sure about that? I admit I haven't tried it, but I don't see why it wouldn't work. The only reason to consult /etc/passwd would be to authenticate the root account, which pam_unix treats as disabled if the password is blank. Su and login require a valid shell entry, but AFAIK nothing else does. Sudo doesn't require the root user to have a shell, and neither does init. So it seems like pretty good insurance to me. If, for example, somebody sets nullok in pam.conf allowing the root user to login with a blank password, the invalid shell entry will block it.

You are right that it would break single-user mode, but you can probably fix that by editing your init script.

Comment Re:Am i missing something here? (Score 1) 237

This is incorrect. LOGGING IN AS ROOT is disabled. You can still trivially get to be root from a user account in terminal by typing "sudo su" and pressing enter then entering the USER password when prompted.

Yes, you are correct. What I meant was any login (invoking the standard pam_unix module) to the root account is disabled, which includes "su root". Sudo works because it uses the setuid bit to elevate your permissions without first authenticating the root account. It is a convenient method to allow people to run programs as root without logging in as root, and linux distributions such as Ubuntu have been setting up the userland that way by default for many years. It works pretty well as long as you have a properly configured /etc/sudoers file.

Comment Re:Am i missing something here? (Score 3, Interesting) 237

No, by default the root account is disabled, but it's there.

This smells like a misconfigured PAM. Apple does a lot of weird and non-standard stuff with the *nix user land, so they probably introduced the vulnerability that way. An improperly configured PAM stack can, for example, try a particular auth mechanism a preconfigured number of times before moving to the next auth mechanism. That fallback mechanism could be the Apple directory service, which doesn't handle the root user and leaves it to the system, but ignores the *nix convention that a passwordless entry in /etc/passwd is a disabled account. Not sure exactly what is happening and don't have a system to test on.

Best workaround is to set the shell of the root user to /bin/false. That will block any attempt to get an interactive login.

Comment Re: He's confusing free speech with Net Neutralit (Score 2) 349

Yeah, and like you just said, that peering agreement is between level3 and Comcast, not Comcast and Netflix. If Comcast is no longer happy with that agreement, they are free to renegotiate it with level3, which will then likely pass on the additional costs to its customers, including Netflix. They can also throttle the bandwidth coming from level3 to enforce the agreement, which wil adversely affect all of level3's customers, including Netflix. And then level3 can then choose to do something about that, maybe by enforcing bandwidth caps, for example. Netflix can respond to that by paying Comcast to host their CDN, which would be cheaper (maybe) than paying level3's bandwidth cap penalty. Etc etc...

All of these are perfectly fine free market contract adjustments, where the contract service is defined as "connection to the Internet to send X data and receive Y data for Z price." If at any time the terms of the contract are exceeded, or one member of the party wants to change the contract, there is nothing wrong with that. The problem is that Comcast does not have a contract with Netflix and wants to force them into one so that it can make money off of Netflix's successful business. It is quite literally a protection racket ("those are some nice bits you have there...wouldn't want anything to happen to them, eh?"), and that is what net neutrality is meant to stop.

Comment Re:Well... (Score 1) 295

Hate to point out the obvious, but the true problem is Americans being too fucking lazy to maintain their health through diet and exercise. If they simply did this, there would be no reason to be demanding magical pills to fix a preventable problem.

The way I see it, there are three major contributors:
    1) The majority of new development in the US is centered around the automobile. We collectively spend way more time in our cars and our air-conditioned homes and office buildings than ever before. The best way to get people to exercise more is to make it easy and pleasant. Make cities more walkable, create green spaces, make neighborhoods more neighborhood-like (ie: less suburban sprawl and more local amenities and services). Do your kids walk/ride bikes to school, or do you drive them? It is no coincidence that older cities like New York, Boston, DC, etc have better stats with respect to obesity and diabetes occurrence.

    2) Childhood obesity. We learn our primary eating habits as children. Whatever you can do to encourage healthy eating for children, whether that be cooking lessons, less junk food, cucumbers and tomatoes instead of mac n' cheese for breakfast, is improvement. The problem is, if you are addicted to fast food, soda, and cheetos before you are 15 years old, it is really hard to change those habits when it starts catching up to you.

    3) Time to cook/eat proper meals. True fact: not everybody likes to cook and will do that. But, if you can reliably work a 40-hour week, you might actually be able to spend some time eating properly, rather than grabbing the high-salt high-carb heavily processed food so you can quickly eat and run. If you cook your own meals it is cheaper and healthier for you in the long run, but you don't have to cook to be healthy. You just need healthy options available and affordable, but that requires time.

Comment Re: Cars of the future (Score 1) 99

If you're referring to this article,
https://www.caranddriver.com/r...

That's not really what they're saying. They are saying if you can't replace your own brake fluid or cabin air filter, or take it to a Firestone to do it, they will charge you $700 for it, which isn't terribly unlike any other luxury car service. What they don't tell you is how much they spent on oil changes, or transmission fluid, or brake service. Hint: they didn't spend anything on it. So including the savings on gas, that's a good deal less than an ice.

Comment Re:tl;dr (Score 1) 261

For example, with all hype and features, OS/2 would crash on 3rd party hardware.

Windows was definitely not less bad than OS/2 in this regard. The difference was that Windows was cheaper and they had OEM bundling early on, which led to better support from vendors (hardware and software). From there it just snowballed. This is how Microsoft won. They didn't have a technically superior product, they just anticipated the market better and aggressively pushed their software out to as many people as they could reach while simultaneously locking out their competition wherever possible.

Novell, while working great for DOS systems, was unusable for Windows. And their push for IPX was not scaling well for multi-site networks.

Not sure what you mean. NetWare had a client for Windows that worked fine, and NetWare did move eventually move to TCP/IP, albeit a bit late in the game. The problem was that Microsoft was able to vastly undercut them on price, which was a great success for the SMB market. For the large network market, most stayed with Novell (or Unix) for some time, but as WinNT matured it started to take over because of the excellent bundling packages Microsoft offered. I think Novell could have recovered if the company had been better managed. They should have split off the key NetWare services (NDS, NSS, NDPS, etc) from NetWare much earlier to compete with Microsoft offerings. WinNT might have been better for file and print services, but NDS remained superior to AD for quite some time, you just couldn't buy it as a standalone package. GroupWise was waaaay better than Exchange, but it was a lot more expensive and required NetWare.

The office alternatives took a very long while to switch to Windows. By that time all new typesetters were pretty much used to Office.

Agreed. That was the beginning of their downfall. That and, again, price. WordPerfect when it was ported was just too expensive, and bulk discounts were not offered to schools to universities the way they were for Office.

Basically people underestimated Windows. It had flaws, it would get blue screens, connecting to the Internet would crash it. However it was the only consumer OS that was good enough for the right price at the time

edits mine

Slashdot Top Deals

Thufir's a Harkonnen now.

Working...