HN user

B5geek

97 karma
Posts1
Comments27
View on HN

I'm going to assume you are a grammar Nazi of the American variety.

thEn is a correct and acceptable spelling in Canada.

###########

As I was typing this up I was looking for references to back up statement. BUT I was wrong. (damn my 4rd grade english teacher!)

I was taught that the two words were grammatically the same it was just a difference in US vs 'British/Canadian' spelling. (i.e. grey vs gray)

So, please ignore my indignant reply. (Which I left in for reference.)

For future versions of myself who will make this mistake again:

THAN = a comparison

Golf balls are smaller THAN bowling balls.

THEN = a statement relating to time.

I went golfing THEN bowling.

http://en.wiktionary.org/wiki/than http://en.wiktionary.org/wiki/then

This is where I really don't understand the concept of trying to force your law/will/idea(ls) on other people.

-Today I posted an image of an apple on my web-page.

-The city in the next town over has decided that images of apples are bad/wrong/evil and has passed a law banning the display of apples.

-The city that I live in gets an angry letter from the other city upset about the portrayal of apples and the wanton disregard for their laws.

Why oh why can't we live in a world where the concept of "If this material is illegal in your country, you shouldn't be looking at it." or "Be aware of laws that pertain to you and respect them or change them if you disagree."

"Profit" is very easy to hide. Income, not so much. The difference is 'net' vs 'gross'.

The horrid nature of current tax law is geared towards lawyers and accountants being creative. The system is geared to reward con-men and punish the honest.

A flat-rate tax system based on income might be more effective but the real danger is the tax-breaks that companies get. I see this all the time with Ford/Chrysler/GM. "We will build a factory in your city/state/county if you give us X-billion in tax breaks."

My thoughts: You want to sell your product don't you? In Canada we had a law called "The AutoPact" [1] which basically said that for every 3 cars that you sell in Canada, 1 must be built here.

Corporate welfare will always be a greater hindrance to tax-coffers then personal welfare will ever be.

Why are we paying companies so they have the privilege of taking our money?

[1]http://en.wikipedia.org/wiki/Canada%E2%80%93United_States_Au...

I have used it, but it is too limited. If they had made it a variable scale (i.e. 0-5 stars) that would have made it vastly more practical and functional.

The way that it is presented as a "remember this item" or "note this for later reference", is completely redundant when you consider that everything you archive is "save this for later".

So to actually answer your question: No. I tried and gave up.

Will the KDE people get the message? </troll> Sorry I had to get that out of the way.

In all seriousness, 'Semantic Web' has always felt like a SciFi inspired version of AI intelligence. A concept that sounds cool, but in reality can't ever work.

Take movie ratings & "suggested viewings" for example. Jim, Bob, and Steve all watch the same movie. Jim thinks it's funny because of the physical gags. Bob thinks it's funny because of the dialog & jokes. Steve likes it because the hot new actress is naked. Dave likes the director and cinematography. All 4 guys give it a rating of 4/5.

With this one data point Streaming-movie-place.com cannot ever 'guess' what to suggest to these guys to offer more movies for them to watch. The hope is that once these guys start watching and rating other films a pattern will emerge. That pattern can then be marketed and offer valid suggestions.

BUT reality is too different. We like different things for different reasons, and no algorithm can ever get it 100% right. How many of you have a Netflix queue of things that you want to see, but the suggested movies are full of crappy suggestions? most or all of us I bet.

Which brings me back to my point; it's a sci-fi illusion. It can never exist in real life. Humans are too damn fickle. (Which brings me back to KDE; I wish they would give up on neopunk/symantic desktop crap. it's bloated, slows the system down and offers nothing in return. Or I am just using it wrong.) </rant>

I must be in the minority (based on the comments that I have read), but I hate it. The other day the PHB announces to the office: We are going to use Slack and move away from IM, Skype, etc. So I signed up. What I don't like: -you need to keep a a tab open all the time,

-you need to keep an eye on that tab in case something comes up,

-the 'notifications' don't work all the time (Archlinux + Firefox)

It's like somebody took all the bad qualities of IRC, and shoehorned it into a web-page and all the horror that brings. The features that I don't understand:

search-able logging of messages. Email and/or Pidgin already does that.

Group messages: Email already does that.

Transferring of files: Email and/or corporate LAN shares already do that.

But it does add the necessity of stopping my workflow every 5-10 minutes so I can check to see if there are any messages that _might_ apply to me.

The quicker it can be killed with fire the happier I will be. Or am I missing the point? curmudgeonly - check

beard - check

Unix admin - check

Perhaps there is no hope for me. Next thing you know people will want to take pictures with their cellphones! =)

This is amazing, thank-you. I would love to see the addition/option of adding static geometric shapes. In other words this would make for an awesome wind-tunnel simulator.

I don't think I am your target audience, but I will respond just so you have at least one data-point.

