I installed FC1 as a text install, via ftp. I thought I selected "install everything", but now I go to install a program and it says no compiler is available etc.
I can ssh to the machine and use the cli (root as required), but I don't know what commands to use to get it to install more things.
I know the ftp site (it's one of my servers) so that's not a problem... but what I'd really like is if I can just install everything that's missing....
Any suggestions for how to do that via cli?
Thanks, Don
On Tue, 2003-12-02 at 13:03, Don wrote:
I installed FC1 as a text install, via ftp. I thought I selected "install everything", but now I go to install a program and it says no compiler is available etc.
[snip]
I know the ftp site (it's one of my servers) so that's not a problem... but what I'd really like is if I can just install everything that's missing....
The easiest way would be to use redhat-config-packages with the --tree option, and then select everything.
Alternatively, you could do it by hand, which requires some playing around to get it right:
If you can somehow mount the install directory containing the rpms (which should be easy if its one of yours, eg by nfs) then you can just
cd <wherever> rpm -Uvh *rpm
and _every_ rpm in that directory will be installed if not so already. This can also be used to update rpms. Be careful with rpms that are compiled for multiple archs, and kernel rpms. Do these first. You should probably do somethimg more like
rpm -Uvh [^k]*i686.rpm then all the k*rpm that aren't kernel ones, then rpm -Uvh [^k]*i386.rpm
(Conversely, to only update rpms that have previously been installed, use `rpm -Fvh *rpm`)
HTH,
On Mon, 2003-12-01 at 20:11, Iain Buchanan wrote:
The easiest way would be to use redhat-config-packages with the --tree option, and then select everything.
I tried that and get this error: [root@rocky root]# redhat-config-packages --tree Unable to import gtk module. This may be due to running without $DISPLAY set. Exception was: could not open display Traceback (most recent call last): File "/usr/share/redhat-config-packages/MainWindow.py", line 11, in ? sys.exit(0) NameError: name 'sys' is not defined
I never did get X installed on that system... I use ssh to come in from another (bigger/faster/more capable) machine.
Alternatively, you could do it by hand, which requires some playing around to get it right:
If you can somehow mount the install directory containing the rpms (which should be easy if its one of yours, eg by nfs) then you can just
That sounds cool, but I don't know how to do that. The ftp server is on a Win2000 machine..... I'm working toward an all-linux set up, but that's anothr story.
cd <wherever> rpm -Uvh *rpm
That sounds the simplest.... all I need now is to learn how to mount a windows folder over the network.... Ill see what I can find ...
Thanks, Don
On Tue, 2003-12-02 at 14:08, Don wrote:
On Mon, 2003-12-01 at 20:11, Iain Buchanan wrote:
The easiest way would be to use redhat-config-packages with the --tree option, and then select everything.
I tried that and get this error:
[snip]
I never did get X installed on that system... I use ssh to come in from another (bigger/faster/more capable) machine.
Ah, yes. That a graphical program, so it will only work with X.
Alternatively, you could do it by hand, which requires some playing around to get it right:
If you can somehow mount the install directory containing the rpms (which should be easy if its one of yours, eg by nfs) then you can just
That sounds cool, but I don't know how to do that. The ftp server is on a Win2000 machine..... I'm working toward an all-linux set up, but that's anothr story.
cd <wherever> rpm -Uvh *rpm
That sounds the simplest.... all I need now is to learn how to mount a windows folder over the network.... Ill see what I can find ...
If you have physical access to the machine, you could insert the cd's into the drive, and cd (change directory) to each cd (compact disc :) one by one. This may leave some dependacy problems across cd's so alternatively you could copy all rpms to a temporary folder, and do it that way.
Thinking about it a bit more, you can copy them via ftp to a local folder, and then do the rpm thing.
HTH,
On Mon, 2003-12-01 at 20:52, Iain Buchanan wrote:
Thinking about it a bit more, you can copy them via ftp to a local folder, and then do the rpm thing.
It's running all the installs now... it seems to install packages that are already installed...
[root@rocky temprpm]# rpm -Uvh *.rpm warning: package glibc = 2.3.2-101 was already added, replacing with glibc <= 2.3.2-101
Is this a bug where decision to skip needs to include the "equal" condition? Or is it a feature that allows the reinstallation of previously installed rpms?
Don
On Tue, 2003-12-02 at 16:07, Don wrote:
[root@rocky temprpm]# rpm -Uvh *.rpm warning: package glibc = 2.3.2-101 was already added, replacing with glibc <= 2.3.2-101
Is this a bug where decision to skip needs to include the "equal" condition? Or is it a feature that allows the reinstallation of previously installed rpms?
No, and no! To reinstall previously installed rpms, you need to use --force. The reason you're seeing this is glibc comes in various flavours for i386, i686, etc. (Remember the 'be careful' part of one of my previous emails? :)
The rpm message (I think) is saying you've already listed glibc on the command line (in *rpm), but its found another one (in *rpm) that it should be doing instead. So its removed the previous one from its about-todo list.
HTH,
Don said:
On Mon, 2003-12-01 at 20:11, Iain Buchanan wrote:
The easiest way would be to use redhat-config-packages with the --tree option, and then select everything.
I tried that and get this error: [root@rocky root]# redhat-config-packages --tree
First off, you didn't read the docs, so this isn't a valid command.
Unable to import gtk module. This may be due to running without $DISPLAY set. Exception was: could not open display Traceback (most recent call last): File "/usr/share/redhat-config-packages/MainWindow.py", line 11, in ? sys.exit(0) NameError: name 'sys' is not defined
I never did get X installed on that system... I use ssh to come in from another (bigger/faster/more capable) machine.
That's why SSH has X-forwarding.
-
Don -
Iain Buchanan -
William Hooper