Difference between revisions of "Fedora 21"
Jump to navigation
Jump to search
m (→Fedora-21 anaconda 21.48-1.1 installer: boot.iso screenshots) |
|||
| Line 100: | Line 100: | ||
:07/29/2014 | :07/29/2014 | ||
| − | *Note | + | *Note The same installer is on the [[Fedora_21#Boot.iso|boot.iso]]; but with more options. |
[[File:F3-Circlepng.png|600px]] | [[File:F3-Circlepng.png|600px]] | ||
: | : | ||
Revision as of 23:39, 29 July 2014
Fedora® version page: 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 |
Fedora 21
- Rawhide is now f 22
- To convert to a F21 and remove rawhide repos:
- Boot.iso - Basically a (Rawhide) Netinstall (Built daily)
- This is Rawhide so it may (or not) work. Latest is 21.48.1-11 Anaconda 07/29/2014
- Works in Virtualbox
- Download:
- https://dl.fedoraproject.org/pub/fedora/linux/development/21/x86_64/os/images/boot.iso
- https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/images/boot.iso
- boot.iso is the same as a netinstall.iso
- For latest Builds builds (and links to them) see:
- fedora-qa Install testing:
- 06/24/2014 NetworkManager--wifi added to comps in f21(rawhide)
- SoaS shows wireless and ad-hoc in f1 Network Neighborhood on install
"If you suddenly find yourself without Wi-Fi,find a wired network connection and:
dnf install NetworkManager-wifi systemctl restart NetworkManager"
DNF vs YUM
Upgrade to rawhide from an existing installation
Release Schedule
As requested on the last FESCo meeting, F21 schedule draft follows (all dates after Change Submission deadline are still labelled as "no earlier than").
Tue 2014-04-08 Change Proposals Submission Deadline Tue 2014-07-08 Change Proposals Freeze (Testable|Complete) - no earlier than Tue 2014-07-08 Branch Fedora 21 from Rawhide - no earlier than Tue 2014-07-22 Alpha Change Deadline - no earlier than Tue 2014-08-05 Alpha Release Public Availability - no earlier than Tue 2014-08-26 Accepted Changes 100% Complete Deadline - no earlier than Tue 2014-08-26 Beta Change Deadline - no earlier than Tue 2014-09-09 Beta Release Public Availability - no earlier than Tue 2014-09-30 Final Change Deadline - no earlier than Tue 2014-10-14 Final Release Public Availability (GA) - no earlier than
Mid October gives us pretty a lot of time for real work to be done before branching (in the beginning of July). I'm going to share this draft with other teams (websites guys asked for). It's based on current schedule structure, adjusted to earlier change process but I don't expect (at least for F21) we want to diverge from what we used to do in pre-next releases. Unless needed of course. One question to discuss is spins process and dates for it - I skipped it for now intentionally. Exact GNOME schedule for 3.14 is not yet available (to put this release into the context of F21 release).
Systemd
- Fedora wiki page
Updating Grub 2 on UEFI systems
Turn off gnome automatic background updates
- NOTE seems to be no longer available:
- To turn off background downloading of updates and forced 10 minute updates on boot of gnome3.10.1
- Root terminal
yum install dconf-editor
- User Terminal
dconf-editor gnome/settings-daemon/plugins/updates
- Uncheck [ ] auto updates
- NOTE this plugin no longer exists in f21(rawhide) 03/14/2014
- see gnome Bug:
- This is modified: 12/28/2013
"This moves more functionality from the gsd updates plugin here: * Notify about successful or unsuccessful offline updates 15 seconds after start. * Monitor for available offline updates and notify about them, once per hour. * Refresh the cache once per day, after 6am. * If important updates are available, or updates have not been installed for at least 7 days, download all available updates. We rely on PackageKit to prepare an offline update when updates have been downloaded. * Avoid mobile networks for cache refresh and downloads."
Logic Map for Updates in gnome
know how to force a reinstall of a kernel
- yum reinstall kernel isn't doing anything
- you need to re-run the scriptlets
- this is not done with "yum reinstall"
- "rpm -q --scripts kernel-version-release" would tell you what to rerun
fedora boot optimization
- Can be dangerous - ADVANCED USERS ONLY
Rawhide Watch
- boot failures with recent rawhide kernels
dogtail
- Being consdered by gnome in IRC GIPMnet #qa for automated testing
Fedora-21 anaconda 21.48-1.1 installer
- This is the installer from Fedora-Live-SoaS-x86_64-21-20140728.iso SoaS LiveCD in Oracle VM VirtualBox
- This is a Preliminary version and will be modified before f21 is released.
- 07/29/2014
- Note The same installer is on the boot.iso; but with more options.
- Install done from Soas terminal with
su liveinst
- Time Zone selected
- [Done} to return to main Hub
Custom Install Screens
- Note only used if you select:
[x]I will configure partitioning
- select type of partition to create in Drop Down menu
- Reclaim space if HD is already formatted
Finish Install
- Configuration
- Root Password and User Creation
- Select Password and User Creation to enter their spokes and return with [Done]
- A weak Password will require entering [done] 2 times to return to main Configuration Spoke
- See yellow warning in bottom of page
- Installing Software
- % completion until [Done]-Reboot appears
Boot.iso
- Larger selections in boot.iso
- Optional packages in server
Sugar-test Cases
- Used in #fedora-qa testing
SoaS v10 testing with activities not included in the standard distribution
Bug Reports
- Blockers Bugs info
New proposed Features
AppInstaller in F21
https://fedoraproject.org/wiki/Changes/AppInstallerContinued
"gnome-software will support installing system add-ons such as fonts and codecs. It will show additional metadata for applications: screenshots, ratings, other details. We will also work with the Fedora infrastructure team to obtain the metadata online for all applications instead of shipping it statically for a limited set."
Fedora.next
https://fedoraproject.org/wiki/Fedora.next
"This all came out of a number of proposals at Flock 2013, including Architecture for a More Agile Fedora and Stephen Gallagher's suggestion that we use that architecture to design, build, and market three distinct Fedora products. This grew into a proposal accepted by the Fedora advisory board, and the formation of Initial Working Groups by FESCo. "