Re: rh7.2 upgrading util-linux package
At 21:16 29-07-02 +0200, Karsten Hopp wrote: %ifnarch s390 s390x /sbin/fdisk %endif Wait a moment... I think it would be wise to have 'fdisk' on s390 as well, and not as a symlink to fdasd. Since 'fdasd' can only talk to devices controlled by the dasd driver, would you not need the pure fdisk to parition any other block device? I believe it just builds out of the box. Rob
Re: rh7.2 upgrading util-linux package
On Mon, 16 Dec 2002 14:35, you wrote: Wait a moment... I think it would be wise to have 'fdisk' on s390 as well, and not as a symlink to fdasd. Since 'fdasd' can only talk to devices controlled by the dasd driver, would you not need the pure fdisk to parition any other block device? I believe it just builds out of the box. You _can_ run fdisk against a file, I've just done it. I did have to set the device geometry. I don't know how to access the partition I created though - perhaps using one of those odd network block drivers, or accessing it via user-mode-linux. The point though is that you can use it to partition a file. -- 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: rh7.2 upgrading util-linux package
Yes, it does build. At some point it will be useful to have it working on Linux/390. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Rob van der Heij Sent: Monday, December 16, 2002 1:36 AM To: [EMAIL PROTECTED] Subject: Re: rh7.2 upgrading util-linux package At 21:16 29-07-02 +0200, Karsten Hopp wrote: %ifnarch s390 s390x /sbin/fdisk %endif Wait a moment... I think it would be wise to have 'fdisk' on s390 as well, and not as a symlink to fdasd. Since 'fdasd' can only talk to devices controlled by the dasd driver, would you not need the pure fdisk to parition any other block device? I believe it just builds out of the box. Rob
Re: rh7.2 upgrading util-linux package
I was looking for something else and stumbled onto this post from the end of July which I had missed at that time. (Too much good info on this list!) To fix a collision between util-linux and s390-tools, Karsten Hopp said: The correct way would be to edit the util-linux.spec file and rebuild the package with the patched spec file. Search for /sbin/fdisk in the %files section and either comment it out or better surround with ifnarch like this: %ifnarch s390 s390x /sbin/fdisk %endif Neat trick. Good to know. But this worries me. IBM needs to figure out if they *really* need a custom 'fdisk' in the S390 Tools kit since they clearly will need normal FDISK to support SCSI. I would prefer that the FDISK included in Util-Linux be properly patched than to see two versions of it. If there must be two, then it might be wise to rename the newcomer 'fdisk390'. Thoughts? -- RMT
Re: rh7.2 upgrading util-linux package
Rick, More careful reading ( =:o ) of the thread reveals that s390utils provides fdasd, and a symbolic link to that named fdisk. So, the real name doesn't conflict, just the link. In the future, the link could be replaced by a real module, perhaps just the same as fdisk is now, but enhanced for Linux/390. Personally, I would have preferred that fdasd never have existed, rather that the fdisk code been upgraded to handle all disk types. I still think that is the way to go in the future. It will be one less difference between Linux in general and Linux/390 to trip up newcomers. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Rick Troth Sent: Friday, December 13, 2002 2:12 PM To: [EMAIL PROTECTED] Subject: Re: rh7.2 upgrading util-linux package I was looking for something else and stumbled onto this post from the end of July which I had missed at that time. (Too much good info on this list!) To fix a collision between util-linux and s390-tools, Karsten Hopp said: The correct way would be to edit the util-linux.spec file and rebuild the package with the patched spec file. Search for /sbin/fdisk in the %files section and either comment it out or better surround with ifnarch like this: %ifnarch s390 s390x /sbin/fdisk %endif Neat trick. Good to know. But this worries me. IBM needs to figure out if they *really* need a custom 'fdisk' in the S390 Tools kit since they clearly will need normal FDISK to support SCSI. I would prefer that the FDISK included in Util-Linux be properly patched than to see two versions of it. If there must be two, then it might be wise to rename the newcomer 'fdisk390'. Thoughts? -- RMT
Re: rh7.2 upgrading util-linux package
Mark Post wrote: Rick Troth wrote: IBM needs to figure out if they *really* need a custom 'fdisk' in the S390 Tools kit since they clearly will need normal FDISK to support SCSI. I would prefer that the FDISK included in Util-Linux be properly patched than to see two versions of it. If there must be two, then it might be wise to rename the newcomer 'fdisk390'. [...] More careful reading ( =:o ) of the thread reveals that s390utils provides fdasd, and a symbolic link to that named fdisk. So, the real name doesn't conflict, just the link. In the future, the link could be replaced by a real module, perhaps just the same as fdisk is now, but enhanced for Linux/390. Personally, I would have preferred that fdasd never have existed, rather that the fdisk code been upgraded to handle all disk types. I still think that is the way to go in the future. Hmm, I'm not entirely sure about that. The fdisk program on Linux was originally made to be a one-on-one functional replacement for the equivalent DOS program named FDISK, dealing with the IBM PC hard disk partition table format. These days, the Linux implementation of fdisk appears to also support some other partitioning schemes, such as BSD/SUN and SGI. Other Unix systems have had tools to manipulate their own disk partition tables, going by various names, such as disklabel, mkpart, parted, etc. The PC platform has added one level of confusion to the partition table story in that several UNIX implementations took their own partitioning scheme with them and added it on top of the original IBM PC partition table, which was primarily used to segregate different operating systems. E.g. FreeBSD has both an fdisk utility to manipulate the PC partition table, which is primarily used to give FreeBSD a partition (named slice in this context) in the view of any other operating systems that might be on there, and a disklabel utility to manipulate its own partition table that is used to define the various partitions used for different filesystems such. Linux, not having a non-PC history behind it, did things a bit differently and used the PC partition table as its native partition table on PC platforms. The situation with Linux/390 DASD is obviously entirely different, with Linux partitions being defined as items in the platform's native VTOC table. There is no relation at all with the IBM PC partition table scheme. Now, since Linux/390 also supports SCSI disks these days, it could very well deal with disks with PC, Sun, BSD or SGI partition tables, and thus the solution to exclude the existing fdisk program from the S/390 platform, as suggested, is clearly wrong. The conclusion must be that the link from fdisk to fdasd was a mistake, perhaps borne out of a desire to make Linux on S/390 look just like Linux on PC. Whether one wants to add IBM DASD VTOC partitioning support to fdisk, I have to wonder. This is a fundamentally different scheme, and there is no interaction whatsoever between them. My choice would be to keep it separate, choose a fitting name from a wider Unix context, rather than the current fdasd name, which contrasts it to fdisk in a narrow PC Linux context, and make sure there is no confusion with the fdisk program. Does anyone know what these tools on UTS and/or AIX/370 were called? -- Willem Konynenberg [EMAIL PROTECTED] Konynenberg Software Engineering
Re: rh7.2 upgrading util-linux package
thanks Karsten, worked great. ~ Daniel [EMAIL PROTECTED] wrote: Hello, The correct way would be to edit the util-linux.spec file and rebuild the package with the patched spec file. Search for /sbin/fdisk in the %files section and either comment it out or better surround with ifnarch like this: %ifnarch s390 s390x /sbin/fdisk %endif Karsten On Mon, Jul 29, 2002 at 03:10:19PM -0400, [EMAIL PROTECTED] wrote: Hopefully this forum is okay for this question... I was hoping to upgrade the util-linux package for advisory RHSA-2002:132-14 (http://rhn.redhat.com/errata/RHSA-2002-132.html) rebuilt util-linux from src.rpm, went to install # rpm -Uhv util-linux-2.11f-17.7.2.s390.rpm Preparing...### [100%] file /sbin/fdisk from install of util-linux-2.11f-17.7.2 conflicts with file from package s390utils-20011109-6 /sbin/fdisk is just a symlink to /sbin/fdasd, provided by s390utils (installed from a redhat built s390.rpm). Would removing the symlink, rpm -Uhv --force, and then re-replacing fdisk with the symlink be a bad idea? What's the rpm-friendly way? (I'd rather use the tool correctly) Thanks for any guidance, ~ Daniel -- Karsten Hopp| Mail: [EMAIL PROTECTED] Red Hat Deutschland | Tel: +49-711-96437-0 Hauptstaetterstr.58 | Fax: +49-711-96437-111 D-70178 Stuttgart | http://www.redhat.de
Re: rh7.2 upgrading util-linux package
Hello, The correct way would be to edit the util-linux.spec file and rebuild the package with the patched spec file. Search for /sbin/fdisk in the %files section and either comment it out or better surround with ifnarch like this: %ifnarch s390 s390x /sbin/fdisk %endif Karsten On Mon, Jul 29, 2002 at 03:10:19PM -0400, [EMAIL PROTECTED] wrote: Hopefully this forum is okay for this question... I was hoping to upgrade the util-linux package for advisory RHSA-2002:132-14 (http://rhn.redhat.com/errata/RHSA-2002-132.html) rebuilt util-linux from src.rpm, went to install # rpm -Uhv util-linux-2.11f-17.7.2.s390.rpm Preparing...### [100%] file /sbin/fdisk from install of util-linux-2.11f-17.7.2 conflicts with file from package s390utils-20011109-6 /sbin/fdisk is just a symlink to /sbin/fdasd, provided by s390utils (installed from a redhat built s390.rpm). Would removing the symlink, rpm -Uhv --force, and then re-replacing fdisk with the symlink be a bad idea? What's the rpm-friendly way? (I'd rather use the tool correctly) Thanks for any guidance, ~ Daniel -- Karsten Hopp| Mail: [EMAIL PROTECTED] Red Hat Deutschland | Tel: +49-711-96437-0 Hauptstaetterstr.58 | Fax: +49-711-96437-111 D-70178 Stuttgart | http://www.redhat.de
