Do you have a unamemod script that I could use or modify. I am not all that familiar with bash scripting. I may have to generate results for other options, such as uname -a or uname -n, -v, etc. The install scripts are buried in compressed tar files, so I'm not sure which uname commands I will have to generate. I think, I could just modify the uname -r or -a commands to put out the correct kernel version, and then pass the rest on to the actual uname program. Does this make sense? Thanks, -cm On Mon, 2006-03-20 at 09:30 +1100, Cameron Simpson wrote: > On 19Mar2006 22:57, Mostafa Z. Afgani <mostafa.afgani@xxxxxxxxxxxxxxxxxx> wrote: > | Mostafa Z. Afgani wrote: > | >2. From your shell > | > $ alias uname='/tmp/unamemod' > | >done. Now $(uname -r) from that console will report 2.4.20 > | > | Oops .. looks like I spoke too soon <embarrassed> .. won't work when > | uname is called from a script .. > > Yep. > > | So, as Craig said, modifying the script > | is your best bet .. of course you could still create the unamemod script > | and then link that to /bin/uname temporarily -- but I guess that's more > | trouble than it's worth ;) > > I have on occasion made a /tmp/bin/uname script as you describe and > put /tmp/bin at the front of $PATH. It is easier to modify the install > script usually, but I have had to deal with things whose install scripts > unpack archives that contain install scripts, and so it's easier to put > a special uname (or whatever) in and hack $PATH. > > Cheers, > -- > Cameron Simpson <cs@xxxxxxxxxx> DoD#743 > http://www.cskk.ezoshosting.com/cs/ > > Newtons 4th law: > For every action there is an equal and opposite beaureaucratic policy. > - Adrian Tritschler, ajft@xxxxxxxxxxxxx >
