April 2009 - Arch-general - lists.archlinux.org

Re: [arch-general] [Fwd: [arch-announce] Dropping i686 support]
by kludge 03 Apr '09

03 Apr '09

Loui Chang wrote: > On Wed, Apr 01, 2009 at 02:35:34PM -0500, kludge wrote: >> leslie: fuck you and your macho-nerd, myth-of-progress bullshit. >> >> all the rest: i'm really upset with this decision. the basic >> assumption that anyone who matters is spending money on new hardware is >> fucked-up. > > I LOLed. alright, alright, ya' got me. the best jokes contain a kernel of truth, and this one hit real close to home. i maintain the basic premise of leslie's comment (serious or not) is widely held and fundamentally bad for the world. *and* i woke up with a hang-over, so please forgive me for being a bit too credulous. sheesh, kludge

4 3

[arch-general] Make arch-announce read only?
by pyther 03 Apr '09

03 Apr '09

I was wondering if we could make arch-announce a read only list. Sort of like the dev mailing list. Anyone who tries to respond to an announcement could get an email saying something along the lines of "If you have a comment about an announcement, please post it on the arch-general list. Thank you." I do not filter the arch-announce mailings for obvious reason and I do not think I am alone. It is very annoying to see replies in my inbox. ~pyther

5 5

[arch-general] Fatal Error
by arunix 02 Apr '09

02 Apr '09

