There are more than a few things that AMD besides gaming and over clocking (Intel strong points) that make an AMD a good choice. I don't want to start holy war here but there is not much real gap here 10-5% in my tests at best. The price * power use thing shows AMD is a good choice in many places. Price alone makes me deploy more than a few AMD clusters. Don't just look at the max value on the "speedometer" to see how good a car is, we mostly drive at the speed limit. Take from it what you will.
Better yet, have an old leatherman belt case or cell phone holder? Have a spring loaded cord for keys that you hate to use when it jingles? Combine, recycle and triumph. It seems that the key ball fits in the case on your belt. The retractable cord keeps em on you and handy. No jingles. Add a bit of something fluffy to the case to take up any space left (if your key ball is small) and you can even pass the absolute silence test. IE "The Dune (tm) don't jingle your keys like poorly tied water tokens test" for you in the know. On the other hand, as he parent said, use less or flat keys. I personally go the Dune route as I am cool that way.
Don't get me wrong, I love centralized backups and backup server/client software (bacula for example). However I use old school methods for a bare metal restore. For simple things blanking the free space and then make a "dd" image is all you need. However you do it, keep it simple, and there may be no need to do bare metal on the whole of a file servers data set. Once I get the core of it back up I can use my favorite software to get the system up-to-the-last-snapshot current.
LVM and Raid can be a little complex if you boot off it so ill give some tips. A nice small boot like SLAX (may favorite) or Knoppix is needed to start any bare metal restore. Pick something that supports the hardware and had LVM and or Raid. Either make a custom disk to add your backup data to the volume or have a 2nd DVD drive. Boot and restore.
I make my backups via simple methods like rsync and tar. I use a few simple scrips to do it all. So simple that it is easy to restore by hand if need be. This makes the restore safer as it can be done a host of ways. Not to mention these unix tools are present in all distributions. Probably the biggest reason for the old school way is that on a bare metal restore often hardware may change. New drives etc, basically failure can be a reason to upgrade etc. Many utilities can choke on big hardware changes, new drive sizes and such.
I take detailed system information and note it in the backup as human notes. Then grab your raid & LVM configuration and write a quick script to rebuild these features via the command line. Basically just a list of the actions you take to make a file system and format them the desired files system types manually. These same scripts will also re-apply boot loader and such as well. If the volumes change after a failure I can just issue updated commands (or edit the script) and make a similar layout of the filesystem. Then just open the tar balls via script or by hand and populate the new filesystem with the files you archived. With a bit of practice all of this can be automated by scripts. But if you need to vary the procedure due to hardware changes or as a way to clone a system you can.
Of course it would behave like JBOD if you applied LVM over many non-redundant volumes. To expect redundancy protection from a tool that does not provide it by nature is like expecting blood from stones. Use LVM to best effect on whopping great raid volumes. This way and you get the effect of partitions, the flexibility to change your mind about layout. Not to mention snapshot and other useful things. The redundancy is managed by the raid method you use. Choose your tools well, use more as needed.
If all you have is a hammer, every problem will be treated like a nail.
Thankfully I have a wrench as well.
Ok, I'll put my few cents in. Before I start let me say, Welcome to the club. The Job of scientists is truly one of the most fun and free jobs you can have. Don't expect to be payed well for the skill you will some day have. I can easily make 5X what I do as a scientist in business or management with my skill level. But I am never bored, thats a big plus. I choose my own hours (usually means 60 + per week) but I don't have to work mornings if I don't like it. I get to play with cool toys. Yes it silly but havening fun with $2,000,000 instruments is a geek thing, I like it. I get to write, publish and get the prestige that brings.
On to the question now. The first day will be a tour and paper work. You will be given a manual of procedures and safety controls. You will be asked to read it and sign it. Later you may take a test on it. You will also find out what certifications you may need, use of biological organism, radioisotopes etc... These will all have their own safety manual/course and you will take these tests and such over the next few weeks.
In an ideal situation shortly (maybe not the first day) you will be assigned a lab and or office space. It will be far too small and you may share with another junior lab jock. You will find you are at the bottom of the totem pole and will be probably assigned a project to work on. This will likely be small and not very important, its is to get you lab legs. This project will be a collaborative effort with someone. Maybe the professor himself if he is a in lab guy otherwise a medium to high lab guy. Your real job is to play well with others and to learn whatever you need to learn to work on that project. In time you will get into new projects and some you may even pick yourself. However, you will always be expected to be ready to update your skills yourself at any time, with a book, a protocol, a class or just ask questions. Be considerate and a team player. Even if the flavor of the lab is every man for himself. In the start we all need mentoring, if you need lots of help spread it out over all the lab mated you can take freely too. This way you don't take any one persons time too often. Be ready to work long hours, results is the key and it may take you 10X the time (due to repeats) a fully trained guy needs. Be ready to put that time in on demand.
One important thing is to find out the lab culture quickly, make no enemies and try to make friends. Lab culture can vary, to a lab of team based collaborators to a group of individuals all working on 1 single personal project. Know a collaborative lab by the papers they produce, lots of lab members names in the by line, collaborative. Only professor and one other guy. Individual work labs can be somewhat cutthroat where each lab member is out for his project to get all the time and $$. If the culture is somewhat cutthroat (and this happens) due to resource allocation limitations, be sure to know this early and be ready to protect your turf, when you have one.
At first you may have a project but it may never finish, its a learning thing. Only protect turf when its needed, as it can cause bad blood. Be sure to understand that at first you will be less skilled than many. So concentrate on getting confirmed skills, friends and respect. These are far more important that any small starter project.
You may feel small,and the boss may not seem to help with it. Just remember, a good professor wont let you fall if your project gets shot down as long as you have real skills (learned) and good interpersonal ability. You have to trust this, there is no other way. The lab director is a dictator, maybe benevolent, maybe not (this happens) but you can't top him/her ever. If you really think you have been marginalized badly (after a year or so, and it will take time to tell) maybe you need to move to a new lab.
Very often a professor will have favorites and you can't seem to get good breaks. However, your lab mates have about a 4 year life in
Its fast, but not as fast as I would have hopped with parallel access. They better get the speed up or the cost down to hit it big. Right now I'd take either direction, as they both have decent applications. Good progress though, time will tell.
I don't have my screen inverted, but I have a screen flipped 90 degrees to make better use of a second monitor. The second link was exactly what I needed.
Not to defend vista, but lets get the facts strait. It seems that there are 2 modes to the reduced functionality, Basically if you don't activate you get the black screen and are screwed. They will treat pirates the nearly same as they do in XP with updates only. Sigh, I would have hoped for more aggressive blocking. Just to give people a chance to consider the true cost of Vista.
non-genuine key:
Can use Windows Vista features
Can activate Windows Vista
Can change the product key
Can log on without a time constraint to perform certain activities (no 1 hour restriction)
Can not use certain Windows Vista features such as Aero Glass and the Windows ReadyBoost.
Can not obtain some content from Microsoft Download center.
Out-of-grace period for activation:
Can activate Windows Vista
Can remotely script Windows Vista
Can change the product key
Can log on to Windows Vista for one hour to obtain a new product key or to access data on the local computer.
Can use most of the features that are available in Windows Vista.
Can activate the Windows Vista product key.
Can remotely access a shared network location.
Can remain logged on
Can run Windows Vista in safe mode
Can not play built-in games
Can not use premium features such as Aero Glass, ReadyBoost, and BitLocker.
Can not log on for more than one hour
Ok, then (note, you will need a newer kernel than can mount HFS+ RW, depend on ipod model);
Blank the free space before you backup then,
mount -t hpfs -o rw/dev/sdc2/mnt/ipod
dd if=/dev/zero of=/mnt/ipod/blank.file
rm/mnt/ipod/blank.file
umount/dev/sdc2
then backup with dd:
dd if=/dev/sdc2 | gzip > ipodbackup.img.gz
or if you want to backup the firmware too:
dd if=/dev/sdc | gzip > ipodbackup.img.gz
For some more detailed info on ipod and linux things... http://pag.csail.mit.edu/~adonovan/hacks/ipod.html
Don't forget to backup the firmware too/dev/sd1, you may need it. Generally I take an "empty" backup of a virgin fully zeroed device with no files, firmware and partition structure and all, then I can do a simple factory restore. If you don't have a new device it trivial to make one. Just mount it, copy off your tunes to the hdd, zero the free space on the second partition. Unmount it, then take the image of the ipod and you are set for a Linux based restore. What was said before was essentially right, dd is the way. Put a few of these sorts of commands (tweaked for your personal settings) in a bash script, and add a shortcut to your desktop or a menu, now its easy too.
I make servers and work boxes, I do use 64 bits from time to time but most of the code on them will do 32 just fine so I am not even hung up on 64 bits. I just feel Opteron is where its at in my world, and will be for quite some time. Its good enough, cheap enough and can do 64 and 32 bits and is so close to the same performance that keeping a consistent closet (that means spare parts for all) has more value than the difference.
I don't game much so perhaps you are right on that front. However have one rule, never overclock if you want to keep your job. At home its fine I suppose, but in my closet its cool low power chips that perform well in stock form only (AMD with low memory latency is also very good here). I can't speak for the rest of you, just me.
"Intel's Core 2 Duo is clearly the most attractive processor on the market..."
That quote sums it up, Its An Intel-Fanboy article.
That said, I still lean AMD. If Intel lowers the cost on these chips and AMD stays where they are Intel will really have a lead. They certainly have a good product now. However, Once you add the and chips and boards to the basket (by new egg prices) the Intel solution is easily $100-200 more expensive when comparing equivalent power (especially budget) processors. Its not much but in the under $1000 basic box range thats significant.
However, even if AMD gets $200 more expensive per set ill stay with it for my servers. They have treated me way too well to dump over chump change. Intel will have to be better, cheaper and keep the edge for quite some time before I jump ship.
I am sure I would be glad to see Linux get "out" more. Its easily customized and can be made to run on damed near anything so I am sure it would work quite well. By using Linux I am sure they can save a bundle on licenses to development software in the short term. However, I am unsure about the rest (the bit the reviewer stated, on this really saving cost in the long run).
I always thought that much of the real cost of a "space" probe (besides getting actually it there) was the space hardened chips and tech. Not so much the software. As far as I know NASA dose not have to "pay" to use patents and such. but making this gear on such limited exotic fab specs is crazy expensive.
Using of the shelf gear for the test devices is nice and but those IC will not take hard radiation gracefully. So wont these devices have to be rebuilt from the ground up if there were to actually be used. This of course would be come with significant software re-writes since much of this of the shelf gear would be too costly to space harden, when simply making a simple cheap new implementation would do better. This of course would defeat many or all off the self harware "cost" arguments.
Compared to the huge cost of making space probes in man hours and technology I really dbout software cost has much impact on the total cost of a probe. Instead, I would prefer them to use Linux because it may well be the "best" software to use in such probes.
Yes! Thats it, give me POP3 and then I can use whatever mail thing I most prefer, for free. And don't forget you can use Gmail as a outgoing SMP server too, also for free as well.
Thats why Yahoo is not what I would prefer to use, and of course it is now my "disposable" mail account if I want some degree of anonymous personal mail or just a trap for the inevitable flow of crap spam from some site registration. The nice thing is Gmail can be accessed from the web too. Gmail is still not my "primary mail" I use work mail and such, but as time goes by and jobs change or you move etc, its nice to have that "other" personal mail account to keep. Whatever mail I use it better work with my favorite mail manager or i just wont check them. Gmail dose this so I use it often, yahoo will not not so it gets the spam is and is checked may be once a month.
Why is this such an issue any way?
Uhh guys, it may not be Bayer's fault that it happened at all. For those of you that know rice is uhhh WIND pollinated and I bet they grew some of their test plots NEAR the places that rice is grown. Then some of the normal grown crops around can get pollinated by the test crop and the rest is history. This happens and i need not be a controversy. Its just a small excuse for a protection racket in japan see below, really this all boils down to the GMO debate
OK, OK, I hate this argument in general but I have Karma to burn and i see so many insightful posts that are well frankly off. They are best described as Ignorant of GMO = Fear of GMO.
I am a Molecular Biologist (IE I can and have made "GMO" plants), So I am biased. However, I am also well versed. in the issue. Here I will quickly debunk a number of common arguments against GMO.
General answerer:
Regardless of what some people want we have a few GMO crops and there will be more to come. Perhaps herbicide resistant that or this is not the best usage of this technology but it is the first. If these simple products cant go to market how will we ever see the true power. Drugs to extend and save lives in plants. MMR or other vaccines in bananas so any person in a 3rd world country can grow and have needed vaccines for the populations with out dependence on 1st world charity. These dreams are here now, personally I find these ideas exciting. When GMO becomes more associated with life saving i think the FUD will lessen. Until then when you hear statistical numbers and emotional arguments just think and learn and remember the TTM (see below) number can be twisted so easily.
Fears:
Genetic modification is unnatural:
We have been doing this for years, the ancestors of corn resembles crab grass, we just modified it by selection the seed from the most fit specimen and selecting that to grow. Over the years we have made truly massive changes, far more than any molecular biologist can do today.
Genetic modification will/may cause unknown allergies:
See MIVF and SPAGETTIE below, most food allergies are caused by a very specific and select group of proteins and chemicals. Yes if you transfered the genes for one of these you may get new food allergies. But 99.99% of geese have virtually zero risk of this effect. Food allergies are VERY rare even among all foods. And there is a concentration issue. The protein (food storage protein) in peanuts that is the source of allergies is present in super high concentrations ( think 5-10% of the dry weight of the peanut). This is because its a energy storage source for the seed. The herbicide resistance protein is going to be many orders of magnitude less ( think 0.001%). However, the is never 0 risk, its just ludicrously small.
genetic modification may lead to "unspecified unknown problems in consumers":
this is pure fear on faith, See MIVF and SPAGETTIE below. Risks are small and that is why there are massive amounts of tests. However just remember in the end we change 1 or 2 genes only, and may be incidentally destroy one or 2 natural ones when we make a GMO. We do not give the plant new powers beyond the target gene. If the purified herbicide resistance protein is safe in massive amounts (ie feed the concentrated extract of it to a rat) it will be safe in the supper tinny amounts in the crop.
Genetic modification will/may increase pesticide/herbicide use:
Actually no, this is pure FUD. Being able to spray in the middle of a crop growth means you can spray less at the start of the season and may be don't have to use several other more toxic products (germination inhibitors) to keep the field extra clean (think virtually sterile). This is because you can knock the weeds back later in the season so the newly germinated ones can't catch up with the now rapidly growing crop.
Genetic modified crops are likely to be more contaminated with herbicides:
See above, if you g
Or you can obscure the plate legally by simply putting your tail gate down if you drive a truck. This is legal and of course defensible in this day and age of high gas prices, you get better gas mileage in most trucks if you do it. This is not going to work all the time, aka if you have front plates (and they aim the camera there) or they actually install the camera some place other on a high pole. Fortunately, not all US states require a front plate, and vandals being what they are will keep cameras up on poles. The result is that they will not likely get a good view if yer tail gate is down, and its not economically to put up both front and back cameras just yet. All in all this is much more easily done than buying "plate spray" or other plate modification just to risk next week a new anti-whatever you did law, complete with plate tamper detectors.
Hmmm ill try the LD_LIBRARY_PATH thing, tomorrow thanks for the tip.
As for requiring 32 bit X11 libraries, I really can't say, it certainly would not install under 64 bit, and would as the same user the 32 bit chroot. However, once installed, (note/home is mounted bind inside 32 chroot) that same user can run it outside the 32 bit chroot as well. Since there is only limited 32 bit support in this AMD64 disto, Goggle Earth in this case must only have access to / know the locations of the 64 bit X11 libraries.
It works well installed by a user in Debain AMD64 sarge, had to install it under 32 bit chroot, but will run in both 32 and 64 bit sides after unpack. It seems to want to use software gl, not accelerated graphics with my properly installed fglrx module (ATI driver) but thats ok, its plenty fast as is for my needs.
I see quite a few negative comments here about this and I really wonder why. When I was a student and a budding EE I used to tear apart all sorts of things and "tweak" them. I was always proud when I could get a meaningful result, an "improvement" or at lease a change that suited me (or hinted that with abit of work it could). I used to enjoy making contrived serial data transmitter adapters out of old cordless phones or other even more completely nutty things. Was I cool, probably not. Such silly junk experiments may seem simple and contrived to a real EE, but at the time I learned quite a bit from them, as much by failure as by success. As silly as it may sound in the end I really learned to properly rework and make my own simple boards. Such useful skills don't come easily to some, as many of you may know, it takes practice. Doing such projects just for fun, was if little else practice. Ultimately this curiosity taught more meaningful skills.
When I did a project well I wanted to tell others and show them, because at my level of skill it was cutting edge cool, for me. To all those that ask "why do his to a SNES?," I say this. There is no crime here, this may be one of the few simple projects that could have mass appeal to a certain subset of the slashdot crowd. Heck, thinking back, I wish I had tried doing something this cool as an undergrad. Keep up the good work.
I do something similar, i use a random generated matrix used to decode simple passwords like "father" into a complex password, each month I generate a new matrix and file the old one, just in case I need to use a backup (when I backup I write the sheet id on the media). Only I know the column I use this month (I suppose it can be the real month too) and the simple key I use with cipher to get out my password. As long as in don't tell anyone my simple cipher, I can use it as many times as I like, on as many sites and computers, I just change the matrix. If I am good I may remember the complex password, if not, its easy to look up. I put my matrix right on the wall over my monitor or terminal.
Here is the python code if you care, white space was eaten see placeholders.
uc = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
lc = uc.lower()
digits = "0123456789"
funny = "!@#$%^&*-_"
vowels = "aeiou"
cols = 12
counter = 0
import random
print version + " sheet-" + random.choice(uc) + random.choice(digits) + random.choice(digits)
print "C 1 2 3 4 5 6 7 8 9 10 11 12"
for letter in lc:
[TAB] line = letter
[TAB] while counter
[TAB][TAB] counter = counter+1
[TAB][TAB] if letter in vowels:
[TAB][TAB][TAB] line = line + " " + random.choice(uc) + random.choice(funny)
[TAB][TAB] else:
[TAB][TAB][TAB] line = line + " " + random.choice(lc) + random.choice(digits)
[TAB] print line
[TAB] counter = 0
Old, but valid news
on
Sudo vs. Root
·
· Score: 2, Insightful
This "problem" has been around a while and is not really a Mac OS X thing problem. In short poorly configured systems are less secure, imagine that. I can make my self type 3 or 4 different passwords to get to sudo or root, will this make me more secure, perhaps. However I guarantee that if Apple did this the first thing every user would do is enable root, or otherwise make it more sane and easy to administer the system. If by some greater decree they made it impossible to do this, fewer people will want such system, as it will make them harder to use. Whatever you do, if you have boot, you have "root" ( or at lease root like access). In short it is possible to layer on many levels of security over the "root" access of a system but it this actually wise?
I don't use much OS X but I do use Linux quite abit. When I set up my machines, of course I use root access, lazy heck no. I have hordes of little tweaks and such to perform, packages to install, things to edit and permissions to set. If I had to use sudo, my first command would be to open a root bash shell. As for security, a new system it not accessible to the outside, thats it. After a system is up and running, I tighten things up.
First thing, as mentioned, is to disable root access by ssh. Of course, use public keys instead of passwords where possible. However why not go a simple step further, and the article missed that. Most of my accounts, and certainly all those accessible with ssh don't even need the privileges to use sudo or su to root at all. In fact in most cases my externally accessible shell accounts have a very limited set of commands they can run, simply because shell access is so insecure to begin with (hello gcc under remote shell users). I feel that this is clean and efficient and not a real pain to setup.
If you are paranoid and want a 2nd password for "root" access, use such a limited user for all users, then make a second account that may use sudo or root and log the heck out of it. Make each prospective admin su to that first. in the end, its only how much security is reasonable that wins. if you need more unplug the box and lock the thing up in a closet to prevent physical access by lock key, this too can be broken...
When a pack of wolves hunt a herd of sheep, as a sheep you need not out run the wolves to be safe, only the slower sheep. These slower sheep (aka windows) are generally quite abit slower these days than you (OS X). However, this all depends on the number of wolves you keep (or allow) on your netoworks... If you can't generally trust your users you have other problems.
Guess I can't mod this thread now, but it must be a said. Regulate a sector of business and its growth will slow end of story.
Governments, businesses, lawyers isp's, and such are all playing an increasingly complex game of regulation and political maneuvering these days. Much less than in years before. All this extra "stuff" has a cost, it slows the speed of development and growth of most aspects of the service. Primarily due to the extra hoops and liabilities that users must now jump through and avoid.
This once happened with the expansion of the USA into the new unpopulated territories in the west. Before regulation you had true freedom and could do so many things, the resources where there to be tapped and there was little penalty for abusing them. Basically it was a rush to be the best, damn the laws, sense, reason or moderation. As regulation came, so did law order and subsequently slower progress. This maturation cycle is unfortunately unlikely to stop now that the "value" (different depending on who you are, car dealer or government) of the Internet is more or less universally recognized.
Now "they" all want a hand the mix of regulations and laws. All seem to think that net wold be better if...., and that is the problem. Every one wants to fix than, encourage this, and ban that bad act. The net as we knew ins days past with it's with its free porn and heady freedom is gone, sigh, one more frontier being tamed. That will mean less freedom on the net, guaranteed. Hope this all comes, like the wild west, with improvements in welfare and public safety, but that has yet to be realized.
From my point of view and IAAMB (I am a molecular biologist) this is only encouraging. it has been shown several times and through several ways you can get nerves to regrow in a living animal. We have seen stems cells, hormones smooth surfaces, and now injectable protein gel however all these tricks fail on a few levels. But there are some issues I have:
1.) Such procedures are useless for fixing old damage, scar tissue build up physically prevents nerves from "having a place to grow into". Additionally, large gaps are still impossible, so for big lesions or paternally using a surgical procedure to prep a site to regenerate will not fly. You cant just cut out the chunk of "damaged goods" and let it regrow fresh. So unless you use this trick as the article suggests at the time of injury ( surgery time perhaps), before scar forms you have ) chance of help.
2.) The other problem is one of myelination, the insulation around the axon on each motor nerve. Adult tissue lacks the ability to produce significant amounts of myelin to sheath nerves. Fetal stem cells cant, but not adult tissue. So it is likely that any nerves grown this way will be de-myelinated and not at all good for good signal transmission. Incidentally, one common type of de-myelinated nerve is the sensory nerve. just imagine, fix a arm amputation this way and i bet you will get VERY weal motor control, and potentially full or malformed sensory information due to the very good regrowth of random sensory nerves (think life long chronic pain). This side effect has been seen in a number of spinal injury patients given experimental stem cell treatment in china (right location I think).
3.) Of course proteins are small, nano even, but how is this "Nanotech". This would be more like "Biotech", ahh well the rain of buzz words to sell ideas shall continue unabated.
Hmm that FA was totally devoid of any real details. As it seems to me, and granted I do not develop on cell processors, and I am not a stickler for the "next big thing", but these things may be interesting. Unfortunately, if they want me to use them I need to know it works for me. I want my existing code to compile with minimal changes so I can test the new platform in the raw. I have the resources to test a few "maybe good may be not" systems a year. What I want to know in short is, If it "could" work well. This means I need to use my existing code base in part (their tier IV). I am happy to optimize in my spare time and if need be, once I know it "could be the thing". If the platform passes that test I'll buy a few more units and make a real go if it. I don't think that the cell processor is to that point yet, too little hardware on sale righ now and no software, and there lies the problem. Open source compiler support would be a big plus, but if the platform is "just that good" I can make an exception.
As if the AOL customer service was reason enough to avoid it, now they add a whole new insult. Cell phone like plan gouging and hidden pricing with contractual commitments. Of course, on the upside, this will make people switch to a new provider via economic pressure. You have to love natural selection in progress.
Slashdot Mirror
There are more than a few things that AMD besides gaming and over clocking (Intel strong points) that make an AMD a good choice. I don't want to start holy war here but there is not much real gap here 10-5% in my tests at best. The price * power use thing shows AMD is a good choice in many places. Price alone makes me deploy more than a few AMD clusters. Don't just look at the max value on the "speedometer" to see how good a car is, we mostly drive at the speed limit. Take from it what you will.
Better yet, have an old leatherman belt case or cell phone holder? Have a spring loaded cord for keys that you hate to use when it jingles? Combine, recycle and triumph. It seems that the key ball fits in the case on your belt. The retractable cord keeps em on you and handy. No jingles. Add a bit of something fluffy to the case to take up any space left (if your key ball is small) and you can even pass the absolute silence test. IE "The Dune (tm) don't jingle your keys like poorly tied water tokens test" for you in the know. On the other hand, as he parent said, use less or flat keys. I personally go the Dune route as I am cool that way.
Don't get me wrong, I love centralized backups and backup server/client software (bacula for example). However I use old school methods for a bare metal restore. For simple things blanking the free space and then make a "dd" image is all you need. However you do it, keep it simple, and there may be no need to do bare metal on the whole of a file servers data set. Once I get the core of it back up I can use my favorite software to get the system up-to-the-last-snapshot current.
LVM and Raid can be a little complex if you boot off it so ill give some tips. A nice small boot like SLAX (may favorite) or Knoppix is needed to start any bare metal restore. Pick something that supports the hardware and had LVM and or Raid. Either make a custom disk to add your backup data to the volume or have a 2nd DVD drive. Boot and restore.
I make my backups via simple methods like rsync and tar. I use a few simple scrips to do it all. So simple that it is easy to restore by hand if need be. This makes the restore safer as it can be done a host of ways. Not to mention these unix tools are present in all distributions. Probably the biggest reason for the old school way is that on a bare metal restore often hardware may change. New drives etc, basically failure can be a reason to upgrade etc. Many utilities can choke on big hardware changes, new drive sizes and such.
I take detailed system information and note it in the backup as human notes. Then grab your raid & LVM configuration and write a quick script to rebuild these features via the command line. Basically just a list of the actions you take to make a file system and format them the desired files system types manually. These same scripts will also re-apply boot loader and such as well. If the volumes change after a failure I can just issue updated commands (or edit the script) and make a similar layout of the filesystem. Then just open the tar balls via script or by hand and populate the new filesystem with the files you archived. With a bit of practice all of this can be automated by scripts. But if you need to vary the procedure due to hardware changes or as a way to clone a system you can.
Of course it would behave like JBOD if you applied LVM over many non-redundant volumes. To expect redundancy protection from a tool that does not provide it by nature is like expecting blood from stones. Use LVM to best effect on whopping great raid volumes. This way and you get the effect of partitions, the flexibility to change your mind about layout. Not to mention snapshot and other useful things. The redundancy is managed by the raid method you use. Choose your tools well, use more as needed.
If all you have is a hammer, every problem will be treated like a nail.
Thankfully I have a wrench as well.
Ok, I'll put my few cents in. Before I start let me say, Welcome to the club. The Job of scientists is truly one of the most fun and free jobs you can have. Don't expect to be payed well for the skill you will some day have. I can easily make 5X what I do as a scientist in business or management with my skill level. But I am never bored, thats a big plus. I choose my own hours (usually means 60 + per week) but I don't have to work mornings if I don't like it. I get to play with cool toys. Yes it silly but havening fun with $2,000,000 instruments is a geek thing, I like it. I get to write, publish and get the prestige that brings.
On to the question now. The first day will be a tour and paper work. You will be given a manual of procedures and safety controls. You will be asked to read it and sign it. Later you may take a test on it. You will also find out what certifications you may need, use of biological organism, radioisotopes etc... These will all have their own safety manual/course and you will take these tests and such over the next few weeks.
In an ideal situation shortly (maybe not the first day) you will be assigned a lab and or office space. It will be far too small and you may share with another junior lab jock. You will find you are at the bottom of the totem pole and will be probably assigned a project to work on. This will likely be small and not very important, its is to get you lab legs. This project will be a collaborative effort with someone. Maybe the professor himself if he is a in lab guy otherwise a medium to high lab guy. Your real job is to play well with others and to learn whatever you need to learn to work on that project. In time you will get into new projects and some you may even pick yourself. However, you will always be expected to be ready to update your skills yourself at any time, with a book, a protocol, a class or just ask questions. Be considerate and a team player. Even if the flavor of the lab is every man for himself. In the start we all need mentoring, if you need lots of help spread it out over all the lab mated you can take freely too. This way you don't take any one persons time too often. Be ready to work long hours, results is the key and it may take you 10X the time (due to repeats) a fully trained guy needs. Be ready to put that time in on demand.
One important thing is to find out the lab culture quickly, make no enemies and try to make friends. Lab culture can vary, to a lab of team based collaborators to a group of individuals all working on 1 single personal project. Know a collaborative lab by the papers they produce, lots of lab members names in the by line, collaborative. Only professor and one other guy. Individual work labs can be somewhat cutthroat where each lab member is out for his project to get all the time and $$. If the culture is somewhat cutthroat (and this happens) due to resource allocation limitations, be sure to know this early and be ready to protect your turf, when you have one.
At first you may have a project but it may never finish, its a learning thing. Only protect turf when its needed, as it can cause bad blood. Be sure to understand that at first you will be less skilled than many. So concentrate on getting confirmed skills, friends and respect. These are far more important that any small starter project.
You may feel small,and the boss may not seem to help with it. Just remember, a good professor wont let you fall if your project gets shot down as long as you have real skills (learned) and good interpersonal ability. You have to trust this, there is no other way. The lab director is a dictator, maybe benevolent, maybe not (this happens) but you can't top him/her ever. If you really think you have been marginalized badly (after a year or so, and it will take time to tell) maybe you need to move to a new lab.
Very often a professor will have favorites and you can't seem to get good breaks. However, your lab mates have about a 4 year life in
Its fast, but not as fast as I would have hopped with parallel access. They better get the speed up or the cost down to hit it big. Right now I'd take either direction, as they both have decent applications. Good progress though, time will tell.
You may want to see these 2 links:
http://ask.slashdot.org/article.pl?sid=00/06/27/0248218
http://ubuntuforums.org/showthread.php?t=148177
I don't have my screen inverted, but I have a screen flipped 90 degrees to make better use of a second monitor. The second link was exactly what I needed.
Not to defend vista, but lets get the facts strait. It seems that there are 2 modes to the reduced functionality, Basically if you don't activate you get the black screen and are screwed. They will treat pirates the nearly same as they do in XP with updates only. Sigh, I would have hoped for more aggressive blocking. Just to give people a chance to consider the true cost of Vista.
reference
http://support.microsoft.com/kb/925582
Ill summarize what you can do:
non-genuine key:
Can use Windows Vista features
Can activate Windows Vista
Can change the product key
Can log on without a time constraint to perform certain activities (no 1 hour restriction)
Can not use certain Windows Vista features such as Aero Glass and the Windows ReadyBoost.
Can not obtain some content from Microsoft Download center.
Out-of-grace period for activation:
Can activate Windows Vista
Can remotely script Windows Vista
Can change the product key
Can log on to Windows Vista for one hour to obtain a new product key or to access data on the local computer.
Can use most of the features that are available in Windows Vista.
Can activate the Windows Vista product key.
Can remotely access a shared network location.
Can remain logged on
Can run Windows Vista in safe mode
Can not play built-in games
Can not use premium features such as Aero Glass, ReadyBoost, and BitLocker.
Can not log on for more than one hour
Blank the free space before you backup then,
mount -t hpfs -o rw
dd if=/dev/zero of=/mnt/ipod/blank.file
rm
umount
then backup with dd:
dd if=/dev/sdc2 | gzip > ipodbackup.img.gz
or if you want to backup the firmware too:
dd if=/dev/sdc | gzip > ipodbackup.img.gz
For some more detailed info on ipod and linux things
http://pag.csail.mit.edu/~adonovan/hacks/ipod.htm
Don't forget to backup the firmware too
The first $100 Million pays for the movie and the next probably goes right into someones bad habits (or poor business sense).
And if your very lucky you can make a down payment on the next rehab...
I make servers and work boxes, I do use 64 bits from time to time but most of the code on them will do 32 just fine so I am not even hung up on 64 bits. I just feel Opteron is where its at in my world, and will be for quite some time. Its good enough, cheap enough and can do 64 and 32 bits and is so close to the same performance that keeping a consistent closet (that means spare parts for all) has more value than the difference.
I don't game much so perhaps you are right on that front. However have one rule, never overclock if you want to keep your job. At home its fine I suppose, but in my closet its cool low power chips that perform well in stock form only (AMD with low memory latency is also very good here). I can't speak for the rest of you, just me.
"Intel's Core 2 Duo is clearly the most attractive processor on the market..." That quote sums it up, Its An Intel-Fanboy article.
That said, I still lean AMD. If Intel lowers the cost on these chips and AMD stays where they are Intel will really have a lead. They certainly have a good product now. However, Once you add the and chips and boards to the basket (by new egg prices) the Intel solution is easily $100-200 more expensive when comparing equivalent power (especially budget) processors. Its not much but in the under $1000 basic box range thats significant.
However, even if AMD gets $200 more expensive per set ill stay with it for my servers. They have treated me way too well to dump over chump change. Intel will have to be better, cheaper and keep the edge for quite some time before I jump ship.
I am sure I would be glad to see Linux get "out" more. Its easily customized and can be made to run on damed near anything so I am sure it would work quite well. By using Linux I am sure they can save a bundle on licenses to development software in the short term. However, I am unsure about the rest (the bit the reviewer stated, on this really saving cost in the long run).
I always thought that much of the real cost of a "space" probe (besides getting actually it there) was the space hardened chips and tech. Not so much the software. As far as I know NASA dose not have to "pay" to use patents and such. but making this gear on such limited exotic fab specs is crazy expensive.
Using of the shelf gear for the test devices is nice and but those IC will not take hard radiation gracefully. So wont these devices have to be rebuilt from the ground up if there were to actually be used. This of course would be come with significant software re-writes since much of this of the shelf gear would be too costly to space harden, when simply making a simple cheap new implementation would do better. This of course would defeat many or all off the self harware "cost" arguments.
Compared to the huge cost of making space probes in man hours and technology I really dbout software cost has much impact on the total cost of a probe. Instead, I would prefer them to use Linux because it may well be the "best" software to use in such probes.
Yes! Thats it, give me POP3 and then I can use whatever mail thing I most prefer, for free. And don't forget you can use Gmail as a outgoing SMP server too, also for free as well.
Thats why Yahoo is not what I would prefer to use, and of course it is now my "disposable" mail account if I want some degree of anonymous personal mail or just a trap for the inevitable flow of crap spam from some site registration. The nice thing is Gmail can be accessed from the web too. Gmail is still not my "primary mail" I use work mail and such, but as time goes by and jobs change or you move etc, its nice to have that "other" personal mail account to keep. Whatever mail I use it better work with my favorite mail manager or i just wont check them. Gmail dose this so I use it often, yahoo will not not so it gets the spam is and is checked may be once a month.
Why is this such an issue any way? Uhh guys, it may not be Bayer's fault that it happened at all. For those of you that know rice is uhhh WIND pollinated and I bet they grew some of their test plots NEAR the places that rice is grown. Then some of the normal grown crops around can get pollinated by the test crop and the rest is history. This happens and i need not be a controversy. Its just a small excuse for a protection racket in japan see below, really this all boils down to the GMO debate
OK, OK, I hate this argument in general but I have Karma to burn and i see so many insightful posts that are well frankly off. They are best described as Ignorant of GMO = Fear of GMO.
I am a Molecular Biologist (IE I can and have made "GMO" plants), So I am biased. However, I am also well versed. in the issue. Here I will quickly debunk a number of common arguments against GMO.
General answerer:
Regardless of what some people want we have a few GMO crops and there will be more to come. Perhaps herbicide resistant that or this is not the best usage of this technology but it is the first. If these simple products cant go to market how will we ever see the true power. Drugs to extend and save lives in plants. MMR or other vaccines in bananas so any person in a 3rd world country can grow and have needed vaccines for the populations with out dependence on 1st world charity. These dreams are here now, personally I find these ideas exciting. When GMO becomes more associated with life saving i think the FUD will lessen. Until then when you hear statistical numbers and emotional arguments just think and learn and remember the TTM (see below) number can be twisted so easily.
Fears:
Genetic modification is unnatural:
We have been doing this for years, the ancestors of corn resembles crab grass, we just modified it by selection the seed from the most fit specimen and selecting that to grow. Over the years we have made truly massive changes, far more than any molecular biologist can do today.
Genetic modification will/may cause unknown allergies:
See MIVF and SPAGETTIE below, most food allergies are caused by a very specific and select group of proteins and chemicals. Yes if you transfered the genes for one of these you may get new food allergies. But 99.99% of geese have virtually zero risk of this effect. Food allergies are VERY rare even among all foods. And there is a concentration issue. The protein (food storage protein) in peanuts that is the source of allergies is present in super high concentrations ( think 5-10% of the dry weight of the peanut). This is because its a energy storage source for the seed. The herbicide resistance protein is going to be many orders of magnitude less ( think 0.001%). However, the is never 0 risk, its just ludicrously small.
genetic modification may lead to "unspecified unknown problems in consumers":
this is pure fear on faith, See MIVF and SPAGETTIE below. Risks are small and that is why there are massive amounts of tests. However just remember in the end we change 1 or 2 genes only, and may be incidentally destroy one or 2 natural ones when we make a GMO. We do not give the plant new powers beyond the target gene. If the purified herbicide resistance protein is safe in massive amounts (ie feed the concentrated extract of it to a rat) it will be safe in the supper tinny amounts in the crop.
Genetic modification will/may increase pesticide/herbicide use:
Actually no, this is pure FUD. Being able to spray in the middle of a crop growth means you can spray less at the start of the season and may be don't have to use several other more toxic products (germination inhibitors) to keep the field extra clean (think virtually sterile). This is because you can knock the weeds back later in the season so the newly germinated ones can't catch up with the now rapidly growing crop.
Genetic modified crops are likely to be more contaminated with herbicides:
See above, if you g
Or you can obscure the plate legally by simply putting your tail gate down if you drive a truck. This is legal and of course defensible in this day and age of high gas prices, you get better gas mileage in most trucks if you do it. This is not going to work all the time, aka if you have front plates (and they aim the camera there) or they actually install the camera some place other on a high pole. Fortunately, not all US states require a front plate, and vandals being what they are will keep cameras up on poles. The result is that they will not likely get a good view if yer tail gate is down, and its not economically to put up both front and back cameras just yet. All in all this is much more easily done than buying "plate spray" or other plate modification just to risk next week a new anti-whatever you did law, complete with plate tamper detectors.
Hmmm ill try the LD_LIBRARY_PATH thing, tomorrow thanks for the tip.
/home is mounted bind inside 32 chroot) that same user can run it outside the 32 bit chroot as well. Since there is only limited 32 bit support in this AMD64 disto, Goggle Earth in this case must only have access to / know the locations of the 64 bit X11 libraries.
As for requiring 32 bit X11 libraries, I really can't say, it certainly would not install under 64 bit, and would as the same user the 32 bit chroot. However, once installed, (note
It works well installed by a user in Debain AMD64 sarge, had to install it under 32 bit chroot, but will run in both 32 and 64 bit sides after unpack. It seems to want to use software gl, not accelerated graphics with my properly installed fglrx module (ATI driver) but thats ok, its plenty fast as is for my needs.
Nice going google.
I see quite a few negative comments here about this and I really wonder why. When I was a student and a budding EE I used to tear apart all sorts of things and "tweak" them. I was always proud when I could get a meaningful result, an "improvement" or at lease a change that suited me (or hinted that with abit of work it could). I used to enjoy making contrived serial data transmitter adapters out of old cordless phones or other even more completely nutty things. Was I cool, probably not. Such silly junk experiments may seem simple and contrived to a real EE, but at the time I learned quite a bit from them, as much by failure as by success. As silly as it may sound in the end I really learned to properly rework and make my own simple boards. Such useful skills don't come easily to some, as many of you may know, it takes practice. Doing such projects just for fun, was if little else practice. Ultimately this curiosity taught more meaningful skills.
When I did a project well I wanted to tell others and show them, because at my level of skill it was cutting edge cool, for me. To all those that ask "why do his to a SNES?," I say this. There is no crime here, this may be one of the few simple projects that could have mass appeal to a certain subset of the slashdot crowd. Heck, thinking back, I wish I had tried doing something this cool as an undergrad. Keep up the good work.
I do something similar, i use a random generated matrix used to decode simple passwords like "father" into a complex password, each month I generate a new matrix and file the old one, just in case I need to use a backup (when I backup I write the sheet id on the media). Only I know the column I use this month (I suppose it can be the real month too) and the simple key I use with cipher to get out my password. As long as in don't tell anyone my simple cipher, I can use it as many times as I like, on as many sites and computers, I just change the matrix. If I am good I may remember the complex password, if not, its easy to look up. I put my matrix right on the wall over my monitor or terminal.
Here is the python code if you care, white space was eaten see placeholders.
uc = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
lc = uc.lower()
digits = "0123456789"
funny = "!@#$%^&*-_"
vowels = "aeiou"
cols = 12
counter = 0
import random
print version + " sheet-" + random.choice(uc) + random.choice(digits) + random.choice(digits)
print "C 1 2 3 4 5 6 7 8 9 10 11 12"
for letter in lc:
[TAB] line = letter
[TAB] while counter [TAB][TAB] counter = counter+1
[TAB][TAB] if letter in vowels:
[TAB][TAB][TAB] line = line + " " + random.choice(uc) + random.choice(funny)
[TAB][TAB] else:
[TAB][TAB][TAB] line = line + " " + random.choice(lc) + random.choice(digits)
[TAB] print line
[TAB] counter = 0
This "problem" has been around a while and is not really a Mac OS X thing problem. In short poorly configured systems are less secure, imagine that. I can make my self type 3 or 4 different passwords to get to sudo or root, will this make me more secure, perhaps. However I guarantee that if Apple did this the first thing every user would do is enable root, or otherwise make it more sane and easy to administer the system. If by some greater decree they made it impossible to do this, fewer people will want such system, as it will make them harder to use. Whatever you do, if you have boot, you have "root" ( or at lease root like access). In short it is possible to layer on many levels of security over the "root" access of a system but it this actually wise?
I don't use much OS X but I do use Linux quite abit. When I set up my machines, of course I use root access, lazy heck no. I have hordes of little tweaks and such to perform, packages to install, things to edit and permissions to set. If I had to use sudo, my first command would be to open a root bash shell. As for security, a new system it not accessible to the outside, thats it. After a system is up and running, I tighten things up.
First thing, as mentioned, is to disable root access by ssh. Of course, use public keys instead of passwords where possible. However why not go a simple step further, and the article missed that. Most of my accounts, and certainly all those accessible with ssh don't even need the privileges to use sudo or su to root at all. In fact in most cases my externally accessible shell accounts have a very limited set of commands they can run, simply because shell access is so insecure to begin with (hello gcc under remote shell users). I feel that this is clean and efficient and not a real pain to setup.
If you are paranoid and want a 2nd password for "root" access, use such a limited user for all users, then make a second account that may use sudo or root and log the heck out of it. Make each prospective admin su to that first. in the end, its only how much security is reasonable that wins. if you need more unplug the box and lock the thing up in a closet to prevent physical access by lock key, this too can be broken...
When a pack of wolves hunt a herd of sheep, as a sheep you need not out run the wolves to be safe, only the slower sheep. These slower sheep (aka windows) are generally quite abit slower these days than you (OS X). However, this all depends on the number of wolves you keep (or allow) on your netoworks... If you can't generally trust your users you have other problems.
Guess I can't mod this thread now, but it must be a said. Regulate a sector of business and its growth will slow end of story.
...., and that is the problem. Every one wants to fix than, encourage this, and ban that bad act. The net as we knew ins days past with it's with its free porn and heady freedom is gone, sigh, one more frontier being tamed. That will mean less freedom on the net, guaranteed. Hope this all comes, like the wild west, with improvements in welfare and public safety, but that has yet to be realized.
Governments, businesses, lawyers isp's, and such are all playing an increasingly complex game of regulation and political maneuvering these days. Much less than in years before. All this extra "stuff" has a cost, it slows the speed of development and growth of most aspects of the service. Primarily due to the extra hoops and liabilities that users must now jump through and avoid.
This once happened with the expansion of the USA into the new unpopulated territories in the west. Before regulation you had true freedom and could do so many things, the resources where there to be tapped and there was little penalty for abusing them. Basically it was a rush to be the best, damn the laws, sense, reason or moderation. As regulation came, so did law order and subsequently slower progress. This maturation cycle is unfortunately unlikely to stop now that the "value" (different depending on who you are, car dealer or government) of the Internet is more or less universally recognized.
Now "they" all want a hand the mix of regulations and laws. All seem to think that net wold be better if
From my point of view and IAAMB (I am a molecular biologist) this is only encouraging. it has been shown several times and through several ways you can get nerves to regrow in a living animal. We have seen stems cells, hormones smooth surfaces, and now injectable protein gel however all these tricks fail on a few levels. But there are some issues I have:
1.) Such procedures are useless for fixing old damage, scar tissue build up physically prevents nerves from "having a place to grow into". Additionally, large gaps are still impossible, so for big lesions or paternally using a surgical procedure to prep a site to regenerate will not fly. You cant just cut out the chunk of "damaged goods" and let it regrow fresh. So unless you use this trick as the article suggests at the time of injury ( surgery time perhaps), before scar forms you have ) chance of help.
2.) The other problem is one of myelination, the insulation around the axon on each motor nerve. Adult tissue lacks the ability to produce significant amounts of myelin to sheath nerves. Fetal stem cells cant, but not adult tissue. So it is likely that any nerves grown this way will be de-myelinated and not at all good for good signal transmission. Incidentally, one common type of de-myelinated nerve is the sensory nerve. just imagine, fix a arm amputation this way and i bet you will get VERY weal motor control, and potentially full or malformed sensory information due to the very good regrowth of random sensory nerves (think life long chronic pain). This side effect has been seen in a number of spinal injury patients given experimental stem cell treatment in china (right location I think).
3.) Of course proteins are small, nano even, but how is this "Nanotech". This would be more like "Biotech", ahh well the rain of buzz words to sell ideas shall continue unabated.
Hmm that FA was totally devoid of any real details. As it seems to me, and granted I do not develop on cell processors, and I am not a stickler for the "next big thing", but these things may be interesting. Unfortunately, if they want me to use them I need to know it works for me. I want my existing code to compile with minimal changes so I can test the new platform in the raw. I have the resources to test a few "maybe good may be not" systems a year. What I want to know in short is, If it "could" work well. This means I need to use my existing code base in part (their tier IV). I am happy to optimize in my spare time and if need be, once I know it "could be the thing". If the platform passes that test I'll buy a few more units and make a real go if it. I don't think that the cell processor is to that point yet, too little hardware on sale righ now and no software, and there lies the problem. Open source compiler support would be a big plus, but if the platform is "just that good" I can make an exception.
my $0.02
As if the AOL customer service was reason enough to avoid it, now they add a whole new insult. Cell phone like plan gouging and hidden pricing with contractual commitments. Of course, on the upside, this will make people switch to a new provider via economic pressure. You have to love natural selection in progress.