Dec 112010
 

http://www.daskochrezept.de/rezepte/gefuellte-und-ueberbackene-auberginen-melitzanes-paputsakia_28756.html

http://www.daskochrezept.de/rezepte/israelischer-borschtsch-saft_44424.html

http://www.daskochrezept.de/rezepte/kroatischer-gemuesereis-mit-kaese_85725.html

http://www.daskochrezept.de/rezepte/jaiza-po-russki-russische-eier_1317.html

http://www.daskochrezept.de/rezepte/kwass_65076.html

http://www.daskochrezept.de/rezepte/pilz-kohlrouladen_86884.html

http://www.daskochrezept.de/rezepte/rotes-sauerkraut_88072.html

http://www.daskochrezept.de/rezepte/russische-quarkspeise_20010.html

http://www.daskochrezept.de/rezepte/borschtsch-mit-meerrettichsahne_86037.html

http://www.daskochrezept.de/rezepte/armenisches-omelette-mit-mazun_29.html

http://www.daskochrezept.de/rezepte/boehmische-knoblauchsuppe_11151.html

http://www.russlandjournal.de/rezepte/getraenke/moosbeersaft/

http://www.daskochrezept.de/rezepte/tschech-knoedel_58170.html

http://www.daskochrezept.de/rezepte/scharfe-kaesesuppe_74700.html

http://www.daskochrezept.de/rezepte/schnittlauch-ajvar_84701.html

http://www.daskochrezept.de/rezepte/schopska-bulgarischer-salat_81273.html

http://www.daskochrezept.de/rezepte/wodka-kobieta_107806.html

http://www.daskochrezept.de/rezepte/ajlasan-gemueseeintopf-aus-armenien_105628.html

Nov 092010
 

Many thanks to wishie from #alsa, who wrote most of this file!

# 2008-11-15
#
# This .asoundrc will allow the following:
#
# - upmix stereo files to 5.1 speakers.
# - playback real 5.1 sounds, on 5.1 speakers,
# - allow the playback of both stere(oupmixed) and surround(5.1) sources at the same time.
# - use the 6th and 7th channel (side speakers) as a separate soundcard, i.e. for headphones
#   (This is called the "alternate" output throughout the file, device names prefixed with 'a')
# - play mono sources in stereo (like skype & ekiga) on the alterate output
#
# Make sure you have "8 Channels" and NOT "6 Channels" selected in alsamixer!
#
# Please try the following commands, to make sure everything is working as it should.
#
# To test stereo upmix :      speaker-test -c2 -Ddefault -twav
# To test surround(5.1):      speaker-test -c6 -Dplug:dmix6 -twav
# To test alternative output: speaker-test -c2 -Daduplex -twav
# To test mono upmix:         speaker-test -c1 -Dmonoduplex -twav
#
#
# It may not work out of the box for all cards. If it doesnt work for you, read the comments throughout the file.
# The basis of this file was written by wishie of #alsa, and then modified with info from various sources by 
# squisher.

#Define the soundcard to use
pcm.snd_card {
    type hw
    card 0
    device 0
}

# 8 channel dmix - output whatever audio, to all 8 speakers
pcm.dmix8 {
    type dmix
    ipc_key 1024
    ipc_key_add_uid false
    ipc_perm 0660
    slave {
        pcm "snd_card"
        rate 48000
        channels 8
        period_time 0
        period_size 1024
        buffer_time 0
        buffer_size 5120
    }

# Some cards, like the "nforce" variants require the following to be uncommented. It routes the audio to t he correct speakers.
    bindings {
        0 0
        1 1
        2 4
        3 5
        4 2
        5 3
        6 6
        7 7
    }
}

# upmixing - duplicate stereo data to all 6 channels
pcm.ch51dup {
    type route
    slave.pcm dmix8
    slave.channels 8
    ttable.0.0 1
    ttable.1.1 1
    ttable.0.2 1
    ttable.1.3 1
    ttable.0.4 0.5
    ttable.1.4 0.5
    ttable.0.5 0.5
    ttable.1.5 0.5
}