Hello :-) i am again posting here i have problem with wmiirc boz when i start X it works bt when i come back with the command ctrl+alt+backkey(backspace) it shows me error The error are :-( (EE)failed to load module"type1"(module doesnot exist,0) (EE)failed to load module"record"(module doesnot exist,0) wmii:not missing fontset for '-*-------font-------" : KSC5601.1987-0, GB2312.1980.0 xlib:extension "Generic event extension" missing on display "0:0" wmii:note :extension "Generic event extension" missing on display "0:0" xIO :fatal IO error 11(Resource temperorily unaviable) on X server ":0.0" after 1166 (1166 unknown processed) with 0 event remaning xinit: for X server lost waiting for X server to shutdown wmii:fatal : cannot read file /directory 'event broken' :Broken Pipe xIO :fatal IO error 11(Resource temperorily unaviable) on X server ":0.0" wmii: fatal: cant mount connection refused /home/arunix/.wmii/wmiirc : line 38 : echo: write error Broken Pipe here is wmiirc file dont understand whts wrong with it? #!/bin/sh -f # Configure wmii # Configuration Variables MODKEY=Mod4 UP=k DOWN=j LEFT=h RIGHT=l # Colors tuples: "<text> <background> <border>" WMII_NORMCOLORS='#888888 #222222 #333333' WMII_FOCUSCOLORS='#ffffff #285577 #4c7899' WMII_BACKGROUND='#333333' WMII_FONT='-*-fixed-medium-r-*-*-13-*-*-*-*-*-*-*' set -- $(echo $WMII_NORMCOLORS $WMII_FOCUSCOLORS) WMII_MENU="dmenu -b -fn '$WMII_FONT' -nf '$1' -nb '$2' -sf '$4' -sb '$5'" WMII_9MENU="wmii9menu -font '$WMII_FONT' -nf '$1' -nb '$2' -sf '$4' -sb '$5' -br '$6'" WMII_TERM="xterm" # Column Rules wmiir write /colrules <<! /.*/ -> 58+42 ! # Tagging Rules wmiir write /tagrules <<! /XMMS.*/ -> ~ /MPlayer.*/ -> ~ /.*/ -> sel /.*/ -> 1 ! # Status Bar Info status() { echo -n $(uptime | sed 's/.*://; s/,//g') '|' $(date) } # Event processing # Processed later by `wmiiloop' and evaled. # Duplicate the eval line and replace 'eval' with 'echo' for details. eventstuff() { cat <<'!' # Events Event Start case "$1" in wmiirc) exit; esac Event Key fn=$(echo "$@" | sed 's/[^a-zA-Z_0-9]/_/g') Key_$fn "$@" Event CreateTag echo "$WMII_NORMCOLORS" "$@" | wmiir create "/lbar/$@" Event DestroyTag wmiir remove "/lbar/$@" Event FocusTag wmiir xwrite "/lbar/$@" "$WMII_FOCUSCOLORS" "$@" Event UnfocusTag wmiir xwrite "/lbar/$@" "$WMII_NORMCOLORS" "$@" Event UrgentTag shift wmiir xwrite "/lbar/$@" "*$@" Event NotUrgentTag shift wmiir xwrite "/lbar/$@" "$@" Event LeftBarClick shift wmiir xwrite /ctl view "$@" # Actions Action quit wmiir xwrite /ctl quit Action exec wmiir xwrite /ctl exec "$@" Action rehash proglist $PATH >$progsfile Action status set +xv if wmiir remove /rbar/status 2>/dev/null; then sleep 2 fi echo "$WMII_NORMCOLORS" | wmiir create /rbar/status while status | wmiir write /rbar/status; do sleep 1 done Event ClientMouseDown client=$1; button=$2 case "$button" in 3) do=$(eval $WMII_9MENU -initial "${menulast:-SomeRandomName}" Nop Delete Fullscreen) case "$do" in Delete) wmiir xwrite /client/$client/ctl kill;; Fullscreen) wmiir xwrite /client/$client/ctl Fullscreen on;; esac menulast=${do:-"$menulast"} esac # Key Bindings Key $MODKEY-Control-t case $(wmiir read /keys | wc -l | tr -d ' \t\n') in 0|1) echo -n $Keys | tr ' ' '\012' | wmiir write /keys wmiir xwrite /ctl grabmod $MODKEY;; *) wmiir xwrite /keys $MODKEY-Control-t wmiir xwrite /ctl grabmod Mod3;; esac Key $MODKEY-space wmiir xwrite /tag/sel/ctl select toggle Key $MODKEY-d wmiir xwrite /tag/sel/ctl colmode sel default Key $MODKEY-s wmiir xwrite /tag/sel/ctl colmode sel stack Key $MODKEY-m wmiir xwrite /tag/sel/ctl colmode sel max Key $MODKEY-a Action $(actionlist | eval $WMII_MENU) & Key $MODKEY-p sh -c "$(eval $WMII_MENU <$progsfile)" & Key $MODKEY-t wmiir xwrite /ctl "view $(tagsmenu)" & Key $MODKEY-Return eval $WMII_TERM & Key $MODKEY-Shift-space wmiir xwrite /tag/sel/ctl send sel toggle Key $MODKEY-f wmiir xwrite /client/sel/ctl Fullscreen toggle Key $MODKEY-Shift-c wmiir xwrite /client/sel/ctl kill Key $MODKEY-Shift-t wmiir xwrite "/client/$(wmiir read /client/sel/ctl)/tags" "$(tagsmenu)" & Key $MODKEY-$LEFT wmiir xwrite /tag/sel/ctl select left Key $MODKEY-$RIGHT wmiir xwrite /tag/sel/ctl select right Key $MODKEY-$DOWN wmiir xwrite /tag/sel/ctl select down Key $MODKEY-$UP wmiir xwrite /tag/sel/ctl select up Key $MODKEY-Shift-$LEFT wmiir xwrite /tag/sel/ctl send sel left Key $MODKEY-Shift-$RIGHT wmiir xwrite /tag/sel/ctl send sel right Key $MODKEY-Shift-$DOWN wmiir xwrite /tag/sel/ctl send sel down Key $MODKEY-Shift-$UP wmiir xwrite /tag/sel/ctl send sel up ! for i in 0 1 2 3 4 5 6 7 8 9; do cat <<! Key $MODKEY-$i wmiir xwrite /ctl view "$i" Key $MODKEY-Shift-$i wmiir xwrite /client/sel/tags "$i" ! done } # WM Configuration wmiir write /ctl << EOF font $WMII_FONT focuscolors $WMII_FOCUSCOLORS normcolors $WMII_NORMCOLORS grabmod $MODKEY border 1 EOF export WMII_MENU WMII_9MENU WMII_FONT WMII_TERM export WMII_FOCUSCOLORS WMII_SELCOLORS WMII_NORMCOLORS # Feed events to `wmiiloop' for processing eval "$(eventstuff | sed 's/^[ ]//' | { . wmiiloop; })" echo "$Keys" | tr ' ' '\n' | wmiir write /keys # Functions Action() { action=$1; shift if [ -n "$action" ]; then Action_$action "$@" \ || conf_which $action "$@" fi } proglist() { paths=$(echo "$@" | sed 'y/:/ /') ls -lL $paths 2>/dev/null \ | awk '$1 ~ /^[^d].*x/ && NF > 2 { print $NF }' \ | sort | uniq } # Misc progsfile="$WMII_NS_DIR/.proglist" Action status & proglist $PATH >$progsfile & xsetroot -solid "$WMII_BACKGROUND" & # Setup Tag Bar seltag="$(wmiir read /tag/sel/ctl 2>/dev/null)" wmiir ls /lbar | while read bar; do wmiir remove "/lbar/$bar" done wmiir ls /tag | sed -e 's|/||; /^sel$/d' | while read tag; do if [ "X$tag" = "X$seltag" ]; then echo "$WMII_FOCUSCOLORS" "$tag" | wmiir create "/lbar/$tag" else echo "$WMII_NORMCOLORS" "$tag" | wmiir create "/lbar/$tag" fi done # More functions tagsmenu() { wmiir ls /tag | sed 's|/||; /^sel$/d' | eval $WMII_MENU } actionlist() { { proglist $WMII_CONFPATH echo -n $Actions | tr ' ' '\012' } | sort | uniq } conf_which() { which=$(which which) prog=$(PATH="$WMII_CONFPATH" $which $1); shift [ -n "$prog" ] && $prog "$@" } # Stop any running instances of wmiirc echo Start wmiirc | wmiir write /event || exit 1 wmiir read /event | while read event; do set -- $event event=$1; shift Event_$event $@ done 2>/dev/null -- View this message in context: http://www.nabble.com/Fatal-Error-tp22805236p22805236.html Sent from the arch general mailing list archive at Nabble.com.

4 7

[arch-general] [Fwd: [arch-announce] Dropping i686 support]
by David Rosenstrauch 02 Apr '09

02 Apr '09

Hmmm ... My only concern about this is that it's often difficult or impossible to run an x86_64 distro inside a VM. So one very definite negative of this change is that it'd restrict many/most people's ability to run Arch inside of a VM - something I've done many times, and have found very convenient, and which would be a shame to lose. Just my $0.02. DR -------- Original Message -------- Subject: [arch-announce] Dropping i686 support Date: Wed, 01 Apr 2009 01:03:08 -0000 From: Recent News Updates <announce(a)archlinux.org> Reply-To: Arch Linux Announcements <arch-announce(a)archlinux.org> To: arch-announce(a)archlinux.org Recently the developers have been discussing the possibility of adding some additional optimizations to our i686 port to improve multimedia support. This would involve reducing the compatibility with older systems. As some of you may have heard ([1], Google translation [2]), this discussion has resulted in the decision to focus exclusively on the x86_64 port. The overall opinion of the developers is that the x86_64 port is now complete enough to justify this decision and that this is in keeping with Arch's philosophy of supporting current generation hardware. The x86_64 architecture has been available since 2002 (compared to i686 which is from 1995), and we believe most of our i686 users have x86_64 compatible hardware. An official time-line for the deprecation of the i686 port has not been established, but an official announcement needs to be made, as the decision has already been leaked to the ArchLinux-BR community. However, it is likely that major updates (GNOME, KDE, Xor g, etc) will not be built for i686 in the immediate future. Users will still be able to build packages for i686 packages using ABS. As most of the architecture specific patches are for x86_64, this should be relatively pain free. [1] <a href="http://groups.google.com/group/archlinux-br/browse_thread/thread/d1b6075adf…">http://groups.google.com/group/archlinux-br/browse_thread/thread/d1b6075adf…</a> [2] <a href="http://translate.google.com/translate?prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2…">http://translate.google.com/translate?prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2…</a> URL: http://www.archlinux.org/news/440/ _______________________________________________ arch-announce mailing list arch-announce(a)archlinux.org http://www.archlinux.org/mailman/listinfo/arch-announce

31 51

[arch-general] Orphan core
by Baho Utot 02 Apr '09

02 Apr '09

Can someone please orphan core and extra so I can adopt it?

4 4

[arch-general] Sick of xf86-video-intel? Use the framebuffer device!
by Pierre Schmitz 02 Apr '09

02 Apr '09

Hi all, I am a proud user of an Intel 855GM chipset. Some time ago when the i810 xorg dirver was replaced by the xf86-viedo-intel performance were decreased from version to version and in the end it was unusable due to too many bugs an problems. * support for tv-out was dropped (ok, not that important for me) * xv does not work. You either get a green or blue square or your whole X crashes. * all kinds of false rendering * extremly slow 2D performance. Even with UXA I can watch the single elements redrwaing if I switch tabs in konqueror for example * too slow to watch videos on youtube or even a DVD * overall instability * suspend/resume is just a matter of luck When I was just seeing garbage on my screen (=unusable) with the new 2.6.29 kernel I started looking for alternatives: * xorg vesa driver: faster than intel and stable; bu still performance was not that great (of course, there is no hw acceleration) * vesafb+fbdev: similar performance; fast switching to vc and back is nice :-) Finally I got intelfb working. Togehter with the xorg fbdev driver this seems to solve all my problems. It is really fast and stable. Suspend/Resume works fine and as a bonus I get fast vc switching (who needs kms for this? ;) Well, there is no support for xv, but I can watch DVDs with x11 output driver without issues. Using mplayer with fbdev output it is even possible to watch 720p videos. The problem is: you have to compile your own kernel. The stock kernel provides the intelfb module but you cannot use it because vesafb is compiled in. I did not find a way to work around this. As soon as you start the kernel with a vga=XXX parameter vesafb gets loaded and other fb drivers cannot work. So, here is a patch and a precompiled kernel for those who want to try it: http://users.archlinux.de/~pierre/packages/src/intelfb.patch http://users.archlinux.de/~pierre/packages/i686/kernel26-intelfb-2.6.29-4- i686.pkg.tar.gz It is also possible to build intelfb as a module; just add intel_agp and intelfb to your modules list in mkinitcpio.conf. I hope this is helpful for some of you, Pierre -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre(a)jabber.archlinux.de WWW http://www.archlinux.de

