Re: neat? bash stuff that I didn't know.
John McKown wrote:
OK, likely another you didn't know that?!? type observation. But I found
it interesting anyway.
First: using redirection to write to or read from an IP port
command /dev/tcp/${HOST}/${PORT}
News to me. Filed for future trial and use.
will establish a TCP connection to ${PORT} on ${HOST}. Replace
/dev/tcp/... with /dev/udp/... and it will do udp instead of tcp. This
redirects stdout. Of course, using instead of will redirect stdin and
do a read. So, if you like netcat to send some data ala
command | nc ${HOST} ${PORT}
you can use the above redirection instead and
command /dev/tcp/${HOST}/${PORT}
instead of
nc -l ${HOST} ${PORT} | command
NBD - but it saves forking a process.
but how does one carry on a sensible conversation? I can send stuff to
sendmail, but how do I get its responses?
16:23 [sum...@bobtail ~]$ ls -l /dev/tcp/ns
ls: /dev/tcp/ns: No such file or directory
16:24 [sum...@bobtail ~]$ ls -l /dev/tcp/ns:22
ls: /dev/tcp/ns:22: No such file or directory
16:24 [sum...@bobtail ~]$ echo /dev/tcp/ns:22
/dev/tcp/ns:22
16:24 [sum...@bobtail ~]$ echo /dev/tcp/ns:22
bash: /dev/tcp/ns:22: No such file or directory
16:24 [sum...@bobtail ~]$ echo /dev/tcp/ns/22
16:24 [sum...@bobtail ~]$ echo /dev/tcp/ns/25
16:24 [sum...@bobtail ~]$ echo /dev/tcp/ns/25 | cat /dev/tcp/ns/25
cat: /dev/tcp/ns/25: No such file or directory
16:25 [sum...@bobtail ~]$ echo /dev/tcp/ns/25 | cat /dev/tcp/ns/25
220 ns.demo.lan ESMTP Postfix
16:25 [sum...@bobtail ~]$ cat /dev/tcp/ns/25
[1] 14558
16:25 [sum...@bobtail ~]$ 220 ns.demo.lan ESMTP Postfix
echo quit /dev/tcp/ns/25
16:25 [sum...@bobtail ~]$
16:25 [sum...@bobtail ~]$ echo quit /dev/tcp/ns/25
16:25 [sum...@bobtail ~]$
===
( command ) and ( command )
Another nifty, similar to doing $( command ), except that the command
input for ( command ) or command output for ( command ) is available
for writing by the outer command via a /dev/fd/n file or the command
input for ( command ) is available for reading by the outer command via
a /dev/fd/n.
Although this is an interesting way to pipe, I already have a work
around.
Example:
cmd1 infile1 infile2 infile3 ( cmd2 )
assumes cmd1 cannot write its output to stdout, so a normal pipe won't
work. But it can be done via:
cmd1 infile1 infile2 infile3 /dev/fd1 | cmd2
cmd1 ( cmd2 ) ..parms...
can be be done via:
cmd2 | cmd1 /dev/fd/0 ...parms...
I think this sort of thing is a bit OS-dependent. It works with some
(2.4 and later I suspect) Linux kernels, likely not with *BSD, Solaris
and such, but I don't have any alternative systems to test on.
where cmd1 cannot read its input from stdin for some reason.
Of course if you need more than one, the above work arounds don't work,
such as:
cmd1 infile1 infile2 outfile1 outfile2
could be
cmd1 ( cmd2 ) ( cmd3 ) ( cmd4 ) ( cmd5 )
The above I know about and, on occasion I've fed two streams into diff.
There is also this:
generateSomeStuff | tee /dev/tty | consumeSomeStuff
which only works when there's a tty available (ie not do daemonised
processes)
and
could be combined with 1 above to log what's sent or received.
There is also this:
(echo 5) 5tempfile
where tempfile could be something above. I've used this sometimes in
scripts: think of any kind of program that produces more than one report
and you will find a use.
Copy this into your bash session:
\rm tempfile ;(ls -l 5) 5tempfile;ls -l tempfile
For more,
man bash
and look for
redirection
process substitution
command substitution
Some of the material there is new to me, I assume it's new in bash 3.x.
--
Cheers
John
-- spambait
1...@coco.merseine.nu z1...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: neat? bash stuff that I didn't know.
On 02/27/2009 09:28 AM, John Summerfield wrote:
John McKown wrote:
First: using redirection to write to or read from an IP port
command /dev/tcp/${HOST}/${PORT}
but how does one carry on a sensible conversation? I can send stuff to
sendmail, but how do I get its responses?
See bftpget (an ftp client with bash-builtins only) in
ftp://ftp.heise.de/pub/ct/listings/0702-178.zip
(from an article in a german journal which is unfortunately not freely
available on the net:
http://www.heise.de/kiosk/archiv/ct/2007/2/178_kiosk).
16:23 [sum...@bobtail ~]$ ls -l /dev/tcp/ns
ls: /dev/tcp/ns: No such file or directory
16:24 [sum...@bobtail ~]$ ls -l /dev/tcp/ns:22
ls: /dev/tcp/ns:22: No such file or directory
AFAIK, these are pseudo files handled internally by bash, so they won't
appear in the file system.
( command ) and ( command )
[snip]
via a /dev/fd/n.
Bash meanwhile implements process substitution by means of /dev/fd,
optionally by means of named pipes (FIFOs).
I think this sort of thing is a bit OS-dependent. It works with some
(2.4 and later I suspect) Linux kernels, likely not with *BSD, Solaris
and such, but I don't have any alternative systems to test on.
Linux implements /dev/fd as a symlink to /proc/self/fd.
I found /dev/fd/... available on Solaris 10 (on Sparc) implemented with
character devices.
(echo 5) 5tempfile
where tempfile could be something above. I've used this sometimes in
scripts: think of any kind of program that produces more than one report
and you will find a use.
Redirection of arbitrary file descriptors is very handy, especially in
combination with the exec shell builtin. E.g., configure from autoconf
makes heavy use of it.
Steffen
Linux on System z Development
IBM Deutschland Research Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: neat? bash stuff that I didn't know.
To get data back from a network daemon using this technique is quite
trivial, if you are using an X windows desktop. Simply open up two
xterms.
xterm 1:
# tee rx.log /dev/tcp/host/port
xterm 2:
# echo arbitrary message| tee tx.log /dev/tcp/host/port
Send whatever you want to your remote host, and watch the response
spew out on your terminal. You can also go back through the logs
later if you like.
Erik Johnson
On Fri, Feb 27, 2009 at 7:09 AM, Steffen Maier ma...@linux.vnet.ibm.com wrote:
On 02/27/2009 09:28 AM, John Summerfield wrote:
John McKown wrote:
First: using redirection to write to or read from an IP port
command /dev/tcp/${HOST}/${PORT}
but how does one carry on a sensible conversation? I can send stuff to
sendmail, but how do I get its responses?
See bftpget (an ftp client with bash-builtins only) in
ftp://ftp.heise.de/pub/ct/listings/0702-178.zip
(from an article in a german journal which is unfortunately not freely
available on the net:
http://www.heise.de/kiosk/archiv/ct/2007/2/178_kiosk).
16:23 [sum...@bobtail ~]$ ls -l /dev/tcp/ns
ls: /dev/tcp/ns: No such file or directory
16:24 [sum...@bobtail ~]$ ls -l /dev/tcp/ns:22
ls: /dev/tcp/ns:22: No such file or directory
AFAIK, these are pseudo files handled internally by bash, so they won't
appear in the file system.
( command ) and ( command )
[snip]
via a /dev/fd/n.
Bash meanwhile implements process substitution by means of /dev/fd,
optionally by means of named pipes (FIFOs).
I think this sort of thing is a bit OS-dependent. It works with some
(2.4 and later I suspect) Linux kernels, likely not with *BSD, Solaris
and such, but I don't have any alternative systems to test on.
Linux implements /dev/fd as a symlink to /proc/self/fd.
I found /dev/fd/... available on Solaris 10 (on Sparc) implemented with
character devices.
(echo 5) 5tempfile
where tempfile could be something above. I've used this sometimes in
scripts: think of any kind of program that produces more than one report
and you will find a use.
Redirection of arbitrary file descriptors is very handy, especially in
combination with the exec shell builtin. E.g., configure from autoconf
makes heavy use of it.
Steffen
Linux on System z Development
IBM Deutschland Research Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Strange LVM Device Mapper messages
Dmesg doesn't give any new clues that I can tell. The underlying hardware is an EMC DMX2000 array, which is a RAID box of some type. zlinuxhdxgwdev1:/etc/cron.daily # dmesg Linux version 2.6.16.60-0.27-default (ge...@buildhost) (gcc version 4.1.2 20070115 (SUSE Linux)) #1 SMP Mon Jul 28 13:08:09 UTC 2008 We are running under VM (64 bit mode) Detected 1 CPU's Boot cpu address 0 On node 0 totalpages: 65536 DMA zone: 65536 pages, LIFO batch:15 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 0 pages, LIFO batch:0 HighMem zone: 0 pages, LIFO batch:0 Built 1 zonelists Kernel command line: root=/dev/dasda1 dasd=100-101,300-301 vmpoff=LOGOFF TERM=dumb BOOT_IMAGE=0 PID hash table entries: 2048 (order: 11, 65536 bytes) Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Memory: 243260k/262144k available (4749k kernel code, 0k reserved, 2015k data, 212k init) Calibrating delay loop... 3643.80 BogoMIPS (lpj=18219008) Security Framework v1.0.0 initialized Mount-cache hash table entries: 256 checking if image is initramfs... it is Freeing initrd memory: 3115k freed cpu 0 phys_idx=0 vers=FF ident=09CD13 machine=2097 unused=8000 Brought up 1 CPUs migration_cost=1000 NET: Registered protocol family 16 debug: Initialization complete cio: Channel measurements not available, continuing. audit: initializing netlink socket (disabled) audit(1235057434.788:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered (default) io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 Channel measurement facility using extended format (autodetected) NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 16384 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered NET: Registered protocol family 1 Freeing unused kernel memory: 212k freed dasd(eckd): 0.0.0100: 3390/0C(CU:3990/01) Cyl:3338 Head:15 Sec:224 dasd(eckd): 0.0.0100: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasda:VOL1/ 0X0100: dasda1 dasda2 dasd(eckd): 0.0.0101: 3390/0C(CU:3990/01) Cyl:3338 Head:15 Sec:224 dasd(eckd): 0.0.0101: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasdb:VOL1/ 0X0101: dasdb1 dasd(fba): 0.0.0300: 9336/10(CU:6310/80) 32MB at(512 B/blk) dasdc:CMS1/ LXSWAP(MDSK): dasdc1 kjournald starting. Commit interval 5 seconds EXT3 FS on dasda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 32484k swap on /dev/dasdc1. Priority:-1 extents:1 across:32484k device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-de...@redhat.com dm-netlink version 0.0.2 loaded vmur: z/VM virtual unit record device driver loaded. qdio: loading QDIO base support version 2 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver qeth: loading qeth S/390 OSA-Express driver qeth: Device 0.0.0900/0.0.0901/0.0.0902 is a Guest LAN QDIO card (level: V532) with link type GuestLAN QDIO (portname: dontcare) qeth: Hardware IP fragmentation not supported on eth0 qeth: VLAN enabled qeth: Multicast enabled qeth: IPV6 enabled qeth: Broadcast enabled qeth: Using SW checksumming on eth0. qeth: Outbound TSO not supported on eth0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. loop: loaded (max 8 devices) kjournald starting. Commit interval 5 seconds EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. eth0: no IPv6 routers present device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table process `sitar' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time; Use net.ipv6.neigh.default.base_reachable_time_ms instead. device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper: ioctl: error adding target to table device-mapper: table: 253:4: mirror: Device lookup failure device-mapper:
SLES11
http://distrowatch.com/?newsid=05349 http://www.novell.com/linux/releasenotes/x86_64/SUSE-SLES/11/#s390x Looks like Z9 processor or newer Ann Smith Mainframe Systems Support -zVM and zLinux Support Integrated Technology Delivery IBM Global Service Integrated Operations At The Hartford Work phone: 860-547-6110 Pager: 800-204-6367 Email: mailto:ann.sm...@thehartford.com This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES11
On Fri, 27 Feb 2009 12:51:01 -0500 Smith, Ann (ISD, IT) said: http://www.novell.com/linux/releasenotes/x86_64/SUSE-SLES/11/#s390x Looks like Z9 processor or newer This is really BAD NEWS. It basically says that if you want to stay current, you better be able to afford to buy a new processor. Why does it have to be like this? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES11
On Fri, Feb 27, 2009 at 01:27:45PM -0500, Aria Bamdad wrote: It basically says that if you want to stay current, you better be able to afford to buy a new processor. Why does it have to be like this? The short answer is because IBM is _not_ a non-profit corporation. The longer answer involves the costs to IBM of supporting older platforms versus the income those platforms generate. Or was the question retorical? -- May the LORD God bless you exceedingly abundantly! Dave Craig - - - - - - - - - - - - - - - - - - - - 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' --from _Nightfall_ by Asimov/Silverberg -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
zLinux / Oracle Conference
If anyone is interested in Oracle on zLinux, this conference: http://www.zseriesoraclesig.org/; would be of great interest. It will be a pretty intense week, and for the price is one of the best price performers in the conference calender. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 begin:vcard fn:Barton Robinson n:Robinson;Barton adr;dom:;;PO 391209;Mountain View;CA;94039-1209 email;internet:bar...@velocitysoftware.com title:Sr. Architect tel;work:650-964-8867 x-mozilla-html:FALSE url:VelocitySoftware.com version:2.1 end:vcard
Re: SLES11
David L. Craig wrote: The short answer is because IBM is _not_ a non-profit corporation. The longer answer involves the costs to IBM of supporting older platforms versus the income those platforms generate. Or was the question retorical? But wait.. The latest developerworks linux stream does not contains such restriction. The only one I see in ... http://www.ibm.com/developerworks/linux/linux390/development_recommended.html .. is that gathering fcp statistics requires a z9 or better. And they support the whole line of z hardware already. So it does not seem to be an IBM decision ! So the only restriction I can see here is one imposed by Novell (by forcing a -mtune or -mcpu=z9 at compile time from what I could gather).. What does Novell have to gain by restricting which z machine SLES 11 may run on ? Restricting to z/Arch (no 31 bit) was already, IMHO, a bad enough restriction.. But cutting itself from its z800/z900/z890/z990 customer base ? And personally, in those trouble days where a lot of businesses have indefinitely postponed hardware upgrades, I find imposing such arbitrary restriction to be very counter-productive. --Ivan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 smime.p7s Description: S/MIME Cryptographic Signature
Re: SLES11
On 2/27/09 3:02 PM, Ivan Warren i...@vmfacility.fr wrote: And they support the whole line of z hardware already. So it does not seem to be an IBM decision ! There's direct influence decisions, and there are indirect influence on decisions. Consider: when IBM releases a new hardware platform, the price of maintenance on the older systems generally goes up. Novell has bills to pay, too, and paying a continually increasing maintenance price (and finding space/power/parts, etc) for a bunch of older systems just so you can stay on older tech a little bit longer (especially if IBM has incentive programs on z10s) doesn't work in the numbers game. You start factoring in how long it takes to test a distribution on multiple platforms (and you have to run the test suites completely on both models of each generation), and that starts to add up to real money. Cutting down to two generations (z9 and z10) cuts that cost by more than half. I'm not saying I like it, but it's pretty clear if you do the math what a real z800 (and it has to be the real thing to satisfy the LPAR/bare metal requirement) costs to maintain vs a shiny new z10. People do enough bitching about licensing prices -- do you really want to pay more? Restricting to z/Arch (no 31 bit) was already, IMHO, a bad enough restriction.. But cutting itself from its z800/z900/z890/z990 customer base ? We made the same decision for OpenSolaris. I don't like it, but I can't afford to keep that many machines running just so some folks can stay in the past. And personally, in those trouble days where a lot of businesses have indefinitely postponed hardware upgrades, I find imposing such arbitrary restriction to be very counter-productive. It's a realistic business decision. Do the math. The result is pretty clear. I'd bet you start seeing some similar testing platform pressure in the Intel space as well, for similar reasons. You can't test everything, and you can't support everything forever. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES11
On Feb 27, 2009, at 2:02 PM, Ivan Warren wrote: What does Novell have to gain by restricting which z machine SLES 11 may run on ? Restricting to z/Arch (no 31 bit) was already, IMHO, a bad enough restriction.. But cutting itself from its z800/z900/z890/z990 customer base ? And personally, in those trouble days where a lot of businesses have indefinitely postponed hardware upgrades, I find imposing such arbitrary restriction to be very counter-productive. And although David has outlined the reasons that vendors may drop support for backlevel hardware (or software), there are *other* vendors from whom you can buy support for those things, if it's important that you have commercial support. Feel free to contact me off-list. Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES11
On Fri, 27 Feb 2009 15:04:55 -0600 Adam Thornton said: And although David has outlined the reasons that vendors may drop support for backlevel hardware (or software), there are *other* vendors from whom you can buy support for those things, if it's important that you have commercial support. Feel free to contact me off-list. Adam I don't think the problem here is support. I think the release notes say that SLES 11 does not even run on non z9/z10 machines. I fully understand that it is difficult an expensive to hang on to older processors and keep on supporting them but you don't have to keep them on maintenance agreements either. If the z800 that you do testing on died, you go out and get a new one for less than the cost of a PC. Aria -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES11
On Feb 27, 2009, at 3:14 PM, Aria Bamdad wrote: On Fri, 27 Feb 2009 15:04:55 -0600 Adam Thornton said: And although David has outlined the reasons that vendors may drop support for backlevel hardware (or software), there are *other* vendors from whom you can buy support for those things, if it's important that you have commercial support. Feel free to contact me off-list. Adam I don't think the problem here is support. I think the release notes say that SLES 11 does not even run on non z9/z10 machines. Fair enough. I was reading it as I want to stay current, but I can't afford new hardware. There are vendors who *will* work with you to, say, leave the original vendor support behind, but move to a more modern codebase, on older hardware, is the position I was trying to get across. Which is to say, SLES 11 doesn't run on z800, but almost all of the software that goes into SLES 11 does. I fully understand that it is difficult an expensive to hang on to older processors and keep on supporting them but you don't have to keep them on maintenance agreements either. If the z800 that you do testing on died, you go out and get a new one for less than the cost of a PC. I think you buy expensive PCs. Either that or the used market in z800s is REALLY cold. What does a used z800 cost these days? Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES11
On Fri, 27 Feb 2009 15:39:26 -0600 Adam Thornton said: I don't think the problem here is support. I think the release notes say that SLES 11 does not even run on non z9/z10 machines. Fair enough. I was reading it as I want to stay current, but I can't afford new hardware. More or less, that is true. The problem with IBM hardware pricing is that if you want to buy an IFL only machine, the will cut you a deal you can't refuse. However, if you have any standard workload that needs a standard CP, then you pay through the nose. There are vendors who *will* work with you to, say, leave the original vendor support behind, but move to a more modern codebase, on older hardware, is the position I was trying to get across. That is good to know and I may have to go that route. Which is to say, SLES 11 doesn't run on z800, but almost all of the software that goes into SLES 11 does. I fully understand that it is difficult an expensive to hang on to older processors and keep on supporting them but you don't have to keep them on maintenance agreements either. If the z800 that you do testing on died, you go out and get a new one for less than the cost of a PC. I think you buy expensive PCs. Either that or the used market in z800s is REALLY cold. What does a used z800 cost these days? Well, I was exaggerating a bit but even today, you can get a low end z800 for maybe less than $10K! Aria. Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: neat? bash stuff that I didn't know.
Erik N Johnson wrote:
To get data back from a network daemon using this technique is quite
trivial, if you are using an X windows desktop. Simply open up two
xterms.
xterm 1:
# tee rx.log /dev/tcp/host/port
xterm 2:
# echo arbitrary message| tee tx.log /dev/tcp/host/port
Send whatever you want to your remote host, and watch the response
spew out on your terminal. You can also go back through the logs
later if you like.
Erik Johnson
Did you try that Erik? Did tried several things of that kind. I think
the problem I had is that it creates two sessions.
On Fri, Feb 27, 2009 at 7:09 AM, Steffen Maier ma...@linux.vnet.ibm.com wrote:
On 02/27/2009 09:28 AM, John Summerfield wrote:
John McKown wrote:
First: using redirection to write to or read from an IP port
command /dev/tcp/${HOST}/${PORT}
but how does one carry on a sensible conversation? I can send stuff to
sendmail, but how do I get its responses?
See bftpget (an ftp client with bash-builtins only) in
ftp://ftp.heise.de/pub/ct/listings/0702-178.zip
(from an article in a german journal which is unfortunately not freely
available on the net:
http://www.heise.de/kiosk/archiv/ct/2007/2/178_kiosk).
16:23 [sum...@bobtail ~]$ ls -l /dev/tcp/ns
ls: /dev/tcp/ns: No such file or directory
16:24 [sum...@bobtail ~]$ ls -l /dev/tcp/ns:22
ls: /dev/tcp/ns:22: No such file or directory
AFAIK, these are pseudo files handled internally by bash, so they won't
appear in the file system.
( command ) and ( command )
[snip]
via a /dev/fd/n.
Bash meanwhile implements process substitution by means of /dev/fd,
optionally by means of named pipes (FIFOs).
I think this sort of thing is a bit OS-dependent. It works with some
(2.4 and later I suspect) Linux kernels, likely not with *BSD, Solaris
and such, but I don't have any alternative systems to test on.
Linux implements /dev/fd as a symlink to /proc/self/fd.
I found /dev/fd/... available on Solaris 10 (on Sparc) implemented with
character devices.
� (echo 5) 5tempfile
where tempfile could be something above. I've used this sometimes in
scripts: think of any kind of program that produces more than one report
and you will find a use.
Redirection of arbitrary file descriptors is very handy, especially in
combination with the exec shell builtin. E.g., configure from autoconf
makes heavy use of it.
Steffen
Linux on System z Development
IBM Deutschland Research Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Gesch�ftsf�hrung: Erich Baier
Sitz der Gesellschaft: B�blingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Cheers
John
-- spambait
1...@coco.merseine.nu z1...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
