Handbook Talk:AMD64/Installation/Tools

From Gentoo Wiki
Jump to:navigation Jump to:search
Before creating a discussion or leaving a comment, please read about using talk pages. In particular, sign comments using ~~~~ and add new discussions at the bottom of the page. New discussions should be made visible with {{Talk|date = 2024-05-18}}.
== Discussion title ==

{{Talk|date = 2024-05-13}}

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 11:29, 14 May 2024 (UTC)
:: Another reply [[User:Larry|Larry]] 09:12, 18 May 2024 (UTC)
:: Your reply ~~~~

Navigate to first:

warning about not using logrotate

Talk status
This discussion is done.

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

Talk status
This discussion is done as of 2022-11-27.

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

Talk status
This discussion is done as of April 20th, 2017.

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

Talk status
This discussion is done as of August 22nd, 2018.

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 USE option 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 (talkcontribs) 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... test is 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

Talk status
This discussion is done.

"choose this package based on it's logging potential": it's should be its. Niku (talk) 06:19, 17 December 2018 (UTC)

complete, thanks for noticing. --Grknight (talk) 13:38, 17 December 2018 (UTC)

Redundant networking tools section

Talk status
This discussion needs help as of March 11, 2019.
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

Talk status
This discussion needs help.
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)