Inaccuracy in Installation Guide
by Adam Williamson
Someone on the forums kindly pointed out an inaccuracy in the
Installation Guide:
https://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Quick_St...
"All data will be erased during installation from the disks you select
at this stage. Do not select disks that contain data you want to
preserve."
This is not correct. It would be correct to say that no data can
*possibly* be deleted from any disks you *don't* select at this stage,
but it is not true that all data will be removed from disks you *do*
select. Suggesting that this is the case prevents people from following
lots of common install paths.
What actually happens to the data on the selected disks depends on the
user's choices at Installation Options and 'custom partitioning' or
Reclaim Space. If you go to custom partitioning, basically, you're in
complete control of what happens; you can do all sorts of stuff from
there, but no data/partitions will be lost unless you explicitly choose
for that to happen.
If the disk has sufficient unpartitioned space and you just pick the
easiest 'install into empty space' path, no existing data will be
disturbed, though any existing bootloader in the MBR will be overwritten
(this is normal and has always been the case).
If you go through Reclaim Space, you get the choice of what existing
partitions to delete or resize.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
10 years, 8 months
F20 Self Contained Change: GLIBC 2.18
by Jaroslav Reznik
= Proposed Self Contained Change: GLIBC 2.18 =
https://fedoraproject.org/wiki/Changes/GLIBC218
Change owner(s): Carlos O'Donell <carlos(a)redhat.com>
Switch GLIBC in Fedora 20 to GLIBC version 2.18.
== Detailed description ==
GLIBC 2.18 will be released at the end of July 2013; we have started closely
tracking the GLIBC 2.18 development code in Fedora Rawhide and are addressing
any issues as they arise. There should be little difference from the users
perspective between GLIBC 2.17 used in F19 and GLIBC 2.18 used in F20.
== Scope ==
Proposal owners: Update glibc to 2.18 from tested upstream release.
Other developers: N/A (not a System Wide Change)
Release engineering: N/A (not a System Wide Change)
Policies and guidelines: N/A (not a System Wide Change)
The library is backwards compatible with the version of glibc that was shipped
in Fedora 19. All packages do not need to be rebuilt.
10 years, 8 months
F20 Self Contained Change: Shared Certificate Tools
by Jaroslav Reznik
= Proposed Self Contained Change: Shared Certificate Tools =
https://fedoraproject.org/wiki/Changes/SharedCertificateTools
Change owner(s): Stef Walter <stefw(a)redhat.com>
Fedora now has infrastructure for sharing system trusted certificates between
the various crypto libraries.
Tools are being worked on for adding/removing these shared trusted
certificates, as well as blacklisted certificates. This is being worked on
upstream in the p11-kit project.
This change integrates that upstream work into Fedora.
== Detailed description ==
A tool will be added to the p11-kit-trust package which can be used to perform
the following actions:
* Add a trust anchor
* Disable a trust anchor
* Remove an added trust anchor
* Blacklist a certificate or key
* Remove an blacklisted certificate or key
Because not all crypto implementations read their trusted information directly
from the dynamic database, the tool will take care of extracting things as
appropriate after making a change. This will enable administrators to run a
single command to add an anchor (and perform other tasks).
== Scope ==
p11-kit has had work done to have the trust module store changes. The initial
tool has been written upstream. Remainder of the tool needs completion.
The ca-certificates package will need some minor tweaks to make sure the new
tools integrate correctly with it.
Although this feature can potentially affect a large number of packages, the
implementation is well bounded. It is limited to a p11-kit (with one or two
lines changed in ca-certificates).
Proposal owners: stefw, see above
Other developers: kaie (for ca-certificates)
Release engineering: N/A (not a System Wide Change)
Policies and guidelines: N/A (not a System Wide Change)
10 years, 8 months
F20 Self Contained Change: Application Installer
by Jaroslav Reznik
= Proposed Self Contained Change: Application Installer =
https://fedoraproject.org/wiki/Changes/AppInstaller
Change owner(s): Richard Hughes <rhughes(a)redhat.com>, together with the
desktop team
We will replace the existing gnome-packagekit frontends (gpk-update-viewer and
gpk-application) by a new application.
== Detailed description ==
The current PackageKit frontends are focused on (surprise!) packages.
The new tool, tentatively named gnome-software, is designed from the beginning
for installing applications. It will present applications with information
that is relevant to users (screenshots, reviews, descriptions, ratings,...)
instead of information that is relevant for packagers (dependencies, package
size, file lists,...).
It will be possible to search and browse for available applications.
gnome-software will also be used to present information about available and
installed updates. Notifications about available updates will launch gnome-
software if the user chooses to see details. gnome-software will be fully
integrated with 'offline updates' - if an update includes system packages, it
will be done as an offline update, regardless whether it gets initiated from the
gnome-shell menu, a notification, or the gnome-software UI.
To improve some problematic aspects of the updates user experience (long
waits, locks), we will use the new hawkey backend for PackageKit.
== Scope ==
Proposal owners:
* Implement minimal required functionality for application installation in
gnome-software
* Implement minimal required functionality for updates in gnome-software
* Replace gpkg-update-viewer
* Package gnome-software
* Include a hawkey backend in PackageKit and use it
Other developers:
* Use gnome-software instead of gpk-update-viewer when dealing with updates in
gnome-settings-daemon, gnome-shell and gnome-control-center
Release engineering:
* Make metadata available for packaged applications in Fedora (screenshots,
icons, ratings,...). Not all of this needs to be in place for F20
Policies and guidelines:
* No immediate changes needed; longer-term, we probably want to make changes
to way applications are distributed and installed
* The update experience will also benefit from proposed changes to batch
updates
10 years, 8 months
F20 Self Contained Change: Hadoop
by Jaroslav Reznik
= Proposed Self Contained Change: Hadoop =
https://fedoraproject.org/wiki/Changes/Hadoop
Change owner(s): Matthew Farrellee <matt(a)fedoraproject.org>
Provide native Apache Hadoop packages.
== Detailed description ==
Apache Hadoop is a widely used, increasingly complete big data platform, with
a strong open source community and growing ecosystem. The goal is to package
and integrate the core of the Hadoop ecosystem for Fedora, allowing for
immediate use and creating a base for the rest of the ecosystem.
== Scope ==
Proposal owners:
* Note: target is Apache Hadoop 2.0.5-alpha
* Package all dependencies needed for Apache Hadoop 2.x
* Package the Apache Hadoop 2.x software
Other developers: N/A (not a System Wide Change)
Release engineering: N/A (not a System Wide Change)
Policies and guidelines: N/A (not a System Wide Change)
10 years, 8 months
Re: introduction - Pete
by Ryan Gough
Hi Pete,
I am currently working on the sys admin guide so if you want to get onto
the cloud guide, go for it. Pete Travis got me onto the sys admin guide
this morning, so the cloud guide is still up for grabs :)
Ryan
10 years, 8 months
F20 System Wide Change: ARM as primary Architecture
by Jaroslav Reznik
= Proposed System Wide Change: ARM as primary Architecture =
https://fedoraproject.org/wiki/Changes/ARM_as_Primary
Change owner(s): Dennis Gilmore <dennis(a)ausil.us>, Peter Robinson
<pbrobinson(a)gmail.com>
Make ARM a primary architecture. Add armv7hl to the i686 and x86_64 as arches
that we build and support. This will mean that all packages supported by the
ARM architecture must build for ARM to be released. With the release of Fedora
19 we have deprecated support for software floating support (ARMv5tel sfp) so
the only proposed addition to primary architectures is currently ARMv7
hardware floating point 32 bit support (ARMv7 hfp 32bit).
== Detailed description ==
The Changing IT landscape has started to focus on greener technologies as well
as cheaper mass produced devices that allow for fully functional cheap devices
for lower socio-economic areas and other markets like education and "makers".
ARM SoCs have traditionally been the domain of embedded and mobile
applications but are now finding their way into more traditional computing
devices like desktop, notebook and server markets. Fedora ARM currently works
on many different devices with wider support coming with each new mainline
kernel release.
For this change we will enable armv7hl builds on primary koji, and compose arm
trees as with the other primary architectures. Fedora has in the Phoenix data
centre 96 quad core Calxeda EnergyCore server nodes. Some of these nodes will
remain allocated to the arm secondary architecture koji instance for building
updates for the current Fedora 18 and 19 releases. When Fedora 18 goes end of
life the ARMv5 softfp nodes will able to be be reallocated to other tasks.
Infrastructure has expressed an interest in testing and experimenting with
some of its workloads on ARM, some are allocated to QA and some for releng.
There is currently 24 nodes configured in primary koji ready to go as builders,
there is the capacity to add up to 24 more when ARM becomes primary if
desired.
The kernel is now a multi platform unified ARMv7 kernel supporting a number of
SoCs with support expanding with each new upstream release. We build a base
and LPAE variant similar to i686. There is an ARM specific (ARMv7 and aarch64)
kernel maintainer working in collaboration with the Fedora kernel team. The
releases are composed using the exact same tooling as used for the primary
architectures. Disk images for development boards are generated by appliance-
creator and the kickstarts live in spin-kickstarts, they take a similar format
as the livecds on primary but are shipped as an OEM disk image, and like
primary initial-setup is used to do final user configuration. Like primary pungi
is used to generate an install tree, PXE install trees are created but current
bootloaders don't support isofs so ISO images aren't currently created.
== Scope ==
Add armv7hl to list of arches for f20-build and future build tags in koji
compose armhfp trees with i386 and x86_64. Requisite build hardware already
exists in phx2 and is configured to work with mainline koji.
Proposal owners: change the arches in koji, import the matching ARMv7 rawhide
builds into koji. Update Release Engineering scripts to automatically build
armhfp trees along with i686 and x86_64.
Other developers: submit builds as normal, in the event of unexpected build
failures liaise with the ARM Team to help debug and fix issues.
Release engineering: Will need to add armhfp to the release processes and make
arm install trees and disk images with each milestone compose. Release
Engineering are part of the team of people proposing the Change.
Policies and guidelines: armv7hl builds will be required to complete for
builds to be successful in koji
10 years, 8 months
Introduction - Pete
by petmor@iinet.net.au
Hi
My name is Peter and I'm from Brisbane (other side of the country to
Ryan). I also work in IT and have been using Linux since about 2005
and Fedora for about 5 years (Nas/Lamp/Laptops). My main role is a
BA so I have documentation experience. The Cloud project sounds
interesting so if Ryan doesn't get back I'd be interested in helping
out. I'm not sure how to start though as I have no experience with
Fedora in the Cloud or the items that need documentation. I'd love
to learn it though and what better way to learn it than documenting
it.
ta
Peter
----- Original Message -----
From: docs(a)lists.fedoraproject.org
To:
Cc:
Sent:Sat, 06 Jul 2013 12:00:04 +0000
Subject:docs Digest, Vol 113, Issue 5
Send docs mailing list submissions to
docs(a)lists.fedoraproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://admin.fedoraproject.org/mailman/listinfo/docs
or, via email, send a message with subject or body 'help' to
docs-request(a)lists.fedoraproject.org
You can reach the person managing the list at
docs-owner(a)lists.fedoraproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of docs digest..."
Today's Topics:
1. Re: introduction - Ryan (Matthew Miller)
2. introduction - Ryan (Ryan Gough) (Ryan)
3. readme-burning-isos (Pete Travis)
----------------------------------------------------------------------
Message: 1
Date: Fri, 5 Jul 2013 08:05:06 -0400
From: Matthew Miller
To: For participants of the Documentation Project
Subject: Re: introduction - Ryan
Message-ID:
Content-Type: text/plain; charset=utf-8
On Fri, Jul 05, 2013 at 04:43:33PM +0800, Ryan Gough wrote:
> I'm looking at getting involved in the project as I have been a
long
> time user of Fedora (e.g. since Core 1) and would like to start
> contributing. My name is Ryan, I'm from Western Australia (GMT+8).
I
> am an IT technician and have been using linux as a hobby since 2k4
> (using RH9). I have also had the opportunity to work with RHEL in
my
> job during a project as well as having worked with a couple of
other
> distros. In my line of work I have often needed to produce
> documentation to a professional standard and I feel I can
contribute
> this way currently. I believe I should be able to contribute 4
hours a
> week at this point in time.
Hi Ryan! That sounds awesome. One area we could really use
improvement on is
the Cloud Guide -- this got off to a great start but kind of stalled
about
https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/...
Interested?
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁
------------------------------
Message: 2
Date: Sat, 06 Jul 2013 01:18:54 +0800
From: Ryan
To: docs(a)lists.fedoraproject.org
Subject: introduction - Ryan (Ryan Gough)
Message-ID:
Content-Type: text/plain; charset="utf-8"
Message is now signed with my pgp signature
On Fri, 2013-07-05 at 12:00 +0000,
docs-request(a)lists.fedoraproject.org
wrote:
> Today's Topics:
>
> 1. introduction - Ryan (Ryan Gough)
>
>
>
----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 5 Jul 2013 16:43:33 +0800
> From: Ryan Gough
> To: docs(a)lists.fedoraproject.org
> Subject: introduction - Ryan
> Message-ID:
>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Everyone,
>
> I'm looking at getting involved in the project as I have been a
long
> time user of Fedora (e.g. since Core 1) and would like to start
> contributing. My name is Ryan, I'm from Western Australia (GMT+8).
I
> am an IT technician and have been using linux as a hobby since 2k4
> (using RH9). I have also had the opportunity to work with RHEL in
my
> job during a project as well as having worked with a couple of
other
> distros. In my line of work I have often needed to produce
> documentation to a professional standard and I feel I can
contribute
> this way currently. I believe I should be able to contribute 4
hours a
> week at this point in time.
>
> Regards,
> Ryan
> irc: _terminal_
> FAS: t3rm1n4l
>
>
> ------------------------------
>
> --
> docs mailing list
> docs(a)listsfedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/docs
>
> End of docs Digest, Vol 113, Issue 4
> ************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL:
------------------------------
Message: 3
Date: Sat, 06 Jul 2013 00:26:54 -0600
From: Pete Travis
To: For participants of the Documentation Project
Subject: readme-burning-isos
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
I've updated the content of readme-burning-isos to better reflect the
current release, and the new 1GB image size targets in particular. At
this point, we should be providing instructions for creating USB
media
in the same document, perhaps by borrowing liberally from the
Installation Guide. I plan to work on the idea over the next few
days,
please share your thoughts.
In the meantime, the optical-only readme-burning-isos has been
published. Will one of the maintainers for this Transifex resource[1]
please push source POTs? I have pot/ and the tx config committed in
git[2] for your convenience.
[1]
https://fedora.transifex.com/projects/p/fedora-readme-burning-isos/
[2] ssh://git.fedorahosted.org/git/docs/readme-burning-isos.git
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL:
------------------------------
--
docs mailing list
docs(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/docs
End of docs Digest, Vol 113, Issue 5
************************************
10 years, 8 months
Introducing myself
by Yoana Ruseva
Hello everyone,
My name is Yoana and I am from Varna, Bulgaria. I would like to join the
Fedora Documentation Project, at the moment I am working on the Fedora
Power Management Guide, with the help of jhradilek. I am looking
forward to contributing to the community and working with you :)
Cheers,
--
Yoana Ruseva
Technical Writer
Engineering Content Services
Red Hat Czech, s. r. o.
Purkynova 99
612 45 Brno Czech Republic
10 years, 8 months
Fedora Docs Meeting Minutes - 8Jul2013
by Pete Travis
====================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
https://fedoraproject.org/wiki/Docs_Project_meetings
====================================================================================================
Meeting started by randomuser at 14:01:18 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-07-08/fedora_docs.20...
.
Meeting summary
---------------
* Roll Call (randomuser, 14:01:18)
* follow up on action items (randomuser, 14:05:33)
* ACTION: randomuser to clear master branch of RNs and wiki beats
(randomuser, 14:07:11)
* Release Notes - Changes coming (randomuser, 14:07:19)
* LINK: http://fedoraproject.org/wiki/Changes (randomuser, 14:14:10)
* Guide Status (randomuser, 14:18:35)
* please help jhradilek identify where the system administrator's
guide needs work (randomuser, 14:23:36)
* whoever publishes next, if you see an error about some other guide
when running install_book, please report it to the list
(randomuser, 14:34:15)
* LINK:
https://fedoraproject.org/wiki/Docs_Project_admin_tasks_for_new_contributors
(randomuser, 14:36:39)
* Guide Owners, if you have tasks that are easy to pick up, please
help out new contributors by adding them to the list (randomuser,
14:37:11)
* Outstanding BZ Tickets (randomuser, 14:43:31)
* LINK: http://tinyurl.com/lbrq84 (randomuser, 14:43:39)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=755563
(randomuser, 14:44:31)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=707687
(randomuser, 14:46:35)
* Open Floor (randomuser, 14:53:27)
* LINK: https://fedorahosted.org/fedora-infrastructure/ticket/3860 <-
if folks could answer those questions or add to cc folks who can, we
can try and move that forward. ;) (nirik, 14:55:27)
* LINK: https://fedorahosted.org/fedora-infrastructure/ticket/3860
(randomuser, 14:57:45)
Meeting ended at 15:00:08 UTC.
Action Items
------------
* randomuser to clear master branch of RNs and wiki beats
Action Items, by person
-----------------------
* randomuser
* randomuser to clear master branch of RNs and wiki beats
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* randomuser (63)
* jhradilek (21)
* pkovar (8)
* jreznik (7)
* nirik (5)
* zodbot (4)
* pbokoc (2)
* Capesteve (2)
* yruseva (1)
* sgordon (1)
* Sparks (1)
-----------------------
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
10 years, 8 months