It’s surprising to see people surprised by the fact that even a Linux installation disc is running a full multitasking OS, not some cut-down restricted toy. So being able to enter data while other stuff is happening in the background is just par for the course <http://www.zdnet.com/blog/hardware/first-look-ubuntu-1104-natty-narwh...>.
> It’s surprising to see people surprised by the fact that even a Linux > installation disc is running a full multitasking OS, not some cut-down > restricted toy. So being able to enter data while other stuff is happening > in the background is just par for the course > <http://www.zdnet.com/blog/hardware/first-look-ubuntu-1104-natty-narwh...>.
> On 4/2/2011 3:09 AM, Lawrence D'Oliveiro wrote: >> It’s surprising to see people surprised by the fact that even a Linux >> installation disc is running a full multitasking OS, not some cut-down >> restricted toy. So being able to enter data while other stuff is >> happening >> in the background is just par for the course >> <http://www.zdnet.com/blog/hardware/first-look-ubuntu-1104-natty-narwh...>.
>> Can’t other systems do this?
The big innovator of Ubuntu is..........., guess! HINT: "Windows snapping by dragging windows to screen edges (a la *Windows* *7* ).
<sigh, why do they have to copy almost every feature of Windows?>
On Sat, 2 Apr 2011 19:48:19 +0200, Clogwog wrote: > "Big Steel" <Steel...@990Steel.com> schreef in bericht > news:n-2dnQYzkP0ulQrQnZ2dnUVZ_ridnZ2d@earthlink.com... >> On 4/2/2011 3:09 AM, Lawrence D'Oliveiro wrote: >>> It¢s surprising to see people surprised by the fact that even a Linux >>> installation disc is running a full multitasking OS, not some cut-down >>> restricted toy. So being able to enter data while other stuff is >>> happening >>> in the background is just par for the course >>> <http://www.zdnet.com/blog/hardware/first-look-ubuntu-1104-natty-narwh...>.
>>> Can¢t other systems do this?
> The big innovator of Ubuntu is..........., guess! > HINT: "Windows snapping by dragging windows to screen edges (a la *Windows* > *7* ).
> <sigh, why do they have to copy almost every feature of Windows?>
>> I have always found this a huge plus of distros that come as a Live >> CD/DVD by default. Whenever I install Ubuntu on one of our lab PCs at >> work, I can connect to our online system database to make the entry >> for the system I'm installing /while/ it's installing. So sweet.
> I'm curious why this is even a manual step?
> At my house for example I have a domain controller with various power-on > and log-on scripts that run automatically whenever a computer boots up or > a user logs into the network.I've automated these scripts to the point > where my Postgres database gets populated automatically with exactly this > sort of data.
Linux distros offer features like “KickStart” or “AutoYAST” to save you the trouble.
>>> I have always found this a huge plus of distros that come as a Live >>> CD/DVD by default. Whenever I install Ubuntu on one of our lab PCs at >>> work, I can connect to our online system database to make the entry >>> for the system I'm installing /while/ it's installing. So sweet.
>> I'm curious why this is even a manual step?
>> At my house for example I have a domain controller with various power-on >> and log-on scripts that run automatically whenever a computer boots up or >> a user logs into the network.I've automated these scripts to the point >> where my Postgres database gets populated automatically with exactly this >> sort of data.
>Linux distros offer features like “KickStart” or “AutoYAST” to save you the >trouble.
Huh??? Save me the trouble of what exactly?????
How in the world are KickStart and AutoYAST even close to what I just described?
>>>> I have always found this a huge plus of distros that come as a Live >>>> CD/DVD by default. Whenever I install Ubuntu on one of our lab PCs at >>>> work, I can connect to our online system database to make the entry >>>> for the system I'm installing /while/ it's installing. So sweet.
>>> I'm curious why this is even a manual step?
>>> At my house for example I have a domain controller with various power-on >>> and log-on scripts that run automatically whenever a computer boots up or >>> a user logs into the network.I've automated these scripts to the point >>> where my Postgres database gets populated automatically with exactly this >>> sort of data.
>>Linux distros offer features like ´KickStart¡ or ´AutoYAST¡ to save you the >>trouble.
> Huh??? Save me the trouble of what exactly?????
> How in the world are KickStart and AutoYAST even close to what I just > described?
They aren't. Olive Oil is obviously totally and completely lost in the web of technology. As usual.
BTW You sound like the ultimate geek!!!!!! Cool!!! Hahahaha -- flatfish+++ Please visit our hall of Linux idiots. http://linuxidiots.blogspot.com/
>>>>> I have always found this a huge plus of distros that come as a Live >>>>> CD/DVD by default. Whenever I install Ubuntu on one of our lab PCs at >>>>> work, I can connect to our online system database to make the entry >>>>> for the system I'm installing /while/ it's installing. So sweet.
>>>> I'm curious why this is even a manual step?
>>>> At my house for example I have a domain controller with various >>>> power-on >>>> and log-on scripts that run automatically whenever a computer boots up >>>> or >>>> a user logs into the network.I've automated these scripts to the point >>>> where my Postgres database gets populated automatically with exactly >>>> this >>>> sort of data.
>>>Linux distros offer features like ´KickStart¡ or ´AutoYAST¡ to save you >>>the >>>trouble.
>> Huh??? Save me the trouble of what exactly?????
>> How in the world are KickStart and AutoYAST even close to what I just >> described?
>They aren't. >Olive Oil is obviously totally and completely lost in the web of >technology. >As usual.
It reminded me one time when I asked Rex for proof for some of his ridiculous claims. His "proof" was a bunch of random links to sites that really didn't have much of anything to do with proving what he wrote. But he figured that if he threw out enough random links then it's good enough.
In this case tossing out a few unrelated products and claiming it'll save the the trouble looks like the same thing. What KickStart and AutoYAST do is nice... but it's not nearly the same thing.
>BTW You sound like the ultimate geek!!!!!! >Cool!!! >Hahahaha
It's an obsession. But I'm not nearly as bad as I used to be. Every winter I get bored (short days, cold weather, etc) so I leave the TV set on in the background, grab my computer and do a "project." I can enjoy tinkering, it gives me a chance to learn a thing or two and I have something interesting when I'm all done.
>>>>>> I have always found this a huge plus of distros that come as a Live >>>>>> CD/DVD by default. Whenever I install Ubuntu on one of our lab PCs at >>>>>> work, I can connect to our online system database to make the entry >>>>>> for the system I'm installing /while/ it's installing. So sweet.
>>>>> I'm curious why this is even a manual step?
>>>>> At my house for example I have a domain controller with various >>>>> power-on >>>>> and log-on scripts that run automatically whenever a computer boots up >>>>> or >>>>> a user logs into the network.I've automated these scripts to the point >>>>> where my Postgres database gets populated automatically with exactly >>>>> this >>>>> sort of data.
>>>>Linux distros offer features like ´KickStart¡ or ´AutoYAST¡ to save you >>>>the >>>>trouble.
>>> Huh??? Save me the trouble of what exactly?????
>>> How in the world are KickStart and AutoYAST even close to what I just >>> described?
>>They aren't. >>Olive Oil is obviously totally and completely lost in the web of >>technology. >>As usual.
> It reminded me one time when I asked Rex for proof for some of his > ridiculous claims. His "proof" was a bunch of random links to sites that > really didn't have much of anything to do with proving what he wrote. But he > figured that if he threw out enough random links then it's good enough.
> In this case tossing out a few unrelated products and claiming it'll save > the the trouble looks like the same thing. What KickStart and AutoYAST do > is nice... but it's not nearly the same thing.
Rex uses a tactic based upon overloading the person questioning him with information hoping that the person won't actually check.
Roy Schestowitz uses the same tactic with his SPAM bots.
>>BTW You sound like the ultimate geek!!!!!! >>Cool!!! >>Hahahaha
> It's an obsession. But I'm not nearly as bad as I used to be. Every winter I > get bored (short days, cold weather, etc) so I leave the TV set on in the > background, grab my computer and do a "project." I can enjoy tinkering, it > gives me a chance to learn a thing or two and I have something interesting > when I'm all done.
Cool! I wish I could do stuff like that! Programming and me are like oil and water. We don't mix well :(
>>>> I have always found this a huge plus of distros that come as a Live >>>> CD/DVD by default. Whenever I install Ubuntu on one of our lab PCs at >>>> work, I can connect to our online system database to make the entry >>>> for the system I'm installing /while/ it's installing. So sweet.
>>> I'm curious why this is even a manual step?
>>> At my house for example I have a domain controller with various power-on >>> and log-on scripts that run automatically whenever a computer boots up >>> or a user logs into the network.I've automated these scripts to the >>> point where my Postgres database gets populated automatically with >>> exactly this sort of data.
>>Linux distros offer features like “KickStart” or “AutoYAST” to save you >>the trouble.
> Huh??? Save me the trouble of what exactly?????
All that nonsense you had to go through.
> How in the world are KickStart and AutoYAST even close to what I just > described?
They scale up to thousands, even tens of thousands of machines, which your Windows scripts will not.
On Sun, 03 Apr 2011 12:29:50 +1200, Lawrence D'Oliveiro wrote: > Linux distros offer features like “KickStart” or “AutoYAST” to save > you the trouble.
Red Hat's kickstart is very nice. I've just had to install 7 new linux servers at work. The app they will run is currently supported on RHES 4.7 32bit (also 32 bit on windows, they only support SunOS 64bit).
They will support 64bit on their next SP and, so they tell us also RHES 5.5. This is imminent and the project timescale gives me the time to evaluate the 3 versions. So with kickstart I have installed RHES 4.7 32bit and 64 bit and and RHES 5.5 64 bit on these systems.
One simple boot command to install each OS version which takes < 10 minutes for each. Only manual thing I had to do was copy paste the grub menu.lst config to present all 3 OS choices at boot. This was all done using HP's iLO java console from my office Linux desktop system.
Clogwog wrote: > The big innovator of Ubuntu is..........., guess! > HINT: "Windows snapping by dragging windows to screen edges (a la > *Windows* *7* ).
Compiz and Grid plugin predate Windows 7 window snapping feature, and is more flexible and configurable. Also you are confusing Ubuntu innovation with upstream projects' innovation.
> <sigh, why do they have to copy almost every feature of Windows?>
>>>> At my house for example I have a domain controller with various >>>> power-on >>>> and log-on scripts that run automatically whenever a computer boots up >>>> or a user logs into the network.I've automated these scripts to the >>>> point where my Postgres database gets populated automatically with >>>> exactly this sort of data.
>>>Linux distros offer features like “KickStart” or “AutoYAST” to save you >>>the trouble.
>> Huh??? Save me the trouble of what exactly?????
>All that nonsense you had to go through.
>> How in the world are KickStart and AutoYAST even close to what I just >> described?
>They scale up to thousands, even tens of thousands of machines, which your >Windows scripts will not.
You're not very bright. For starters there is no reason why my scripts wouldn't scale to thousands of users but that's not the point.
What my scripts do (from my earlier post) is:
<quote> Things that get recorded are:
the hardware inventory free disk space any hardware or system errors, etc.
If a hardware configuration changes - I get notified. If a new device driver is installed - I get notified. If a computer starts getting low on disk space, is having hardware errors, system errors or is missing service packs or is running an old version of Flash... I get notified. </quote>
So do tell me *exactly* how AutoYast or KickStart would automatically record the hardware inventory in a database. Or notify me if the hardware in a machine changes. How would AutoYast or Kickstart tell me if a machine is low on diskspace or if a machine is having hardware errors or system errors.
And don't make up shit either... the way you did when you made an idiotic claim of how embedded Python only supports a limited subset of regular Python.
>>They scale up to thousands, even tens of thousands of machines, which your >>Windows scripts will not.
> For starters there is no reason why my scripts wouldn't scale to thousands > of users ...
One obvious reason is how you do remote execution. On Linux/Unix systems, you can take just about any local command
cmd
and execute it on a remote host as follows:
ssh remote_host cmd
whereas on Windows you can’t. The best PowerShell can manage is to use the complex and clumsy WMI functions to perform tasks on remote machines, which is completely different from how they’re done locally.
>>>They scale up to thousands, even tens of thousands of machines, which >>>your >>>Windows scripts will not.
>> For starters there is no reason why my scripts wouldn't scale to >> thousands >> of users ...
> One obvious reason is how you do remote execution.
Nice attempt at snip and run. Then again, you were simply talking out your ass so it's no wonder you did this. Here... let me restore what you snipped and ran away from:
<quote> What my scripts do (from my earlier post) is:
<quote> Things that get recorded are:
the hardware inventory free disk space any hardware or system errors, etc.
If a hardware configuration changes - I get notified. If a new device driver is installed - I get notified. If a computer starts getting low on disk space, is having hardware errors, system errors or is missing service packs or is running an old version of Flash... I get notified. </quote>
So do tell me *exactly* how AutoYast or KickStart would automatically record the hardware inventory in a database. Or notify me if the hardware in a machine changes. How would AutoYast or Kickstart tell me if a machine is low on diskspace or if a machine is having hardware errors or system errors.
>>> They scale up to thousands, even tens of thousands of machines, which your >>> Windows scripts will not.
>> For starters there is no reason why my scripts wouldn't scale to thousands >> of users ...
> One obvious reason is how you do remote execution. On Linux/Unix systems, > you can take just about any local command
> cmd
> and execute it on a remote host as follows:
> ssh remote_host cmd
> whereas on Windows you can’t. The best PowerShell can manage is to use the > complex and clumsy WMI functions to perform tasks on remote machines, which > is completely different from how they’re done locally.
LOL... You are an idiot. PowerShell v2 lets you create remote sessions you dolt. You are stuck in v1.
>>>They scale up to thousands, even tens of thousands of machines, which your >>>Windows scripts will not.
>> For starters there is no reason why my scripts wouldn't scale to thousands >> of users ...
> One obvious reason is how you do remote execution. On Linux/Unix systems, > you can take just about any local command
> cmd
> and execute it on a remote host as follows:
> ssh remote_host cmd
> whereas on Windows you can???t. The best PowerShell can manage is to use the > complex and clumsy WMI functions to perform tasks on remote machines, which > is completely different from how they???re done locally.
We have Erik Funkenbusch in here awhile back crooning about the glories of Powershell, where remote support is built into the shell at both ends.
ssh? Once you've got that, you've got all the remote support you need. No need for implementing a specific, limited set of commands that are capable of being remoted. With ssh any command-line command can be remoted, and its return status used to make a decision.
And with clusterssh? Fergeddaboudid, winbois.
-- Horses
When a nation follows the Way, Horses bear manure through its fields; When a nation ignores the Way, Horses bear soldiers through its streets. There is no greater mistake than following desire; There is no greater disaster than forgetting contentment; There is no greater sickness than seeking attainment; But one who is content to satisfy his needs Finds that contentment endures. -- Lao Tse, "Tao Te Ching"
>>>> They scale up to thousands, even tens of thousands of machines, which your >>>> Windows scripts will not.
>>> For starters there is no reason why my scripts wouldn't scale to thousands >>> of users ...
>> One obvious reason is how you do remote execution. On Linux/Unix systems, >> you can take just about any local command
>> cmd
>> and execute it on a remote host as follows:
>> ssh remote_host cmd
>> whereas on Windows you can???t. The best PowerShell can manage is to use the >> complex and clumsy WMI functions to perform tasks on remote machines, which >> is completely different from how they???re done locally.
> LOL... You are an idiot. PowerShell v2 lets you create remote sessions > you dolt. You are stuck in v1.
One common problem is ERROR: Access is denied. Solution: Launch PowerShell with elevated rights, in simple language: Run as administrator.
Security experts will hold up the hands in horror at this suggestion, but if you get the error message: "The rpc server is unavailable", then I suggest that you turn off the firewall on both machines.
> In message <inb7gj$t...@dont-email.me>, Ezekiel wrote:
>> Nice attempt at snip and run.
> Nice attempt at moving the goalposts.
You're such a clueless idiot always talking about shit that you don't understand at all.
Larry - "Linux distros offer features like "KickStart" or "AutoYAST" to save you the trouble."
What my scripts do (from my earlier post) is:
Things that get recorded are:
the hardware inventory free disk space any hardware or system errors, etc.
If a hardware configuration changes - I get notified. If a new device driver is installed - I get notified. If a computer starts getting low on disk space, is having hardware errors, system errors or is missing service packs or is running an old version of Flash... I get notified. </quote>
So do tell me *exactly* how AutoYast or KickStart would automatically record the hardware inventory in a database. Or notify me if the hardware in a machine changes. How would AutoYast or Kickstart tell me if a machine is low on diskspace or if a machine is having hardware errors or system errors.
>>>>> They scale up to thousands, even tens of thousands of machines, which >>>>> your Windows scripts will not.
>>>> For starters there is no reason why my scripts wouldn't scale to thousands >>>> of users ...
>>> One obvious reason is how you do remote execution. On Linux/Unix systems, >>> you can take just about any local command
>>> cmd
>>> and execute it on a remote host as follows:
>>> ssh remote_host cmd
>>> whereas on Windows you can???t. The best PowerShell can manage is to use >>> the complex and clumsy WMI functions to perform tasks on remote machines, >>> which is completely different from how they???re done locally.
>> LOL... You are an idiot. PowerShell v2 lets you create remote sessions >> you dolt. You are stuck in v1.
> One common problem is ERROR: Access is denied. > Solution: Launch PowerShell with elevated rights, in simple language: Run > as administrator.
> Security experts will hold up the hands in horror at this suggestion, but > if you get the error message: "The rpc server is unavailable", then I > suggest that you turn off the firewall on both machines.
> Reinventing ssh/sshd, badly.
I have set this up on many machines and I have never had to run with elevated privledges nor turn off the firewall... Obviously, I had to be an admin to install ps and I had to be an admin to configure remote access - but, never beyond that.
I don't believe that his "problems" are common in anyway, or I think I would have seen it by now.
On Mon, 04 Apr 2011 06:19:53 -0400, Chris Ahlstrom wrote: > ssh? Once you've got that, you've got all the remote support you > need. No need for implementing a specific, limited set of commands > that are capable of being remoted. With ssh any command-line > command can be remoted, and its return status used to make a > decision.
Don't forget port tunneling in either direction, a pseudo X server which tunnels a remote X client, running another ssh to run commands on systems you cannot get to directly. Combine ssh and screen and you don't even need to keep the ssh session open to the remote machine. You can reconnect later like from home after work.
