HN user

akl

133 karma

SRE at Google, former troublemaker at AWS. All opinions written here are my own.

https://akl.io/

Posts1
Comments46
View on HN

I think you're misunderstanding - GNU/Linux is a multi-user OS regardless of if it is run in a kvm/xen/etc container or on bare metal.

Even if only one person (or no persons) ever log in, the machine is capable of running processes under multiple users and it is best practice to maintain this so that all users do not share the same level of privilege.

A move away from having man pages isn't necessarily a thing to be celebrated - a well-written man page is an extremely useful thing.

In the ideal case, you might have a quality man page that provides usage information and links to more detailed documentation (that would include tutorials, implementation info, etc.) on the web somewhere.

Jawbone has a competing product, and even Samsung Galaxy S4's latest phone includes some of the functionality (ie: a pedometer) people look to Fitbit for.

My anecdotal experiences with GS4 vs my Fitbit One shows the Fitbit One to be superior, but I'm more likely to forget my Fitbit than I am to forget my phone.

> Please, if you find an issue like this, be nice. Tell the maintainers privately. Don't post to Reddit, HN, or a public Gist. RubyGems.org is completely volunteer run. No one gets paid to work on it. Thanks for your patience everyone.

It'd probably go a long way if you guys considered making an easily-discoverable security page with information on who to contact, how you prefer that contact to take place and how long they should expect to have to wait to hear back from you.

Actually using Ed 14 years ago

I'm honestly curious - what's a use case for scripting the editing of files that's not better satisfied by using a scripting language? I see the value of Arch's focus on minimalism more than keeping ed around in this case, but I'm happy to be wrong.

If your terminal is broken, there are plenty of ways (reset, stty sane, whatever) to fix that. I'm also not sure why having an extra binary on my system is a good safety guard against a broken keyboard.

The ajax term case is valid I guess, though I'm not sure how common that is. I was in a case like that a year or so ago and ended up using cat and sed to get the thing back on the network.

I can't help but wonder if all of this might have gone away had they even just appeared to take this issue seriously. They didn't even bother to reply to my request for access logs on my account, personally.

Perhaps, but Apple has some extremely friendly replacement policies that I personally have used (busted iBook replaced with a black macbook!) and have heard of others running into. Just the other day there was a reddit thread about this, actually:

http://www.reddit.com/r/apple/comments/eaqm5/its_this_kinda_...

The points about directing people to their store over other stores and minimizing the secondary market are probably the main reasoning behind offering engraving.

It hasn't been well publicized after the original announcement (and isn't prominently placed on their plans page, either) but I've had great success with Cloudkick's free developer plan on my personal virt (which is still down..):

https://www.cloudkick.com/accounts/signup/developer/

CK sent me a text message as soon as my host went down earlier, which gave me time to file the ticket against Linode.

Only caveat - they don't provide a signed RPM, which can cause some administrative hardship for linux users using rpm-based distributions (most of the yum operations require you to add an extra cli option to allow working with unsigned rpm's), but it's a minor complaint given that their agent isn't mandatory and doesn't need a lot of updates.

I have IRC to thank for learning a lot about basic client/server communications and networking back in my early teens.

Certainly not the best protocol ever invented, but I have fond memories of figuring out how it worked.

Absolutely! However, I would argue that if you are looking to conserve energy, moving the sshd port is not something that should be at the top of your list. :)

That's good for your mac mini, but not a normal use case for a server running sshd (needing to be quiet, that is). Something that might also work for you would be to limit inbound access from known-trusted ip ranges, as well.

Running sshd on a nonstandard port isn't in itself a bad idea (other than the potential difficulty of logging into the server later if you forget the port or something), but it shouldn't be considered a strong security measure at all.

It may sound bad, but it's a legitimate feeling to have; there's a horrible feeling of stagnation and boredom when you are the technical escalation point for everyone you know - or at least there was for me.