Handbook Talk:AMD64/Installation/Tools
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using
~~~~:
A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC) : A reply [[User:Sally|Sally]] 10:54, 5 November 2024 (UTC) :: Your reply ~~~~
warning about not using logrotate
Should be mensioned that if app-admin/sysklogd OR app-admin/syslog-ng is used that logs won't be cleared automatically like on meta-log by default.
Current warning is not efficient enough.
Kreyren (talk) 21:30, 26 August 2018 (UTC)
It already says this. --Grknight (talk) 18:42, 27 October 2018 (UTC)
systemd's journal
Link on journal of systemd should be added for the user to know how to use it.
Kreyren (talk) 21:30, 26 August 2018 (UTC)
- A note was added at some point to mention systemd's journald service. Explaining how to use journalctl goes beyond the scope of the Handbook. --Maffblaster (talk) 11:35, 27 November 2022 (UTC)
Installing system tools
I'd recommend having a highlight box around the statement which reads "If sysklogd or syslog-ng are going to be used.." to make it stand out more with regard to the need for logrotate. Not only this, but I'd also mention that logrotate is rather redundant without a cron daemon, and I personally have fallen into the trap of having some large log files stall a working system because something spammed the system-log to death [literally!] !
-- veremit (talk) 02:08, 21 February 2017 (UTC)
- Ok, I used the Tip template for it, and linked to logrotate immediately as that page also mentions the use of cron. --SwifT (talk) 16:32, 20 April 2017 (UTC)
USE flag conflict
emerge --ask net-wireless/iw net-wireless/wpa_supplicant complains
!!! The ebuild selected to satisfy "sys-apps/dbus" has unmet requirements.
- sys-apps/dbus-1.10.24::gentoo USE="X test -debug -doc -elogind (-selinux) - static-libs -systemd -user-session" ABI_X86="(64) - 32 (-X32)"
The following REQUIERED_USE flag constraints are unsatisfied:
test? ( debug )
The above constraints are a subset of the following complete expressions:
at-most-one-of ( elogind systemd ) test? ( debug )
(dependency required by "net-wireless/wpa_supplicant-2.6-r6::gentoo[dbus]" [ebuild])
(dependency required by "net-wireless/wpa_supplicant" [argument])
-- necktwi (talk) 17:24, 22 August 2018 (UTC)
- This mean if you have <test> use flag are enabled then you should also enable <debug> use flag. <test> use flag is not required for standard gentoo usage. --Cronolio (talk) 18:49, 22 August 2018 (UTC)
test is set as a Portage feature. So remove test as a value from FEATURES in make.conf. This is not an issue with our documentation. This is a support question. Please refer to #gentoo (webchat) or the mailing list for support. --Maffblaster (talk) 20:43, 22 August 2018 (UTC)
- Isn't it productive to update the documentation with the suggestion on
USEoption that avoids this error so that new users don't have to get sidetracked from the installation in search of the solution? — The preceding unsigned comment was added by Necktwi (talk • contribs) 22:13, August 22, 2018
Handbook:AMD64/Working/USE#Satisfying_REQUIRED_USE_conditions --Cronolio (talk) 11:22, 23 August 2018 (UTC)
- By having FEATURES set at all, the user already has sidetracked from the installation process. This is never a issue for anyone following the Handbook to install Gentoo...
testis not set in FEATURES by default, nor is it recommended anywhere in the installation section of the Handbook. FEATURES can be reviewed by reading man make.conf on a user's local PC and if it is unclear then support can be obtained via the proper channels or by reading other Portage related documentation here on the wiki (see Portage, /etc/portage/make.conf, Handbook:AMD64/Full/Working#Portage_features, etc.).
- You can review the whole installation section right here and see that Portage's FEATURES variable is not mentioned. Make sense? --Maffblaster (talk) 18:37, 23 August 2018 (UTC)
Setting the developer preset has given the error. I have reset to Desktop/gnome. But I want to debug drm kernel modules. Should I need developer preset?
trivial typo
"choose this package based on it's logging potential": it's should be its. Niku (talk) 06:19, 17 December 2018 (UTC)
Redundant networking tools section
Tip: To get this fixed sooner, use {{Proposal}}.
I suggest replacing/merging Handbook:AMD64/Installation/Tools#Networking_tools with a reminder to download and prepare the networking tools in Handbook:AMD64/Full/Networking and/or Network_management prior to rebooting. IMO, it is just confusing to have a triplicate mini-section on networking. --Rad (talk) 20:16, 11 March 2019 (UTC)
Mention thermald
Tip: To get this fixed sooner, use {{Proposal}}.
thermald makes a substantial difference to performance on modern Intel CPUs and prevents premature throttling.
We should recommend that users install & enable it for openrc/systemd as appropriate.
Note that it's covered at Power_management/Guide#powercap_sysfs_driver but it's rather hidden away. --Sam (talk) 10:20, 10 July 2023 (UTC)
Proposal: Link to wiki pages alongside package names, where available
Users might find it helpful if we link to the relevant wiki page, where available, alongside package names, e.g. something like:
- sysklogd (app-admin/sysklogd) - Offers the traditional set of system logging daemons.
- Added in Special:Diff/1316829/1316831, thanks!
- --csfore (talk) 16:32, 20 October 2024 (UTC)
DHCP client installation
Better rephrase:
Most users will need a DHCP client to connect to their network. If none was installed, then the system might not be able to get on the network thus making it impossible to download a DHCP client afterwards.
... to something like:
Most users will need a DHCP client to connect to their network. If none was installed, then the system might not be able to get on the network thus making it impossible to download a DHCP client afterwards without a static IP configuration.
--Duxsco (talk) 18:10, 19 September 2024 (UTC)
- Done in Special:Diff/1314107/1316829, thanks!
- --csfore (talk) 16:18, 20 October 2024 (UTC)
Add a NetworkManager in section Networking tools
- provides a proposal that can be merged as is, but as of 2024-10-29,
- that proposal has not remained unchanged and uncontested for 30 days.
A large number of desktop environments use NetworkManager as the network tool, and nmtui and nmcli are also available on the command line. I don't think we should ignore this.
Df1050 (talk) 09:09, 9 October 2024 (UTC)
- In my opinion, NetworkManager should probably be the default suggestion for the Handbook arches that support it (everything but HPPA and MIPS currently) simply because of how widespread it is. An argument might also be made for Systemd-networkd too for systemd users.
- I wrote up this initial draft:
If networking was previously configured in the Configuring the system step and network setup is complete, then this 'networking tools' section can be safely skipped. In this case, proceed with the section on Configuring a bootloader.
Installing a DHCP client
Most users will need a DHCP client to connect to their network. If none were installed, then the system might not be able to get on the network thus making it impossible to download a DHCP client afterwards without statically configuring an IP address.
A DHCP client obtains automatically an IP address for one or more network interface(s). The default recommendation is NetworkManager:
root #emerge --ask net-misc/networkmanagerWhich can subsequently be added to the default runlevel for OpenRC with:
root #rc-update add NetworkManager defaultFor systemd, enable the service with:
root #systemctl enable NetworkManagerEnsure all other DHCP daemons are removed from the default runlevel to ensure different DHCP software does not interfere with each other.
- Please give feedback, thank you!
- --csfore (talk) 01:52, 27 October 2024 (UTC)