Skip to main content
Version: 1.0

Upgrading

Upgrading from 1.x to 2.x#

Installation#

The installation of ircd-yeti 2 works exactly the same as installing 1.x.

For example:

./configure -prefix=$HOME/ircdmake -j2make install

Modules#

In ircd-yeti 2, the "m_" prefix has been dropped from all module names. You will need to update any configuration files, as appropriate, and use the non-prefixed name of a module when using the MODULE command.

The following modules have been removed from ircd-yeti 2:

  • sethost

User modes#

The following user modes have been removed in ircd-yeti 2:

  • +h, sethost
  • +q, common channels only; see umode +G (soft callerID)

The following user modes have been changed in ircd-yeti 2:

  • Debug notices have been moved from umode +g to umode +E

Configuration changes#

  • The tls::identity::dh_elliptic_curve setting has been renamed to tls::identity:supported_groups. It is configured in the same way.
    • Solution: simply rename the setting.
  • ipcheck {} blocks have been removed.
    • Solution: use exempt {} blocks instead.
  • spoofhost {} blocks have been removed.
    • Solution: remove any spoofhost {} blocks.
  • cloak::ipv4_format_host, cloak::ipv6_format_host and cloak::host_suffix have been removed.
    • Solution: use cloak::value instead, which now uses variable substitution.
  • SETHOST feature setting has been removed.
    • Solution: remove it from any features {} blocks.
  • SETHOST_USER feature setting has been removed.
    • Solution: remove it from any features {} blocks.
  • SETHOST_AUTO feature setting has been removed.
    • Solution: remove it from any features {} blocks.
  • HIS_STATS_SPOOFHOSTS feature setting has been removed.
    • Solution: remove it from any features {} blocks.
  • The default value for WHOIS_CHAN_PRIVACY feature setting has been changed to TRUE.
    • Solution: you now only need to specify this setting if setting it to FALSE.
  • The default value for ANNOUNCE_INVITES feature setting has been changed to TRUE.
    • Solution: now you only need to specify this setting if setting it to FALSE.
    • Note: The actual invite notification is now handle by the cap_invitenotify module.