Re: Help needed with Debian/390 under hercules configuration errors
On Sat, Jan 18, 2003 at 07:47:52PM -0500, Matt Zimmerman wrote: > On Thu, Jan 16, 2003 at 10:53:27PM -0500, Peter J. Farley III wrote: > > > 0% [Connecting to 192.168.0.1 (198.168.0.1)] > > Err http://security.debian.org stable/updates/main Packages > > Could not connect to 192.168.0.1:3128 (192.168.0.1), connection timed out > > ... > > Failed to fetch > > http://security.debian.org/dists/stable/updates/main/binary-s390/Packag > > es Could not connect to 192.168.0.1:3128 (192.168.0.1), connection > > timed out > > 192.168.0.1:3128 happens to be where my Squid proxy is. Did that bit of > configuration leak into the image that I built somewhere? I'm away from > home right now and can't check it, but it should be simple to fix when I get > back if this is the case. I have returned home and had a chance to look into this, and upon inspection it appears that the image is fine. When initial configuration runs (when you telnet into it), http://192.168.0.1:3128 will be given as the _default_ proxy address, but you are prompted to change it and it is not used for anything until after this point. "Enter http proxy information, or leave blank for none:" -- - mdz
Re: SuSE Linux - TOC
On Tue, Jan 28, 2003 at 12:56:44PM +0800, John Summerfield wrote: > On Tue, 28 Jan 2003 11:58, you wrote: > > [rdiff-backup] > > The rsync solutions differ in that you could offer them as Windows shares via > Samba, and users could peruse directories and files as they were at the time > of the backup. > > The rsync solutions are similar in that they're bandwidth-efficient, and you > can (don't have to though) use ssh for security. > > No messing round with patch, all users see is a set of full backups. > > The volume of disk space required is the sum of one copy of all files backed > up plus whatever metadata Linux (or whatever *x you use) stores. Right. The difference is between storing incremental changes to files, and storing complete copies of every modified file. It is a tradeoff between convenience and space efficiency (for large files, a simple rsync backup is very space-inefficient). > It's ideal for retrieving that file some twit deleted, recovering fom > unintended updates (including viruses), and requires no special action (once > setup) by admin types. If that is desirable, this is (in my experience) most conveniently achieved by providing a volume manager snapshot (with, e.g., LVM or EVMS) on a nightly basis, providing an exact, complete filesystem image from some point in the past, which only takes up space for the chunks which have been modified since then. > And, it doesn't matter what format the files are. This is true for all of the solutions we have discussed. -- - mdz
Re: SuSE Linux - TOC
On Tue, 28 Jan 2003 11:58, you wrote: > On Tue, Jan 28, 2003 at 06:53:52AM +0800, John Summerfield wrote: > > Take a look at rsync for backups. There are scripts around that allow > > you to maintain more-or-less any number of full backups on disk for > > instant recovery. > > One such solution is rdiff-backup (packaged in Debian). > > Description: Backup program to use deltas for history > rdiff-backup is a script that backs up one directory to another. The > target directory ends up a copy of the source directory, but extra reverse > diffs are stored in a special subdirectory of that target directory, so you > can still recover files lost some time ago. The idea is to combine the best > features of a mirror and an incremental backup. rdiff-backup also preserves > subdirectories, symlinks, special files, permissions, uid/gid ownership (if > it is running as root), and modification times. Finally, rdiff-backup can > operate in a bandwidth efficient manner over a pipe, like rsync. Thus you > can use rdiff-backup and ssh to securely back a hard drive up to a remote > location, and only the differences will be transmitted. The rsync solutions differ in that you could offer them as Windows shares via Samba, and users could peruse directories and files as they were at the time of the backup. The rsync solutions are similar in that they're bandwidth-efficient, and you can (don't have to though) use ssh for security. No messing round with patch, all users see is a set of full backups. The volume of disk space required is the sum of one copy of all files backed up plus whatever metadata Linux (or whatever *x you use) stores. It's ideal for retrieving that file some twit deleted, recovering fom unintended updates (including viruses), and requires no special action (once setup) by admin types. And, it doesn't matter what format the files are. I reckon that one of the rsync solutions would work very well with traditional backups to removable media. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: SuSE Linux - TOC
On Tue, Jan 28, 2003 at 06:53:52AM +0800, John Summerfield wrote: > Take a look at rsync for backups. There are scripts around that allow > you to maintain more-or-less any number of full backups on disk for > instant recovery. One such solution is rdiff-backup (packaged in Debian). Description: Backup program to use deltas for history rdiff-backup is a script that backs up one directory to another. The target directory ends up a copy of the source directory, but extra reverse diffs are stored in a special subdirectory of that target directory, so you can still recover files lost some time ago. The idea is to combine the best features of a mirror and an incremental backup. rdiff-backup also preserves subdirectories, symlinks, special files, permissions, uid/gid ownership (if it is running as root), and modification times. Finally, rdiff-backup can operate in a bandwidth efficient manner over a pipe, like rsync. Thus you can use rdiff-backup and ssh to securely back a hard drive up to a remote location, and only the differences will be transmitted. -- - mdz
Re: samba config help needed
Originally I wrote:
I have the file sharing and printing all worked out using Samba 2.2 under
SuSE Linux version 7 Enterprise Server for S/390. I have uploaded print
drivers and that also went as documented. The only problem I am now having
is that when I print, it goes nowhere (into the great bit-bucket-in-the sky)
and I need to prove the printing capability by 9:00 am PST 1/29/2003. Any
assistance you can give me would be greatly appreciated.
I incorrectly sent this original post directly to Tzafrir rather than the
distribution list. Anyway, after the response I received I made the
modification
suggested and now I receive this message. This makes me believe that I do
not
have environment variables %p and %s set correctly. The machine known as
MB2ITBE1
should be my default printer and when I print "lpr /etc/fstab" from the
Linux
command line it prints to this printer just fine. But with the change made
to
debug "lpc > /tmp/prints/print_%p_%s" I don't believe the %s is set
correctly?
Can someone confirm this information.
Thanks
Doug
-rw-rw-rw-1 tsg74sysprog37 Jan 27 18:49 print_MB2ITBE1_%s
tsg74@becrlnx1:/tmp/prints > cat print*
Printer 'lpMB2ITBE1' does not exist!
tsg74@becrlnx1:/tmp/prints >
On Mon, 27 Jan 2003 [EMAIL PROTECTED] wrote:
> Tzafrir,
>
>
A bad time to ask me (this is 3:30 AM, and I'm supposed to be in bed by
now). I don't have the original thread, but:
- in smb.conf, [global]: what is the value of "printing" ?
The default is "bsd", and it means that printing should just use 'lpr
-Pprintername' and query using lpq .
Do you have cups installed? Maybe change that to cups ?
Anyway, you can manually set:
'print command' , 'lpq command' , 'lprm command'
This gives rise to a useful debugging technique:
create the directory "/tmp/prints" . Maybe it should be world-writable
(chances it shouldn't)
Then set in smb.conf:
lpq command = /bin/cat > /tmp/prints/print_%p_%s
This should send the current print job to a file
/tmp/print/print_PRINTER_NAME .
Then try printing it with:
cat /tmp/print/print_PRINTER_NAME |lpr PRINTER
Also, increase the debug level of samba to 3 . Have a look at the log of
the host from which you print.
Have a look at the file Printing.txt of the samba docs
Another thing: to print using smbclient from the local linux machine,
comment to the share of the printer with smbclient ('smbclient
//hostname/share' , or maybe 'smbclient //hostname/share -U %') and use
the command "print" .
Please follow-up to the list.
BTW: maybe try connecting to some irc server, to #linuxhelp ...
I'm off to bed now
--
Tzafrir Cohen
mailto:[EMAIL PROTECTED]
http://www.technion.ac.il/~tzafrir
Re: 2 questions: How to add gifabit OSA, and kernel crash after samba installed
On Mon, 27 Jan 2003, Bill Stermer wrote: > Mark Wrote: > > > That's right - this is a known problem. You can fix it by > > either upgrading > > Linux or Samba. We upgraded to a later release of Samba to > > get around the problem. > > What release level of Samba do you have installed that eliminated this problem? I recommend installing *ALL* updated packages applicable to your system. I can't speak for others, but I understand that Red Hat does some level of testing to ensure that updated packages fit the relevant release. For that reason, it would appear to visitors that I'm using an older version of Apache, but in fact it is the version Red Hat released to fix the problems that emerged a few months ago. In using Red Hat's version I can reasonably expect if there are further problems then there will be further updates I can install with minimal risk of upsetting something else. If I download the source from apache.org, then I have to figure how to build, install, configure it, integrate it with everything else. And I also have to watch out for security alerts myself; maybe Apache has a list for such, maybe it hasn't. I'm on the relevant RH list and I get almost all the notices applicable to my system from one source. Probably you can apply all your maintenance faster than you can download and build Samba. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: SuSE Linux - TOC
On Mon, 27 Jan 2003, Post, Mark K wrote: > _Do_ backup Linux with non-Linux tools while it's if you want a real DRA I can't guess what the missing word is, so JIC... > backup. Just keep in mind the limitations of that, and what to expect on > the other end. Forced file system checks and all the rest. There's really > little other option for a DRA situation. If you can get to the state where > your root file system (and as many others as possible) is mounted read-only, > that will certainly help things. If you backup open(rw) Linux filesystems, you get somewhat the same result you get if you press the BRS, but probably worse. You will have files and directories with inconsistent data, and quite likely beyond repair.. Remember, you cannot backup what's in the Linux cache, My guess is the need for backup of ro filesystems is somewhat limited. > > Mark Post > > -Original Message- > From: John Summerfield [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 27, 2003 5:56 PM > To: [EMAIL PROTECTED] > Subject: Re: SuSE Linux - TOC > > > On Mon, 27 Jan 2003, Post, Mark K wrote: > > > Keep in mind that those DF/DSS dumps will be at a "partition" level, and > not > > a file level. So, they would be more appropriate for a DRA recovery than > > anything. Since there's no integration between that tool, and what goes > on > > "inside" the Linux/390 image, it can't really be used as the base level > for > > later incremental backups. > > Do *NOT* backup Linux with non-Linux tools while it's running. > > > -- > > > Cheers > John. > > Join the "Linux Support by Small Businesses" list at > http://mail.computerdatasafe.com.au/mailman/listinfo/lssb > -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: DASD not recognized in Debian
On Mon, 27 Jan 2003, Sivey,Lonny wrote: > Hi Scott, > > I think you may be running into problems because the Debian kernel is > compiled with the DEVFS option turned on. You need to reference your > dasd with /dev/dasd/ where is the device address instead of > /dev/dasda /dev/dasdb etc. what happens if you run devfsd ? (apt-get install devfsd) Does it add /dev/dasd* ? If not: It is a bug of devfsd, right? -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir
Re: Microsoft shows Linux some respect
On Sat, 25 Jan 2003, John Summerfield wrote: > On Fri, 24 Jan 2003, Tzafrir Cohen wrote: > > > > > Try to print a word document, without popping-up the GUI. > > I used other software than word; mostly SmartSuite. I think I could > print a WordPro doc, though maybe not a spreadsheet. Filling in forms? > No, can't simulate keyboard input without extra software. > > However, mass installs and mass updates, the facilities are there, and > from what I've seen so far, better than Debian. Partially because all those things are much easier to create on linux. e.g: mass-install: If the hardware is the same: createan image and extract it. Create a small script to edit the some minimal parameters (*very* minimal). Mass updates: Make sure everyone has a local apt source of the company, and that everyone is running apt-cron. They'll update over-night . If you want to initiate it: add a script that runs 'apt-get update' etc. on all of them. There are a number of systems (havea look in freshmeat)for convinient execution of ssh on multiple servers. Mass-installs on different hardware: This is indeed one weak point of debian. It is not that hard to ammend. I know some people working on quite similar things. Whenever someone will really need such a thing, it will be added to debian ;-) -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir
Re: 2 questions: How to add gifabit OSA, and kernel crash after samba installed
Mark Wrote: > That's right - this is a known problem. You can fix it by > either upgrading > Linux or Samba. We upgraded to a later release of Samba to > get around the problem. What release level of Samba do you have installed that eliminated this problem? > Regards, > Mark Darvodelsky > Data Centre - Mainframe & Facilities > Royal SunAlliance Australia > Phone: +61-2-99789081 > Email: [EMAIL PROTECTED] Thanks, Bill Stermer ACS - City of Anaheim
Re: 2 questions: How to add gifabit OSA, and kernel crash after samba installed
>> (2) I configured and started Samba. I mounted a subdirectory in Linux to >> my NT machine as drive N:. As soon as I open the N; drive, Linux crashed >> with the following messages. >> >> kernel BUG at fcntl.c:4171 >> illegal operation: 0001 >> CPU: 0 >> Process Smbd >> .. >> >> The Samba release is 2.2.0.a >> Thanks. > >First thing to do after installing software is apply all maintenance. >It's there to fix problems like this and open gates for crackers to walk >through. That's right - this is a known problem. You can fix it by either upgrading Linux or Samba. We upgraded to a later release of Samba to get around the problem. Regards, Mark Darvodelsky Data Centre - Mainframe & Facilities Royal SunAlliance Australia Phone: +61-2-99789081 Email: [EMAIL PROTECTED] CAUTION - This message is intended for the addressee named above It may contain privileged or confidential information. If you are not the intended recipient of this message you must not use, copy, distribute or disclose it to anyone other than the addressee. If you have received this message in error please return the message to the sender by replying to it and then delete the message from your computer. Internet emails are not necessarily secure. Royal & SunAlliance does not accept responsibility for changes made to this message after it was sent
Re: SuSE Linux - TOC
_Do_ backup Linux with non-Linux tools while it's if you want a real DRA backup. Just keep in mind the limitations of that, and what to expect on the other end. Forced file system checks and all the rest. There's really little other option for a DRA situation. If you can get to the state where your root file system (and as many others as possible) is mounted read-only, that will certainly help things. Mark Post -Original Message- From: John Summerfield [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 5:56 PM To: [EMAIL PROTECTED] Subject: Re: SuSE Linux - TOC On Mon, 27 Jan 2003, Post, Mark K wrote: > Keep in mind that those DF/DSS dumps will be at a "partition" level, and not > a file level. So, they would be more appropriate for a DRA recovery than > anything. Since there's no integration between that tool, and what goes on > "inside" the Linux/390 image, it can't really be used as the base level for > later incremental backups. Do *NOT* backup Linux with non-Linux tools while it's running. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: SuSE Linux - TOC
On Mon, 27 Jan 2003, Post, Mark K wrote: > Keep in mind that those DF/DSS dumps will be at a "partition" level, and not > a file level. So, they would be more appropriate for a DRA recovery than > anything. Since there's no integration between that tool, and what goes on > "inside" the Linux/390 image, it can't really be used as the base level for > later incremental backups. Do *NOT* backup Linux with non-Linux tools while it's running. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: SuSE Linux - TOC
On Mon, 27 Jan 2003, Scott Chapman wrote: > you can either do full-volume dumps using your existing OS/390 > infrastructure (assuming you have one) or file-level backups from within > Linux, or possibly a combination thereof. Full-volume dumps really only > work for static volumes. File-level backups require something like Amanda > (open source) or Tivoli Storage Manager or I think a few other options. > One solution might be to do file-level backups to a set of volumes that are > then dumped from OS/390. That might make for fine DR recovery, but perhaps > less so for day-to-day activities. Take a look at rsync for backups. There are scripts around that allow you to maintain more-or-less any number of full backups on disk for instant recovery. They work by using 'cp -l' to archive full copies (using hard links) and rsync to update one to be the latest. My explanation is probably confusing; check the rsync website. You'll be "so glad you did." -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: SuSE Linux - TOC
Keep in mind that those DF/DSS dumps will be at a "partition" level, and not a file level. So, they would be more appropriate for a DRA recovery than anything. Since there's no integration between that tool, and what goes on "inside" the Linux/390 image, it can't really be used as the base level for later incremental backups. Mark Post -Original Message- From: paultz [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 5:31 PM To: [EMAIL PROTECTED] Subject: Re: SuSE Linux - TOC Hi Doug, As you said, Samba will do file/print serving just fine. Here's a who's-doing-what list from IBM that will give you a taste of other software that's available for various things: http://www-1.ibm.com/servers/eserver/zseries/solutions/s390da/linuxproduct.h tml As to backups, you can use DFDSS with CDL DASD. Regards, Paul
Re: SuSE Linux - TOC
On Mon, 27 Jan 2003, Doug Clark wrote: > At this time I am trying to provide management with the various components > of a Linux system in order to justify the replacement of a half-dozen file > servers and print servers with Linux/Samba configuration. > > I understand that the OS is basically free, and that there is a cost for > license support from SuSE. > There is also hardware cost involved with our particular implementation that > I can identify. > > What I am interested is the range of "supporting products" not an > endorsement of any particular product. Rather, I want > to know what "other" software is needed to support a mission critical > network of printers and files. What type of backup and recovery software is > available. I know that there are products that manage performance, dasd > usage, print output, security, etc. that would play into the cost. There is > also the cost of training system admins. > > If there is a site that details out the various software packages available > for Linux and or any other information that you believe is appropriate > please send me an e-mail. > > Thanks, > > Doug Clark [EMAIL PROTECTED] First, I recommend you get yourself a PC and install Linux on that. Boxed sets for PCs are much cheaper than support contracts, and the software's pretty much the same. If you have complete freedom as to rules you follow wrt account management & verification & such (unlikely, I know) then you can do it all with Linux. If there are specific products on other platforms (such as RACF) that you need to integrate with, ask specfically about those. Any distribution of Linux includes software for file and print sharing (Samba does that and a bit more). The exact selection depends on the distribution. Linux also comes with quite a selection of backup software; I've seen Amanda get favourable mention here before. > -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
SLES8 Install problem
I've gone through this install a few times now and I keep getting stuck at the part where it scans the CD for software selection. It comes back after about 35 min. and says "Not enough disk spaces even for a minimal installation". My last attempt was with 69.6 MB SWAP and 2 full 3390-3 (2.2G each) Any ones else get through this? I did dasdfmt and fdasd the disks outside of YAST2 as indicated by the README file. dasdfmt -b 4096 -l lnxnnn -d cdl -v -p -f /dev/dasdx fdasd /dev/dasdx Any one else been through this? How much does it want? The README says 1.3G is sufficient for a 31-bit install. Marcy Cortes Wells Fargo Services Co
Re: SuSE Linux - TOC
Funny--I'm doing the exact same thing myself at the moment. I think you already identified everything on my list: z/VM z/VM optional products (dirmaint, RACF, etc.) Linux and VM administrator training Linux Service (bug fixes, patches, upgrades) Linux Support (question/problem determination) Performance Monitoring tool (e.g. Velocity Software) Backup software (e.g. Tivoli Storage Manager) Personnel Processor, memory, disk Some things I've considered but may not include: Chargeback system integration - depends a lot on how one decides to charge back for these virtual servers. Backup subsystem costs - Assuming it will integrate into our existing TSM or OS/390 backup solutions, it should get a percentage of those fixed costs. Enterprise monitoring/maintenance tools - If you have a stated direction that every server will run software "X" to do password maintenance or availability monitoring, or whatever then those costs probably should be quantified as awell. I have service and support listed separately because my belief is that you can contract for those separately and it may in fact be advantageous to do so. To answer your particular questions re. backup and performance: for backup you can either do full-volume dumps using your existing OS/390 infrastructure (assuming you have one) or file-level backups from within Linux, or possibly a combination thereof. Full-volume dumps really only work for static volumes. File-level backups require something like Amanda (open source) or Tivoli Storage Manager or I think a few other options. One solution might be to do file-level backups to a set of volumes that are then dumped from OS/390. That might make for fine DR recovery, but perhaps less so for day-to-day activities. Performance needs to be tracked from VM's perspective, and maybe from Linux's. Therefore some sort of VM monitor like RTM (not necessarily a recommendation!) or Velocity Software's product is probably required. I believe Candle also has some sort of VM/Linux monitoring package. For our pilot project we didn't look beyond VM's own monitor and top in Linux, but I believe we would trial a 3rd party solution if we went forward. Scott Chapman Doug Clark <[EMAIL PROTECTED] To: [EMAIL PROTECTED] > cc: Sent by: LinuxSubject: SuSE Linux - TOC on 390 Port <[EMAIL PROTECTED] ARIST.EDU> 01/27/03 04:53 PM Please respond to Linux on 390 Port At this time I am trying to provide management with the various components of a Linux system in order to justify the replacement of a half-dozen file servers and print servers with Linux/Samba configuration. I understand that the OS is basically free, and that there is a cost for license support from SuSE. There is also hardware cost involved with our particular implementation that I can identify. What I am interested is the range of "supporting products" not an endorsement of any particular product. Rather, I want to know what "other" software is needed to support a mission critical network of printers and files. What type of backup and recovery software is available. I know that there are products that manage performance, dasd usage, print output, security, etc. that would play into the cost. There is also the cost of training system admins. If there is a site that details out the various software packages available for Linux and or any other information that you believe is appropriate please send me an e-mail. Thanks, Doug Clark [EMAIL PROTECTED]
Re: SuSE Linux - TOC
Hi Doug, As you said, Samba will do file/print serving just fine. Here's a who's-doing-what list from IBM that will give you a taste of other software that's available for various things: http://www-1.ibm.com/servers/eserver/zseries/solutions/s390da/linuxproduct.html As to backups, you can use DFDSS with CDL DASD. Regards, Paul
SuSE Linux - TOC
At this time I am trying to provide management with the various components of a Linux system in order to justify the replacement of a half-dozen file servers and print servers with Linux/Samba configuration. I understand that the OS is basically free, and that there is a cost for license support from SuSE. There is also hardware cost involved with our particular implementation that I can identify. What I am interested is the range of "supporting products" not an endorsement of any particular product. Rather, I want to know what "other" software is needed to support a mission critical network of printers and files. What type of backup and recovery software is available. I know that there are products that manage performance, dasd usage, print output, security, etc. that would play into the cost. There is also the cost of training system admins. If there is a site that details out the various software packages available for Linux and or any other information that you believe is appropriate please send me an e-mail. Thanks, Doug Clark [EMAIL PROTECTED]
Re: cmsfs bug fix
There is a CMSFS 1.1.6 on the BMC FTP site which incorporates Richard Hirst's patch. Utility mode (user-land) seems fine. Kernel-land (the driver) is still not reliable for other reasons. ftp://ftp.bmc.com/pub/cmsfs/cmsfs-1.1.6.tar.gz
Re: DASD not recognized in Debian
correct Scott Chapman Matt Zimmerman <[EMAIL PROTECTED] To: [EMAIL PROTECTED] > cc: Sent by: LinuxSubject: Re: DASD not recognized in Debian on 390 Port <[EMAIL PROTECTED] ARIST.EDU> 01/27/03 11:14 AM Please respond to Linux on 390 Port On Mon, Jan 27, 2003 at 11:02:38AM -0500, Adam Thornton wrote: > Debian uses the devfs. Its DASD is named things like > /dev/dasd/device/0151/part1 rather than /dev/dasda /dev/dasdb, etc. > > I'm confused as to how you did this, because Debian can write a correct > IPL record for a devfs system. Possibly because he was booted from a non-devfs system at the time it was written. -- - mdz
Re: ZIPL - confused and dazed
Seems I got over-zealous in removing some of the early e-mails from this thread, so this may have been eliminated as a possible cause. I thought I saw in one of the mailings that the devices in question are mod 9's. There is a fix available from Suse for a hang condition in mod 9's formatted in CDL, so my first question would be, "Have you applied this fix?" because the mod 9's aren't going to work without it. Just putting in my 2-cents worth. Steve Arden [EMAIL PROTECTED] IBM-Global Services @ Lucent > Return-Path: <[EMAIL PROTECTED]> > X-MIMETrack: Serialize by Router on AA2MTA/Hennepin(Release 5.0.10 |March 22, 2002) at 01/27/2003 09:49:40 AM > MIME-Version: 1.0 > Content-type: text/plain; charset=us-ascii > Approved-By: [EMAIL PROTECTED] > Sender: Linux on 390 Port <[EMAIL PROTECTED]> > From: James Melin <[EMAIL PROTECTED]> > Subject: Re: ZIPL - confused and dazed > To: [EMAIL PROTECTED] > Precedence: list > > I think I have a telling message now, on why the IPL halted. > > After I got the partition check messages: > > > Partition Check: > dasda:VOL1/ L40D1C :dasda dasda1 > dasdb:VOl1/ L40D18: dasdb > > After a while, this shows up. > > <7> dasd_erp(3990): /dev/dasdb(94:4),0d18@0x2f6: > Perform logging requested > > Then it hangs. > > I can certainly go back through a dasdfmt/fdasd process and re-install to > see if I missed anything but I'd rather not > > > > |-+> > | | "Post, Mark K" | > | | <[EMAIL PROTECTED]| > | | m> | > | | Sent by: Linux on| > | | 390 Port | > | | <[EMAIL PROTECTED]| > | | IST.EDU> | > | || > | || > | | 01/24/2003 01:41 | > | | PM | > | | Please respond to| > | | Linux on 390 Port| > | || > |-+> > >--- ---| > | | > | To: [EMAIL PROTECTED] | > | cc: | > | Subject: Re: ZIPL - confused and dazed | > >--- ---| > > > > > James, > > Not sure if the install did it or not. Theoretically, you should be able > to > just issue the zipl command (with no parameters) to make sure. > > Mark Post > > -Original Message- > From: James Melin [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 24, 2003 9:07 AM > To: [EMAIL PROTECTED] > Subject: Re: ZIPL - confused and dazed > > > I found what appears to be my new root volume at /mnt/. Apparantly YaST has > already built a zipl.conf file for me? Does this mean that YaST also > handled the IPL record? The zipl.conf file contains the correct dasd > devices. I see it still keeps the annoying behaviour of rearranging things > so that dasda1 is your swap volume. > > I just want to make sure that the ipl record has been written. If so, I > will attempt to IPL the new system. > > > > > > |-+> > | | "Post, Mark K" | > | | <[EMAIL PROTECTED]| > | | m> | > | | Sent by: Linux on| > | | 390 Port | > | | <[EMAIL PROTECTED]| > | | IST.EDU> | > | || > | || > | | 01/23/2003 03:52 | > | | PM | > | | Please respond to| > | | Linux on 390 Port| > | || > |-+> > > > > --- > ---| > | > | > | To: [EMAIL PROTECTED] > | > | cc: > | > | Subject: Re: ZIPL - confused and dazed > | > > > > --- > ---| > > > > > James, > > The /boot directory can be on any physical disk on your system. That then > becomes the device number you IPL from. A lot of people have it in their > root file system, which by default will wind up on /dev/dasdb1 on a SuSE > system. The "df" command will show you all your currently mounted file > systems. "/" should be at the top. > > Mark Post > >
Re: DASD not recognized in Debian
On Mon, Jan 27, 2003 at 11:02:38AM -0500, Adam Thornton wrote: > Debian uses the devfs. Its DASD is named things like > /dev/dasd/device/0151/part1 rather than /dev/dasda /dev/dasdb, etc. > > I'm confused as to how you did this, because Debian can write a correct > IPL record for a devfs system. Possibly because he was booted from a non-devfs system at the time it was written. -- - mdz
Re: DASD not recognized in Debian
On Mon, Jan 27, 2003 at 07:35:50AM -0500, Scott Chapman wrote: > I took down one of the virtual servers, and attached it's minidisk to > another one running SuSE. I then used debootstrap to install the base > configuration on that minidisk. I then configured the base Debian image > and ran zipl to make it bootable. I detached the minidisk from the SuSE > system, logged on to the VM userid for the Debian system and tried to IPL > it (device 151). It seemed to start the boot process ok, but it fails > trying to access the ext2 filesystem on the minidisk that has the root > filesystem--which is the same minidisk it was booting off from. I can > re-attach the minidisk to the SuSE system and access the file system fine, > but I can't even do an fdasd on the volume from the Debian system--almost > like Debian isn't recognizing the DASD at all, despite being able to boot > from it. Debian uses the devfs. Its DASD is named things like /dev/dasd/device/0151/part1 rather than /dev/dasda /dev/dasdb, etc. I'm confused as to how you did this, because Debian can write a correct IPL record for a devfs system. Your /boot/paramfile file should have something like root=/dev/dasd/0151/part1 ro noinitrd dasd=0151-0152 vmpoff="LOGOFF" But it sounds like you have root=/dev/dasdb1 at the start instead. > Even trying to run fdasd fails on Debian: > (none):~# fdasd /dev/dasdb > fdasd /dev/dasdb > > fdasd error: device verification failed > The specified device is not a valid DASD device > (none):~# fdasd /dev/dasd/0151/device would work, though. Adam -- [EMAIL PROTECTED] "My eyes say their prayers to her / Sailors ring her bell / Like a moth mistakes a light bulb / For the moon and goes to hell." -- Tom Waits
Re: Z/VM Backups and Restores
Mr. Ketchens, We use DDR backup and restore on our VM system. We are not running ZVM. DDR is a very good backup process for backing up intire packs. It alows you to restore for address to address or the intire pack. It is very simple to use. Mike Lovins City of Tulsa, Oklahoma >>> [EMAIL PROTECTED] 01/27/03 08:51AM >>> I need to know what's used a very good backup/restore application in z/VM. I need to know what I can use without having to purchase anything. I've read something about DDR, but I want some input on whether that is the best way to go. Lemarr Ketchens Ryerson Tull, Inc. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: ZIPL - confused and dazed
I think I have a telling message now, on why the IPL halted. After I got the partition check messages: Partition Check: dasda:VOL1/ L40D1C :dasda dasda1 dasdb:VOl1/ L40D18: dasdb After a while, this shows up. <7> dasd_erp(3990): /dev/dasdb(94:4),0d18@0x2f6: Perform logging requested Then it hangs. I can certainly go back through a dasdfmt/fdasd process and re-install to see if I missed anything but I'd rather not |-+> | | "Post, Mark K" | | | <[EMAIL PROTECTED]| | | m> | | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | || | || | | 01/24/2003 01:41 | | | PM | | | Please respond to| | | Linux on 390 Port| | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: ZIPL - confused and dazed | >--| James, Not sure if the install did it or not. Theoretically, you should be able to just issue the zipl command (with no parameters) to make sure. Mark Post -Original Message- From: James Melin [mailto:[EMAIL PROTECTED]] Sent: Friday, January 24, 2003 9:07 AM To: [EMAIL PROTECTED] Subject: Re: ZIPL - confused and dazed I found what appears to be my new root volume at /mnt/. Apparantly YaST has already built a zipl.conf file for me? Does this mean that YaST also handled the IPL record? The zipl.conf file contains the correct dasd devices. I see it still keeps the annoying behaviour of rearranging things so that dasda1 is your swap volume. I just want to make sure that the ipl record has been written. If so, I will attempt to IPL the new system. |-+> | | "Post, Mark K" | | | <[EMAIL PROTECTED]| | | m> | | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | || | || | | 01/23/2003 03:52 | | | PM | | | Please respond to| | | Linux on 390 Port| | || |-+> > --- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: ZIPL - confused and dazed | > --- ---| James, The /boot directory can be on any physical disk on your system. That then becomes the device number you IPL from. A lot of people have it in their root file system, which by default will wind up on /dev/dasdb1 on a SuSE system. The "df" command will show you all your currently mounted file systems. "/" should be at the top. Mark Post -Original Message- From: James Melin [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 4:31 PM To: [EMAIL PROTECTED] Subject: ZIPL - confused and dazed I have my system built. all that remains is for me to run zipl and I should be able to build it. I don't know where /boot is supposed to be . I cannot seem to locate my root volume even though cat /proc/dasd/devices indicates the volume is available. don't I need to be able to run zipl from the root volume of the new file system I just installed? What should I really put in /etc/zipl.conf? I'm basically staring a tthe 2-3 pages of the SuSE manual and going 'this assumes I know more than I do' I wouldn't normalyl give up so soon and ask this fairly benign question but we're doing a power-on reset on sunday. So I have tomorrow to get this thing to IPL-able or start over and re-install monday.
Re: DASD not recognized in Debian
Thanks! Sure enough, page 46 in "Installing Debian GNU Linux 3.0 for S/390" is "Device Names in Linux". Totally skipped over it... Debian boots now. Scott Stefan Gybas cc: Sent by: LinuxSubject: Re: DASD not recognized in Debian on 390 Port <[EMAIL PROTECTED] ARIST.EDU> 01/27/03 07:48 AM Please respond to Linux on 390 Port Scott Chapman wrote: >/dev/dasd/0151:VOL1/ 0X0180: p1 >/dev/dasd/0152:VOL1/ 0X0152: p1 Debian uses DevFS on S/390 so the device files are named /dev/dasd//* instead of /dev/dasd[a-z]*. is the device number, e.g. 0151. > Even trying to run fdasd fails on Debian: > (none):~# fdasd /dev/dasdb > fdasd /dev/dasdb Try fdasd /dev/dasd/0151/disc Regards, Stefan Gybas
Re: System Installation Suite on zSeries ?
IBM has released a cloning tool that might meet your needs. It can be downloaded from the URL: http://www.vm.ibm.com/devpages/CHONGTS/ The download includes setup and usage documentation. Good luck. Dave Jones Sine Nomine Associates Houston - Original Message - From: "Seifert, Harald" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 27, 2003 7:59 AM Subject: System Installation Suite on zSeries ? I'm searching for a tool to clone Linux Images under z/VM. I have found in the IBM Redbook "Linux on zSeries & S/390: System Management" Chapter 8 the System Installation Suite described, but there is stated that SIS is beta on zSeries. Does anyone have some experiences with SIS on zSeries ? -- Harald Seifert Informatik-Systemprogrammierung HUK Coburg Bahnhofsplatz 96444 Coburg Phone +049 (0)9561-961787 Fax+049 (0)9561-963671 Mailto [EMAIL PROTECTED]
Re: Z/VM Backups and Restores
Also, check our OFFLINDR - the price is right, and it works. http://www.clueful.co.uk/mbeattie/s390/offlindr.jcl On Monday 27 January 2003 09:51, you wrote: I need to know what's used a very good backup/restore application in z/VM. I need to know what I can use without having to purchase anything. I've read something about DDR, but I want some input on whether that is the best way to go. Lemarr Ketchens Ryerson Tull, Inc. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: System Installation Suite on zSeries ?
Hi, there is a GA product By BMC Software called DML (Deployment Manager for Linux) it have a cloning feature and many other features. Regards, Avinoam Hirschberg -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Seifert, Harald Sent: Monday, January 27, 2003 3:59 PM To: [EMAIL PROTECTED] Subject: System Installation Suite on zSeries ? I'm searching for a tool to clone Linux Images under z/VM. I have found in the IBM Redbook "Linux on zSeries & S/390: System Management" Chapter 8 the System Installation Suite described, but there is stated that SIS is beta on zSeries. Does anyone have some experiences with SIS on zSeries ? -- Harald Seifert Informatik-Systemprogrammierung HUK Coburg Bahnhofsplatz 96444 Coburg Phone +049 (0)9561-961787 Fax+049 (0)9561-963671 Mailto [EMAIL PROTECTED]
Z/VM Backups and Restores
I need to know what's used a very good backup/restore application in z/VM. I need to know what I can use without having to purchase anything. I've read something about DDR, but I want some input on whether that is the best way to go. Lemarr Ketchens Ryerson Tull, Inc. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: DASD not recognized in Debian
Hi Scott, I think you may be running into problems because the Debian kernel is compiled with the DEVFS option turned on. You need to reference your dasd with /dev/dasd/ where is the device address instead of /dev/dasda /dev/dasdb etc. Lonny -Original Message- From: Scott Chapman [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 7:36 AM To: [EMAIL PROTECTED] Subject: DASD not recognized in Debian I wanted to install Debian on one of our virtual servers just to see it work and possible to keep around as a "demo" system if we don't move forward witha full SuSE/VM installation at this time. Unfortunately I haven't been successful. I took down one of the virtual servers, and attached it's minidisk to another one running SuSE. I then used debootstrap to install the base configuration on that minidisk. I then configured the base Debian image and ran zipl to make it bootable. I detached the minidisk from the SuSE system, logged on to the VM userid for the Debian system and tried to IPL it (device 151). It seemed to start the boot process ok, but it fails trying to access the ext2 filesystem on the minidisk that has the root filesystem--which is the same minidisk it was booting off from. I can re-attach the minidisk to the SuSE system and access the file system fine, but I can't even do an fdasd on the volume from the Debian system--almost like Debian isn't recognizing the DASD at all, despite being able to boot from it. I've probably missed something "obvious"--if somebody could point it out to me, I'd appreciate it. Thanks! Scott Chapman American Electric Power dasd: initializing... debug: dasd: new level 3 dasd: Registered successfully to major no 94 dasd(eckd): ECKD discipline initializing dasd(eckd): /dev/dasdb ( 94: 4),0151@03: 3390/0A(CU:3990/01) Cyl:1365 Head:15 Sec:224 dasd(eckd): /dev/dasdb ( 94: 4),0151@03: 3390/0A(CU:3990/01): Configuration da ta read debug: dasdb: new level 3 dasd(eckd): /dev/dasdb ( 94: 4),0151@03: (4kB blks): 982800kB at 48kB/trk comp atible disk layout dasd(eckd): /dev/dasdc ( 94: 8),0152@04: 3390/0A(CU:3990/01) Cyl:50 Head:15 Se c:224 dasd(eckd): /dev/dasdc ( 94: 8),0152@04: 3390/0A(CU:3990/01): Configuration da ta read debug: dasdc: new level 3 dasd: waiting for responses... dasd(eckd): /dev/dasdc ( 94: 8),0152@04: (4kB blks): 36000kB at 48kB/trk compa tible disk layout Partition check: /dev/dasd/0151:VOL1/ 0X0180: p1 /dev/dasd/0152:VOL1/ 0X0152: p1 Checking root file system... fsck 1.27 (8-Mar-2002) fsck.ext2: No such file or directory while trying to open /dev/dasdb1 /dev/dasdb1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 Even trying to run fdasd fails on Debian: (none):~# fdasd /dev/dasdb fdasd /dev/dasdb fdasd error: device verification failed The specified device is not a valid DASD device (none):~#
Re: DASD not recognized in Debian
Scott Chapman wrote: /dev/dasd/0151:VOL1/ 0X0180: p1 /dev/dasd/0152:VOL1/ 0X0152: p1 Debian uses DevFS on S/390 so the device files are named /dev/dasd//* instead of /dev/dasd[a-z]*. is the device number, e.g. 0151. Even trying to run fdasd fails on Debian: (none):~# fdasd /dev/dasdb fdasd /dev/dasdb Try fdasd /dev/dasd/0151/disc Regards, Stefan Gybas
Re: System Installation Suite on zSeries ?
You might want to look at Levanta, which I saw recently at LinuxWorld... http://www.linuxcare.com/products/levanta/features.epl Bill -Original Message- From: Seifert, Harald [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 8:59 AM To: [EMAIL PROTECTED] Subject: System Installation Suite on zSeries ? I'm searching for a tool to clone Linux Images under z/VM. I have found in the IBM Redbook "Linux on zSeries & S/390: System Management" Chapter 8 the System Installation Suite described, but there is stated that SIS is beta on zSeries. Does anyone have some experiences with SIS on zSeries ? -- Harald Seifert Informatik-Systemprogrammierung HUK Coburg Bahnhofsplatz 96444 Coburg Phone +049 (0)9561-961787 Fax+049 (0)9561-963671 Mailto [EMAIL PROTECTED]
Memories
See http://vm.marist.edu/~vmshare/browse?fn=HISTORY&ft=MEMO Quite a few familiar names *_*. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: System Installation Suite on zSeries ?
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Seifert, Harald Sent: Monday, January 27, 2003 3:59 PM To: [EMAIL PROTECTED] Subject: System Installation Suite on zSeries ? I'm searching for a tool to clone Linux Images under z/VM. I have found in the IBM Redbook "Linux on zSeries & S/390: System Management" Chapter 8 the System Installation Suite described, but there is stated that SIS is beta on zSeries. Does anyone have some experiences with SIS on zSeries ? -- Harald Seifert Informatik-Systemprogrammierung HUK Coburg Bahnhofsplatz 96444 Coburg Phone +049 (0)9561-961787 Fax+049 (0)9561-963671 Mailto [EMAIL PROTECTED]
System Installation Suite on zSeries ?
I'm searching for a tool to clone Linux Images under z/VM. I have found in the IBM Redbook "Linux on zSeries & S/390: System Management" Chapter 8 the System Installation Suite described, but there is stated that SIS is beta on zSeries. Does anyone have some experiences with SIS on zSeries ? -- Harald Seifert Informatik-Systemprogrammierung HUK Coburg Bahnhofsplatz 96444 Coburg Phone +049 (0)9561-961787 Fax+049 (0)9561-963671 Mailto [EMAIL PROTECTED]
Re: have to remount after restart
On Sunday 26 January 2003 19:27, you wrote: > If your filesystem is ext2 you specify ext2, and if it is ReiserFS you > specify reiserfs, like this: > /dev/hda/all/usr reiserfsdefaults 1 2 > > Rob Reiser recommends that you not auto check that filesystem with the standard fsck tools (journaling filesystem, it autochecks anyway and replays logs as needed). /dev/hda/all/usr reiserfsdefaults 0 0
DASD not recognized in Debian
I wanted to install Debian on one of our virtual servers just to see it work and possible to keep around as a "demo" system if we don't move forward witha full SuSE/VM installation at this time. Unfortunately I haven't been successful. I took down one of the virtual servers, and attached it's minidisk to another one running SuSE. I then used debootstrap to install the base configuration on that minidisk. I then configured the base Debian image and ran zipl to make it bootable. I detached the minidisk from the SuSE system, logged on to the VM userid for the Debian system and tried to IPL it (device 151). It seemed to start the boot process ok, but it fails trying to access the ext2 filesystem on the minidisk that has the root filesystem--which is the same minidisk it was booting off from. I can re-attach the minidisk to the SuSE system and access the file system fine, but I can't even do an fdasd on the volume from the Debian system--almost like Debian isn't recognizing the DASD at all, despite being able to boot from it. I've probably missed something "obvious"--if somebody could point it out to me, I'd appreciate it. Thanks! Scott Chapman American Electric Power dasd: initializing... debug: dasd: new level 3 dasd: Registered successfully to major no 94 dasd(eckd): ECKD discipline initializing dasd(eckd): /dev/dasdb ( 94: 4),0151@03: 3390/0A(CU:3990/01) Cyl:1365 Head:15 Sec:224 dasd(eckd): /dev/dasdb ( 94: 4),0151@03: 3390/0A(CU:3990/01): Configuration da ta read debug: dasdb: new level 3 dasd(eckd): /dev/dasdb ( 94: 4),0151@03: (4kB blks): 982800kB at 48kB/trk comp atible disk layout dasd(eckd): /dev/dasdc ( 94: 8),0152@04: 3390/0A(CU:3990/01) Cyl:50 Head:15 Se c:224 dasd(eckd): /dev/dasdc ( 94: 8),0152@04: 3390/0A(CU:3990/01): Configuration da ta read debug: dasdc: new level 3 dasd: waiting for responses... dasd(eckd): /dev/dasdc ( 94: 8),0152@04: (4kB blks): 36000kB at 48kB/trk compa tible disk layout Partition check: /dev/dasd/0151:VOL1/ 0X0180: p1 /dev/dasd/0152:VOL1/ 0X0152: p1 Checking root file system... fsck 1.27 (8-Mar-2002) fsck.ext2: No such file or directory while trying to open /dev/dasdb1 /dev/dasdb1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 Even trying to run fdasd fails on Debian: (none):~# fdasd /dev/dasdb fdasd /dev/dasdb fdasd error: device verification failed The specified device is not a valid DASD device (none):~#
Natural for Linux 390
ADABAS, Natural and Entire Network are available for Linux for S/390 ? I couldn´t find the onformation on SOFTWARE AG SITE. Where do i get the information. Regards.
