June 2011 - Arch-general - lists.archlinux.org

[arch-general] [signoff] kernel26-2.6.39.1-1
by Tobias Powalowski 11 Jun '11

11 Jun '11

Hi guys, please signoff 2.6.39 series for both arches. Upstream changes: http://kernelnewbies.org/LinuxChanges WARNING: AUFS2 support is gone for now, if this is no showstopper we should go move it to [core]. If noone has real objections, I hope to get this kernel into [core]. Along with this the binary modules mentioned on the previous thread will be removed from [core] and [extra]: - tiacx (broken) - ndiswrapper (not needed anymore) - intel536/537 (does not compile on .39 series) - madwifi (obsolete) - martian (old modem driver) - tiacx-lts - ndiswrapper-lts greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

4 3

[arch-general] blacklisting/MOD_AUTOLOAD - what drove the change?
by David C. Rankin 11 Jun '11

11 Jun '11

Guys, Just curious for the reason behind the changes to blacklisting and MOD_AUTOLOAD. What drove the change? -- David C. Rankin, J.D.,P.E.

2 1

[arch-general] Dejavu sans mono fonts rendering issue.
by mwnn 11 Jun '11

11 Jun '11

Hi, I am unable to configure fonts on my new arch linux system. The fonts from the old slackware installation are similar to http://i.imgur.com/UcwHS.png. The new arch linux fonts look like http://imageshack.us/photo/my-images/695/newemacs.jpg/ Regards, mwnn

4 5

Re: [arch-general] [arch-announce] Deprecation of net-tools
by Heiko Baums 11 Jun '11

11 Jun '11

Am Wed, 08 Jun 2011 16:01:15 -0000 schrieb "Arch Linux: Recent news updates: Tom Gundersen" <announce(a)archlinux.org>: > Tom Gundersen wrote: > > 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. > ... > We want to encourage the use of more > advanced network solutions, such as `networkmanager` or our own > `netcfg`. Well, I don't want to say anything, but netcfg still depends on net-tools. ;-) Heiko

7 16

[arch-general] EveryDNS compulsory migration to Dyn
by Abdul Halim 11 Jun '11

11 Jun '11

I can't help but notice that ArchLinux is using EveryDNS for its DNS server. And since I also use EveryDNS DNS server, what is the plan for ArchLinux domain administrator since EveryDNS users need to migrate to Dyn by 31-Aug-2011? Will the administrator use the paid service or something else?

2 1

[arch-general] EveryDNS compulsory migration to Dyn
by Abdul Halim 11 Jun '11

11 Jun '11

I can't help but notice that ArchLinux is using EveryDNS for its DNS server. And since I also use EveryDNS DNS server, what is the plan for ArchLinux domain administrator since EveryDNS users need to migrate to Dyn by 31-Aug-2011? Will the administrator use the paid service or something else?

1 0

[arch-general] On deprecation of net-tools
by Magnus Therning 11 Jun '11

11 Jun '11

With the recent deprecation of net-tools I did notice some changes: - The binary 'hostname' now accepts remarkably few options, specifically 'hostname -d' no longer works. - The command 'dnsdomainname' disappeared. (I'm not really sure why I ended up using it though, since 'hostname -d' would have worked just as well.) I have read FS#24647 already, so I'm aware that some of this is being worked on. What I'm wondering is, what can I do in the meantime to get 'hostname -d' back? -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus(a)therning.org jabber: magnus(a)therning.org twitter: magthe http://therning.org/magnus Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. -- Alan Kay

2 2

Re: [arch-general] [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
by Marek Otahal 10 Jun '11

10 Jun '11

Hello Tom, thanks for the pre-announcement, looks good. I have just a question.. Since net-tools are going to be abandoned (I was wondering how i "misuninstalled" the package), what do i use as an alternative to ifconfig? I use wicd or manually bring LAN up, and it occurred to me network interfaces failed due to missing ifconfig command. What is the new one? Thanks On Tuesday 07 of June 2011 23:21:11 Tom Gundersen wrote: > 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 > -- Marek Otahal :o)

15 25

[arch-general] mpd fails to start
by Madhurya Kakati 10 Jun '11

10 Jun '11

Hello, Recently mpd has stopped working. It doesn't start up at boot and when i run "rc.d start mpd" I get this error /etc/rc.d/mpd: line 6: 24502 Aborted /usr/bin/mpd /etc/mpd.conf &>/dev/null. I am using gnome3(if thats somehow causing the problem.) I believe its due to some ALSA pulseaudio mixup but I am not sure. However if I run "sudo mpd" I get this output: [papul@papuldesktop ~]$ sudo mpd output: No "audio_output" defined in config file output: Attempt to detect audio output device output: Attempting to detect a alsa audio device output: Successfully detected a alsa audio device and after that if I run "mpc play" I get this: [papul@papuldesktop ~]$ mpc play Metallica - The Unforgiven II [paused] #4/8 0:00/6:36 (0%) volume: n/a repeat: off random: off single: off consume: off ERROR: problems opening audio device Please help coz I haven't been able to listen to music for quite sometime now. :(

2 3

[arch-general] hwclock and openntpd
by Yclept Nemo 10 Jun '11

10 Jun '11

A recent announcement said: * The adjustment of the hwclock for drift is moved into a daemon that should not be used in most scenarios as it can lead to subtle bugs (especially if using dual-boot or ntp). If you know what you are doing and want to adjust the hardware clock for drift, add `"hwclock"` to your `DAEMONS` array. I use openntpd, and with hwclock disabled - DAEMONS=(!hwclock ...) - I've been getting these errors every reboot: "Superblock last mount time is in the future (by less than a day, probably due to the hardware clock being incorrectly set) - fixed" Perhaps openntpd does not set the hwclock. Therefore, should openntpd be used in conjuction with the hwclock daemon?

5 4