Athlon64 Access
by Si Jones
Hi Everyone,
Noticed that some of you require athlon64 access, if you require one that
is standard FC3 build then please email me with your details and I will
set you up a ssh account.
This should be enough for you to sort some of the cross-platform problems?
19 years, 2 months
dmraud in initrd in fc4
by Niki Waibel
have not found any mails in this list about dmraid...
is it planned to put it into the fc4 initrd, to be
able to boot from ie serial ata raid drives
(a simple >>dmraid -ay<< at the right position
of the boot script should be sufficient. maybe
some sata_XXX and dmraidXXX modules have to
be loaded before ...)?
maybe it is already there -- have not yet found time
to test fc4-testX ...
rds, niki
--
niki w. waibel - system administrator @ newlogic technologies ag
19 years, 2 months
radical suggestion for fc4 release
by seth vidal
Hi folks,
this is a touch silly but possibly useful and it would definitely cut
down on the old crap blocking up cdroms.
how about if we kill all rpm spec file changelog entries OLDER than 2
years.
they'll still live on in older srpms and rpms but it'd be a useful
reduction and it would make the specfiles that much smaller, along with
the rpm headers.
thoughts?
-sv
19 years, 2 months
SSL certificate management/storage
by Joe Orton
There was a brief thread on this at the end of last year; obviously
"certificate management" is a problem of vast scope but it would be good
to sort out at least some simple filesystem conventions for FC4. Some
simple problems I'd like to solve:
1. certificate storage is split between /etc/httpd/conf/ssl.*
for mod_ssl-specific stuff, and and /usr/share/ssl for system-wide
2. ... and /usr/share/ssl is Very Wrong for "config data" like certs
3. increasing number of daemon packages are creating self-signed
certs in %post scripts; could/should this be unified?
Any comments?
joe
19 years, 2 months
New Install Idea
by Robert Spangler
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I had posted this idea on the Fedora list and the feed back showed some
interest. It seems to take a long time to install Fedora and I believe a
better way of doing it would be to have a bare bone install CD. It was
suggested that I post the same idea here for you fine folks.
Presently you down load minimum of 3 CD's or the DVD and install. After the
install you run yum which again downloads all the latest software that you
have installed.
The idea would be to have a bare bone install CD. What this CD should contain
is just enough software to get the system to the point where it could connect
to a Repository. system and then download the latest up to date versions of
the software you want to install. I was thinking somewhere along the lines
of how the new Debian install works. You could keep the same install look
that is now present in Fedora just when it comes time to install the system
software it downloads what is needed from the Internet.
With this type of install I can a great improvement. You will only be
downloading the software you want which will not require you to download
large amounts of software you don't need. Also you will always have the most
up to date software installed on your system.
I am not suggesting to stop making the ISO images just give the installer a
choice of downloading the complete CD set or one small CD which will connect
them to a Repository. site to download the latest version of everything they
want to install.
Just a thought. Thnx for your time.
- --
Regards
Robert
Smile... it increases your face value!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFCBQbb0xJrO8dQYHgRAv9/AKCxUey+tgqFLUsq5h5sVftOo3BRHQCgtVr+
JDzfWzWRr30XyHxssOAbEwU=
=24K+
-----END PGP SIGNATURE-----
19 years, 2 months
rawhide report: 20050206 changes
by Build System
New package python-sqlite3
Python bindings for sqlite3
New package sqlite3
Library that implements an embeddable SQL database engine
Updated Packages:
coreutils-5.2.1-40
------------------
* Sat Feb 05 2005 Tim Waugh <twaugh(a)redhat.com> 5.2.1-40
- Undo last change (bug #145266).
elfutils-0.99-2
---------------
* Sat Feb 05 2005 Jeff Johnson <jbj(a)redhat.com> 0.99-2
- upgrade to 0.99.
* Sun Sep 26 2004 Jeff Johnson <jbj(a)redhat.com> 0.97-3
- upgrade to 0.97.
* Tue Aug 17 2004 Jakub Jelinek <jakub(a)redhat.com> 0.95-5
- upgrade to 0.96.
kernel-2.6.10-1.1126_FC4
------------------------
* Sat Feb 05 2005 Dave Jones <davej(a)redhat.com>
- 2.6.11-rc3-bk2
openoffice.org-1.1.3-5.7.0
--------------------------
* Sat Feb 05 2005 Dan Williams <dcbw(a)redhat.com> - 1.1.3-5
- Disable Evo2 connector on FC4 builds until we can get it ported to Evo 2.2
* Tue Feb 01 2005 Dan Williams <dcbw(a)redhat.com> - 1.1.3-4
- #rh146328# Fix printer discovery
* Tue Feb 01 2005 Dan Williams <dcbw(a)redhat.com> - 1.1.3-3
- #rh146580# Dump upstream Novell patch that shifts rows on paste in Calc
rpmdb-fedora-1:4-0.20050206
---------------------------
19 years, 2 months
repoclosure.py
by seth vidal
Hey,
I just wrote a script using the yum modules to check to see if a set of
repositories have dependency closure for all packages in the
repositories.
it's very simple and obvious but it has some nice results:
I ran:
cutter:~$ python ./repoclosure.py development
Not running a root, might not be able to import all of cache
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 1
development
Num Packages in Repos: 2663
package: openoffice.org - 1.1.3-2.7.i386 from development
unresolved deps:
libedataserver.so.3
libebook.so.8
package: gnome-python2-nautilus - 2.6.0-5.i386 from development
unresolved deps:
libnautilus.so.2
package: struts11-webapps-tomcat5 - 1.1-1jpp_2fc.noarch from development
unresolved deps:
tomcat5
package: nautilus-media - 0.8.1-4.i386 from development
unresolved deps:
libnautilus.so.2
package: evolution-connector - 2.0.3-1.i386 from development
unresolved deps:
libcamel.so.0
libedata-book.so.1
libedata-cal.so.5
libedataserver.so.3
libgal-a11y-2.2.so.1
libgal-2.2.so.1
libebook.so.8
libecal.so.6
so that's kinda cool b/c now we know what packages simply aren't going
to resolve out in development right now if you tried to install or
update to them.
http://linux.duke.edu/yum/download/misc/repoclosure.py
I think it works okay, it seems to at least :)
You run it like:
repoclosure.py repoid repoid repoid
or if you want it to check your default repositories that you have
enabled in your yum configuration then just run:
repoclosure.py
You need to have yum 2.1.13 installed to really test it.
The only other thing you might want to do is either:
1. run repoclosure.py as root
2. run yum makecache as root with the repositories you want to use
enabled.
thanks,
-sv
19 years, 2 months