From Fedora Project Wiki

< Changes

Revision as of 14:48, 25 July 2017 by Jkurik (talk | contribs) (→‎Current status)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



Do not install /etc/profile.d/ and /etc/profile.d/256term.csh.


Current status

Detailed Description

Currently Fedora installs some scripts to be executed every time a shell is started which perform some heuristics to set $TERM based on the terminal emulator being used. This is a work-around and it's better to for the terminal emulator to set $TERM properly on its own. Various terminal emulators have been updated to do that. /etc/profile.d/ and /etc/profile.d/256term.csh will not be installed anymore and the $TERM variable set by the terminal emulator will be used.

[The change is trivial in and of itself. I'm making this a system wide change, and a change at all, only because those scripts take part in every shell startup, so it's possible they will have some unforeseen impact or require adjustments in other components. If FeSCO or Wrangler think this does need a change page, I'm ready to drop it.]

Benefit to Fedora

The environment is initialized in a simpler, more predictable way. A step is made towards removing initscripts package. The common path in shell startup is slightly optimized. Less used shells and terminal emulators work out-of-the-box the same as the popular ones.


  • Proposal owners: do the change in initscripts package, work with other developers to fix any identified issues.
  • Other developers: fix any identified issues
  • Policies and guidelines: N/A
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

The change will take effect on old and new systems in the same way when the updated initscripts package is installed.

How To Test

Make sure that $TERM is set properly in various circumstances (a shell open in a terminal emulator, a ssh connection from a Fedora machine to a different machine, a shell connection from a different machine to Fedora, screen session, tmux session, etc.) and that stuff is displayed properly.

User Experience

Should not be noticeable.



Contingency Plan

Restore those two scripts.

  • Contingency deadline: beta freeze
  • Blocks release? No
  • Blocks product? No


Release Notes

None needed.