Is there a standard process for getting things added to Fedora's kernel
package. In particular, I'm interested in the hdaps modules (IBM's Hard
Drive Active Protection System). I believe it has been in the stable
kernel since 2.6.14.
Or, am I just thinking about this wrong. Do uncommon modules not go in
the kernel package? Do they usually get packaged separately?
GnuPG Fingerprint: 3597 1B8D C7A5 C5AF 2E19 EFF5 2FC3 BE99 D123 6674
Just a quick blurb.
Fedora 7 Test 1 has been released today. For this particular release, we only
did a Desktop spin of the package collection. We are still fine tuning
targetted spins of the collection as part of the merger of Core and Extras.
We also produced a LiveCD that has the ability to install to your harddrive,
should you wish.
http://fedoraproject.org/wiki/Releases/7 has the gory details of our work on
the 7th release of Fedora.
DVD, CD and network installation are available.
Please read the Important Warnings below in this announcement for more
The recommended method of download is via BitTorrent from this site.
HTTP, FTP, and RSYNC downloads are available from Fedora Project mirrors
listed above. Note that not all mirrors may be synced at this time.
Release Engineer: Fedora
I understand I'll get flamed for suggesting this but..
A "whatprovides python\(abi\)" tells me :
python.x86_64 2.4.4-1.fc6 updates
Which is what I expect and is all cool.
But here is an idea. Often to make the transition easier on people we
(fedora) provides compatibility libraries. This is great.
Just wondering though, with the dropping of Legacy ( which I will in no
way debate because that's been done to death and explained enough
already ), I was thinking by just throwing a few more compat-libs into
the mix it might help out those who otherwise find an upgrade daunting..
There looks to be these compat-libs shipping now :
Would it be at all feasible to add some more into extras? Perhaps :
I am not suggesting to keep them maintained with security or other
patches. But to simply offer them once as an unsupported method of
allowing FC upgrades while maintaining some legacy apps to those who
would like it.
Yep I know people who want to run an 'old' software stack should use
another distro but if that is the case why have any compat-libs at all?
I'm not sure what list this is really appropriate for, so apologies if
this is the wrong forum. I noticed that the Fedora EULA still include
notes about export restrictions, specifically:
"... understands that certain of the software are subject to export controls
under the U.S. Commerce Departments Export Administration Regulations
Cuba, Iran, North Korea, etc. are all restricted areas. Out of
curiosity how is that being enforced on the Fedora infrastructure end,
and how is that restriction handling passed to mirrors? Is each
mirror required to implement their own set of restrictions? Does a
Fedora mirror server in Canada (or some other non-restricted country)
sidestep that issue? If so, doesn't that basically make the EULA
clause moot (from a once the dam is broken kinda perspective)?