1. Option for selecting individual packages during install seems to be missing (bugzilla 105646).
2. After installation, when I booted up everything looked OK untill I got to firstboot when the cursor did not react normally (bounced around the screen). Once I got to gdm and gnome/metacity, the cursor responded normally (bugzilla 105648).
3. Thank you for including the vmware driver in XFree86. Did going to Fedora make this "easier"?
On Friday 26 September 2003 10:51, Chris Ricker wrote:
On Fri, 26 Sep 2003, Gene C. wrote:
- Option for selecting individual packages during install seems to be
missing (bugzilla 105646).
Deliberately removed. See Bug #91716 (which you filed ;-)
Mmmm ... my memory is very short term only it seems
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 26 Sep 2003 11:02:01 -0400, Gene C. wrote:
On Friday 26 September 2003 10:51, Chris Ricker wrote:
On Fri, 26 Sep 2003, Gene C. wrote:
- Option for selecting individual packages during install seems to be
missing (bugzilla 105646).
Deliberately removed. See Bug #91716 (which you filed ;-)
Mmmm ... my memory is very short term only it seems
Clicking the "my bugs" link at the bottom of the bugzilla screen might help. You just need to be logged in.
- -- Michael, who doesn't reply to top posts and complete quotes anymore.
Hello Chris,
Deliberately removed. See Bug #91716 (which you filed ;-)
Is this the correct bug number? I am not authorized to access this bug...
Bye, Leonard.
-- How clean is a war when you shoot around nukelar waste? Stop the use of depleted uranium ammo! End all weapons of mass destruction.
On Fri, 26 Sep 2003, Leonard den Ottolander wrote:
Hello Chris,
Deliberately removed. See Bug #91716 (which you filed ;-)
Is this the correct bug number? I am not authorized to access this bug...
It's correct. Unfortunately, that bug is only accessible by RH and RH's beta team (see http://beta.redhat.com), which I hadn't noticed or I wouldn't have mentioned it here. Sorry about the confusion.
later, chris
On Fri, 2003-09-26 at 05:28, Gene C. wrote:
- Option for selecting individual packages during install seems to be missing
(bugzilla 105646).
Intentional. We recommend using redhat-config-packages if you have additional software to install not covered by the component groups screen. We're going to a model where everything interesting (as the designer of the comps file deems it) has to be in a component group in the comps file. I think it makes more sense for interactive use to get through the install quickly w/o alot of questions and then use a tool designed for the task (in this case, redhat-config-packages) to complete the operation.
You can still turn on individual packages in kickstart as always.
Michael Fulbright msf@redhat.com
On Friday 26 September 2003 10:51, Michael Fulbright wrote:
On Fri, 2003-09-26 at 05:28, Gene C. wrote:
- Option for selecting individual packages during install seems to be
missing (bugzilla 105646).
Intentional. We recommend using redhat-config-packages if you have additional software to install not covered by the component groups screen. We're going to a model where everything interesting (as the designer of the comps file deems it) has to be in a component group in the comps file. I think it makes more sense for interactive use to get through the install quickly w/o alot of questions and then use a tool designed for the task (in this case, redhat-config-packages) to complete the operation.
You can still turn on individual packages in kickstart as always.
OK, I like the option at install time but doing it post install should be OK too. However, this "change" should be mentioned in the RELEASE-NOTES which it does not appear to be (at least where I looked under installation).
It might also be nice if there was an option under firstboot to take invoke the package installer to do this.
On Fri, 2003-09-26 at 10:59, Gene C. wrote:
OK, I like the option at install time but doing it post install should be OK too. However, this "change" should be mentioned in the RELEASE-NOTES which it does not appear to be (at least where I looked under installation).
We will do that.
It might also be nice if there was an option under firstboot to take invoke the package installer to do this.
I think on the 'Install Additional Software' screen which we already have this could be done somewhat cleanly. I'll ask Brent about it.
Michael Fulbright msf@redhat.com
On Friday 26 September 2003 10:51, Michael Fulbright wrote:
On Fri, 2003-09-26 at 05:28, Gene C. wrote:
- Option for selecting individual packages during install seems to be
missing (bugzilla 105646).
Intentional. We recommend using redhat-config-packages if you have additional software to install not covered by the component groups screen. We're going to a model where everything interesting (as the designer of the comps file deems it) has to be in a component group in the comps file. I think it makes more sense for interactive use to get through the install quickly w/o alot of questions and then use a tool designed for the task (in this case, redhat-config-packages) to complete the operation.
This would be fine except that, after an upgrade from RHL 9, redhat-config-packges still seems to think that RHL 9 is installed instead of Fedora Core 0.94. That is, the packages and groups it lists as choices to add are still those of RHL 9, including removed packages like LPRng. (This also leads to things like package groups being listed as "not installed" due to the removal of packages like libunicode-devel.)
John Thacker
John Alexander Thacker (thacker@math.cornell.edu) said:
This would be fine except that, after an upgrade from RHL 9, redhat-config-packges still seems to think that RHL 9 is installed instead of Fedora Core 0.94. That is, the packages and groups it lists as choices to add are still those of RHL 9, including removed packages like LPRng. (This also leads to things like package groups being listed as "not installed" due to the removal of packages like libunicode-devel.)
Was this upgrade done with the installer?
What does 'rpm -q comps' say?
Bill
On Fri, Sep 26, 2003 at 06:22:07PM -0400, Bill Nottingham wrote:
John Alexander Thacker (thacker@math.cornell.edu) said:
This would be fine except that, after an upgrade from RHL 9, redhat-config-packges still seems to think that RHL 9 is installed instead of Fedora Core 0.94. That is, the packages and groups it lists as choices to add are still those of RHL 9, including removed packages like LPRng. (This also leads to things like package groups being listed as "not installed" due to the removal of packages like libunicode-devel.)
Was this upgrade done with the installer?
Yes.
What does 'rpm -q comps' say?
[jat48@thacker jat48]$ rpm -q comps comps-9-0.20030313
Aha. Hmm, the same thing happened with rpmdb-redhat, although I did upgrade that by hand. I didn't know about comps.
0.94 < 9, so the installer apparently didn't do the upgrade, since the RHL 9 package looked newer to rpm. In fact to upgrade comps right now I have to use --force.
<go away, come back after testing>
After doing that upgrade it seems to work better, with only a few references to groups referencing packages which don't exist anymore. Those errors don't seem to be critical.
John
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 26 Sep 2003 18:47:57 -0400, John Alexander Thacker wrote:
Was this upgrade done with the installer?
Yes.
What does 'rpm -q comps' say?
[jat48@thacker jat48]$ rpm -q comps comps-9-0.20030313
Aha. Hmm, the same thing happened with rpmdb-redhat, although I did upgrade that by hand. I didn't know about comps.
0.94 < 9, so the installer apparently didn't do the upgrade, since the RHL 9 package looked newer to rpm.
And a higher epoch was not set either.
In fact to upgrade comps right now I have to use --force.
Don't. Use --oldpackage instead. It's safer.
- -- Michael, who doesn't reply to top posts and complete quotes anymore.
Michael Schwendt writes:
Aha. Hmm, the same thing happened with rpmdb-redhat, although I did upgrade that by hand. I didn't know about comps.
0.94 < 9, so the installer apparently didn't do the upgrade, since the RHL 9 package looked newer to rpm.
And a higher epoch was not set either.
Filed the other day: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=105746
On Friday 26 September 2003 11:15 am, John Alexander Thacker wrote:
This would be fine except that, after an upgrade from RHL 9, redhat-config-packges still seems to think that RHL 9 is installed instead of Fedora Core 0.94. That is, the packages and groups it lists as choices to add are still those of RHL 9, including removed packages like LPRng. (This also leads to things like package groups being listed as "not installed" due to the removal of packages like libunicode-devel.)
This is due to the versioning of the comps package. RHL9's version is 9.0; Fedora Core 0.94 has a comps version of 0.94. So rpm -Uvh --oldpackage comps (it is on disc 1, IIRC) and it at least shows the right packages. However, redhat-config-packages still won't work right for me; I insert disc 1 like it wants and it doesn't recognize it as disc 1. Although redhat-config-packages appears to still be a work-in-progress: no preferences are working, sources is hardwired at ALL, etc.
- Option for selecting individual packages during install seems to be missing
(bugzilla 105646).
Intentional. We recommend using redhat-config-packages if you have additional software to install not covered by the component groups screen. We're going to a model where everything interesting (as the designer of the comps file deems it) has to be in a component group in the comps file. I think it makes more sense for interactive use to get through the install quickly w/o alot of questions and then use a tool designed for the task (in this case, redhat-config-packages) to complete the operation.
This strikes me as sensible. I've seen people installing Red Hat go through a detailed package selection, taking over half an hour to get everything "just right", then have the install fail due to a hardware issue. Since the Red Hat installer doesn't appear to be able to pick up from where it left off (say, look for a precreated kickstart file on the disk and resume the install?), it's probably best to defer detailed package selection to a post-install task.
Craig Ringer
Hello Michael,
We recommend using redhat-config-packages if you have additional software to install not covered by the component groups screen.
It would be nice if those config utils would run in a console. I think many servers do not run X in the first place.
I think it makes more sense for interactive use to get through the install quickly w/o alot of questions
Individual package selection has always been an option that was skipped by default. So speed of installation has nothing to do with deleting this functionality.
Bye, Leonard.
-- How clean is a war when you shoot around nukelar waste? Stop the use of depleted uranium ammo! End all weapons of mass destruction.
On Fri, 2003-09-26 at 13:12, Leonard den Ottolander wrote:
I think it makes more sense for interactive use to get through the install quickly w/o alot of questions
Individual package selection has always been an option that was skipped by default. So speed of installation has nothing to do with deleting this functionality.
Which just put it off the beaten path and less likely to be noticed quickly when it broke. I had to rework quite a bit of the backend package handling code in anaconda to handle the ability to install both i386 and x86_64 packages on AMD64 (and similarly on other arches), which was then going to require a rework and a pretty large rethink of how the individual package selection worked. Rather than spend time on that, we punted it out and will just get it right for redhat-config-packages (instead of having to do it in two different places).
Finite time + infinite amounts of work == some stuff gets punted
Plus, there's the whole "options don't come for free" argument which Havoc has written about a few times.
Cheers,
Jeremy
On Fri, 2003-09-26 at 08:51, Michael Fulbright wrote:
On Fri, 2003-09-26 at 05:28, Gene C. wrote:
- Option for selecting individual packages during install seems to be missing
(bugzilla 105646).
Intentional. We recommend using redhat-config-packages if you have additional software to install not covered by the component groups screen. We're going to a model where everything interesting (as the designer of the comps file deems it) has to be in a component group in the comps file. I think it makes more sense for interactive use to get through the install quickly w/o alot of questions and then use a tool designed for the task (in this case, redhat-config-packages) to complete the operation.
But I like to *deselect* packages as well during install, will that be an option?
To me this eliminates the usefulness of "optional" in the files. I tis either mandatory or not installed.
On Fri, Sep 26, 2003 at 04:39:59PM -0600, Bill Anderson wrote:
Intentional. We recommend using redhat-config-packages if you have additional software to install not covered by the component groups screen. We're going to a model where everything interesting (as the designer of the comps file deems it) has to be in a component group in the comps file. I think it makes more sense for interactive use to get through the install quickly w/o alot of questions and then use a tool designed for the task (in this case, redhat-config-packages) to complete the operation.
But I like to *deselect* packages as well during install, will that be an option?
Optimal would be for the system to have no extra packages at all when firstboot gets run, so there would be nothing to deselect :-)
Ideally people who want a minimal firewall and people who want 4 gigs of graphical gizmos have the same set of packages on the harddrive when the machine first boots, the former just doesn't install anything else. It gets a bit tricky if you want to leave out X11 etc. though, firstboot for typical users should run in X, but it should be possible to do similar things in text mode too :-)
On Sat, 2003-09-27 at 10:40, Pekka Pietikainen wrote:
Ideally people who want a minimal firewall and people who want 4 gigs of graphical gizmos have the same set of packages on the harddrive when the machine first boots, the former just doesn't install anything else. It gets a bit tricky if you want to leave out X11 etc. though, firstboot for typical users should run in X, but it should be possible to do similar things in text mode too :-)
If you put a comps file on a floppy and run anaconda with 'linux updates' we use the comps file instead of ours. Create your own install class and package groups and have fun. Make it as small as you like (though I would keep the 'Core' group as is or post-install anaconda will fail because we need some apps). Looking at the sources for anaconda you ought to be able to see how the 'Personal Desktop' and 'Server' options work and go from there.
Michael Fulbright msf@redhat.com