OS/2, eCS & ArcaOS - Technical > Setup & Installation

eCS 2.2 YUM/RPM question

<< < (4/7) > >>

Sigurd Fastenrath:

--- Quote from: Andi B. on January 30, 2013, 12:04:15 pm ---Although answered numerous times here again what I can say from the top of my head -

3) no, yes
4) no
5) 3 dirs are created at root. AFAIR /usr /etc /var


--- Quote ---Might it be possible to answer this easy question with an easy YES or NO?  - > Thanks in Advance!
--- End quote ---
No. As you see above I needed a little more for 5)  ;)

I could give here links to the netlabs rpm sites and readmes, but this is would be more than YES or NO too....  :)

--- End quote ---

Thanks you very much, Andi! I know that I am a bit annoying sometimes  ;)

For 3 your answer is: 3) no, yes

-> that leads me to my initial conclusions:

During install I have two possibilities: install YUM/RPM on bootdrive or on another drive
-> If I want to install it on another Drive this drive has to be already created and formatted before the "real" installation starts, otherwise I will not be able to install ODIN and so on...
-> If the Drive is not present or if I am "Just" a simple user (like me  ::)  ) and I have no deep information about it while installing I will choose the installation drive. In this case I have to have in mind to have more than 2GB at hand, otherwise - as all the executables of future YUM/RPM programs will go into the bootdrive as well - I will soon run out of space.

It is a pitty that I can not use my mother tongue to explain what I want to stress, but this time I will just write a few sentences in German and am sorry for this  8)

-> Ohne entsprechende Hinweise vor oder während der Installation wird Otto Normalverbraucher nicht realisieren können, welch wichtige Entscheidung er zu treffen hat, WO genau YUM/RPM installiert werden soll. Folgt er den Hinweisen von Mensys wonach für die Installation insgesamt 2GB Platz genug wären und ist er sich nicht im klaren, dass bei Installation von YUM/RPM auf dem Bootlaufwerk sein Plattenplatz evtl. zügig zur Neige geht (weil große Teile aller Folgeprogramme ebenfalls dort abgelegt werden), wird er oder sie nicht lange Freude an seiner Installation haben.

Doug Bissett:

--- Quote ---If I want to install it on another Drive this drive has to be already created and formatted before the "real" installation starts, otherwise I will not be able to install ODIN and so on...
--- End quote ---

True, but that is very easy to do. In most cases, on a re-install, the alternate drive will already be set up, and formatted. If it is s new install, and the drive isn't already set up, you can do that when you set up the drive during install. Create all of the volumes, then the install drive is formatted. At that time, there is the option to format the rest of your drives (JFS, HPFS, etc. Not FAT32 or NTFS). Once they are formatted, you are free to use them.

Personally, I take the opportunity to select the alternate drive to contain the %HOME% and %PROGRAMS% directories too. Hopefully, the updated installer will also allow a user to specify the %UNIXROOT% directory at the same time, even if a user chooses not to use RPM/YUM. If that is done, and %UNIXROOT% is placed on an alternate drive, a user should be able to install RPM/YUM some time in the future, without messing up too many things. One of the reasons that I do that, is that I can share those directories between multiple boot drives. I am not sure what implications that would have with RPM/YUM (could be a horror show, if they don't do things properly), but everything else that I have tried works fine.

guzzi:
I already have rpm/yum on an alternate drive. When the new eCS comes out and I would install it on a second boot partition with rpm/yum in the same place as it is now I expect there might be problems because files would get overwritten and the database will get messed up. So I intend -not- to install rpm/yum but simply copy and paste the appropriate lines from the old config.sys to the new one.

ivan:

--- Quote from: guzzi on January 30, 2013, 06:59:04 pm ---I already have rpm/yum on an alternate drive. When the new eCS comes out and I would install it on a second boot partition with rpm/yum in the same place as it is now I expect there might be problems because files would get overwritten and the database will get messed up. So I intend -not- to install rpm/yum but simply copy and paste the appropriate lines from the old config.sys to the new one.

--- End quote ---
And that appears to be the big problem - multiple OS/2 eCS boot partitions on the same machine using common applications installed on a partition that can be used by all boot versions.

Doug Bissett:

--- Quote from: ivan on January 30, 2013, 10:18:24 pm ---
--- Quote from: guzzi on January 30, 2013, 06:59:04 pm ---I already have rpm/yum on an alternate drive. When the new eCS comes out and I would install it on a second boot partition with rpm/yum in the same place as it is now I expect there might be problems because files would get overwritten and the database will get messed up. So I intend -not- to install rpm/yum but simply copy and paste the appropriate lines from the old config.sys to the new one.

--- End quote ---
And that appears to be the big problem - multiple OS/2 eCS boot partitions on the same machine using common applications installed on a partition that can be used by all boot versions.

--- End quote ---

It has been NO PROBLEM, for me, but I haven't tried it with RPM/YUM. I share almost everything, on a common drive, between boot partitions. Some of them are (in no particular order):
SAMBA
GENMAC
OpenOffice 3.2
ODIN
JAVA
QT4
Firefox
PMMail
Thunderbird
BackAgain/2000
CDDVDCreator
DVDDAO
DOS BOX
Electronic Teller
Embelish
FotoGet
House/2
Lotus Smartsuite
PMView Pro
Seamonkey
Photo>Graphics Pro
VirtualBox
FocusWriter
GenealogyJ (JAVA)
Scribus
AVxCAT
PM123
SMplayer/Mplayer
Timidity
VLC
APC UPS monitor
BootAble
ClamAV
DFSEE
eCSMT
FM/2
RSync
and  few more that I don't use much.

Basically, most programs can be shared between boot systems, with no trouble. Doing it that way makes it a LOT easier when the time comes to install a new version of eCS. Generally, you do need to re-install the program, over top of the old, using the new boot system. Sometimes, simply creating icons is enough. WarpIN makes it very easy to just run through your collection of installers, to get it done. The best programs store all of there configuration stuff in their own directory, so it can be used by any boot system. Not too far behind, are those that store config stuff in the %HOME% directory (which also needs to be on the common drive), although I find that that gets badly cluttered. The worst programs, are those that insist on storing configuration stuff on the boot drive, especially when they put it in the system INI files. Even that is not a real problem, it just means that you need to be more careful when installing the programs.

I suspect that RPM/YUM will keep all of the configuration stuff in it's own directory structure, but I am not sure how easy it will be to synchronize it between two boot systems.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version