[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Let's talk about some F9 (and beyond) features for anaconda

Hash: SHA1

Jeremy Katz wrote:
> I'd like to try and get everyone working on anaconda who wants to see
> new features, etc over the next six months (the Fedora 9 timeframe) and
> beyond together next week on IRC for an hour or so to kind of plan
> things out, figure out who's doing what and timing, etc.

Missed that one but here's some ideas if you are still taking 'em.

I created an RFE https://bugzilla.redhat.com/show_bug.cgi?id=381641

iSCSI support was added to anaconda sometime ago.  That's an expensive
option unavailable to some/most Linux users.  I saw the patches post for
the iSCSI support.  I thought that the code could be adapted for ATA
over Ethernet, AOE http://www.coraid.com/tech1.html.  AOE has been in
the kernel for sometime now.  The benefit to Fedora or ES users is
similar to Xen support.  AOE allows a big file server to be a virtual
hard drive dispenser for client PCs.  PCs are great, but if drivers are
made available for the OpenMoko and Maemo platforms, then Fedora could
host embedded devices need for an occasional larger storage area via AOE
disk files as hard drives too. The nslu2 has an example idea
http://www.nslu2-linux.org/wiki/Optware/Vblade . Perhaps a PC in the
stereo rack would be quieter too.  There's a lj article here

Things that may have to be considered
1.) https://bugzilla.redhat.com/show_bug.cgi?id=381541 selinux
configuration may have to be adapted.
2.) aoetools and perhaps the vblade tools will have to be available for
anaconda to broadcast for available AOE drives. You do not have to have
the Coraid hardware with the vblade tools
3.) I believe the "Advanced storage configuration" button is where the
anaconda change should be made
4.) Some sort of init script would be required.
5.) The init script may have to have, say, /etc/sysconfig/aoe information.
6.) The /boot partition may need some adjustsments so that that the
kernel can load the drivers.
7.) Perhaps boot prom considerations are needed for diskless clients
using a server with files uses as disk drives via vblade tools.

RFE posted https://bugzilla.redhat.com/show_bug.cgi?id=381661

I have to use a USB keyboard during installation of F8 on PlayStation 3,
PS3, hardware.  However the PS3 console also supports bluetooth devices.
 It would be great to pair and use a keyboard and mouse during the
installation of a Fedora release, if possible.  Both stage one and stage
two would be modified. I wonder if this would be a similar idea like
using a serial console during installation.   The bluetooth keyboard and
mouse would be used during installation and also be the final system
keyboard and mouse after installation.

Thanks for considering input into F9.


Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]