# this creates a six channel soundcard
# and outputs to the eight channel one
# i.e. for usage in mplayer I had to define in ~/.mplayer/config:
#   ao=alsa:device=dmix6
#   channels=6
pcm.dmix6 {
    type route
    slave.pcm dmix8
    slave.channels 8
    ttable.0.0 1
    ttable.1.1 1
    ttable.2.2 1
    ttable.3.3 1
    ttable.4.4 1
    ttable.5.5 1
}

# share the microphone, i.e. because virtualbox grabs it by default
pcm.microphone {
    type dsnoop
    ipc_key 1027
    slave {
        pcm "snd_card"
    }
}

# rate conversion, needed i.e. for wine
pcm.2chplug {
    type plug
    slave.pcm "ch51dup"
}
pcm.a2chplug {
    type plug
    slave.pcm "dmix8"
}

# routes the channel for the alternative
# 2 channel output, which becomes the 7th and 8th channel 
# on the real soundcard
pcm.alt2ch {
    type route
    slave.pcm "a2chplug"
    slave.channels 8
    ttable.0.6    1
    ttable.1.7    1
}

# skype and ekiga are only mono, so route left channel to the right channel
# note: this gets routed to the alternative 2 channels
pcm.mono_playback {
    type route
    slave.pcm "a2chplug"
    slave.channels 8
    # Send Skype channel 0 to the L and R speakers at full volume
    ttable.0.6    1
    ttable.0.7    1
}

# 'full-duplex' device for use with aoss
pcm.duplex {
    type asym
    playback.pcm "2chplug"
    capture.pcm "microphone"
}

pcm.aduplex {
    type asym
    playback.pcm "alt2ch"
    capture.pcm "microphone"
}

pcm.monoduplex {
    type asym
    playback.pcm "mono_playback"
    capture.pcm "microphone"
}

# for aoss
pcm.dsp0 "duplex"
ctl.mixer0 "duplex"

# softvol manages volume in alsa
# i.e. wine likes this
pcm.mainvol {
    type softvol
    slave.pcm "duplex"
    control {
        name "2ch-Upmix Master"
        card 0
    }
}

#pcm.!default "mainvol"

# set the default device according to the environment
# variable ALSA_DEFAULT_PCM and default to mainvol
pcm.!default {
    @func refer
    name { @func concat 
           strings [ "pcm."
                     { @func getenv
                       vars [ ALSA_DEFAULT_PCM ]
                       default "mainvol"
                     }
           ]
         }
}

# uncomment the following if you want to be able to control
# the mixer device through environment variables as well
#ctl.!default {
#    @func refer
#    name { @func concat 
#           strings [ "ctl."
#                     { @func getenv
#                       vars [ ALSA_DEFAULT_CTL
#                              ALSA_DEFAULT_PCM
#                       ]
#                       default "duplex"
#                     }
#           ]
#         }
#}

Wine

wine unfortunately dosen’t seem to try to open the default device, but the following snippet inserted into your ~/.wine/user.reg will do the trick:

[Software\Wine\Alsa Driver]
"AutoScanCards"="N"
"DeviceCount"="1"
"DeviceCTL1"="default"
"DevicePCM1"="default"
"UseDirectHW"="N"

Older Version

This version doesn’t setup the side speakers as a second soundcard.

# upmix.and.dmix.intel8x0 begins ###
#This asoundrc is for snd_intel8x0 based cards.
#It will allow the following:
#
# upmix stereo files to 5.1 speakers.
# playback real 5.1 sounds, on 5.1 speakers,
# allow the playback of both stere(upmixed) and surround(5.1) sources at the same time.
# upmix mono sound from skype
#
#
#Please try the following commands, to make sure everything is working as it should.
#
# To test stereo upmix : speaker-test -c2 -Ddefault -twav
# To test surround(5.1): speaker-test -c6 -Dplug:dmix6 -twav
#
#
#It may not work out of the box for all cards. If it doesnt work for you, read the comments throughout the file.
#If it still doesnt work with your setup, please speak to me (wishie) in #alsa on irc.freenode.net

