docs-commits October 2014

docs-commits@lists.fedoraproject.org

9 participants
171 discussions

[install-guide/F21-rewrite] Adding info about switching kb layouts to Intro to Anaconda
by pbokoc 10 Oct '14

10 Oct '14

commit 12541224fc06dd23ed6edfbbc8ad97f3e132bb7f Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Fri Oct 10 17:41:08 2014 +0200 Adding info about switching kb layouts to Intro to Anaconda en-US/Installing_Using_Anaconda.xml | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) --- diff --git a/en-US/Installing_Using_Anaconda.xml b/en-US/Installing_Using_Anaconda.xml index d52feda..15bd690 100644 --- a/en-US/Installing_Using_Anaconda.xml +++ b/en-US/Installing_Using_Anaconda.xml @@ -202,6 +202,9 @@ <para> Additionally, elements in each screen can be toggled using their respective shortcuts. These shortcuts are highlighted (underlined) when you hold down the <keycap>Alt</keycap> key; to toggle that element, press <keycombo><keycap>Alt</keycap><keycap><replaceable>X</replaceable></keycap></keycombo>, where <replaceable>X</replaceable> is the highlighted letter. </para> + <para> + Your current keyboard layout is displayed in the top right hand corner. Only one layout is configured by default; if you configure more than layout in the <guilabel>Keyboard Layout</guilabel> screen (<xref linkend="sect-installation-gui-keyboard-layout" />), you can switch between the these layouts by clicking the layout indicator. + </para> <xi:include href="WelcomeSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="SummaryHub.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

1 0

[install-guide/F21-rewrite] Better xref in inst.lang= (Boot Options)
by pbokoc 10 Oct '14

10 Oct '14

commit 1bccf11492ade649a7bed3737888fa4dea5daf71 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Fri Oct 10 16:09:37 2014 +0200 Better xref in inst.lang= (Boot Options) en-US/Boot_Options.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml index 704d064..2e7bc03 100644 --- a/en-US/Boot_Options.xml +++ b/en-US/Boot_Options.xml @@ -314,7 +314,7 @@ <term><option>inst.lang=</option></term> <listitem> <para> - Sets the language to be used during the installation. Language codes are the same as the ones used in the <command>lang</command> Kickstart command as described in <xref linkend="appe-kickstart-syntax-reference" />. On systems where the <package>system-config-language</package> package is installed, a list of valid values can also be find in <filename>/usr/share/system-config-language/locale-list</filename>. + Sets the language to be used during the installation. Language codes are the same as the ones used in the <command>lang</command> Kickstart command as described in <xref linkend="sect-kickstart-commands-lang" />. On systems where the <package>system-config-language</package> package is installed, a list of valid values can also be find in <filename>/usr/share/system-config-language/locale-list</filename>. </para> </listitem> </varlistentry>

1 0

[install-guide/F21-rewrite] Finishing intro to Anaconda
by pbokoc 10 Oct '14

10 Oct '14

