[arch-dev-public] [signoff] coreutils-8.12-2, initscripts-2011.06.3-1, net-tools-1.60-16, udev-171-2, yp-tools-2.12-2, ypbind-mt-1.33-2, iproute2-2.6.38-3
A few minor issues cropped up, so we needed to update two more packages - ypbind-mt: moved the nisdomainname config file here from net-tools, and fix the rc script; and - iproute2: move /usr/bin/ip to /bin/ip, and add a symlink so old packages will still work. Please test and signoff everything (or the subset of the packages that you use at least). Cheers, Tom On Thu, Jun 2, 2011 at 5:28 PM, Tom Gundersen <teg@jklm.no> wrote:
Hi guys,
After the discussion regarding initscripts-2011.06.1 we decided that things would be simpler if we move all the above packages in one go (thanks to Gaetan and Thomas for the help!), so please test and sign off.
Below is a summary of changes, I will write a nicer summary for the front page before moving to core.
---- udev ----
As mentioned in several previous emails, we have been working to remove modules-load.sh from udev. This should simplify the package significantly (so it should be easier to submit bugs upstream and we will benefit more easily from any fixes and improvements they do), at least on my machine I also notice a small but significant speedup in boot time (2,5 sec, or about 10%). In this release of udev, modules-load.sh is finally removed.
This means that our custom blacklisting of modules no longer works, but this should not be a problem as modprobe has native support for blacklisting. For details see 'man modprobe.conf'. Furthermore, as of the latest modules-init-tools release you can blacklist modules on the kernel command line by using the following syntax: "modprobe.blacklist=mod1,mod2,mod3". Alternatively modules can be disabled by using the syntax "mod1.disable=1".
---- net-tools ----
It is now more than a decade since the last net-tools release, so we no longer want to rely on this package. With these changes it is not installed by default any longer, but can be used by those who prefer to keep the old behavior. In order to do this we did three things:
1) initscripts now defaluts to using iproute2 2) hostname is now provided by coreutils 3) nisdomainname is now provided by yp-tools
---- Initscripts: ----
Big changes:
1) We gain support for iproute2, and net-tools is now optional (thanks to Dave Reisner). If you don't update your rc.conf, everything should work as before (using net-tools), pleas shout if it does not.
2) MOD_AUTOLOAD no longer has any effect (modules are always autoloaded).
3) blacklisting modules in the MODULES array is no longer supported, use modprobe's native blacklisting instead (see 'man modprobe.conf'). An announcement will be made about this before moving to core.
4) We no set domainname at boot. Supporting this was complicated by the move of the binary to yp-tools, and is done in the ypbind rc script instead.
Otherwise there are some bugfixes, and quite a bit of improvements made to rc.d.
Thanks to all who contributed:
Clément Démoulins (1): Add a zsh completion script for the command rc.d.
Dave Reisner (3): network/rc.sysinit: remove dead code network: deprecate net-tools, add iproute2 support rc.d: declare ENV as an array
Eric Bélanger (1): rc.d: Add error message when daemon script is not found
Gerardo Exequiel Pozzi (2): use mount -n for devpts and shm add killall5 omit pid functionality
Sebastien Luttringer (8): Add syntax to vim modeline in rc.d script Add TERM var to rc.d cleaned env Improve coloring on light and transparent term Add rc.d bash completion rc.d bash completion detect running daemon rc.d zsh completion detect running daemons rc.d: Remove cd from the loop rc.d: print usage if not enough argument
Thomas Bächler (1): Fix typo
Tom Gundersen (13): releasing: update instructinos after going through it once makefile: do not make functions executable udev: generate blacklist on boot fixup: also clear /tmp if it is a mountpoint Merge remote-tracking branch 'seblu/master' Revert "udev: generate blacklist on boot" depraction: MOD_AUTOLOAD and MODULES blacklisting net: add examples Merge branch 'snowman' agetty: keep baud rate from kernel if possible fixup: stat_busy/stat_done -> status fixup: network: deprecate net-tools nisdomainname: remove support
[2011-06-05 00:50:12 +0200] Tom Gundersen:
A few minor issues cropped up, so we needed to update two more packages - ypbind-mt: moved the nisdomainname config file here from net-tools, and fix the rc script; and - iproute2: move /usr/bin/ip to /bin/ip, and add a symlink so old packages will still work.
Signoff both. -- Gaetan
On 5 June 2011 01:50, Tom Gundersen <teg@jklm.no> wrote:
A few minor issues cropped up, so we needed to update two more packages - ypbind-mt: moved the nisdomainname config file here from net-tools, and fix the rc script; and - iproute2: move /usr/bin/ip to /bin/ip, and add a symlink so old packages will still work.
Please test and signoff everything (or the subset of the packages that you use at least).
Signoff x86_64.
This should be moved to [core] quickly. If you try to create a testing chroot, it will proceed to install the 'base' group. Problem is, net-tools-1.60-16 no longer belongs to that group, but the old version (1.60-14) from [core] does. However, the latter causes file conflicts with the latest coreutils package. :)
On 7 June 2011 19:02, Evangelos Foutras <foutrelis@gmail.com> wrote:
This should be moved to [core] quickly.
If you try to create a testing chroot, it will proceed to install the 'base' group. Problem is, net-tools-1.60-16 no longer belongs to that group, but the old version (1.60-14) from [core] does. However, the latter causes file conflicts with the latest coreutils package. :)
Workaround if anyone needs to create new testing chroots: - Hit ^Z after pacman has downloaded the database for [core], but before the initial database sync finishes. - Go into the chroot's /var/lib/pacman/sync. - Move core.db to core.db.tar.gz so that vim recognizes it as a gzipped tarball. - Edit the core.db.tar.gz file in place using vim and remove the base group from net-tools. - Exit vim and rename the database back to core.db. - Execute fg to resume the stopped pacman process. :p
On Tue, Jun 7, 2011 at 6:02 PM, Evangelos Foutras <foutrelis@gmail.com> wrote:
This should be moved to [core] quickly.
If you try to create a testing chroot, it will proceed to install the 'base' group. Problem is, net-tools-1.60-16 no longer belongs to that group, but the old version (1.60-14) from [core] does. However, the latter causes file conflicts with the latest coreutils package. :)
Thanks for the heads up! Could we have one more signoff for i686 before the move? I'll post my suggested announcements in a reply to this thread. Cheers, Tom
Since these update introduces some important changes I'd like to make two announcements before it is moved to core (which should be as soon as we have the missing i686 signoff). Drafts below, comments welcome. Announcement one: ============================================= Deprecation of net-tools This April marked the ten year anniversary of the last net-tools release. We decided to look at this as an opportunity to deprecate net-tools and provide alternative, and better maintained, solutions for net-tools functionality. This has a few consequences, but most people should not notice. `hostname` ---------- This binary is now provided by `coreutils`, rather than by `net-tools`. `domainname` (a.k.a. `nisdomainname`, a.k.a `ypdomainname`) ----------------------------------------------------------- These binaries are now provided by `yp-tools`, rather than by `net-tools`. Furthermore, the domain name is no longer set by initscripts, rather it is dealt with entirely by the ypbind rc script. Before this change the domain name was handled inconsistently, sometimes being read from `/etc/conf.d/nisdomainname`, and sometimes from `/etc/defaultdomain`. From now on, the domain name is only ever read from `/etc/conf.d/nisdomainname`. `network` ------------------------------ A new syntax is introduced in `rc.conf` for configuring a simple network setup using `iproute2` rather than `net-tools`. The old functionality is still preserved for those preferring to stay with that, but do not expect updates for this. The new syntax is very simplistic and only supports one wired network device (configured statically or by dhcp) and we do not expect to add more features in the future. We want to encourage the use of more advanced network solutions, such as `networkmanager` or our own `netcfg`. Announcement two: ============================================= Changes to module blacklisting Since the dawn of time we have shipped our homegrown system for blacklisting kernel modules (in various incarnations). This has served us well, but we (or rather our various upstreams) have now reached a point where it is no longer necessary. We have therefore decided to remove all our module blacklisting logic, and rely entirely on the blacklisting provided by `modprobe`. This means a change in syntax, and a minor change in functionality. We hope that the short-term inconvenience will be justified by the long-term gain. The different notions of blacklisting -------------------------------------------- The notion of module blacklisting that we have used is (sadly) slightly different from what is used by modprobe. * our blacklisting: a blacklisted module, or any module that depends on it, will never be loaded automatically by udev, but may be loaded manually. * modprobe's blacklisting: a blacklisted module will not be loaded automatically, but may be loaded if another non-blacklisted module depends on it, or if it is loaded manually. * disabling a module: one can get similar behavior to what we used to provide by forcing a module to always fail loading, it will not be possible to load it manually. Boot time blacklisting --------------------------- Modules can be blacklisted at boot time by appending `modprobe.blacklist=mod1,mod2,mod3` to the kernel command line (in grub, lilo or syslinux). Alternatively, the modules can be disabled altogether by appending `mod1.disable=1 mod2.disable=1 mod3.disable=1` instead. Persistent blacklisting --------------------------- Rather than blacklisting modules in `rc.conf`, use modprobe's native configuration files. These can be found in /etc/modprobe.d/, and are documented in `man modprobe.d`. The replacement of `rc.d`'s `MODULES=(!mod1 !mod2 !mod3)` is to add a `.conf` file to `/etc/modprobe.d/` with the contents: blacklist mod1 blacklist mod2 blacklist mod3 Alternatively, to ensure that the modules are never inserted, even if they are needed by other modules you load: install mod1 /bin/false install mod2 /bin/false install mod3 /bin/false
On Tue, Jun 7, 2011 at 11:21 PM, Tom Gundersen <teg@jklm.no> wrote:
Drafts below, comments welcome.
Thanks to everyone who commented on the draft! Cheers, Tom
On 7 June 2011 21:49, Tom Gundersen <teg@jklm.no> wrote:
On Tue, Jun 7, 2011 at 6:02 PM, Evangelos Foutras <foutrelis@gmail.com> wrote:
This should be moved to [core] quickly.
If you try to create a testing chroot, it will proceed to install the 'base' group. Problem is, net-tools-1.60-16 no longer belongs to that group, but the old version (1.60-14) from [core] does. However, the latter causes file conflicts with the latest coreutils package. :)
Thanks for the heads up!
Could we have one more signoff for i686 before the move? I'll post my suggested announcements in a reply to this thread.
Here's another signoff for i686. The announcements look good too. :)
participants (3)
-
Evangelos Foutras
-
Gaetan Bisson
-
Tom Gundersen