3 4

[arch-general] Adding LDFLAGS to /etc/makepkg.conf
by Alexandre Bique 01 Apr '09

01 Apr '09

Hi, I am trying these FLAGS: CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -ftree-vectorize -ftree-parallelize-loops=4" CXXFLAGS="${CFLAGS}" And i need to link to libgomp so i tried to add LDFLAGS="-lgomp" But it doesn't work. What should i do doctor ? Thanks. -- Alexandre Bique

2 3

[arch-general] HAL mount options
by Edgar Kalkowski 01 Apr '09

01 Apr '09

Hi! Until now I used /etc/fstab to mount my usb memory stick but I would like to switch that task to hal now to be able to use the cool removable devices widget of plasma. The problem is that I defined some options in /etc/fstab and cannot get hal to use the same options. The fstab line look like this: LABEL=USB-Stick /mnt/USB-Stick vfat uid=root,gid=users,showexec,user,noauto,umask=002,utf8,shortname=mixed 0 0 From what I googled on the web I deduced that I should create a file named /etc/hal/fdi/policy/20-USB-Stick.fdi and fill it with the following content: <?xml version="1.0" encoding="UTF-8"?> <deviceinfo version="0.2"> <device> <match key="volume.uuid" string="4908-87A8"> <merge key="volume.policy.mount_option.showexec" type="bool">true</merge> </match> </device> </deviceinfo> The volume uuid (4908-87A8) was obtained via "$ /lib/udev/vol_id /dev/sdc1" where sdc1 is the partition on my usb stick I want to mount. I restarted hal and tried it after creating this fdi file but it does not work. The executable bit is still set for both directories and folders. As this didn't work I did not yet try to implement the other options. Does anyone have an idea? Is there some documentation about these fdi files on the web that I did not find? Thanks in advance for your help! Edgar

