erm, probably not.. to be honest, I just use the folder view widget cause I prefer it to having icons everywhere:-) I'm pretty sure it used to be like that though.
you can't have both. would the plasma functions go under or over the icons? what happens when you drag an icon onto a plasma widget?
Why don't you just make a full-screen file browser widget?
In Debian they use a 70-persistent-net.rules file to tag interfaces with the same name
Once it's booted, yes. Getting this stuff running in an auto-build via kickstart and suchlike isn't quite as easy. You just want to cable up servers and make $interface "the one in the top left" and not have to wait for the kernel to randomly assign it on the first boot and use trial and error to find it.
To be honest, I'm quite worried about this. Isn't this one of the harbingers of the apocalypse? In other news, the moon went crimson and the river Thames boiled over last night.
Here's some good news.. after winning the 2009 scene.org awards, we have this bloke doing music for us. It's amazing how awards attract talent!
http://www.youtube.com/watch?v=B4iRfUAhA9E
btw.. I learned to type on an Amiga. Those keys have a lot of travel. If you hit the baseboard your finger bounces back ready to hit another. I use one of those ergonimic microsoft split keyboards. I got RSI once. I'm left handed.
I use the mouse at work (switching windows) with my right hand. Then I go home and aim for head-shots with my left hand. It's the mouse, not the keyboard which gives you RSI. Never had it since.
You have to see me type. You're wasting three fingers! Most people complain about the chainsaw noise coming from my keyboard, but, well, I can't demonstrate it on facebook, but I am fast. Anything involving right pinky (i'm left handed) pisses me off
but I also don't need to keep my fingers strictly on the home keys.
I do.. and I be I type faster than you:-). XML was invented by someone who wanted to give me RSI.
Out of interest, which finger do you hit closing curly brace with?. I'm on a UK keyboard here, but I'm pretty sure the american ones are in the same place right by the enter key.
As I say.. experience makes you a faster typist
I'm one of those rare sysadmins who can code.. infact my group won the 2009 scene.org award for best 64k demo of the year:-) I spent ages making it possible to rebuild our dev boxes with a mouse click so that developers can have root on them. if they completely fuck it up i can rebuild it in 10 minutes. This has never happened. Developers aren't as stupid as sysadmins make out. Ok, some are, but they don't mess about with the apache configs. I leave that up to the senior ones.
I keep complaining about the second best sysadmin in our team inlining templates in his puppet code. When I object, he says it's down to "personal taste". When I talk computer science stuff to him he says "i never did all that compsci stuff!". I could lend him some books but he considers that an attribute. I don't tolerate ignorance.
As it happens, Mr willful ignorance doesn't type too fast either. That said, people do complain about the chainsaw noise coming from my keyboard. It's office etiquette not to piss your colleagues off with mental typing:-)
To you're quite right.. adding comments or making a meaningful class hierarchy is a chore unless you have experience where it becomes an almost sub-conscious default brain action, and typing fast is a result of spending a lot of time behind a computer, and experience comes with typing. I'm starting to sway in the direction of "I don't trust a non-fast typist"!
I think it might be the other way round. Typing isn't important for programming (I spent more time thinking than typing), but I do type at an insanely fast speed (ask anyone around me.. they usually complain about the noise:-)). This is just a bi-product of being sat behind a computer for a very long time. No matter how fast you can type, you still have to hit those curly braces with your right pinky and that grinds you straight to a halt! And don't even get me started on the plus sign.
Another thing I'm doing is adding directories to make things a bit easier. I have this directory structure:
classes: class inheritance of machines
modules: reusable modules. No specific data such as IP addresses allowed in here.
roles: contains the nodes. One file per machine rather than having a massive nodes file so different sysadmins don't have SVN clashes with eachother and can work a bit more independently
glue: links classes and modules together with specific data.
So in classes I've got server.pp which is inherited by dev.pp which is inherited by dev-web.pp. This calls glue::system::setup{$hostname: env => dev} to set up resolv.conf, etc. The glue stuff also uses inheritance for location-specific stuff:
class glue::base {}
class glue::location1 inherits base {}
define glue::setup($env) { include $location }
the documentation has improved, but the tutorial doesn't tell you everything you need to know. This is buried in the reference manual, so your first ever attempt to use puppet won't be very good.
Stuff like the inheritance model.. it's documented what it is but could provide better examples of how to use it. Eventually after figuring it out, I had a bit of a rewrite on my hands.
I've been using puppet for 2 years now and gave a talk about it at a conference. A lot of people's puppet configs overuse variables and automation stuff after not thinking the design of the system through.
We've got certain rules, like how all templates are embedded in a custom resource so you know where the variables are coming from. eg.
So $foo always gets passed in. If it was set elsewhere in the config, you would end up reading someone's template and not having a clue where its getting its values from.
To everyone who marked this as flamebait.. I guess the truth hurts. Computer science and "managing complexity" are things that will never occur to someone who thinks perl is anything more than a temporary solution to a big problem which it didn't solve.
o be totally accurate, Puppet has support for managing Ruby gems.
And thus my later comment about how puppet is full of booby traps:-) I've been using puppet for 2 years and stood up to give a talk about it (well, architecture design in general) and I didn't know that! Either way, I've got a script to convert gems into RPMs, so I don't need it.
btw.. one of the wonderful things about automated systems: devs get root. WHAAAAT? yep! less tickets for us, and if they completely screw their server up (this has never happened) I can rebuild it with a mouse click
Better still is the tickets you get actually work. They've already tried the change on their dev box, so when they want an apache change to qa/stage/live, they send you stuff which actually works, rather than "could you try this Rewrite please?" and sending the ticket backwards and forwards until you get something which works. It's bliss.
I believe the "Camel" has a few lines from Larry Wall saying "you don't have to know the whole of perl to use perl". Not the same with puppet.. there's booby traps everywhere. I have dev/qa/stage/live environments, so naturally I was passing this around as $environment
Turns out that $environment is a hard-coded puppet "fact", and now I need to use it. One massive perl -p -i -e coming up!
btw. The puppet tutorial will leave you none the wiser. You have to just spend time with it and use it for practice. How I did it: spent 4 months writing the config, then rm -rf and started all over again:-) Second attempt took 3 weeks.
This is ok on a single machine, but if your entire system of 90+ servers is fully configuration-managed, you can't automate this.
Perl, PEAR, pythonforge, ruby gems and any other suchlike are BANNED:-) I've written a python script to convert pear tarballs into rpms:-)
I trust rpm and that is the only package installer on my systems.
I don't want to start a perl versus python war.. ok, I will., Something that python does right is provide a very complete default library. There is "pythonforge" but I've never used it.
CPAN is what you get when you get every idiot on the internet to dump crap code into a global repository. There's a few gems in there, but the majority sucks. It also spews files all over/usr which confuses your packaging system and any CPAN modules worth packaging are provided by the vendor.
Ruby's claim to be "more object-orientated than python" was written by someone who doesn't like python's indentation. Duck-typing as a very bad idea.
That IS evidence. Needs further investigation. The varroa mite which came from African bees (who have evolved the ability to scratch them off) has not been found in many cases of colony collapse disorder, and has been known to invade the European species of bee for the last 50 years.
Slashdot Mirror
erm, probably not.. to be honest, I just use the folder view widget cause I prefer it to having icons everywhere :-) I'm pretty sure it used to be like that though.
you can't have both. would the plasma functions go under or over the icons? what happens when you drag an icon onto a plasma widget? Why don't you just make a full-screen file browser widget?
Once it's booted, yes. Getting this stuff running in an auto-build via kickstart and suchlike isn't quite as easy. You just want to cable up servers and make $interface "the one in the top left" and not have to wait for the kernel to randomly assign it on the first boot and use trial and error to find it.
To be honest, I'm quite worried about this. Isn't this one of the harbingers of the apocalypse? In other news, the moon went crimson and the river Thames boiled over last night.
well, there's actually a really easy way to tell if your house is haunted:
it isn't.
well, some console FPSs have auto-aim to try to make up for it. Just not all.
Here's some good news.. after winning the 2009 scene.org awards, we have this bloke doing music for us. It's amazing how awards attract talent! http://www.youtube.com/watch?v=B4iRfUAhA9E
btw.. I learned to type on an Amiga. Those keys have a lot of travel. If you hit the baseboard your finger bounces back ready to hit another. I use one of those ergonimic microsoft split keyboards. I got RSI once. I'm left handed.
I use the mouse at work (switching windows) with my right hand. Then I go home and aim for head-shots with my left hand. It's the mouse, not the keyboard which gives you RSI. Never had it since.
You have to see me type. You're wasting three fingers! Most people complain about the chainsaw noise coming from my keyboard, but, well, I can't demonstrate it on facebook, but I am fast. Anything involving right pinky (i'm left handed) pisses me off
:-)
The word "opulent" takes seconds off my life
I do.. and I be I type faster than you :-). XML was invented by someone who wanted to give me RSI.
Out of interest, which finger do you hit closing curly brace with?. I'm on a UK keyboard here, but I'm pretty sure the american ones are in the same place right by the enter key.
As I say.. experience makes you a faster typist :-) I spent ages making it possible to rebuild our dev boxes with a mouse click so that developers can have root on them. if they completely fuck it up i can rebuild it in 10 minutes. This has never happened. Developers aren't as stupid as sysadmins make out. Ok, some are, but they don't mess about with the apache configs. I leave that up to the senior ones.
:-)
I'm one of those rare sysadmins who can code.. infact my group won the 2009 scene.org award for best 64k demo of the year
I keep complaining about the second best sysadmin in our team inlining templates in his puppet code. When I object, he says it's down to "personal taste". When I talk computer science stuff to him he says "i never did all that compsci stuff!". I could lend him some books but he considers that an attribute. I don't tolerate ignorance.
As it happens, Mr willful ignorance doesn't type too fast either. That said, people do complain about the chainsaw noise coming from my keyboard. It's office etiquette not to piss your colleagues off with mental typing
To you're quite right.. adding comments or making a meaningful class hierarchy is a chore unless you have experience where it becomes an almost sub-conscious default brain action, and typing fast is a result of spending a lot of time behind a computer, and experience comes with typing. I'm starting to sway in the direction of "I don't trust a non-fast typist"!
Java likes to use XML a lot. Try typing XML at any reasonable speed without knitting your fingers into a nice warm scarf.
I think it might be the other way round. Typing isn't important for programming (I spent more time thinking than typing), but I do type at an insanely fast speed (ask anyone around me.. they usually complain about the noise :-)). This is just a bi-product of being sat behind a computer for a very long time. No matter how fast you can type, you still have to hit those curly braces with your right pinky and that grinds you straight to a halt! And don't even get me started on the plus sign.
Another thing I'm doing is adding directories to make things a bit easier. I have this directory structure:
classes: class inheritance of machines
modules: reusable modules. No specific data such as IP addresses allowed in here.
roles: contains the nodes. One file per machine rather than having a massive nodes file so different sysadmins don't have SVN clashes with eachother and can work a bit more independently
glue: links classes and modules together with specific data.
So in classes I've got server.pp which is inherited by dev.pp which is inherited by dev-web.pp. This calls glue::system::setup{$hostname: env => dev} to set up resolv.conf, etc. The glue stuff also uses inheritance for location-specific stuff:
class glue::base {}
class glue::location1 inherits base {}
define glue::setup($env) { include $location }
the documentation has improved, but the tutorial doesn't tell you everything you need to know. This is buried in the reference manual, so your first ever attempt to use puppet won't be very good.
Stuff like the inheritance model.. it's documented what it is but could provide better examples of how to use it. Eventually after figuring it out, I had a bit of a rewrite on my hands.
I've been using puppet for 2 years now and gave a talk about it at a conference. A lot of people's puppet configs overuse variables and automation stuff after not thinking the design of the system through.
We've got certain rules, like how all templates are embedded in a custom resource so you know where the variables are coming from. eg.
<%= foo %> # template
gets wrapped in:
define dotemplate($foo) { file "blah": content => template("module/blah") }
So $foo always gets passed in. If it was set elsewhere in the config, you would end up reading someone's template and not having a clue where its getting its values from.
To everyone who marked this as flamebait.. I guess the truth hurts. Computer science and "managing complexity" are things that will never occur to someone who thinks perl is anything more than a temporary solution to a big problem which it didn't solve.
Don't ever get a job in a big corporation. It sounds like politics isn't your thing :-)
hehe.. my original post is now -1 flamebait :-D I guess the truth hurt too many people!
And thus my later comment about how puppet is full of booby traps :-) I've been using puppet for 2 years and stood up to give a talk about it (well, architecture design in general) and I didn't know that! Either way, I've got a script to convert gems into RPMs, so I don't need it.
btw.. one of the wonderful things about automated systems: devs get root. WHAAAAT? yep! less tickets for us, and if they completely screw their server up (this has never happened) I can rebuild it with a mouse click
Better still is the tickets you get actually work. They've already tried the change on their dev box, so when they want an apache change to qa/stage/live, they send you stuff which actually works, rather than "could you try this Rewrite please?" and sending the ticket backwards and forwards until you get something which works. It's bliss.
I believe the "Camel" has a few lines from Larry Wall saying "you don't have to know the whole of perl to use perl". Not the same with puppet.. there's booby traps everywhere. I have dev/qa/stage/live environments, so naturally I was passing this around as $environment
:-) Second attempt took 3 weeks.
Turns out that $environment is a hard-coded puppet "fact", and now I need to use it. One massive perl -p -i -e coming up!
btw. The puppet tutorial will leave you none the wiser. You have to just spend time with it and use it for practice. How I did it: spent 4 months writing the config, then rm -rf and started all over again
This is ok on a single machine, but if your entire system of 90+ servers is fully configuration-managed, you can't automate this. Perl, PEAR, pythonforge, ruby gems and any other suchlike are BANNED :-) I've written a python script to convert pear tarballs into rpms :-)
I trust rpm and that is the only package installer on my systems.
You're right.. you can duck-type in python. The difference is that ruby encourages it like it's a good thing.
I don't want to start a perl versus python war.. ok, I will., Something that python does right is provide a very complete default library. There is "pythonforge" but I've never used it. CPAN is what you get when you get every idiot on the internet to dump crap code into a global repository. There's a few gems in there, but the majority sucks. It also spews files all over /usr which confuses your packaging system and any CPAN modules worth packaging are provided by the vendor.
Ruby's claim to be "more object-orientated than python" was written by someone who doesn't like python's indentation. Duck-typing as a very bad idea.
That IS evidence. Needs further investigation. The varroa mite which came from African bees (who have evolved the ability to scratch them off) has not been found in many cases of colony collapse disorder, and has been known to invade the European species of bee for the last 50 years.