Installing D3 on Linux
Marik
problem which I hope someone can solve. In particular I hope Mark Brown or
someone else from PICK Systems reads this since I have been unable to get
any help from PICK.
I have loaded Linux on a new server which did not have any operating system
previously loaded. I created a 3gb Linux primary partition, 2 - 120mb Linux
swap partitions and a 5.5gb extended partition which I separated into 3 Pick
partitions (SDA5, SDA6, SDA7), ID type 62. I mounted the CD, did the tar
command and got to the menu (in section 3 of the D3 installation manual)
where you can change the amount of memory, number of ports, number of
phantoms, etc. Selection 13 which has to do with partitions does not show
the hard drive info that is shown in the manual (Volume 1, SDA, etc); that
space is blank. When I attempt to add a partition (SDA5,SDA6 & SDA7),
nothing happens.
I assume that I have made an error in fdisk when setting up the original
partitions but can't find anything in the manual.
Any help would be appreciated. Thanks in advance.
Best regards,
Bob Marik
Bryan Buchanan
Bob,
Do "fdisk" then "p" to display partition table and post the results.
I usually make all my partitions (except swap) type 83, Linux Native,
but I doubt this makes any difference.
When you choose option 13, another table of options comes up,
I think there is an option "u" to use a named partition. This should
display all the partitions on the drive, from which you can choose
those to use for D3.
Bryan
Bill Millikin
RedHat kernel required for anything older than the beta of 7.2 .. Every
time I try to do the same thing, I get the same results. Use an old RedHat
4.2, or a Caldera 1.2, or TurboLinux of the same vintage, and the partitions
will show up just as nice as can be.
The interesting thing I've found is that once D3 is installed on the old
Linux, you can upgrade Linux and everything continues working very well.
HTH
Bill Millikin -
Garry Dixon
I had this problem before, the way round it is to manually create a
pick0 item containing the disk statements required. If you are creating
a new pick0 then you can just place the disk entries in pick0 file in
/usr/lib/pick/
disk /dev/sda5 0 <number of blocks>
To find the number of blocks fdisk -l /dev/sda
The number of blocks must be an even number otherwise Pick will
complain.
When you run the D3_setup the disk entries will be in option 13.
I think this problem has been fixed on later releases of D3/Linux.
Garry Dixon
Tony Gravagno
think some rebuttal is required to comments made so far in this thread.
1) Marik wrote: "I am in the process of trying to install D3 on Linux"
-- Which version of D3 and which version of Linux? In all the threads in this
forum on this topic, it has been stated all too many times that specific versions
of D3 are certified to work on specific versions of Linux. An accurate response
can't be provided without release information.
2) Marik wrote: "I have been unable to get any help from PICK"
-- Who did you call and what was the response? You have a simple question with a
simple answer and I don't think they would have any technical problems answering
it, so something else must be going on.
3) Bryan wrote:
> When you choose option 13, another table of options comes up,
> I think there is an option "u" to use a named partition. This should
> display all the partitions on the drive, from which you can choose
> those to use for D3.
--This is correct and I believe it's the answer for you, Marik. D3 Linux, from
looking at a partition table with names like "sda1, hdb2, etc", has no way to know
what partition was reserved for D3, so you need to go and Use Existing, or create
new partitions yourself. If you do create new partitions, remember to reboot the
system after you have done the "Install with Current Settings", otherwise the
partition table will not be registered properly. (That's a Linux thing, not a D3
thing.) From there, you can do the "d3 -0" and install ABS and files.
4) Bill wrote: "My guess is that you're installing on a new kernel, instead of the
4.2 RedHat kernel required for anything older than the beta of 7.2 .. Every
time I try to do the same thing, I get the same results."
-- 4.2 kernel? The highest kernel available is in the 2.2 range. You mean the
base release of RedHat 4.2? D3 7.1 is built, tested, and supported over RedHat
5.0 and 5.1 - why even attempt to install over an old release like 4.2? D3 7.2 is
built, tested, and supported over RedHat 6.1 (though it should work fine over 6.0
as well), why are dealers trying to re-engineer it to run over previous releases?
5) Bill wrote: "Use an old RedHat 4.2, or a Caldera 1.2, or TurboLinux of the same
vintage, and the partitions will show up just as nice as can be."
--That could be true, but then your environment will be unsupportable by Pick
Systems. How can they take responsibility for the functionality of your
environment when you have installed using software that has never been tested? I
don't know what the Support agreements say, but just think for yourself what
happens if you call someone and ask "why doesn't xxx work" and it turns out you
are running in an environment they've never seen before. You can't reasonably
expect anyone to support that software.
6) Bill wrote: "The interesting thing I've found is that once D3 is installed on
the old Linux, you can upgrade Linux and everything continues working very well."
-- That is interesting. If you are talking about patches, that's one thing, or
perhaps RedHat 5.0 to 5.1 upgrades for a D3 Linux 7.1. Regarding D3 7.2 over
RedHat 5.x - I wouldn't even try it. Or D3 7.1 over RedHat 6.x - I wouldn't try
this either (maybe 6.0, but not 6.1). In any case, I personally wouldn't trust
any such a cross-environment, and again it can't be supported effectively. The
unqualified statement with the words "old Linux", "upgrade", and "everything" are
way too general. If you could provide specifics, that would be nice, but as it
is, your statement implies a general truth which is technically incorrect.
7) Garry wrote: "I had this problem before, the way round it is to manually create
a pick0 item containing the disk statements required ... I think this problem has
been fixed on later releases of D3/Linux."
--Yes, creating disk lines manually is an option. As I said however, how does D3
know which disk lines are available for it? It's not a D3 problem. In a system
where logical disk volumes can have names like "pick0", D3_setup can parse for the
string 'pick' and make a guess that this is probably a usable disk volume.
Otherwise, the user must Add a new volume or Use an existing one.
It's not my intent to take issue with the individuals here, only the specific
comments indicated above.
Regards,
Tony
--
Tony Gravagno @Home
http://members.home.net/gravagno/index.html
George Shaunfield
doesn't seem to make any difference. In the D3 Virtual Disk option (as you
have stated your configuration) no partitions show up until you choose
U)se existing partition. Then ALL of your partitions will be listed. Be
sure you choose only the partitions you have designated for D3 (and not
formatted). You were just about there.
George Shaunfield
AccounTron
Bryan Buchanan wrote:
>
> Marik wrote:
>
> > I am in the process of trying to install D3 on Linux but have run into a
> > problem which I hope someone can solve. In particular I hope Mark Brown or
> > someone else from PICK Systems reads this since I have been unable to get
> > any help from PICK.
> >
> > I have loaded Linux on a new server which did not have any operating system
> > previously loaded. I created a 3gb Linux primary partition, 2 - 120mb Linux
> > swap partitions and a 5.5gb extended partition which I separated into 3 Pick
> > partitions (SDA5, SDA6, SDA7), ID type 62. I mounted the CD, did the tar
> > command and got to the menu (in section 3 of the D3 installation manual)
> > where you can change the amount of memory, number of ports, number of
> > phantoms, etc. Selection 13 which has to do with partitions does not show
> > the hard drive info that is shown in the manual (Volume 1, SDA, etc); that
> > space is blank. When I attempt to add a partition (SDA5,SDA6 & SDA7),
> > nothing happens.
> > I assume that I have made an error in fdisk when setting up the original
> > partitions but can't find anything in the manual.
> >
> > Any help would be appreciated. Thanks in advance.
> >
> > Best regards,
> > Bob Marik
>
> Bob,
>
> Do "fdisk" then "p" to display partition table and post the results.
>
> I usually make all my partitions (except swap) type 83, Linux Native,
> but I doubt this makes any difference.
>
> When you choose option 13, another table of options comes up,
> I think there is an option "u" to use a named partition. This should
> display all the partitions on the drive, from which you can choose
> those to use for D3.
>
> Bryan
Richard Ginsburg
D3 7.1 is built, tested, and supported over RedHat 5.0 and 5.1 - why even
attempt to install over an old release like 4.2? D3 7.2 is built, tested,
and supported over RedHat 6.1 (though it should work fine over 6.0 as well),
why are dealers trying to re-engineer it to run over previous releases?
Tony,
With regard to Linux versions and D3 versions:
D3Linux 7.1 is certified for RedHat 5.0 and 5.1, yes? Why not 5.2 which
appears to be the production release. We have only been installing with 5.2
for all our D3Linux systems.
D3Linux 7.2 was made to work with RedHat 6.0 and has now been updated to
work with 6.1. As I understand their numbering system, I believe that there
is going to be a production release called 6.2. Has anyone at Pick Systems
spoken to the folks at RedHat to confirm this? Will D3Linux 7.2 still work
with RedHat 6.0 or 6.1 - if 6.2 becomes fact?
I think the problem here is that you can buy every release of RedHat
Linux from 4.2 to 6.1 in most stores. Users are snatching up copies and
building servers to try out this new thing. As VAR's we often get involved
with a user site that has a particular version of RedHat running and we need
to have the correct version of D3Linux for them or force them to upgrade.
--
Richard Ginsburg can be reached at:
E-Mail: fawn...@mindspring.com
Web...: http://www.fawnridge.com
Phone.: 561.488.4815
Fax...: 561.488.3821
Only the finest software is called COMPASS...
Garry Dixon
current disk partitions. This is due to the setup process not being
able to detect the disks, possibly due to the fdisk changing the way it
works in different releases of Linux.
Garry Dixon
-----Original Message-----
From: George Shaunfield [mailto:geo...@accountron.com]
Posted At: 23 January 2000 04:49
Posted To: pick
Conversation: Installing D3 on Linux
Tony Gravagno
partitioning of disks should take care of this. Page 23 of the 7.2Beta
installation guide, under Red Hat Linux Installation, states "When the
installation is complete, a final reboot is required to load all packages".
Further, after doing "install D3 with chosen settings", the last thing to do
is reboot (page 43).
Tony
Garry Dixon wrote:
> Taking the U)se existing partition does not always produce a list of
> current disk partitions. This is due to the setup process not being
> able to detect the disks, possibly due to the fdisk changing the way it
> works in different releases of Linux.
>
> Garry Dixon
>
> From: George Shaunfield [mailto:geo...@accountron.com]
> I agree with Bryan. Leaving the partition type at 83 or changing it to
> 62
> doesn't seem to make any difference. In the D3 Virtual Disk option (as
> you
> have stated your configuration) no partitions show up until you choose
> U)se existing partition. Then ALL of your partitions will be listed. Be
> sure you choose only the partitions you have designated for D3 (and not
> formatted). You were just about there.
[snip]
--
Tony Gravagno - Pick Systems
Corporate Technical Account Manager
USA ph. 949-260-5104 fax 949-261-5308
http://www.picksys.com
http://members.home.net/gravagno/index.html
Garry Dixon
the D3_setup and not the Linux Setup. As pointed out by John Keefe in
the other half of this thread the fdisk -l option doesn't work in Redhat
6.0 and as D3 uses this form to get the partitions it cannot work.
I am quite sure that Pick has this covered in the 7.2/6.1 release.
On another point I think it shows that Pick is moving in the right
direction by pulling the 7.2 for Redhat 6.0 and going for 6.1. I don't
mind having to wait a couple of months before a release that will last a
lot longer.
Garry Dixon
-----Original Message-----
From: Tony Gravagno [mailto:to...@picksys.com]
Posted At: 24 January 2000 21:25
Posted To: pick
Conversation: Installing D3 on Linux
Subject: Re: Installing D3 on Linux