commit ffd90d071c922a76feba13395eb3ebd8a1c6ecb2 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Fri Oct 10 15:25:08 2014 +0200 Finishing intro to Anaconda en-US/Installing_Using_Anaconda.xml | 48 +++++++++++++++++++++++++++++++++- 1 files changed, 46 insertions(+), 2 deletions(-) --- diff --git a/en-US/Installing_Using_Anaconda.xml b/en-US/Installing_Using_Anaconda.xml index 8ec59f0..d52feda 100644 --- a/en-US/Installing_Using_Anaconda.xml +++ b/en-US/Installing_Using_Anaconda.xml @@ -149,14 +149,58 @@ <section id="sect-installation-text-mode"> <title>Installing in Text Mode</title> <para> - text + Text mode installation offers an interactive, non-graphical interface for installing &PRODUCT;. This may be useful on systems with no graphical capabilities; however, you should always consider the available alternatives before starting a text-based installation. Text mode is limited in the amount of choices you can make during the installation. + </para> + <para> + There are two alternatives to text mode which can both be used even if the installation system does not have a graphical display. You can either connect to the installation system using VNC and perform an interactive graphical installation remotely (see <xref linkend="chap-vnc-installations" />), or you can create a Kickstart file to perform the installation automatically (see <xref linkend="chap-kickstart-installations" />). + </para> + <para> + <remark>TODO: screen of text mode hub</remark> + </para> + <para> + Installation in text mode follows a pattern similar to the graphical installation: There is no single fixed progression; you can configure many settings in any order you want using the main status screen. Screens which have already been configured, either automatically or by you, are marked as <literal>[x]</literal>, and screens which require your attention before the installation can begin are marked with <literal>[!]</literal>. Available commands are displayed below the list of available options. + </para> + <para> + Limits of interactive text mode installation include: + </para> + <itemizedlist> + <listitem> + <para> + The installer will always use the English language and the US English keyboard layout. You can configure your language and keyboard settings, but these settings will only apply to the installed system, not to the installation. + </para> + </listitem> + <listitem> + <para> + You can not configure any advanced storage methods (LVM, software RAID, FCoE, zFCP and iSCSI). + </para> + </listitem> + <listitem> + <para> + It is not possible to configure custom partitioning; you must use one of the automatic partitioning settings. You also cannot configure where the boot loader will be installed. + </para> + </listitem> + </itemizedlist> + <para> + To start a text mode installation, boot the installation with the <option>inst.text</option> boot option used either at the boot command line in the boot menu, or in your PXE server configuration. See <xref linkend="chap-booting-the-installation" /> for information about booting and using boot options. </para> </section> <section id="sect-installation-graphical-mode"> <title>Installing in the Graphical User Interface</title> <para> - text + The graphical installation interface is the preferred method of manually installing &PRODUCT;. It allows you full control over all available settings, including custom partitioning and advanced storage configuration, and it is also localized to many languages other than English, allowing you to perform the entire installation in a different language. The graphical mode is used by default when you boot the system from local media (a CD, DVD or a USB flash drive). + </para> + <para> + The sections below discuss each screen available in the installation process. Note that due to the installer's parallel nature, most of the screens do not have to be completed in the order in which they are described here. + </para> + <para> + Each screen in the graphical interface contains a <guilabel>Help</guilabel> button. This button opens the <application>Yelp</application> help browser displaying the section of the <citation>&PRODUCT; Installation Guide</citation> relevant to the current screen. + </para> + <para> + You can also control the graphical installer with your keyboard. Use <keycap>Tab</keycap> and <keycombo><keycap>Shift</keycap><keycap>Tab</keycap></keycombo> to cycle through active control elements (buttons, check boxes, etc.) on the current screen, <keycap>Up</keycap> and <keycap>Down</keycap> arrow keys to scroll through lists, and <keycap>Left</keycap> and <keycap>Right</keycap> to scroll through horizontal toolbars or table entries. <keycap>Space</keycap> or <keycap>Enter</keycap> can be used to select or remove a highlighted item from selection and to expand and collapse drop-down menus. + </para> + <para> + Additionally, elements in each screen can be toggled using their respective shortcuts. These shortcuts are highlighted (underlined) when you hold down the <keycap>Alt</keycap> key; to toggle that element, press <keycombo><keycap>Alt</keycap><keycap><replaceable>X</replaceable></keycap></keycombo>, where <replaceable>X</replaceable> is the highlighted letter. </para> <xi:include href="WelcomeSpoke.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

1 0

[release-notes] SHOGUN machine learning toolkit
by Pete Travis 10 Oct '14

10 Oct '14

commit d25bf73d2c9eab958942f308afd9c76a535f8483 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Thu Oct 9 23:07:48 2014 -0600 SHOGUN machine learning toolkit en-US/Development_Tools.xml | 14 +++++++++++++- 1 files changed, 13 insertions(+), 1 deletions(-) --- diff --git a/en-US/Development_Tools.xml b/en-US/Development_Tools.xml index 543bfb5..3e33e81 100644 --- a/en-US/Development_Tools.xml +++ b/en-US/Development_Tools.xml @@ -61,6 +61,18 @@ </para> </important> </section> - + <section id="devtools-shogun"> + <title>SHOGUN Machine Learning Toolbox</title> + <para> + The machine learning toolbox's focus is on large scale kernel methods and especially on <ulink url="http://en.wikipedia.org/wiki/Support_vector_machine">Support Vector Machines (SVM)</ulink>. It provides a generic SVM object interfacing to several different SVM implementations, among them the state of the art <ulink url="http://en.wikipedia.org/wiki/LIBSVM">LibSVM</ulink>. Each of the SVMs can be combined with a variety of kernels. + </para> + <para> + One of its key features is the "combined kernel" which can be constructed by a weighted linear combination of a number of sub-kernels, each of which not necessarily working on the same domain. An optimal sub-kernel weighting can be learned using Multiple Kernel Learning. Currently SVM 2-class classification and regression problems can be dealt with. However SHOGUN also implements a number of linear methods like Linear Discriminant Analysis (LDA), Linear Programming Machine (LPM), (Kernel) Perceptrons and features algorithms to train hidden Markov-models. + </para> + <para> + Learn more about <package>SHOGUN</package> at <ulink url="http://shogun-toolbox.org/doc/en/current/" /> + </para> + </section> + </section>