#Define the soundcard to use
pcm.snd_card {
    type hw
    card 0
    device 0
}

# 6 channel dmix - output whatever audio, to all 6 speakers
pcm.dmix6 {
    type dmix
    ipc_key 1024
    ipc_key_add_uid false
    ipc_perm 0660
    slave {
        pcm "snd_card"
        #rate 48000
        channels 6
        period_time 0
        period_size 1024
        buffer_time 0
        buffer_size 4096
    }

# Some cards, like the "nforce" variants require the following to be uncommented. It routes the audio to t he correct speakers.
    bindings {
        0 0
        1 1
        2 4
        3 5
        4 2
        5 3
    }
}

# upmixing - duplicate stereo data to all 6 channels
pcm.ch51dup {
    type route
    slave.pcm dmix6
    slave.channels 6
    ttable.0.0 1
    ttable.1.1 1
    ttable.0.2 1
    ttable.1.3 1
    ttable.0.4 0.5
    ttable.1.4 0.5
    ttable.0.5 0.5
    ttable.1.5 0.5
}

# rate conversion, needed i.e. for wine
pcm.2chplug {
    type plug
    slave.pcm "ch51dup"
}

# 'full-duplex' device for use with aoss
pcm.duplex {
    type asym
    playback.pcm "2chplug"
    capture.pcm "hw:0"
}

# change default device:
pcm.!default {
    type softvol
    slave.pcm "duplex"
    control {
        name "2ch Master"
        card 0
    }
}

# for aoss
pcm.dsp0 "duplex"
ctl.mixer0 "duplex"

#pcm.default:0 "default"

# upmix.and.dmix.intel8x0 ends ###

# skype is only mono, so route left channel to the right channel
pcm.skype_playback {
    type route
    slave.pcm "2chplug"
    slave.channels 2
    # Send Skype channel 0 to the L and R speakers at full volume
    ttable.0.0    1
    ttable.0.1    1
}

Resources

Other Sites with .asoundrc Examples

Aug 142010
 

Note: This program is only for the current grub version (1.98+), and does not work with grub-legacy (0.xx). Older grub-choose-default versions work with grub-legacy, see GrubChooseDefaultLegacy.

Control Grub Default through a GUI

Do you have a dual boot system? Isn’t it annoying when you want to reboot from Linux into Windows or vice-versa, and you have to wait for the machine to shut down, the BIOS to initialize just so that you can now select the OS that you want to boot into?

grub-choose-default gives you a GUI that you can use to easily select the next default for grub and you can go and grab a snack while your computer reboots without having to wait for anything.

It’s a very simple program that just reads your grub menu entries and then lets you click on the one you want to be the next default.

How It Works

Since grub2 reached version 1.98, setting the default boot entry through the “grub environment” is supported. From Linux, the grub-set-default command is available again, just as before with grub-legacy. Under Windows grub’s code is used to edit the environment directly.

Cross Platform

grub-choose-default is available both for Linux and Windows. It should also work on other Unices, but has not been tested (user reports are welcome).

Under Linux it reads /boot/grub/grub.cfg and sets your choice using grub-set-default.

Under Windows you need to get access to your Linux /boot. If you are running ext2/3, then you can use Ext2IFS, which gives you access to your ext2/3 partitions as regular drives under Windows. Although this software doesn’t work perfectly under Windows 7, there are usable workarounds. See README.win32 in the sources, or read the introductory text of the installer for further information. Grub-set-default currently needs direct file access and thus does not work with /boot on reiserfs or other filesystems (unless someone can point me to a similar FS driver as Ext2IFS).

