On Tue, Jun 8, 2010 at 11:10 AM, Macioce, Larry
larry.maci...@com.state.oh.us wrote:
I tried to reboot the test system today and it sits in init 1 , NONE of
the lvgs can be accessed.
When a reboot occurs, Linux doesn't see volume 207(this was the vol used
to increase the filsesystem)
While it's beyond what you were asking for, here's another vote for Samba
running in SECURITY=DOMAIN mode with winbind if your users are already
authenticating in a Windows Domain / Active Directory type environment.
Word of warning: it is another layer of complexity and relinquishment of
control
Posting on Linux-390 list too...
--- In hercules-...@yahoogroups.com, Harold Grovesteen h.grovst...@...
wrote:
The assumption that has been made is that the files listed in your .ins
file were in fact loaded. That assumption needs to be validated.
Please display real storage for each of the
I'm pretty sure that's by design, and not a problem. The kernel
starts out in 31-bit mode, and then switches to 64-bit mode.
I've been seeing the same thing for years now, and I still do on
my own Hercules setup that can successfully boot up SLES11.
Hi Mark, can you confirm?
$ md5sum
What kind of hardware and operating system are you running this on?
A Ubuntu 8.10 installation. P4 Intel chip, 1GB RAM.
I still end up at disabled wait state with 3.04.1 (though with the older
release of hercules it reports instcount of 18 rather than 2). I'll have to
try this on some
On Tue, Apr 14, 2009 at 3:34 PM, Neale Ferguson wrote:
Can you display the program old PSW and the instruction that the address
portion of the PSW points to? (Actually, the address less the ILC.)
That fished it out. Enabling instruction stepping increased the instruction
count, but not by
I'm having trouble IPLing the starter SLES11 system using Hercules 3.06. The
IPL method should be equivalent to a LPAR load from CD-ROM. The
deployment.pdf included within SuSE's docu directory didn't reveal any
obvious differences why what works for SLES10 SP2 installation under
Hercules doesn't
I would not deny that this might be a problem, but with an instruction
count of 2, it did not get very far, unless of course it is the very
first instruction. This question came up on the Hercules list, and I
recommended this list. Can anyone validate for the poster, the correct
.ins
It used to be the case that there was not a supported upgrade path from
SLES 31-bit to 64-bit addressing modes. Is that still the case? Has
anyone performed a SLES9 SP3 s390 - SLES10 s390x upgrade in place, or
is trying this still more trouble than its worth (i.e. install clean and
be done with
I actually don't think there is any software checking.
We bought support during the period and we never had
to change anything from the original install.
What ends is your ability to pull maintenance from portal.
~ Daniel
--
Thanks,
Would you be willing to send a listing of your logrotate.config
file?.
/etc/logrotate.d/syslog is installed with your syslog package
Just make sure you have logrotate installed and set up in cron (normally
this is done automatically for you, run daily).
~ Daniel
You can also ^C out of the install script at the console and eventually
it will drop you into a shell. Next time you re-ipl, it will pick up in
the install script again.
Once in a shell check the output of /sbin/route. Make sure you can ping
-c 1 ip_of_your_default_gateway, that kind of thing
The information can be found under CORE of your release on portal.
Details:
s390: http://portal.suse.com/psdb/d217ab2113221d24870fee955dc766cf.html
s390x: http://portal.suse.com/psdb/ad5d207a398847172fbd448b7fc0b61d.html
Long story short:
So what's happening? Do you have a half configured package, and dpkg
attempts to finish the configuration and fails?
Does a dpkg --configure -a tell you anything interesting?
~ Daniel
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Dennis Wicks
Sent:
Thanks for the reply!
Nothing is happening! Every thing I have tried with apt-get
just returns 0 upgraded, 0 newly installed, 0 to remove and 0 not
upgraded.
So not sure where the problem is yet... you try to apt-get install a
new package and you get no messages except 0 upgraded, 0 newly
[bromine:/]$ apt-get -o Debug::pkgProblemResolver=yes dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Starting
Starting 2
Done
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[bromine:/]$
There's nothing for
That is exactly the problem. It hasn't finished at all!
Isn't there some way to force it to restart? Or do I just
use the MicroSoft default solution of reformat and reinstall?
You still haven't said what's not working... just that you saw something
that might have been an error message
I can´t get by the initrd 75% problem when installing.
Is this for x86? Was a little confused at all the i386 talk in your email.
Otherwise, this sounds similar to an experience we recently had. When using
either the SLES9 or SLES9-SP1 installation images the process would hang with
zipl
1. Can SAMBA handle nested global groups?
I don't believe so - UNIX/Linux groups cannot contain groups. I recall
someone flattened nested groups somehow, but this was a migration
strategy, not a coexistence one.
Support for nested groups in Samba3 is fairly new. Mind link wrap...
We noticed that when we IPL the z/VM system, the operator console does
not
go into scroll more right away. It starts in ?VM READ? and sits there
with
the ?more? prompt until the 60 second timeout and scrolls the next
screen.
After the IPL is completed and once we hit enter, it will go into
Is anyone aware of any sources that provide mainframe time for porting
linux applications to s390 and zSeries hardware? I seem to remember
some kind of IBM community, and perhaps something offered by
sourceforge, but looking at both now and through this lists archives I
can't find any
Yeah, good luck making this stick.
You *KNOW* the CEO's password is boobies.
And change the combination on my luggage!
(spaceballs)
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL
In conclusions and recommendations,
Our optimal configuration included:
1 MB of Memory
...?
~ Daniel
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Ferguson, Neale
Sent: Monday, March 21, 2005 8:46 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Samba V3
SLES9 uses 3 sources for activating dasds.
If I recall correctly SLES9 activates the dasds in this order:
1. entries in zipl.conf (dasd=)
(dynamically activated by code in the initrd)
2. dasds which were active when mkinitrd was executed. (And exactly in
the
same order)
(These are
In our 2.4 systems we set the dasd device order with zipl.conf. The
order the devices were added corresponded to which minor number it
received... /dev/dasda before /dev/dasdb, etc.
Now our SLES9 system uses the initrd...
In the initrd's linuxrc script, there are a bunch of calls like:
mkinitrd appears to add the dasd devices as they appear in alphabetical
order of /sys/block.
Which means dasda, dasdaa, dasdab, dasdac, dasda* before dasdb, dasdc,
etc.
Is anyone else using SLES9 that, after install time, added more devices
to put you over 26?
Thanks,
~ Daniel
Current: Kernel: 2.4.9-17. Samba: 2.2.8a, Apache: 1.3.22.
You should try a newer RH 7.2 s390 kernel. The 2.4.9-17 kernel for RH
7.2 s390 had a weird interaction with samba.
~ Daniel
--
For LINUX-390 subscribe / signoff /
It depends on the sed...
For example, an update in place from Unix style end of lines to the
Windows carriage return style for some files.
sed -i 's/$/\r/' filename
works on sles9 and fedora core 3, but not sles8
~ Daniel
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL
Many of them are the same type of printer HPLaserJet 4si,
HPLaserJet 5, etc. and distributed to over 150 drops/locations
through-out our campus. During the process of setting up these
printers using Point-and-Print I have scripted several steps to
save time. But I have not been able to
1. Test : zipl.conf without vmpoff=LOGOFF
shell command poweroff does not work for both, VM recognizes shutdown
of
GUEST2, but no logoff
2. Test : zipl.conf with vmpoff=LOGOFF
shell command poweroff works for both, VM recognizes shutdown of
GUEST2,
but no logoff
The guest were running
A pseudo-equivalent to prstat is top, but top lacks prstat's
granularity.
Pstack was ported to linux and is available in at least Debian's and
RedHat's repositories (maybe others), though I don't see anything for
SuSE.
A Fedora srpm is here:
When print files appear in the printshare, they belong to xgroup,
but they have permissions as 600, instead of our intended 660. In
this printshare, that's important because the files don't go straight
to a printer. Instead, a process picks them up and modifies them.
Our work-around is to
URL: http://ftp.sernet.de/pub/samba/sles8-s390/
Works now
~ Daniel
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
Can whomever it is that maintains this please open up the
permissions on the files?
Brandon, I've let Volker L know... I seriously doubt he's on this list.
In the meantime if you are very anxious, I can send you a
samba3-3.0.9-17.src.rpm. I can also send you s390 compiled rpms, but
cannot
was the issue of umounting the lvm. Everytime I was issuing the
umount /dev/system/samba I received an error msg device busy.
Fortunately I knew which other linux servers had the share mounted
(via nfs) and closed down that service to be able to umount it.
How would I be able to assertain
Anyone seen this?
http://www.securityfocus.com/bid/11695/info
Yup, it requires you to mount a smbfs filesystem from a hostile
system onto linux. This is a different animal than samba. This
is a network filesystem mounted kind of like nfs (fs type will say
smbfs).
If you don't have users
A few weeks ago we had what over time grew into a big problem
dispatching guests. Guests would stop being dispatched sometimes for 10
minutes at a time, for no reason that we could identify. Usually
shutting some guests down would get everyone dispatching again, but it
was a mess. We applied
I have a 64-bit SLES 9 test system that I've been playing with. I
recently applied some patches that Suse had recommended applying.
After I recycled the system, it will no longer talk to the guest lan.
It worked prior to the patches and no changes have been been made on
the VM side.
It
What was the amount you gave it (for those that follow)?
The doc said 256MB+ for nfs, 512MB for ftp/VNC. I had 256MB plus some
swap (which the installer activated), and at the time of the failure
this looked like more than enough. The system was up to 110MB just for
buffer/cache with another
From a different client I can consistently get through most of the
install up to zipl segfaulting. When YaST2 attempts to reinstall the
bootloader, and it hangs. 100% repeatable for me.
- What type of disks?
- Amoung of memory?
ECKD DASD (CDL formatted)
256 MB memory, plus the installer
can you give more memory to the guest (just during the
installation phase)?
The SLES9 install completed cleanly after giving it more memory.
Thanks,
~ Daniel
--
For LINUX-390 subscribe / signoff / archive access instructions,
Where did you get the documentation on doing an upgrade from
sles 8 to sles 9? TIA!
There's a docu directory in CD1 (SLES-9-s390-RC5a-CD1.iso). I
didn't look to see if the doc addresses upgrading, but it was an
option during the install process. I'd poke around on CD1 first...
there were
Looks like the kernel has some definite problems. If this is as
repeatable as it sounds, I would report it to SUSE, and perhaps the
LKML.
I switched from a coworkers machine to my linux box here and things are
a bit better. Now twice I've made it all the way through the install up
to zipl
I didn't see anything in the installation doc so I thought I'd ask if
anyone has seen this before:
I'm trying a new install of SLES9 (s390 31bit) under VM. I had
previously formatted all the DASD from another SLES8 system. The
install was working on the second CD (core9/CD1) over NFS (loop
knowing how to interpret the User process fault: interruption code
messages that get generated. Is there a pointer to a document that
contains explanations for these that anyone knows about?
You've probably already seen this, but just in case... there's a
tiny bit in
If you watch the console long enough, do you see anything like:
__alloc_pages: 0-order allocation failed
or
VM: killing process?
How large did you define the guest? How much is a small amount of
swap? What kind of workload? What error message do you get when you
try to log onto the linux
Hi Daniel,
I have seen the __alloc_pages message in /var/log/messages as well as
the VM: Killing process message.
So you are definitely short on storage. Which is why you can get ping
responses, but no new shells/processes forked to log on.
One of the guests is 1280Mb, the other 1792.
Grinder is running on an external PC. So it's not that. Good call
though.
Don't know if you've used this or not, but here's a quick installation
thing that may help to determine if your storage sizes are realistic or
not...
http://www-1.ibm.com/servers/eserver/zseries/os/linux/pdf/avmlinux.pdf
I increased my machine from 32M to 128M. I used the echo 134359738368
/proc/sys/kernel/shmmax
Everytime I reboot, the value returns back to 32M. How do I make this
permanent on a SLES8 machine ?
sysctl called by the startup scripts is the recommended way... check out
/etc/sysctl.conf
The
I was told that linux servers have to be rebooted periodically
to clear out buffers, cache, storage, etc.
Not really. Linux is designed to reclaim/reuse/adjust as needed.
Many people are quite proud of their uptimes...
If you seem to be losing storage, I'd check on the virtual
storage sizes
I'm installing, or trying to, MS Front Page Extensions in my
RH
7.2/Apache LPAR. If you've been able to successfully accomplish this
I'd
like the opportunity to ask some questions. Thanks
I don't know if he still does, but when I was using MS FPSE's on RH 7.2
s/390, joshie.com had
I try a 'rpm --install nano-1.2.3-1.src.rpm' and absolutely nothing
happens.
rpm -qlp nano-1.2.3-1.src.rpm shows the files that will be unpacked by
the rpm. You either want to rpm -bb the_spec_file or simply rpm
--rebuild nano-1.2.3-1.src.rpm.
Good luck,
~ Daniel
For those that are using the Tivoli client for file-level backups on
linux s/390, can anyone comment on their own experiences with Tivoli
client resource requirements? We've recently started backing up a new
file-server. As it was hitting its 430,000th file processed, top was
reporting memory
I've seen that behavior on a system with a lot of open files (it keeps
a
context entry to go back and check later in the run to see if the file
is closed and available), but that doesn't seem to be the case here.
Is
this the first backup of that filesystem on this server? Sometimes the
first
Guessing (WAG mode): Could this memory growth be caused by maintaining
symlink context?
It strikes me that if there are a lot of symlinks that there'd need to
be
kept a list of where they're pointing so that it could ensure
resolution.
Since I've *NO* knowledge of the internals of TSM (I
I don't get a login prompt. But I do get the # sign and can enter
commands. I'm using Hercules, the 390 emulator.
This is in /etc/inittab
1:012356:respawn:/program/to/run
Is it just /bin/bash now?
You might be looking for something like /sbin/sulogin, or /sbin/sulogin
-t 30
You can modify
Has anyone created an LVM from multiple mod 27's (32,720 cylinders) ?
Wasn't any different than 3's or 9's for us. Only thing I can think of
is you might want larger logical volumes now that you have larger PVs,
so your -s parameter on vgcreate might be larger.
This past weekend we had our DR test, and while my linux guests came up
and could talk to each other on the GLAN, none could contact the vm
TCPIP router/gateway (or send traffic outside the virtual network). A
#CP Q NIC DETAILS from the linux guests showed TX Packets getting
discarded, presumably
G'day Vic!
and either VM TCPIP had the wrong IP address (at the Guest
LAN interface)
In this case would the ping to the gateway ip address from
the outside have succeeded?
or the TCPIP machine was not attached to the Guest LAN.
For future reference... how would we reattach it :)?
They
connections are going down, e.g. all ssh sessions get lost with
timeout
etc. A ping doesn't reach the linux. Pings from direct
network-neighbours
to the linux fail, too.
snip
(around 20-45 minutes), suddenly the linux answers again. There are no
error-messages in /var/log/messages.
Sounds
We are going with a lot of Linux Guests under VM. Close to 20 per IFL
and
are wondering about the experiences with the basevol/guestvol
scenario.
How many People accually use this scenario? How much DASD does this
really
save you? Is it worth the time and effort it takes to set this up?
Could
On Thursday, July 08, 2004 10:48 AM Adam Thornton wrote:
On Thu, 2004-07-08 at 09:41, Daniel Jarboe wrote:
the real issue was the
effort that went into applying any updates and keeping the rpm
database
current on each guest. Stability was no problem.
I haven't found a better way to do
Hello I am changing the ip addr of the suse server on s390, in redhat
I
can change in /etc/sysconfig/network-script.. but... where can i
change in
suse 8.. ?
You change it in /etc/sysconfig/network/ifcfg-eth0 (where eth0 is your
interface name).
Or for overkill use YaST
~ Daniel
- Rapid software development
- Lesser quality code, with less efficient use of resources
- Higher resource demands
- Higher minimum requirements for the application
The reason I usually hear:
It used to be that your people's resources were inexpensive
compared to hardware. When
I was successful in getting my Window's printer driver (for an HP
4600) to
upload
to the Samba directory /usr/lib/samba/drivers/3
I used the Windows client to do this, by following the instructions in
Mike's redpaper...Cups Samba
Typically it's /usr/lib/samba/drivers/W32X86/3
What's your
The main reason that I suggest this is because there seems to be a
nasty
bug in Samba (s390) whereby TDB files become corrupt under a
significant
workload. Samba must be recycled to work around the TDB corruption.
This
is being addressed in PMR 68139. There is a workaround to use the
smb.conf
Went to see if there were any samba3 package updates for s390 today
and
found the following link no longer valid:
ftp://ftp.suse.com/pub/people/gd/samba3
Anyone happen to know if that's officially gone or just maybe moved to
another location on their site?
I don't know what became of
Has anyone done a LPAR install on zSeries and then migrated to a zVM
infrastructure ?, any ideas on this ?.
Yes, we started this way. Migration was painless.
I would look at the LPAR install just so that we get a head start on
the
project , the zVM is part of the IBM bundle that will come a
Even if I have not defined them to the linux guest itself, if they've
been
dedicated to the VM guest ID, a cat of /proc/chandev should show me
the
devices right?
/proc/subchannels?
~ Daniel
---
This message is
Even if I have not defined them to the linux guest itself, if they've
been dedicated to the VM guest ID, a cat of /proc/chandev should show
me the devices right?
Yes, they should. In use and chandev reg will be no.
Are they not there? Do they show up in /proc/subchannels?
~ Daniel
linuxdev:/home/hrive # rpm -iv gcc_old.rpm
error: failed dependencies:
ld-linux.so.2 is needed by gcc_old-2.95.3-92
Can you help us resolve this? Where can we find ld-linux.so.2. It is
not
on the Operating System CD's.
Where did you get this rpm? The gcc_old provided with SP3 for
-add the line : MDISK 0204 3390 0001 3338 VMLX05 MR ALL SOME FEW
into my Linux CMS user's USER DIRECT definition.
- Format the device using cpfmtxa z/VM utility.
- CMS format 204 c
- IPL my Linux system.
- check the devices:
cat /proc/dasd/devices
Does it show up in
OK, what's the password for root when installing Gentoo for S/390 from
the
Stage3 file?
I think it was for the x86 stage3 live cd... try that.
~ Daniel
---
This message is the property of Time Inc. or its
OK, what's the password for root when installing Gentoo for S/390
from the Stage3 file?
I think it was for the x86 stage3 live cd... try that.
Or random/not-set? Can you not set your own with passwd at the
console...?
~ Daniel
I'm working with the Stage 3 install which is a pre-generated system.
I tried to do a passwd root newpasswd after performing a chroot
/mnt/gentoo. I suspect this changes the password on the driving
system.
I made sure I changed root's password to the same one I'm using on the
driving
Question:
Can Samba V2.2.8a join an Active Directory domain (which is running
in mixed mode)
as a domain member... and does WINBINDD work in that environment?
Yes, Samba 2.2 is basically a NT-type client. If NT clients can
participate in the AD, so can Samba 2.2.
But winbind doesn't want
Hope people don't mind the OT post, but in rationalizing, it's pretty
easy to connect the dots from Jay Maynard to Hercules to Linux s/390...
http://www.ibiblio.org/jmaynard/TRONcostume/
~ Daniel
---
This
Thanks. The document I am using to build this environment says that if
I
do that then I will not be able to access the R/W DASD even from the
ID i
used to build them since all systems will not see the DASD as R/O. If
there a way around that?
Your R/W guest should not update the dasd that
See: http://www.nytimes.com/2004/04/28/technology/28blue.html
(Free subscription required)
For privacy-paranoid, a lot of news sites (like NYTimes) do not require
subscription info if your HTTP_REFERER is from google.com. If your
client doesn't support changing this you can always search for
out of control and eating up CPU, meanwhile, customers access to the
samba
shares dies. When it happens, there appears to be wy too many
samba
processes spawned, yet only one of them is going bezerk according to
top.
The parent smbd forks one smbd for each connection. So each client
Any idea how to get the @ symbol to work when using the VM console for
linux. It doesn't matter if I use x3270 on linux or a windows-based
3270 client, @ always seems to be treated as a backspace.
Command:
echo [EMAIL PROTECTED]
becomes
echo 134
Command:
echo [EMAIL PROTECTED]
becomes
echo 1234
I am trying to diagnose a problem with vsftpd on sles8 (31 bit).
Certain
windows clients seems to hang for a long time before getting started.
Also
they cannot rename/delete files. Other clients work OK.
Has anyone experienced this
Windows client like %windir%\system32\ftp.exe or windows
for i in `rpm -qa`; do rpm -V $i; done |grep missing
rpm: only one major mode may be specified
Those are backticks around rpm -qa (on my keyboard, upper left, shared
by ~).
~ Daniel
---
This message is the property
And finally, the pain involved isnt so great, we just installed a
linux
vm, compiled and installed the packages that we need (postgres 7.4,
apache
1.3.29, perl 5.8, etc), then copied the non-standard directories (etc,
Do the extra software packages not included in the base get
It's funny, this is the one I use to clone, and I just went
to another instance, found it and copied it back.
Once tar was there, it worked great.
I really appreciate your help
Glad you are back in business now, though the missing binary IS
disconcerting. You should probably take inventory
I just put on SuSE SP3. When I IPL'd, it gives me these messages:
Loading module dasd_mod dasd=$dasd ...
insmod: dasd_mod: no module by that name found
Loading module dasd_eckd_mod ...
insmod: dasd_eckd_mod: no module by that name found
kmod: failed to exec /sbin/modprobe -s -k
Yes, I checked the zipl.conf and then ran zipl.
Does your zipl.conf have a line like ramdisk=/boot/initrd ?
If not, you should probably add it (run mkinitrd if you haven't), and
then run zipl again.
Loading module dasd_mod dasd=$dasd ...
insmod: dasd_mod: no module by that name found
I am ready to do the rpm ?bb quagga-0.96.4.spec. There was a method
to
redirect the output to the terminal and to a file so I can review it.
It
was a redirection command and for the life of me, I cannot get my
syntax
correct. Can someone provide me the syntax?
Something like rpm -bb
creating initrd /boot/initrd for kernel /boot/kernel/image
(version 2.4.21-83-default) (s390)
dasd_mod: failed to add module /lib/modules/2.4.21-83-
default/kernel/drivers/s3
90/block/dasd_mod.o
initrd too small
Run zipl now to update the IPL record!
how do I make it bigger?
How much
At line at 1061 which is:
dd if=/dev/zero of=$tmp_initrd_small bs=1k count=$img_size
2/dev/null
Can you remove the 2/dev/null portion of that, run mkinitrd again
and
see if you get any No space left on device errors?
I did as you suggested, but I don't get any additional messages, it's
the
It looks like that messages is generated around line 837 in the
mkinird,
before your change.
Ugh, my find had wrapped back to the beginning without me realizing.
Okay, on line 844
tar -C $root_dir -cf - $x 2/dev/null | tar -C $tmp_mnt -xpf -
2/dev/null
you're getting a rc 127. It's as if
I'm trying to be able to toggle an additional IP address between two
guests (qdio GLAN, VM's TCPIP is the router). VM 4.3, SLES 8 SP3
guests.
Our VM guy added the additional three devices required for QDIO on one
guest, and then a different three on another. I could have one of the
guests
The one that doesn't work:
noauto;qeth0,0x0710,0x0711,0x0712;add_parms,0x10,0x0710,0x0712,portname:
VMGLAN
noauto;qeth0,0x073c,0x073d,0x073e;add_parms,0x10,0x073c,0x073e,portname:
VMGLAN
Looks like a typo ;) The second one should be qeth1.
D'oh, thank you!
If you use qeth0 for both
I am seeing a build requirement for package tetex. This is not part
of the SuSe SLES8 distribution. I have been unable to determine if
tetex is really necessary or not. Should I install tetex as well?
Any ideas and opinions are welcomed. Thanks.
There are te... and ...tex type packages
I am getting this error on a new Samba (SLES8) printer config...
(first time we're trying samba at this account)
What version of Samba?
When trying to connect to the linux574 printer
You do not sufficient access rights to your machine to connect to the
selected printer
Maybe one of the
Carsten Otte wrote:
Daniel wrote:
The larger the number of cyls for the device, the worse the
ratio gets :(.
That's not true: CDL uses track0 and track1 for internal purposes, the
rest (number of 4k blocks that fit on a track multiplied with amount
of
tracks) is available for partitions.
We have formated a mini disk of 285 Cylinders with :
dasdfmt -b 4096 -n 0104
dev2:/mnt# less /proc/dasd/devices
0104(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096,
51300
blocks, 200 MB
Going over the numbers, the overhead from dasdfmt is startling. At
849,960 bytes a
Hi Dave,
1. I ran the cupsaddsmb command and I see that it created
InfoPrint_1125.PPD, which looks right for my Infoprint 1125
printer.
What's in /var/lib/samba/drivers/, /var/lib/samba/drivers/W32X86/, and
/var/lib/samba/drivers/W32X86/2 or /var/lib/samba/drivers/W32X86/3?
Not
In file included from /usr/include/asm/statfs.h:6,
from /usr/include/linux/vfs.h:4,
from /usr/include/linux/fs.h:13,
from /usr/include/linux/capability.h:17,
from /usr/include/sys/capability.h:24,
from
We have a few linux servers with kernel.hz_timer = 0 that run under
z/VM. I'm not sure how that patch factors into things below.
I know the linux CPU numbers are relative to the CPU z/VM gives the
dispatched guest, but how about idle ticks/jiffies from the linux
perspective? The VM accounting
1 - 100 of 250 matches
Mail list logo