1 0

[release-notes] s/rpstream/upstream/
by Pete Travis 10 Oct '14

10 Oct '14

commit f71c7dff02ef7a3936a2c4fd130802c1084b3406 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Thu Oct 9 22:46:44 2014 -0600 s/rpstream/upstream/ en-US/File_Systems.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/File_Systems.xml b/en-US/File_Systems.xml index bfcaef4..6d60821 100644 --- a/en-US/File_Systems.xml +++ b/en-US/File_Systems.xml @@ -9,7 +9,7 @@ <section id="filesystems-autofs"> <title>Autofs learns amd maps</title> <para> - The <package>autofs</package> package has gained support for amd format automount maps. In the past, amd maps have been handled by the <package>am-utils</package> package, which has seen declining rpstream development. Those that use amd format automount maps are encouraged to test the autofs functionality, and report any issues or feature requests at <ulink url="https://bugzilla.redhat.com" /> + The <package>autofs</package> package has gained support for amd format automount maps. In the past, amd maps have been handled by the <package>am-utils</package> package, which has seen declining upstream development. Those that use amd format automount maps are encouraged to test the autofs functionality, and report any issues or feature requests at <ulink url="https://bugzilla.redhat.com" /> </para> <para> For usage information, refer to <filename>/usr/share/doc/autofs/README.amd-maps</filename>.

1 0

[release-notes] autofs amd maps
by Pete Travis 10 Oct '14

10 Oct '14

commit 3a0ff39a235dbf12fd09f16a60c33dbbabc83538 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Thu Oct 9 22:44:37 2014 -0600 autofs amd maps .gitignore | 3 +-- en-US/File_Systems.xml | 10 +++++++++- 2 files changed, 10 insertions(+), 3 deletions(-) --- diff --git a/.gitignore b/.gitignore index 4ed10cb..1377554 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1 @@ -tmp/ -*~ +*.swp diff --git a/en-US/File_Systems.xml b/en-US/File_Systems.xml index 4b56b38..bfcaef4 100644 --- a/en-US/File_Systems.xml +++ b/en-US/File_Systems.xml @@ -6,7 +6,15 @@ <section> <title>File Systems</title> - <para /> + <section id="filesystems-autofs"> + <title>Autofs learns amd maps</title> + <para> + The <package>autofs</package> package has gained support for amd format automount maps. In the past, amd maps have been handled by the <package>am-utils</package> package, which has seen declining rpstream development. Those that use amd format automount maps are encouraged to test the autofs functionality, and report any issues or feature requests at <ulink url="https://bugzilla.redhat.com" /> + </para> + <para> + For usage information, refer to <filename>/usr/share/doc/autofs/README.amd-maps</filename>. + </para> + </section> </section>

1 0

[release-notes] the best thing about systemd is
by Pete Travis 10 Oct '14

10 Oct '14