2 2

[arch-general] i686 build machines for rent
by Corrado Primier 01 Apr '09

01 Apr '09

Since the decision of discontinuing the i686 binary repo, many people who can't or don't want to switch will need to recompile their packages themselves. Then there's also the problem of devs and TUs who don't have access to an x86_64 machine. Striving to find a solution I came up with an idea: selling processing power! That's right, guys. Do you own one of those slow i686-only dinosaurs? Do you need the power of an x86_64 machine to get your packages built quickly in i686 chroots? I'm here for you! I have a couple of machines I can dedicate to this task. I decided for a "political" price of 20€/year; all revenues will be donated to the OxPD (One x86_64 Per Developer) Project. Before setting everything up I'd like to hear from the community if this is something they're interested in, and I'm obviously also asking all Arch contributors who have a decent machine (x86_64, that is...) to dedicate it to this important project that will allow all of our devs to continue their work for our favorite distro. Corrado Primier (Arch Linux Trusted User)

4 3

[arch-general] ArchLinux install CD for the blind, version 2!
by Chris Brannon 01 Apr '09

01 Apr '09

I am proud to announce the second release of a modified ArchLinux install CD that includes spoken output for blind users. It is mostly equivalent to the official "ftp CD", but the system should start speaking as soon as you boot with it. Speech is provided via the sound card, using the eSpeak software synthesizer and the Speakup screenreader. This CD is only available for the i686 platform; x86-64 is not supported. There are two versions: an Isolinux version and a Grub version. One may obtain ".iso" images via HTTP. Grub: Download URL: http://cmb.tysdomain.com/talkingarch-2009.02-ftp-i686.iso MD5 sum: 932d49d5093e50d8c5fb14527afd17fa Isolinux: Download URL: http://cmb.tysdomain.com/talkingarch-2009.02-ftp-i686-isolinux.iso MD5 sum: 28fa806a745e26424596259a71fc9d64 Thanks to Tyler Littlefield for hosting these files. The following list of steps is a brief guide to installing ArchLinux using this CD. If anyone has trouble with it, send me a private email. The instructions assume that your root partition will be mounted on /mnt. 0. When booting, Grub provides a very long timeout. Press enter once the drive stops spinning. 1. Use the installer on the CD, as per the beginner's guide. 2. Install the alsa-utils and espeak packages: pacman --root=/mnt -S alsa-utils espeak 3. Install the speakup and espeakup packages. These are not yet available in the community repository. There are two ways to install them, depending on how much you trust me. Alternative 1: Use the binary packages from my website. I promise that the speakup package will always match the kernel version available from the official ArchLinux repositories. Append the following two lines to /etc/pacman.conf and /mnt/etc/pacman.conf: [blind] Server = http://members.cox.net/cmbrannon/blind/i686 Install the packages from my custom repository: pacman --root=/mnt -Sy speakup espeakup Alternative 2: Build the packages from source, using the PKGBUILDs available from the Arch User Repository. For convenience, the URLs are: http://aur.archlinux.org/download/speakup/speakup.tar.gz http://aur.archlinux.org/download/espeakup/espeakup.tar.gz If I were going to choose this option, I would probably chroot into the newly installed ArchLinux system in order to build the packages. 4. Customize /mnt/etc/rc.conf: Add speakup and speakup_soft to the MODULES array. Add alsa and espeakup to the DAEMONS array. 5. You also need to save the state of the sound card, so that it will be retrieved on reboot. Execute the command "alsactl store" and copy the file /etc/asound.state to /mnt/etc/asound.state. Alternatively, alsactl -f /mnt/etc/asound.state store 6. When you boot the system from the hard disk, it should start speaking. The ArchLinux developers build their CD images using a set of shell scripts and configuration files named archiso. I added a configuration to archiso that allows me to build accessible CDs. If someone wants to produce customized images containing Speakup, he can do the following. Grab sources using git: git clone http://members.cox.net/cmbrannon/archiso.git git checkout --track -b talkinginst origin/talkinginst All of my work is done on the "talkinginst" branch. The master branch mirrors the master branch from git://projects.archlinux.org/archiso.git Now you have a copy in archiso/. Install the scripts contained in archiso/archiso. In order to create the image, pacman needs to be able to find the speakup and espeakup packages. Add my custom [blind] package repository to /etc/pacman.conf on the host system, as described in the instructions for installing from CD. Change to the archiso/configs/talkinginst directory, and type "make ftp-iso". Alternatively, "make BOOTLOADER=syslinux ftp-iso"" yields an image having Isolinux as its bootloader. There are several more targets for "make". For instance, ftp-usb produces an image suitable for a flash drive. Disclaimer: I am in no way associated with ArchLinux. I don't even have Trusted User status in the community. This CD image is not an official release. It is not endorsed by anyone other than myself. It is provided solely for the convenience of its creator and other blind users. It comes with absolutely no warranty. With kind regards, -- Chris

5 5