cmhamill's comments

You're probably correct, though subjectively I didn't start feeling like something was amiss until Mac OS 9, perhaps as early as 8.5.

I think OS X, as the child of NeXTSTEP and Mac OS, ended up somehow less than the sum of its parts.

I honestly can't tell if this is profound satire or contentless nonsense. Without knowing, it's impossible to discuss this.

I actually think the DNS binary protocol is a rather well-designed one, but others might disagree.

I'm partial to including the `www` prefix, but most of the reasons are aesthetic and not technical.

The summaries for each side:

http://www.yes-www.org

http://no-www.org

This would help immensely with converting our development process to use Docker. My hub ID is cmhamill.

The issue here is actually bricking the device. It's not your standard "do we let people hang themselves or limit the user's capabilities" debate.

A filesystem is a perfectly reasonable way to implement access to the EFI vars.

I assume folks using a smartcard for their everyday encryption are safe from these kinds of attack?

Can anyone confirm that?

If you're expecting trouble from state actors, then yes, you may want to consider other options.

kernelconcepts.de sells them and ships to the U.S.

Location: Connecticut, intent to relocate to Los Angeles in the near-ish future

Remote: yes (or LA)

Willing to relocate: yes if to LA, no otherwise Technologies: Unix administration, Salt Stack, Ansible, Apache, Nginx, Python, Perl, Ruby, Go, SQL, C, etc. I'm a sysadmin, so my job, in principle, is to know everything, and I take that seriously. If I don't know it now, I'll learn it. That's what I'm for.

Résumé/CV: http://resume.cmhamill.org/ (PDF: http://resume.cmhamill.org/resume.pdf)

Email: [email protected]

I can be your jack-of-all-trades.

So, the question that jumps to mind reading this is:

At what point do we acknowledge that we're re-inventing Plan 9 poorly?

I don't mean to be glib (well, maybe a little), but all of this (with some exceptions — zones and jails, mainly) feels incredibly hacked-together.

Perhaps someone paying more attention could tell me if, say, the folks working on the Linux kernel are learning the lessons from Plan 9? kernfs seems promising, at a glance, but I haven't really looked into it.

For some definition of "his basic thesis" meaning "radical misrepresentation of his basic thesis," sure.

Whether you like the ideology behind the forces at work in the American South or not, the real effect of these policies is to make the lives of the poorest and most marginalized people in these states worse. In the American South, it just so happens that this means black folks.

I don't know what you'd want out of an article on this issue, but I sure hope it wouldn't be a false rendering of the realities of the situation in the hopes of pandering to some sense of feel-good political ecumenicalism.

Does anyone have any idea why Linux has a distinction between /dev/random and /dev/urandom?

Legacy adherence to some defunct interface? Ignorance on the part of kernel devs (seems unlikely)?

Not entirely on-topic, but the mention of the various language "stacks" at the beginning of the article reminded me of something I've been wondering.

Why does the de facto standard for web apps in Go-land seem to be using the built-in HTTP server provided by net/http, or otherwise having the program server as its own HTTP server?

Most other languages seem to have converged on FastCGI or some similar model ({W,P}SGI, Rack, etc.).

It irks me a bit because I don't understand why you'd want to do it this way; it seems preferable to have a dedicated HTTP server in pretty much every way I can think of.

Does anyone have any insight there?

To put it more bluntly: I think it's reasonable to argue that Wikipedia is the single most important product of the Internet to date.

Would you folks ever consider releasing a non-omnibus package? I'm averse to packages which include their own dependencies, but have developers who would benefit greatly from GitLab otherwise.

Wesleyan has no hard-and-fast gen ed requirements, which makes this easier to pull off for students.

Some majors do require them for Honors, though.

I asserted nothing of the sort.

Some very strange reactions in this thread. The idea that this somehow validates the notion that Eich's politics don't affect Mozilla as a workplace seems particularly bizarre, to me.

My read on this is that there are employees at Mozilla who feel strongly enough about this to speak publicly, and the most likely reason is because they believe that Eich as CEO will affect their workplace.

My knee-jerk inclination to this post is to yell, "oh holy hell, yes!"

That said, and as others in this thread have noted, there are actually two use cases that need to be satisfied.

1. Here, you've got a base system, and you want to install some piece of software in order to use it. You want this to be guaranteed, for some reasonable definition of "guaranteed," to work with your existing base system.

2. Here, you want to install packages within a segregated environment, and you want those packages to work with any packages previously installed in said environment. You're probably attempting to do something like recreating your deployment environment locally.

It strikes me that there are only two issues preventing the latter from being subsumed by the former.

1. Not all package management systems provide a means to have multiple versions of a package/runtime/what-have-you installed at the same time. Often, this capability is there , but packages need to be specially crafted (unique names, etc.) for it to work. See Debian's various Ruby and Python runtime packages for example.

2. Not all package managers provide a way to install a set of specific package versions in a contained environment which is segregated and requires intention to enter.

(Note that I'm ignoring the "there are different package formats" issue; I don't think is in practice a huge barrier, and the package maintainers should be involved anyway.)

If we could get RPM and YUM to provide those services, then we could remove the vast majority of this duplication.

Alternatively, if we all agreed that developers should just use Linux containers as development environments, then all we'd need is upstream to use native OS packages (which is, really folks, not very hard).

Can we do that pretty please??