diskless support for mkinitrd
by Mark McLoughlin
Hi,
I've just opened this:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=128175
The bug is essentially about how we can sanely merge diskless[1]
support into mkinitrd. Attached to the bug is a diskless-mkinitrd which
is a separate mkinitrd script with diskless support.
Just posting here so anybody who might be interested in the issue can
jump in.
Thanks,
Mark.
[1] - When I say "diskless", I mean that in the sense of a thin-client
booting with e.g PXE and NFS mounting its root directory.
19 years, 9 months
rawhide report: 20040720 changes
by Build System
Updated Packages:
rpmdb-fedora-3-0.20040720
-------------------------
xffm-4.0.6-1
------------
* Tue Jul 20 2004 Than Ngo <than(a)redhat.com> 4.0.6-1
- update to 4.0.6
* Thu Jun 17 2004 Than Ngo <than(a)redhat.com> 4.0.5-4
- own /usr/share/xffm, bug #124825
- use %find_lang macros, bug #124954
- add buildrequires on xfce-mcs-manager-devel, bug #125061
19 years, 9 months
-doc subpackage Group tag
by Steven Pritchard
I was just looking around at other packages to see what Group: tag
should go on a -doc subpackage. It looks like Documentation is the
right group, but I noticed that this is rather inconsistent in the
official packages.
exim-doc Documentation
gtk-doc Development/Tools
kernel-doc Documentation
nasm-doc Development/Languages
selinux-doc System Environment/Base
sendmail-doc Documentation
tclx-doc Development/Languages
tetex-doc Applications/Publishing
tix-doc Development/Languages
xorg-x11-doc Documentation
Given that the Group: tag is essentially meaningless, I wasn't sure
this justified mention in bugzilla, but it probably should be fixed.
Steve
--
Steven Pritchard - K&S Pritchard Enterprises, Inc.
Email: steve(a)kspei.com http://www.kspei.com/
Phone: (618)398-7360 Mobile: (618)567-7320
19 years, 9 months
Fedora Core 3
by Bill Nottingham
Well, it's long overdue, but here's something.
Posted at http://fedora.redhat.com/participate/schedule/
is a preliminary draft of a schedule for Fedora Core 3, reproduced
below. (Please ignore the GNOME 2.6 typo in the online version;
that will be corrected.)
Obviously, a schedule doesn't say much about what's in it.
Here at Red Hat we're working on various things for Fedora Core 3:
- GCC 3.4 - those that have looked at rawhide will have noticed this
- GNOME 2.8
- KDE 3.3
- SELinux, yet again. This includes a new 'targeted' policy that
monitors specifc daemons with less intrusion than the strict
policy in use before.
https://listman.redhat.com/archives/fedora-selinux-list/2004-May/msg00096...
- IIIMF - continued evolution of the new input framework
- Indic language support
- Various desktop-related features, including, but not limited to:
- Pango support for Mozilla
- Remote desktops using VNC
http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
- Printing improvements
http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
- Evolution 2.0
And, random other stuff, of course.
I'm sure there's other stuff people would like to see. What sorts
of things?
Bill
PRELIMINARY Fedora Core 3 Schedule
This schedule is preliminary; it may be modified at any time.
Test users should continue to file bug reports against each test release
even after we have frozen for the next test release; all feedback is
helpful.
+------------------------------------------------------------------------+
| Day | Month | Event |
|-----+-------+----------------------------------------------------------|
| 12 | July | test1 |
|-----+-------+----------------------------------------------------------|
| | | String change deadline (data provided) |
| 25 | Aug | New major version slush (will be exceptions, like GNOME |
| | | 2.8) |
| | | test2 devel freeze |
|-----+-------+----------------------------------------------------------|
| 6 | Sept | test2, string build freeze (builds completed) |
|-----+-------+----------------------------------------------------------|
| 16 | Sept | Translation deadline (data provided) |
| | | test3 devel freeze |
|-----+-------+----------------------------------------------------------|
| 27 | Sept | test3, translation build freeze (builds completed) |
|-----+-------+----------------------------------------------------------|
| | ... | Continual freeze, only critical bugs fixed until release |
|-----+-------+----------------------------------------------------------|
| 6 | Oct | Absolute devel freeze |
|-----+-------+----------------------------------------------------------|
| 13 | Oct | Export approval, mirror master populated by EOD |
|-----+-------+----------------------------------------------------------|
| 14 | Oct | Release to mirrors (morning) |
|-----+-------+----------------------------------------------------------|
| 18 | Oct | Release open, announced |
+------------------------------------------------------------------------+
19 years, 9 months
Yet another FC3 wishlist
by Michel Salim
Hi,
Would it be possible to include support for the Intel Pro Wireless
2100 and 2200 wireless cards? (The drivers are available at
ipw2100.sf.net and ipw2200.sf.net respectively)
Most Centrino laptops come with either of these cards, so it would be
a nice addition. There might be license problems with bundling the
binary firmware, but it is packaged separately from the drivers and
from SuSE 9.1 install reports it seems that SuSE just bundles the
drivers and tell their users to get the firmware themselves.
Thanks,
- Michel
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
19 years, 9 months
Yet another FC3 wishlist
by Michel Salim
Hi,
Would it be possible to include support for the Intel Pro Wireless
2100 and 2200 wireless cards? (The drivers are available at
ipw2100.sf.net and ipw2200.sf.net respectively)
Most Centrino laptops come with either of these cards, so it would be
a nice addition. There might be license problems with bundling the
binary firmware, but it is packaged separately from the drivers and
from SuSE 9.1 install reports it seems that SuSE just bundles the
drivers and tell their users to get the firmware themselves.
Thanks,
- Michel
19 years, 9 months
Package building and alternate kernels (Re: Why is this list so quiet)
by Michel Salim
Reading a recent post in fedora-test-list on the lack of testers for
FC3t1 reminded me of a wishlist I had had ever since I tried using
Fink <fink.sf.net> on Mac OS X.
What we are missing at the moment in Fedora is an easier way to
rebuild packages from source. Not advocating an optimize-like-hell
approach like Gentoo's, but more the approach of Fink or the *BSDs;
i.e. being able to issue a command like 'yum build foo' which will
check all the build requirements of package foo, and for those not
found, download the source packages, rebuild them, and install them
automagically behind the scenes.*
(* I believe Debian does that also, but I can't remember)
With Fedora Core releases happening every six months, people with a
lot of non-Core packages installed would appreciate being able to
quickly rebuild their packages to check for errors, IMHO. Mach might
be able to do this, but unfortunately I'm on a metered connection
right now and could not try it until next month. Which sadly rules me
out of the test periods, so apologies if I introduce suggestions that
have already been implemented or seem naive.
Another thing is to provide alternate kernel images. Not just various
recompiles of the same kernel versions as FC currently does, but older
kernels as well for compatibility reasons. It would be especially nice
if this could be integrated into Anaconda but really, people who need
older kernels could dig up the RPM from the installation media unless
the standard kernel is unbootable.
In my case, for example, the last kernel to support my external
Firewire/USB drive is
kernel-2.6.3-2.1.253.2.1 from FC2t2 (IIRC).
Just my 2 cents,
- Michel
19 years, 9 months
yum request
by David Nielsen
I've been using yum quite a lot lately but as I have a really crappy
router that tends to fail basically when ever it's doing any real work
(like installing packages of the web), it annoys me endlessly that yum
doesn't allow resuming of downloads - say if I get 10-20 megs of a file
and the router cuts out, I'm back to square one. Now I have 100MBit
internet so it's not that bad, but I would imagine a user on 56k would
be slightly less than pleased over this behavior.
So could resuming please be considered for implementation in a future
release of yum?
- David *never ever buy netgear routers.. they suck* Nielsen
19 years, 9 months