Then grub-choose-default searches all your drives for boot/grub/grub.cfg or a grub/grub.cfg. The grub directory can be specified in the configuration file, which is located in the Profile folder’s “Application Data” subdirectory grub-choose-default. Add the line ”grub_dir=D:\grub” to the end of the file, and remember to escape backslashes.

Ending the Session

Most of the time you will want to reboot after setting the new grub entry. How to end a session is specific to the desktop environment in Linux, and in the reboot/ directory are example scripts of how to end a session. The user can install the script of his choice in $XDG_CONFIG_DIR/grub-choose-default/reboot.

Prerequisites

  • GTK 2.16+
  • GIO (on Windows)
  • Python (for building from source)

Older Versions

The page for the old version of grub-choose-default, which is compatible with grub 0.xx, can be found at GrubChooseDefaultLegacy.

Screenshot

License

grub-choose-default is released under the GNU GPL v2. The NSIS installer script is using GNU GPL v3, and the waf scripts the EXPAT license.

The development version can be found at http://github.com/squisher/grub-choose-default .

Ubuntu packages for karmic are at https://launchpad.net/~bugs-da/+archive/grub-choose-default/

  • 2010-08-14 – Version 1.0
    Support to set default for next reboot only. Allow workaround for Windows 7.

Contact

Comments, bug reports, etc. are very welcome. Please look for my email address in the included README file.

Jun 302010
 
May 282010
 

Maybe it’s useful anecdotal reference:
I started rock climbing in the gym, and loved it. The first day I climbed until I couldn’t hold on to the wall any more. I started with top-roping, but also bouldered immediately. I was able to do a V0, but a V1 just evaded me. A couple of days later I had my membership, bought the equipment (I didn’t even wait to consult with my friends on what to buy). I climbed so much that I almost couldn’t sign “in” on my way out.

I’d say about 3 months later I was climbing 5.10s with relative ease. I was advancing very fast according to what I heard from others. I hardly got sore any more, but the joints in my fingers were feeling funny, and hurting a bit if I squeezed them from the side. I had heard that muscles adapt very quickly, but the cartilage takes much longer to grow stronger. I never was in pain, but I was always aware of my joints when I came down from a route.

So I decided to take a step back. I took a week break, but that didn’t change much. So I stopped climbing 5.10s and started to go back to 8s and 9s. I would climb very carefully to improve my technique, or simply climb two in a row. I don’t remember exactly how long I stuck to the schedule, but it was something between 2-4 weeks. It never improved much, but also never got worse, so I decided to go back to climbing harder routes. Then a month later I went on vacation, and took a 3 week break. Again it didn’t seem to relieve the tension I felt in my joints, but I didn’t care that much any more. I would monitor it, but I felt I had been giving it enough time.

In retrospect I don’t remember when exactly it went away. I certainly don’t feel it today any more. I still feel like there was a good chance of me getting injured if I had kept on climbing without the breaks or taking it slower but I have no way of knowing for sure.

Links

May 092010
 

1. Install Mingw.
1. Install Python/Msys (depending on waf or autotools as the toolchain). We assume waf but the procedure should be similar for autotools.
1. Download the gtk all-in-one bundle, and extract it into C:gtk
1. Setup $PATH to include python and the gtkbin directory
1. Happyness ensues

Apr 182010
 

Note: This program is only for grub-legacy (0.9x). Current grub versions, 1.98+, are supported by more recent grub-choose-default versions, see GrubChooseDefault.

Do you have a dual boot system? Isn’t it annoying when you want to reboot from Linux into Windows or vice-versa, and you have to wait for the machine to shut down, BIOS to initialize just so that you can now select the OS that you want to boot into?

grub-choose-default gives you a GUI that you can use to easily select the next default for grub and you can go and grab a snack while your computer reboots without having to wait for anything.

It’s a very simple program that just reads your grub menu entries and then lets you click on the one you want to be the next default.

In grub’s menu.lst file you need to specify default saved, so that grub consults the file default in the grub directory to see which entry it should boot. That file is then modified by grub-choose-default

