NM will
then see your HiperSockets as another "System" connection and manage it for you.
Regards,
Vic
--
Vic Cross
Solutions Engineer, Z Acceleration Team
IBM Z (Worldwide)
E-mail: viccr...@au1.ibm.com Twitter: @viccross
-
be taken around that. I don't have experience
with read-only xfs but a quick search shows some positive results.
Regards,
Vic
--
Vic Cross
Solutions Engineer, Z Acceleration Team
IBM Z (Worldwide)
E-mail: viccr...@au1.ibm.com Twitter: @viccross
-
paddr }}::{{ guest_install_gateway }}:{{
guest_install_netmask }}:{{ guest_install_hostname }}:{{ guest_install_nicid
}}:none
nameserver={{ guest_install_nameserver }}
inst.repo={{ guest_install_baseurl }}/
inst.ks={{ guest_install_ksurl }}/{{guest_install_hostname }}.ks
Regards,
Vic
Vic Cross
Solutions Eng
this system goes live, I'd predict that one of the first questions that
will arise is "why can't I view these documents on my ${PDA}?" I expect that
question would be a lot harder to answer if UNC is used... ;-)
Cheerio,
Vic Cross
environment needs such protection.
I also transposed my client's problem onto your shop -- I thought you were
concerned about the number of pages allocated to VDISKs. That's why I
mentioned the stuff about DELETE/DEFINE of your VDISK swaps.
Best of luck with th
consequences aren't as severe when allocations are more fluid and more
effective sharing is taking place[3]. Unfortunately I haven't used CMM in
anger as I'm a little light on systems to play with nowadays.
Cheerio,
Vic Cross
[1] "Swappiness" controls the likelihood th
other disk vendors might be another way to make things cheaper,
but you'd likely run the risk of becoming unsupported. And, as others
have said, what's cheaper or faster might not necessarily be better (for
various reasons).
Cheerio,
Vic Cross
--
This message has been scanned for vi
On Mon, 2007-04-02 at 16:11 +0200, Rob van der Heij wrote:
> We did it slightly different with an experimental patch to OpenSSH
> that allows for the public keys to be kept in LDAP. That means there's
> only one place where the public key is held. That LDAP server would
> allow the end-user to upl
but convenience (or the lack
thereof) was a barrier. I'm wondering if some little mobile-phone app
that worked over IR or Bluetooth would be a substitute -- people
sometimes take more care of these. ;)
Cheerio,
Vic Cross
[1] Known as OpenSSH-LPK. Used to be hosted by the OpenDarwin project
rejected.
The other thing to check is that all the appropriate NFS support daemons
(portmap, lockd, mountd, statd) are running on both client and server
(rpc.mountd shouldn't be needed on the client, but if something that
*is* needed isn't there you're likely to get strangeness).
> foundSLES-9-s390x
> expected SLES-9-s390x-SP3
>
> linux40:~ #
It's telling you everything you need to know. Your system has installed
versions of the XFree86-Mesa and XFree86-Mesa-32bit packages for which
both SP1 and SP2 had updates. For some reason, these updat
cently did not exhibit the behaviour, i.e.
shutdown -r worked perfectly.
Cheerio,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
For LINUX-390 subscribe
best use of your MIPS, and you are
likely to be disappointed in performance if you try and support a number
of users... However, it's a *great* system to set up to show off how
"Linux is Linux, even on the mainframe"! :)
Cheerio,
Vic Cross
--
This message has been scanned for vi
27;s experience, which I found
via Google, to see if it's relevant:
http://brondsema.net/blog/index.php/2007/02/06/keychain_gpg_agent_pinentry_problems
Cheerio,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
s/ccwgroup/devices/0.0.0f[01]0/layer2
0
1
0f00 is the Layer 3 NIC on this system, 0f10 is Layer 2.
Cheerio,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
ade all the disks present. Rob is lamenting that the DASD driver
is unable to use VOLSER to map disk device to block node (i.e. we're not
able to do something like dasd=L0A201,L0A202,L0A203 on the kernel
command line). Well, maybe lamenting is the wrong word... :)
Cheerio,
Vic Cross
--
This
observant of
your stripe size to see that files did indeed fall across stripe
boundaries and were written across stripe members. Lots of small files
might make this difficult and/or wasteful, but if you have large files
you'd be okay.
Cheerio,
Vic Cross
--
This message has been scanned for viruse
h any attempted writes (the
kernel errors Eric mentioned).
I think what Eric requires is a way to determine if VM has given it to
Linux RO, in order for Linux to activate it the right way... The
hcp/vmcp methods mentioned will be the way to do this.
Cheerio,
Vic Cross
--
This message has b
ndant pathways
to your VIPA [1].
What about Linux on Intel?
Quagga works the same no matter what platform it is built on (subject to
the capabilities of the network hardware of course).
Cheerio,
Vic Cross
[1] Digression: That configuration would possibly work better without
any OSPF at all, by ju
HMCs? ;-)
Cheerio,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROT
re sharing DASD, you don't have different device numbers to
refer to a pack from different LPARs, right...? Why is it a bad idea
for OSAs?
Cheerio,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
---
) --
use a CD-RW while getting the parmfile right, unless you need a new set
of coasters! :D
Cheers,
Vic Cross
PS: Hoping this is helpful... It's *real* late (early?) over here and I
might be starting to ramble :)
--
This message has been scanned for viruses and
dangerous content by M
ate "online" pseudofile in the sys filesystem directory you
found; a result of "1" is good) and that the DASD modules are loaded.
Cheers,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
if the
following is there:
PrintMotd yes
:)
Cheers,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
For LINUX-390 subscribe / signoff / archive access
On 16/06/2006, at 1:02 pm, Ranga Nathan wrote:
Thank you all. I have always been curing sick guests by LINKing their
minidisks to other guests and mounting the partitions.
Occasionally I need to do something in the console.
I tried telnet via putty. Ok, 3270 is better. I am now resigned to it.
r attaching the DASD to the
new system (and before you do vgimport)? It should come back and
tell you that an exported VG was found. You may also have trouble if
the VG you are importing has the same name as a VG that previously
existed on the system (but I would have thought vgscan would sort
tha
- it would seem that they've grown
considerably beyond that now. I doubt they've updated their TCO
analysis accordingly... :)
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
the really critical data about LVM is kept in
the metadata on the PVs. Using vgexport/vgimport is just, well,
nicer IMHO :). Probably not a big issue in your situation, where
you're throwing away the old server, but for moving VGs between
"persistent" systems it's p
h good preparation I imagine you could minimise your
downtime to little more than the duration of the application restart.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL P
nges you might have to make in the
future[1]. Then give the apps people the name rather than the IP
address -- it's easier for you to change (or arrange to have changed)
one DNS entry than for several application people to make possibly
dozens of application changes...
Thanks so much ...
create a routing loop, and this can be very bad
for network operation (and your chances of ever getting the network
people to do you a favour in the future).
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access in
/etc/rc.config
SuSEconfig
exit# <-- return to your running system
umount /mnt/copy/usr /mnt/copy/var /mnt/copy
Replace the DASD names with the actual names you get on your system,
of course, and don't forget
you to have some certain things set up (like IP configuration, backup
clients, etc) that might help you in your recovery task.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions
ort is open against your sshd process but your
DISPLAY variable doesn't correspond, check your shell profile scripts
(/etc/profile, ~/.bash_profile, etc) for a command that sets DISPLAY.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signo
ll required
filesystems are available for the boot to complete.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
G'day Bernie,
On 07/02/2006, at 6:53am, Bernard Wu wrote:
With SLES9 +SP3, I get :
CONCLUSION: System is NOT up-to-date!
foundSLES-9-s390x
expected SLES-9-s390x-SP3
The same minimal install produces 2 different results.
Is SPident -vvv broken ?
There was discussion here about this
stack of cache for a time can borrow it from other
guests that aren't needing it during that interval.
To me it's another example of trading-off between getting absolute maximum
performance and the greatest flexibility in the environment.
Cheers,
Vic Cross
omebody happens to do a vgscan and/or vgchange before you've detached
the DASD, you won't get the VG unexpectedly reappearing on your system.
These changes are undone by the vgimport on the destination system.
Cheers,
Vic Cross
--
will
do the heavy-lifting as far as interface redundancy is concerned, and
you don't have the processor overhead of a bunch of Linux guests
chattering to each other and to the routers nor the storage overhead
of all those add
my own advice I'm doing the same, since it's been
a while since I looked at some of this).
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
uld be a help to you in this
case...
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvind
removed
(replaced by the MAC address, like the multicast display).
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
f your company is using 10/8, then pick
something from 172.16/12 or 192.168/16) and don't try and advertise it or use
it as a backup routing path or anything else. The systems attached to the
Hipersockets will be the only systems that ever need to know about it.
Of course I'd never *really*
"), or use "script", as
already suggested.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
nothing more than security-by-obscurity.
Hope this helps... Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
only be able to reach
consoles at 2nd level by DIALling from 1st level... :)
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LI
an environment variable that you can use? Would be
easier than copying a xinetd configuration dozens (hundreds?) of times...
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL
r system has to do LDAP
lookups to resolve all the UIDs and GIDs in the "ls" output to
names...) If this is the case, find out what configuration would be
stopping the LDAP server from talking to you. Routing might be a problem
here -- can
On Wed, Apr 13, 2005 at 11:51:46AM -0400, Dennis Musselwhite wrote:
> VM63261 is a z/VM 4.3.0 APAR and the most recent service affecting Guest LAN
> on z/VM 4.3.0 would be VM63655 (PTF UM31332) and all prereqs. If that does
> not fix the problem we will need more diagnostic information.
I ran the
G'day all,
I'm stumped. I just applied SP1 to a working SLES9 system, and after the
IPL my Guest LAN connection now appears to be non-functional. I've checked
all the obvious things but so far I'm none the wiser. Connectivity to
another system on the same Guest LAN is fine.
I cannot ping VM TC
oposition than the
budget cuts that might mean job losses. How many CEOs would knock back a
proposal that: a) reduced overheads, and b) didn't involve giving anyone the
sack?
Cheers,
Vic Cross
--
For LINUX-390 subscribe
, the 'normal'
number you'd expect to see will vary from system to system, and you get to
know it -- when something abnormal appears, you "just know". :)
Cheers,
Vic Cross
--
For LINUX-390 subscribe / sig
a line off-list, if you like, if you've got questions about EE.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
inux, then you'd have to be very wary about MsVS
(IMNSHO). What might work today would definitely be unsupported by Ms, and
may become disfunctional in the future if (when?) Microsoft decides to make
MsVS a Windows-only virtualiser.
Cheers,
Vic Cross
[1] VMware did a pilot of a version for
ace that stuff
to the z/VM SMAPI, or even the new feature that came in with z/VM 5.1 that
the very thing.
Cheers,
Vic Cross
PS:
STOMITH: Shoot The Other Machine In The Head
STONITH: Shoot The Other Node In the Head
Yes, I know: you say tomato, I say tomato... :)
Just in case anyone saw STOMI
ver decisions on the actual status of the
application.
As Mark mentioned, there are quite a few of these packages. Keepalived
(which is a sub-project of Linux Virtual Server, btw) is one that from
experience works on Guest LANs (so should work fine on VSWITCHes too
owed to use -- and if it's a Hipersockets
Guest LAN on z/VM, check the DEFINE LAN as that hardware setting is mirrored
there.
> It is like dealing with teenagers!
I would describe everything about working with computers tha
since it was a "clean slate", perhaps it was
easier to have the sysprog do the VTAM work than code the automagics. :)
Cheers,
Vic Cross
[1] With the introduction of Enterprise Extender (HPR over IP) at around
OS/390 2.8, there was a neat circular dependency created: TCP/IP had to
star
,
Vic Cross
(at home, speaking for myself)
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
VSWITCH will not tag-and-send untagged frames since
it cannot guess which VLAN ID to tag them with).
Also, I see a qeth0 in your chandev.conf: make sure that traffic is not being
routed out that interface instead of through the VSWITCH. If you're still
having trouble, we'll need to see
so little DNS traffic, then why not, you know, just
> let them hit the *real* DNS server?
Pretty sure that nscd caches more than just DNS. If you're using NIS or
LDAP, for example, nscd is supposed to prevent you from driving your
information service into the ground whenever some
FL stand
for again? ;) The fact that z/VM is not Linux is not important here -- you
are running z/VM to support Linux workload.
IIRC, the archives have longer discussions about what kinds of z/VM workload
is permitted on IFLs, and other such topics for night-time reading. :)
Cheers,
V
e,
is OSE the correct CHPID type? Should it be OSA?
Cheers,
Vic Cross
PS: On Gigabit/1000BaseT -- it's disappointing that the industry
chooses to use the generic term "Gigabit Ethernet" to refer to a
specific implementation of Ethernet that operates at gigabit speed.
Sigh... No wond
ion - How do I interrupt the
> configuration script so I can issue commands.
You can issue "^c" (without the quotes) to simulate a Ctrl-C, which should
break you out of the script and give you a prompt.
Hope this helps,
Vic Cross
[1] I say *technically* incorrect because I have a system w
to specify
it), the second creates a single partition that uses all space on the device,
the third creates an ext3 filesystem on the partition (if you want a different
filesystem type, substitute the appropriate command).
Chee
nning for the device. These are usually started
from inittab, but you could test just by starting it manually from the
command line of another (working) session. You'll need to know the device
node name (the /dev/ name) of your 3270 and specify that on the getty
comman
ctually
took any notice of those routes would be another question.
I don't mean to harp on that aspect of the configuration, but this was
something that occurred to me as important in this context.
Cheers,
Vic Cross
--
For LI
ig you may end up with a fairly even
distribution anyway (due to some randomness in the timing of ARP responses
from your OSAs), but that's not to say that it's a reason to stay that way
;)
Cheers, hope this helps,
Vic Cross
--
ing anonymous.
Hope this is helpful...
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
s. Your interface will probably
be eth2 until your next reboot, however, so this might be more trouble to you
than it is worth to do it dynamically...
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
On Friday 20 August 2004 18:23, Rob van der Heij wrote:
Rv> I know better than argue with you... I recall the early version had
Rv> tweaked one of the formats since I could not use the same thing to
Rv> decode a tcpdump stream from my PC anymore.
Good point. If you run "tcpdump-qeth -r " on a fil
header to the
packets captured off the network. SuSE included the wrapper script in their
distro (from SLES8, IIRC).
Google for "tcpdump-qeth".
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access in
n be used to increase disk
performance. Before using 'find -atime', check if your filesystems are
mounted this way and "test in an inconspicuous area" to see that the
result is as you expect (I'm pretty sure tha
s with his REXX version of the script. Put one tapemark
between each file and two at the end, and see what difference it makes.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [
On Mon, 26 Jul 2004, Daniel Jarboe wrote:
> In this case would the ping to the gateway ip address from
> the outside have succeeded?
It may well have -- at least it would on most Linux systems. Linux, for
example, will respond to a packet addressed to any of it's configured IP
addresses from any
own, got it redefined
> even-odd-even, and started again (this time WARM).
Your difficulties talking to the OSA would -- should ;) -- not have
impacted the Guest LAN.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff /
rmat so it
won't work on other emulators. Good thinking, but! :)
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visi
ou need to obtain and build the debootstrap source on the
existing system, meet a couple of pre-requisites (including wget) and said
existing system needs to be able to get network access to a Debian APT
repository (but you were going to be configuring for one of those anyway,
right?
the mix (since Tao is built from RHEL3's SRPMs, it
won't relieve RPM-grief).
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
ted. You'll need to fix that, but not before
moving the existing /home into the LV (without overwriting what may
already be on the LV, if it was at some stage successfully mounted). Mark
has some hints on moving filesystems on linuxvm.org that might be use
. Might have been a
peculiarity of the mobo or chipset, but that was useful to me ;)
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO
tty good chance it will work). Then you (and your CE) will have some
ammo when you place the service call. ;)
Other than that, it should all Just Work. Load the z90crypt driver, and
run the test programs given in the Redbook -- you should get good results.
Cheers,
Vic Cross
---
ig change to this box every time you add a Linux guest
OR define the entire subnet of Linux addresses in advance; the latter was
not possible with the OSA-2, because the OAT had a (quite small) limit on
the number of addresses that could be defined there.
Hoping this helps!
Cheers,
Vic Cross
d to failures).
>From a networking perspective VSWITCH provides similar function to having
your guests attached directly to the OSA, but you get the benefit of
having the ability to switch to a different OSA port if a problem happens
on the first one.
Hoping that we're reducing confusion ra
Another point -- don't get VLAN and VSWITCH confused. VLAN is not
required for VSWITCH, meaning that if all your guests can appear to be on
the same network you do not have to configure any VLAN stuff at all (even
at the LAN switch por
network stops at .127 - the broadcast address - and the Linux guest is at
.129).
My suggestions: double-check that there is no firewall product on the PC,
or a firewall configuration on the Linux guest, that is stopping the
traffic flowing. If that's clear, check that IP forwarding is enable
c/ directory (/etc/sysconfig/network, if it's like
my SuSE 9.0 box) for your interface to be correctly configured. You could
copy the ifcfg-eth0 file in that directory and edit as required, or you
could use YaST to set up hsi1 this time and have a look at what files it
changes for future referen
is to a CP/IFL that is not defined
or available to the LPAR, the LPAR will not be able to use the crypto[1].
Cheers,
Vic Cross
[1] I may be wrong on this -- this was a piece of advice we encountered
along our way while diagnosing problems with crypto on a z800, but we
later foun
G24-6298). This will let you check through the
functions that you're doing with 3745s now to find out how those functions
can (or cannot) be performed in other equipment. Only now, whenever you
read "Comms Server for AIX" or &
rt the installation process", yes. "Install", well, no. Sorry to be
a pedant... ;)
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
t played with, but I think both need an existing driver system to
install).
> Lastly, are the Red Hat and SuSE linux versions aboe to show somehing on the
> 3215 console?
Sure, just the same as they do running under VM and using the virtual
3215. On a P/390
eed and not at the speed of the CP.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
probably wouldn't hurt to check it one more time ;)
What about /proc/subchannels and the like? I guess they will have
equivalents in the new kernel... Is there a /proc (or /sys) pseudofile
that is the equivalent of /proc/chandev? These will be other he
f the interface from that.
Sure, the config is not the same as 2.4, but at least you will know the
right numbers to put in places -- very important for getting the EMIO
stuff to work.
When I get some spare time I'm going to give this Gentoo build a try,
after that I mig
:
http://www.redbooks.ibm.com/abstracts/redp3719.html
I'd be keen to hear what you think of it, so please let me know or use the
feedback e-mail address on the Redbooks site.
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff /
correctly finish the system
setup and give you access to YaST.
BTW, "yast" on the command line rather than "Yast", "YaST", "YAST" or
other combinations will work fine.
Cheers,
Vic Cross
--
've specified
on a backup controller doesn't suit... Ideally, you want any TCPIP service
machine you've defined as a controller to be able to back up any other one,
and it adds complexity if you restrict each controller to an RDEV range.
Cheers,
Vic Cross
---
On Tue, 13 Apr 2004, Adam Thornton wrote:
> Mains voltage across the keyboard is more traditional.
Y'know, Adam, I sort-of picked you as a BOFH-type...
;))
Cheers,
Vic Cross
--
For LINUX-390 subscribe / signoff /
s idea... ;) It would probably be further contracted to "Linz"
(i.e. "Lins").
I know that others on the list have expressed a dislike for zLinux (or
IBM-ised to z/Linux) -- why was that? zLinux would get my vote...
Cheers,
Vic Cross
omain 0/1/0
> (109) (DF)
> Anyone know how to persuade it to give a more readable output?
Use the tcpdump-qeth wrapper, instead of invoking tcpdump directly. In
SLES8 it should be provided, although you may have to install anothe
1 - 100 of 283 matches
Mail list logo