Just as seeing the moon doesn't require the same amount of effort as landing on it, reading a DNA sequence doesn't mean that selective modification is "just around the corner."
Who said anything about 'selective modification'? Read what you wrote:
Also, one could use this on embryonic cells obtained through amniocentesis to screen for hereditary diseases is families where there are risk factors.
If you can screen for hereditary diseases, you can also screen for desired traits such as hair color, eye color, propensity for obesity (yes, there's a gene for that), intelligence, etc.
In no time flat, we'll have become a race of athletic, attractive, social and congenial people who all get along, but are all little short in the intelligence department.
The default is only open for users in the 'admin' group. The default for all other users is no sudo access. So you either specifically have to throw a user in the 'admin' group or add a rule that would catch their user account for one or more specific command RE pattern matches that must be created by hand.
Using su without having to resort to forking it off of sudo is a legitimate concern for an Ubuntu user.
Well, I tend to disagree and I won't go into a discussion of sudo vs. su, but it's rather obvious to me, as well as the Ubuntu developers, that using sudo is more secure than doing a 'su' and running things directly as root. I recognize that there are times when doing an su or logging in directly as root may be the easiest way to accomplish something -- especially for experienced *nix users, but the entire system is really setup to use sudo as opposed to su.
I just can't see how you can have very many episodes on Make. Maybe if they threw in autoconf, gcc, and a few other tools, then they could have good show...
Re:Ubuntu annoyances?
on
Ubuntu Kung Fu
·
· Score: 2, Informative
Did you ever consider that some crafty user on a multi-user Ubuntu system may set the root password, and lock you out of sudo?
1) On a multi-user Ubuntu system, typically only one user will have unfettered sudo access. Otherwise, setting the root password requires some sort of root exploit.
2) So long as I have physical access to the box, there is no way anyone could lock me out of root on that same box unless some sort of hardware or BIOS-level whole disk encryption is employed. Given the performance hit, enabling such on multi-user system is generally not wise.
Solar takes a lot of space and puts out a lot less power. It's also costlier. And the process of manufacturing solar panels is horrible for the environment.
Nuclear power is, believe it or not, the cleanest technology we have available, even if you consider the highly radioactive waste and the (typically minute) risk of meltdown.
Sub-$1000 genome sequencing will put the creation of 'designer' kids into the realm of the affordable for much of the middle class. Scary stuff. Now we just need to combine that with cheap and reliable cloning techniques and my plans for world domination will be comlete!
When Sculley took over, Apple had other computer products than the Macintosh, including the Apple II line, and there were other machines on the horizon. In the end, the Macintosh became the main computer line largely because it was the most successful.
Find a company or product that will not immediately collapse when its founder dies or retires.
Except that there was a long period of time between about 1985 and 1998 or so that Jobs was no longer associated with Apple. That's what? Almost 15 years?
Apple didn't immediately collapse and the Macintosh line existed and was largely successful in niche markets without Jobs.
No, Apple doesn't need Jobs, but I think that without Jobs, Apple would lose its sense of direction.
Sculley had the the thing running into the ground well before Spindler came along to piss on Apple's fresh grave. Amelio, believe it or not, was relatively good for Apple -- it was through his efforts that Apple bought NeXT and brought Jobs on board.
Right, but he wasn't picked as a successor. Sculley was to run the day-to-day stuff, leaving Jobs to be the 'visionary leader' over the Macintosh project. Later, it was Sculley who forced Jobs out, mostly because Jobs was trying to basically set the Macintosh group up as totally independent from the rest of the company.
Exactly. But this is what happens -- we want what I call a 'McWorld'. What I mean by that is that we seem to want to put some monkey behind a computer, have them enter a few pieces of information, and spit out a simple answer. No brains, no real skills -- just need someone who can fog a mirror. When you boil everything down to fully-automatic, all-I-need-is-a-mirror-fogger-in-the-seat type of McWorld like that, you get the same results you get at McDonald's -- it works 'good enough' for many, but almost certainly isn't the 'best' product for anybody.
True, but because poster mentions he wants to move from ARM to Atom, that also implies he is moving to a more modern SBC.
Probably, but I wouldn't bet it would be necessarily quadrupling. All sorts of memory configurations are still available. For instance, is the device battery powered? If so, he might order one with less available memory to conserve battery life.
They're intentionally trying to differentiate the versions. It's obvious. The OSE version doesn't have a GUI, doesn't support USB, doesn't support a virtual SATA adapter, doesn't support VRDP, etc.
OTOH, the code is 6 years old, and from what I gather reading the post, it's stable and mature. OTOH, my guess is that if the article poster has written his code in a fairly portable way, it will compile without too much modification on GCC 3.x or 4.x and will run under the newer versions on glibc on a 2.6 kernel.
On the gripping hand, keep in mind that for embedded applications that memory is usually at a premium and the memory footprint of 2.4 is significantly smaller than the 2.6 kernel. Keep in mind that lots of embedded applications are still using a 2.4 kernel and some embedded applications even continue to use MS-DOS or FreeDOS.
I guess if I were making this decision, I'd try to compile and run my code on newer Linux distro in a sandbox to see how much work it would take to make it compile and run in the new environment. Then I'd see how much bigger a custom-built 2.6 kernel is than the existing 2.4 kernel, optimizing the kernel configuration for size and memory consumption, of course.
That work should take no longer than a couple of days.
If it doesn't work out, you can go back to your existing 2.4 configuration. *shrug*
Slashdot Mirror
Just as seeing the moon doesn't require the same amount of effort as landing on it, reading a DNA sequence doesn't mean that selective modification is "just around the corner."
Who said anything about 'selective modification'? Read what you wrote:
Also, one could use this on embryonic cells obtained through amniocentesis to screen for hereditary diseases is families where there are risk factors.
If you can screen for hereditary diseases, you can also screen for desired traits such as hair color, eye color, propensity for obesity (yes, there's a gene for that), intelligence, etc.
In no time flat, we'll have become a race of athletic, attractive, social and congenial people who all get along, but are all little short in the intelligence department.
The default is only open for users in the 'admin' group. The default for all other users is no sudo access. So you either specifically have to throw a user in the 'admin' group or add a rule that would catch their user account for one or more specific command RE pattern matches that must be created by hand.
Using su without having to resort to forking it off of sudo is a legitimate concern for an Ubuntu user.
Well, I tend to disagree and I won't go into a discussion of sudo vs. su, but it's rather obvious to me, as well as the Ubuntu developers, that using sudo is more secure than doing a 'su' and running things directly as root. I recognize that there are times when doing an su or logging in directly as root may be the easiest way to accomplish something -- especially for experienced *nix users, but the entire system is really setup to use sudo as opposed to su.
I just can't see how you can have very many episodes on Make. Maybe if they threw in autoconf, gcc, and a few other tools, then they could have good show...
Did you ever consider that some crafty user on a multi-user Ubuntu system may set the root password, and lock you out of sudo?
1) On a multi-user Ubuntu system, typically only one user will have unfettered sudo access. Otherwise, setting the root password requires some sort of root exploit.
2) So long as I have physical access to the box, there is no way anyone could lock me out of root on that same box unless some sort of hardware or BIOS-level whole disk encryption is employed. Given the performance hit, enabling such on multi-user system is generally not wise.
We do currently have nuclear power plants in the US which produce weapons grade spent fuel.
Unfortunately, they've outsourced their security to a company called 'OBL Security, Inc.', headquartered on the Pakistani/Afghan border.
So I take it you've never driven a Suburban? ;)
Solar takes a lot of space and puts out a lot less power. It's also costlier. And the process of manufacturing solar panels is horrible for the environment.
Nuclear power is, believe it or not, the cleanest technology we have available, even if you consider the highly radioactive waste and the (typically minute) risk of meltdown.
Not to mention four-assed monkeys.
supposedly self-regulating so it won't go critical
Supposedly? Whaddya mean 'supposedly'? Look, if this thing is gonna be buried in MY backyard, I want a LOT MORE than 'supposedly'.
I can only assume this means you have never heard of 2chan.
'sudo -s --' works just as well, without the need to set a password for root.
wut? I like it!
Chicka-chicka-bow-wow, chicka-chicka bonk bonk....
I will, but I gotta P first!
I wish Sony would abandon their silly roll-their-own video service and offer this via the PS3.
Sony owns half of Hollywood (Disney owns the other half). Why should they?
1 Hour Genome Sequencing: 30,000 errors or less or YOUR MONEY BACK!
Sub-$1000 genome sequencing will put the creation of 'designer' kids into the realm of the affordable for much of the middle class. Scary stuff. Now we just need to combine that with cheap and reliable cloning techniques and my plans for world domination will be comlete!
When Sculley took over, Apple had other computer products than the Macintosh, including the Apple II line, and there were other machines on the horizon. In the end, the Macintosh became the main computer line largely because it was the most successful.
Find a company or product that will not immediately collapse when its founder dies or retires.
Except that there was a long period of time between about 1985 and 1998 or so that Jobs was no longer associated with Apple. That's what? Almost 15 years?
Apple didn't immediately collapse and the Macintosh line existed and was largely successful in niche markets without Jobs.
No, Apple doesn't need Jobs, but I think that without Jobs, Apple would lose its sense of direction.
Sculley had the the thing running into the ground well before Spindler came along to piss on Apple's fresh grave. Amelio, believe it or not, was relatively good for Apple -- it was through his efforts that Apple bought NeXT and brought Jobs on board.
Right, but he wasn't picked as a successor. Sculley was to run the day-to-day stuff, leaving Jobs to be the 'visionary leader' over the Macintosh project. Later, it was Sculley who forced Jobs out, mostly because Jobs was trying to basically set the Macintosh group up as totally independent from the rest of the company.
Ummmm...shouldn't that be 0 then?
Exactly. But this is what happens -- we want what I call a 'McWorld'. What I mean by that is that we seem to want to put some monkey behind a computer, have them enter a few pieces of information, and spit out a simple answer. No brains, no real skills -- just need someone who can fog a mirror. When you boil everything down to fully-automatic, all-I-need-is-a-mirror-fogger-in-the-seat type of McWorld like that, you get the same results you get at McDonald's -- it works 'good enough' for many, but almost certainly isn't the 'best' product for anybody.
True, but because poster mentions he wants to move from ARM to Atom, that also implies he is moving to a more modern SBC.
Probably, but I wouldn't bet it would be necessarily quadrupling. All sorts of memory configurations are still available. For instance, is the device battery powered? If so, he might order one with less available memory to conserve battery life.
They're intentionally trying to differentiate the versions. It's obvious. The OSE version doesn't have a GUI, doesn't support USB, doesn't support a virtual SATA adapter, doesn't support VRDP, etc.
OTOH, the code is 6 years old, and from what I gather reading the post, it's stable and mature. OTOH, my guess is that if the article poster has written his code in a fairly portable way, it will compile without too much modification on GCC 3.x or 4.x and will run under the newer versions on glibc on a 2.6 kernel.
On the gripping hand, keep in mind that for embedded applications that memory is usually at a premium and the memory footprint of 2.4 is significantly smaller than the 2.6 kernel. Keep in mind that lots of embedded applications are still using a 2.4 kernel and some embedded applications even continue to use MS-DOS or FreeDOS.
I guess if I were making this decision, I'd try to compile and run my code on newer Linux distro in a sandbox to see how much work it would take to make it compile and run in the new environment. Then I'd see how much bigger a custom-built 2.6 kernel is than the existing 2.4 kernel, optimizing the kernel configuration for size and memory consumption, of course.
That work should take no longer than a couple of days.
If it doesn't work out, you can go back to your existing 2.4 configuration. *shrug*
What do you have to lose?