grub-choose-default is written in Python (which is required to be installed at the moment) and works under Linux and Windows.

Under Linux it reads /boot/grub/menu.lst and writes your choice to /boot/grub/default

Under Windows you need to get access to your Linux /boot. If you are running ext2/3, then you can use Ext2IFS, which gives you access to your ext2/3 partitions as regular drives under Windows. grub-set-default currently needs this and thus does not work with /boot on reiserfs or other filesystems (unless someone can point me to a similar FS driver as for Ext2IFS).
Then grub-choose-default searches all your drives for a grub/menu.lst or a boot/grub/menu.lst. There currently is no way to specify manually where menu.lst resides, please let me know if this is needed.

Introduced in version 0.2 is the ability to reboot right after the new grub default has been set. Under Linux there are many different ways to start the logging off procedure — dependent on the desktop environment that you are using. For that reason (and since any program ran through sudo won’t be able to interact with the desktop environment of the regular user), the reboot is handled by a wrapper script. See the reboot/ subdirectory for supplied scripts. At the moment only scripts for xfce4 and gnome have been included, but it shouldn’t be very hard to adjust them to your current desktop environment. If you do so, please email me your script, and I’ll include it in the next release.

  • Python
  • Python Tk module (included by default under Windows, for Linux might be an extra package (i.e. python-tk for Debian)
  • Windows: Access to /boot as regular files (see above)

grub-choose-default is released under the GNU GPL v2

  • 2008-05-29 – Version 0.3Applying patches from Kjell Braden to fix minor crashes and to add a man page.
  • 2007-08-06 – Version 0.2Addition of reboot feature, checking menu.lst for correct default saved settings.
  • 2007-01-18 – Version 0.1First public release, please check for bugs!

Comments, bug reports, etc. are very welcome. Please look for my email address in the included README file.

Feb 042010
 

Two small utilities for use with old-school dual head setups: namely not
twinview / one big desktop, but rather two X screens. See gentoo wiki for some setup help.

I use this setup because the wrapping the mouse is very smooth, it is very useful to have the logical separation of both screens and now I can easily switch focus and mouse between them just by using the keyboard. Additionally, when I play some nice games in wine, I can lock the mouse into each individual screen, and by need be switch by using the keyboard shortcut.

You xorg.conf needs to contain something similar to:

Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          0 "Screen 0" 3000 0
        Screen          1 "Screen 1" 0 0 #leftOf "Screen 0"
EndSection

for these utilities to work.

mouse-switchscreen

Change the mouse cursor from one screen to the other. Remembers the previous
mouse position for each screen.

The previous mouse-switchscreen has been renamed to mouse-wrapscreen (see below), since the name was confusing.

mouse-wrapscreen

If you have an xorg.conf where both X screens are “separated” on the X
coordinates, then the mouse cursor cannot cross. Which is sometimes desired,
and sometimes not. Using mouse-wrapscreen you can configure them to be
“uncrossable”, and then run it in the background when you do want to be able
to cross the cursor.

Warning (2010-02-04): Mouse-wrapscreen seems to lock up the X server after a recent upgrade on my system. The symptom is that the cursor will just jump back and forth between screens, preventing any other interaction between the user and the X server. The reason is unknown, probably mouse-wrapscreen is triggering a bug in X. If you have any further information or ideas, please contact the author.

”Note: Both use XWarpCursor, which was necessary with xorg 7.4. I haven’t tried
it on older versions of xorg.”

Both tools are based on a program by David Antliff. See the header of the
respective .c files for a brief changelog.

Releases

  • 0.5 (2009-05-17)
    Update for xorg 7.4 and integrate “switchscreen” (prev. homepage is defunct)

http://dsp.mcbf.net/releases/dualscreen-mouse-utils-0.5.tar.gz

Related work

There is switchscreen out there by Sampo Niskanen, however it does not seem to remember the mouse position for each screen.