commit 2e049329b06241f853066f495daf27386b3e3c24 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Thu Oct 9 21:37:53 2014 -0600 the best thing about systemd is en-US/System_Daemons.xml | 207 +++------------------------------------------ 1 files changed, 14 insertions(+), 193 deletions(-) --- diff --git a/en-US/System_Daemons.xml b/en-US/System_Daemons.xml index 59c4504..a9fff93 100644 --- a/en-US/System_Daemons.xml +++ b/en-US/System_Daemons.xml @@ -21,223 +21,44 @@ </itemizedlist> </section> <section id="systemd-private"> - <title>Isolating Services</title> + <title>systemd 215</title> <para> - Two new security-related options are now available to limit long-running services that do not require access to physical devices or the network. + <systemitem class="daemon">systemd</systemitem> in Fedora 21 has been updated to version 215. This release includes substantial enhancements, including improved resource management, service isolation and other security improvements, and network management from <systemitem class="daemon" >systemd-networkd</systemitem>. </para> <para> - The <literal>PrivateDevices</literal> setting, when set to <literal>yes</literal>, provides the service with a private, minimal <filename class="devicefile">/dev</filename> that does not include physical devices. This allows long-running services to have limited access, increasing security. + Many of these improvements enhance management of services running inside containers, and management of the containers themselves. <command>systemd-nspawn</command> creates securely isolated containers, and tools such as <command>machinectl</command> are available to manage them. <systemitem class="daemon">systemd-networkd</systemitem> provides network services for the containers, and <systemitem class="daemon" >systemd</systemitem> itself manages resource allocations. </para> <para> - The <literal>PrivateNetwork</literal> setting, when set to <literal>yes</literal>, provides the service with a network isolated to only a loopback interface. This ensures that long-running services that do not require network access are cut off from the network. - </para> - <para> - For detailed information, refer to <ulink url="https://fedoraproject.org/wiki/Changes/PrivateDevicesAndPrivateNetwork" /> - </para> - </section> - <section id="systemd-stateless"> - <title>Stateless Systems</title> - <para> - The <ulink url="https://fedoraproject.org/wiki/Features/UsrMove">usrmove</ulink> Feature in Fedora 17 began a convention of distribution provided configurations residing in <filename>/usr</filename>, with overriding administrator provided configurations in <filename>/etc</filename>. The systemd project's stateless systems effort goes a step further, to ensure that a system can boot <emphasis>without</emphasis> the configuration files in <filename>/etc</filename>. - </para> - <para> - This capabiity allows systems to be reset to a factory state, or various installation types to share a predictable base system. Read <ulink url="http://0pointer.de/blog/projects/stateless.html" /> to learn about the potential of stateless systems. - </para> - <para> - Changes to <systemitem class="daemon">systemd</systemitem> that enable stateless systems include: - </para> - <itemizedlist> - <listitem> - <para> - <emphasis>systemd-sysusers</emphasis> - </para> - <para> - The <systemitem>systemd-sysitems</systemitem> utlity creates system users in <filename>/etc/passwd</filename> and system groups in <filename>/etc/groups</filename> based on declared entries in <filename>/usr/lib/sysusers.d/</filename>. This ensures that crucial accounts are available in early boot. + To learn more about enhancements to <systemitem class="daemon" >systemd</systemitem>, read: + <itemizedlist> + <listitem> + <para> + <filename>/usr/share/doc/systemd/NEWS</filename> for the upstream changelog. </para> </listitem> <listitem> <para> - <emphasis>tmpfiles snippet for <filename>/etc/filename</filename></emphasis> - </para> - <para> - <filename>/usr/lib/tmpfiles.d/etc.conf</filename> rebuilds essential files in <filename>/etc</filename>, should they be missing. Notably, a symlink is created linking <filename>/etc/os-release</filename> to <filename>/usr/lib/os-release</filename>. + Manpages and other documentation provided with the systemd package, listed with <command>rpm -qd systemd</command>. </para> </listitem> <listitem> <para> - <emphasis>ConditionNeedsUpdate directive</emphasis> - </para> - <para> - Service units can conditionally run only when related files in <filename>/etc</filename> or <filename>/var</filename> are older than the correlating files in <filename>/usr</filename> + <ulink url="http://0pointer.net/blog/projects/stateless.html" /> for an overview of many changes and their intent. </para> </listitem> <listitem> <para> - <emphasis>systemd presets</emphasis> - </para> - <para> - The new command <command>systemctl preset-all</command> applices service preset settings to all unit files. The equivalent operation if the system is booted with an empty <filename class="directory" >/etc</filename>. Preset files for crucial services are provided with systemd in <filename class="directory" >/usr/lib/systemd/system-preset/</filename> + <ulink url="http://www.freedesktop.org/wiki/Software/systemd/" /> for a comprehensive overview of systemd. </para> </listitem> <listitem> <para> - <emphasis>/var recreation</emphasis> - </para> - <para> - A tmpfiles snippet, <filename>/usr/lib/tmpfiles.d/var.conf</filename>, recreates the basic structure of <filename class="directory">/var</filename>, if <filename class="directory" >/var</filename> is empty. + <ulink url="https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet" /> for users new to Fedora and <systemitem class="daemon" >systemd</systemitem> </para> </listitem> - </itemizedlist> - </section> - - - <listitem> - <para> - <emphasis>DefaultInstance= for templates</emphasis> - </para> - <para> - A templated unit file can unclude a <option>DefaultInstance=</option> option. If the template unit is enabled without declaring an instance, the value of <option>DefaultInstance</option> is used. - </para> - </listitem> - - - - <para> - nspawn uses devices cgroup controller, only permits access,creaton to,of API device notes ie /dev/null /dev/random, access for pty - systemd-nspawn has --tmpfs=/path switch to create a tmpfs at /path in the container - `systemd-nspawn --image` boots disk images and linux installations following the discoverable partition specification. - `systemd-nspawn --network-macvlan=` sets up a private macvlan interface; compliments Kind=macvlan setting in .netdev files - systemd-network-wait-online is new, waits for network connectiviry using systemd-networkd - /usr/lib/systemd/network/80-container-host0.network - /usr/lib/systemd/network/80-container-ve.network - systemd ships .network file for systemd-networkd that automatically configures DHCP for network interfaces created by nspawn's --network-veth= or --network-bridge= - unit files gain DeviceAllow to whitelist device access, uses names from /proc/devices - /etc/systemd/network/*.link, man systemd.link - netword veth interfaces prefixed with vb- if --network-bridge or ve- if --network-veth - new tool to save/restore rfkill state on shutdown/reboot [what? how?] - restore state of keyboard backlights in addition to screen backlights - $XDG_RUNTIME_DIR are individual tmpfs instances, allows quota settings, superior isolation. Set default size in logind.conf:RuntimeDirectorySize= defaults to 10% of available physical memory - logind automatically turns off automatic suspending on laptop lid close iff more than one display is closed. This had been left to DEs, but what about when the system starts with the lid closed? - After resuming from suspend, the system won't suspend again for 30s. The system won't suspend due to a laptop lid close until 3 minutes after resume. This gives peripherals that might be used or block suspend time to come up. - systemd-run --property= for resource control properties ie BlockIOWeight=10 - systemd-run --uid --gid --setenv also works in scope mode - - systemd-machine-id-setup has --root arg to operate on a given root directory - `machinectl poweroff` to shut down container - MAC addresses for nspawn containers with the --network-interface= are generated from machineID, so they can be consistent. - Logic for handling legacy init scripts moved out of PID1 and into a dynamically run generator that creates unit files on demand. Units that need the network automatically get a dependency for network-online.target - fsck.repair= boot option declares how the kernel deals with unclean filesystems - preen=safe repair only, yes=force yes, no=no repair - systemd-udevd runs in dissociated mount namespace. To mount directories from udev rules, make sure to pull in mount units via SYSTEMD_WANTS properties. - systemd native support for tcpwrappers removed - system.conf option gains DefaultTImerAccuracySec= that sets default AccuracySec= for .timer units. - timer units get WakeSystem= switch to resume from suspend (given [common] hardware support) - timer units gain Persistent= switch to save to disk when last triggered, causes units to trigger if their last scheduled time was missed due to poweroff. - - """ -As an experimental feature, udev now tries to lock the -disk device node (flock(LOCK_SH|LOCK_NB)) while it -executes events for the disk or any of its partitions. -Applications like partitioning programs can lock the -disk device node (flock(LOCK_EX)) and claim temporary -device ownership that way; udev will entirely skip all event -handling for this disk and its partitions. If the disk -was opened for writing, the close will trigger a partition -table rescan in udev's "watch" facility, and if needed -synthesize "change" events for the disk and all its partitions. -This is now unconditionally enabled, and if it turns out to -cause major problems, we might turn it on only for specific -devices, or might need to disable it entirely. Device Mapper -devices are excluded from this logic. -""" - /dev/log and /dev/initctl moved to /run with symlinks so PrivateSystem units can get them. - systemd-notify fixed to send messages as from the invoking script and not systemd-notify itself. - ReadOnlyDirectories= now applied recursively to submounts. systemd-nspawn --read-only does the same thing. - New unit file RestrictAddressFamilies= restricts the socket address familiew that units are given access to. ie AF_INET,AF_UNIX - units get RuntimeDirectory= RuntimeDirectoryMode= to declare /run workingdirs - units get DeviceAllow= setting to glob against device group names - systemd.conf gains options to set defaults: - DefaultCPUAccounting= - DefaultBlockIOAccounting= - DefaultMemoryAccounting= - - can turn on or off accounting for units, overridden by individual unit configs - - systemd-gpt-auto-generator can discover /srv,/,/home,swap. Supports LUKS. http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec - - systemd doesn't consider dom0s to be virtual machines. - Restart=on-abnormal triggers automatic restarts on all abnormal exit statii, restarts harder than on-failure - Socket units can be owned by SocketUser= or SocketGroup= - ProtectedHome= makes home inaccessible - ProtectedSystem= makes /usr/ read only - systemd-netowrkd runs as "systemd-network" user so it can't write to root owned files. - kbus has support for loading policy into the kernel - kbus has support for loading policy into the kernel - systemd-resolved runs as systemd-resolve user - systemd-resolved provides different /etc/resolv.conf to different interfaces - resolved symlink from /etc/resolv.conf should target /run/systemd/resolv/something - systemd-bus-proxyd runs as systemd-bus-proxy - networkd does veth for containers, and GRE, VTI,IPIP,SIT tunnels - networkd supports matching on system virtualization, arch, kernel command line, hostname, machineID - networkd doesn't dynamically load kernel modules, assumes the kernel can do it. - systemd-detect-virt works without privs - REstartForceExitStatus= return value for main service process exit; force restart of all child processes if seen - Systemctl -H (for remote machines) can connect to containers, ie `systemctl -H user@host:containername` - udev uses dev_port from sysfs instead of dev_id; ensures consistent naming even if devices have the same hardware address on system bus - machined reads /etc/os-release and /usr/lib/os-release, value shown in machinectl (contaniers> - machined reads container IPs, value shown in machinectl - file-heirarchy(7) describes minimized, modernized version of the filesystem systemd expects, similar to heir(5) or FHS. tool: systemd-path - systemd-nspawn filters syscals for kernel module loading, io port access, swap, kexec, more; for security - boot options: systemd.wants= systemd.mask= systemd.debug-shell(TTY9) - journald defaults to SplitMode=uid so users can see their coredumps - coredumpctl gains 'info' commmand to show details - systemd-coredump logs stack trace of running dumps to journal - systemd-coredup optionally stores to /var/lib/systemd/coredump instead of journal - /dev/loop-control /dev/btrfs-control /dev/fd* owned by 'disk' group - cryptsetup-pre for services that need to run before encypted mounts are up - network-pre.target for services like firewall that must start before network is up - service presets?? - systemctl is-system-running - tmpfiles: - L+ force symlink - b+ force block device - c+ force character device - C option to copy files - p+ force fifo - Omitting source for target automatically grabs correlating path based from /usr/share/factory/path - mount units have SloppyOptions= mapping to -s of `mount`. - rpm macros for sysusers, sysctl, binfmt - input group for input devices compliments audio and video groups - networkd does DHCPv4 server - netowrkd does vxlan virtual networks, tun/tap devices, dummy devices - networkd does predictable address assignments to its local interfaces. - netowrkd does automatic allocation of address ranges for interfaces from a pool, used to manage large numbers of interfaces, useful for many nspawn instances. - systemd-timesyncd - ntp client, saves state to disc for RTC-less systems, runs as systemd-timesync - systemctl list-timers;systemctl list-sockets gets --recursive to list timers and sockets inside containers. - FailureAction= option is triggered on unit failure - hostnamed exposes kernel n-v-r, helpful for -H - hostnamed prefers /etc/hostname over dhcp (unless localhost or empty) - when restoring brightness, stay away from lowest setting or lowest 5% - bootchart can show cgroup information - cgroup cpu quotas can be set with CPUQuota=NN% option - StartupCPUShares= and StartupIOWeight= sets limits only during startup - systemctl status with no arguments returns: - starting: startup - running: normal runtime - degraded: at least one failed service - maintenance: rescue/emergency mode - stopping: shutdown - - useful with containers - systemctl list-machines shows containers running systemd and their state - systemctl gets -r switch to recursively enumerate units in containers - partition discovery logic will honor GPT partition flags for read only, ignore - two GPT UUIDs, on discovery, will be mounted as / - for 32,64bit arm. - logind clears all IPC objects on user logout, controlled by RemoveIPC= in logind.conf - journald emergency messages forwarded to all users in the way of `wall` - </para> - --> - - + </para> + </section> </section>

1 0

[release-notes] Created tag container-notes
by Pete Travis 10 Oct '14

10 Oct '14

The lightweight tag 'container-notes' was created pointing to: a728029... too much info about systemd

1 0

[release-notes] too much info about systemd
by Pete Travis 10 Oct '14

10 Oct '14

commit a728029faedae9efc213965f6a21f23361467329 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Thu Oct 9 20:57:15 2014 -0600 too much info about systemd en-US/System_Daemons.xml | 135 ++++++++++++++++++++++++++++++++++++++++++++-- 1 files changed, 130 insertions(+), 5 deletions(-) --- diff --git a/en-US/System_Daemons.xml b/en-US/System_Daemons.xml index 82038f7..59c4504 100644 --- a/en-US/System_Daemons.xml +++ b/en-US/System_Daemons.xml @@ -79,13 +79,113 @@ The new command <command>systemctl preset-all</command> applices service preset settings to all unit files. The equivalent operation if the system is booted with an empty <filename class="directory" >/etc</filename>. Preset files for crucial services are provided with systemd in <filename class="directory" >/usr/lib/systemd/system-preset/</filename> </para> </listitem> + <listitem> + <para> + <emphasis>/var recreation</emphasis> + </para> + <para> + A tmpfiles snippet, <filename>/usr/lib/tmpfiles.d/var.conf</filename>, recreates the basic structure of <filename class="directory">/var</filename>, if <filename class="directory" >/var</filename> is empty. + </para> + </listitem> + </itemizedlist> </section> -

1 0

[release-notes] modular kernel packaging
by Pete Travis 08 Oct '14

08 Oct '14

commit d6c3f08cf906e355952e51effe07bc3cbbeb09b5 Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Tue Oct 7 20:31:16 2014 -0600 modular kernel packaging en-US/Kernel.xml | 24 +++++++++++++++++++++++- 1 files changed, 23 insertions(+), 1 deletions(-) --- diff --git a/en-US/Kernel.xml b/en-US/Kernel.xml index ba8e9f7..4d963de 100644 --- a/en-US/Kernel.xml +++ b/en-US/Kernel.xml @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> -<section> +<section id="kernel"> <title>Kernel</title> <indexterm> <primary>kernel</primary> @@ -15,6 +15,28 @@ <para> Fedora &PRODVER; features the &KERNEL; kernel. </para> + <section id="kernel-packaging"> + <title>Modular Kernel Packaging</title> + <para> + The <package>kernel</package> package is now a meta package that pulls in <package>kernel-core</package> and <package>kernel-modules</package>. The <package>kernel-core</package> package is smaller than a full package and is well-suited for virtualized environments. By optionally uninstalling <package>kernel-modules</package>, cloud image size can be reduced. + </para> + <para> + The <package>kernel-modules</package> package should be included when Fedora is installed on real hardware. + </para> + <important> + <title>Initramfs Changes</title> + <para> + Please note, that a new initramfs is only automatically generated by the <package>kernel-core</package> package but not the <package>kernel-modules</package> package. If you only installed <package>kernel-core</package> at first and install <package>kernel-modules</package> at a later point in time, you need to create a new initramfs manually using dracut, if any of the newly installed modules has become critical for your system's boot up. + </para> + <para> + The <command>dracut</command> utility is used to create the initramfs on Fedora. To regenerate an initramfs for all installed kernels, use the following command: + </para> + <screen> + <prompt>#</prompt> <command>dracut --regenerate-all</command> + </screen> + </important> + </section> + </section>

1 0

← Newer
1
...
10
11
12
13
14
15
16
17
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits October 2014