From Fedora Project Wiki

Revision as of 14:22, 2 October 2008 by Jlaska (talk | contribs) (Added ip=X.X.X.X bug)

DATE TIME WHERE
Thu October 2, 2008 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-qa (need irc help?)

How to join?

For information on joining a Fedora Test Day, see QA/Test_Days#Where_are_Test_Days_held.3F

What to test?

This week's instalment of Fedora Test Day will focus on:

Preparing for Test Day

Depending on the speed of your connection and the time available for testing, there are several methods available for

Live Images

  1. Please download a live ISO image for your architecture:
  2. Prepare your live image by following the instructions at FedoraLiveCD
  3. Or run the dowloaded ISO image in qemu:
     su -c 'qemu -cdrom Fedora-10-Beta-i686-Live.iso -m 512 -std-vga'

Install Media

  1. Consult the installation guide for quick start information to determine the best install method for your needs.
  2. Follow instructions for installing your system.
    • Alternatively, on an already installed system:
      1. Install snake:
        yum install snake
      2. Configure your system for installation:
        snake-install http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Fedora/i386/os

How to test?

Please add your findings to the matrix below or discuss any issues or concerns on IRC #fedora-qa.

netboot boot.iso
The following test matrix was developed by User:Dcantrel
Boot argument dhcp static dhcp static
Network device selection parameters
ksdevice=eth0 (johannbg) works (dcantrell) works
ksdevice=MACADDR (jlaska) works (dcantrell) works
ksdevice=link
ksdevice=BOOTIF (jlaska) works
Network device configuration parameters
ip=X.X.X.X

(also includes gateway=, dns= and netmask=)

(jlaska) 465270
ip=dhcp
Other parameters that require an active network connection
ks=URL
updates=URL
repo=URL

Where to file bugs

Please record any issues/defects discovered in Red Hat's Bugzilla.

Need help?

We'll have a host of QA and Development characters hanging out discussing bugs (aka "features"), expectations, and test areas. I've included details below for how you can contribute below.

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Want to join in?
If you'd like to sign up to help field questions, please add your name to the list above.