I don't use gestures. Ever. For anything (except unlocking my phone, which I am stuck with).

Opera 'introduced' mouse-gestures a long time ago, and like all other attempts I have tried; I cannot understand the point. I don't think that waving my hand/mouse/fingers around like a spell-caster writing runes in the air is ever efficient. There is far too many chances at misinterpretation, and it obscures the target action. Give me buttons. on/off-yes/no simple binary choices that give exact feedback. Need something more analog (i.e. volume slider) let me input a number.

Why systemd? 12 years ago

<quote>systemd was really designed with servers in mind, and really does bring a lot to the table for server admins.</quote>

Which is totally ironic too in that the server-admins hate it. (speaking just for myself here=) )

I am a sysadmin of a medium sized data-center. I am in charge of 100-150 servers at any given point. None of the changes that systemd 'fixes' benefit me or my systems. Boot times? What's the point when it takes 10-minutes for the drive-arrays to spin-up? Logging? I pray a system never dies and I have to access those rotten binary log-files from a live-cd. Network changes/configuration? Nope, every server is configured with static network configs. Power Management? Ha! That's funny. Downtime in minutes costs more then electricity does in a a month.

I could go on. But there is one major caveat: As a laptop user, systemd is fantastic.

As my Debian servers need to and/or get updated and start requiring systemd then I will just migrate them to OpenBSD. This process has already begun.

Systemd is changing things for the wrong group of people. Mobile/Desktop users have alot of wiggle room and areas that need improvement. Server admins need stability; in software, hardware, (script) syntaxes, and interfaces. Users need everything that systemd offers.

I will concede that systemd might be a good fit with Docker, and I am looking into that too; but I guarantee you it will be on it's own box and not homogeneous with the rest of my network.

My small datacenter results mimic BackBlaze too. Dead/dying seagates all over the place. So I notified management that we will only be purchasing Hitachi drives from now on. I have a BackBlaze server that I recently converted to FreeBSD & ZFS. I love the drive-density that Backblaze offers but I HATE the lack of physical notification when a drive dies.

Most ofther file-servers have a front-facing drive caddy, that usually has LEDs on the front to indicate disk access or errors. This is great because you can walk into the datacenter, and SEE which disk has failed. With the backBlaze system you can get /dev/DriveID but not know where in the array that particular disk is.

I will second this recommendation. I was about 1/3 of the way through the book before I realized it was a 'historical' book and not a fiction.

I have in the many years since I read this one, become quite the fan of all his works.

A nice simple test that I like to give as a first-wave elimination:

Have a computer setup and running (all properly configured). Pull the network cable out of the jack a little bit (so it looks like it's plugged in but isn't). Ask the person being interviewed to show me an IP being used by microsoft or google. (so ping/dig/nslookup/etc)

Let the person know that (a) the computer is in working condition (i.e. no drivers are missing) (b) the network works (i.e cables are good, switch is good, DHCP is enabled, etc.) (c) tell them that this is a test to determine their troubleshooting skills

It is always disappointing to see how few ever open a term/cmd window (depending on the OS). 90% of participants just try to open a web-browser and type in "what is the IP address of google"

I am a Sysadmin. The only advice I can think of is this:

Just build stuff.

Make use of virtualization and just start building systems. There is more then one 'role' a sysadmin will play and in some areas each specialty could be its own job.

i.e. A Windows/Active Directory admin vs an Exchange Admin.

Most good admins will know how to do a bunch of various duties, setup a Samba server; building a ZFS array; install a printer driver; configure a company Wiki and all the maintenance needed to maintain these systems.

And learn how to automate 90% of your tasks.

It's your choice if you want to be picky. If you want to only work on Linux systems, or to be more anal; if you only want to work on Debian servers, don't be surprised if it's harder to get a job. Spread yourself out and learn to be a Jack-of-all-trades. I prefer working with linux, but I jump up and resolve Windows headaches for my co-workers because that annoying 10% of the job makes me more attractive to my boss then the neckbeard who is a distro snob and refuses to touch anything except OpenBSD.

Build systems to do one job. One DHCP server, one DNS server, one file server. Then start combining them and optimizing them. break them and then fix them. There are a million 'gotcha's that only show up when you start working with the systems and you never see in youtube videos.

As far as finding work; either 'exaggerate' about some of your experience while contracting, or start working help-desk and get your foot in the door.

Your resume will get you an interview, your real skills will get you the job.

I get Y-combinators' roots and purpose, but blatant advertising on HN is annoying and off-putting.

And this example is vastly different then the "Hey look at the cool thing I made! p.s. I am selling it too."

While all the hard-core programmers and coders around me use vim all the time they ridicule me for using nano.

I'm an admin not a coder, so I usually just edit conf files and firewall rules. I do spend all day at the cli and do write scripts as needed but I haven't found the need to learn vim.

Use what works best for you.