miboot on a 6400
sadfsdf
yellowdog-general@lists.terrasoftsolutions.com
Fri, 30 Jul 2004 13:07:48 -0500
This is a multi-part message in MIME format.
--------------040108060005010705040201
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
I've been looking for that version all over the place, where can I
find it?
Daniel Gimpelevich wrote:
You have not told us which version of miBoot you are using (and saying 1.0a3
means nothing; they're all 1.0a3). Where did you get this miBoot? Is it the
version that comes with YDL? That version does not use boot.conf at all. The
only version that does is the binary-only version that came with LinuxPPC
2000. All other versions must be configured using a resource editor such as
ResEdit.
-- "No gnu's is good gnu's." --Gary Gnu, "The Great Space Coaster"
>> From: sadfsdf <ydl@augustmail.com>
>> Reply-To: yellowdog-general@lists.terrasoftsolutions.com
>> Newsgroups: gmane.linux.yellowdog.general
>> Date: Fri, 30 Jul 2004 11:12:37 -0500
>> Subject: Re: miboot on a 6400
>>
>> Currently im getting a tux with a red X on there. Ive been reading your
>> guide from april of last year
>> (http://lists.terrasoftsolutions.com/pipermail/yellowdog-general/2003-April/00
>> 6938.html)
>> but nothing seems to work, I press space and nothing happens I press tab
>> still nothing happens, i do command+alt+shift+del and I get miboot
>> saying "open error -43"
>>
>>
>> Alexander Holst wrote:
>>
>
>
>>>>>> Message: 10
>>>>>> Date: Fri, 30 Jul 2004 09:14:48 +0300
>>>>>> Subject: Re: miboot on a 6400
>>>>>> From: nathan <nathan@incirlik.net>
>>>>>> To: "yellowdog general lists.terrasoftsolutions.com"
>>>>>> <yellowdog-general@lists.terrasoftsolutions.com>
>>>>>> Reply-To: yellowdog-general@lists.terrasoftsolutions.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> AFAIK, miBoot is really hard to get to work on the PPC/Performa
>>>>>> machines.
>>>
>>>
>>>>
>>>>
>>>> Not really ;) - All my OldWorld Macs (5 in total) boot through it,
>>>> even my beige G3 and my Performa 5200 :)
>>>>
>>
>>
>>>>>> Why not get a copy of BootX 1.2.x. In my experience it's the easiest to
>>>>>> setup and use on the oldworld machines...
>>>
>>>
>>>>
>>>>
>>>> Some people like their machines to be Mac OS free to save some disk
>>>> space and to avoid licence issues ;)
>>>>
>>>> Hi sadfsdf,
>>>>
>>
>>
>>>>>> My directory tree for the miboot partition is like this
>>>>>> |-- System Folder (note: Mac OS has blessed the folder)
>>>>>> | |-- Finder
>>>>>> | |-- System
>>>>>> | |-- boot.conf
>>>>>> |-- Linux Kernels
>>>>>> | |-- vmlinux-2.4.22-2f
>>>>>> | |-- vmlinux-2.24.22-2fBOOT
>>>>>> |-- ramdisk.image.gz
>>>>>> |-- boot.conf
>>>
>>>
>>>>
>>>>
>>>> You have _two_ boot.conf files! Use one or the other - I assume miboot
>>>> gets confused which one to use. I usually erase the one in the System
>>>> Folder and use one at the root level of the HFS partition. It is
>>>> easier to manage from the Linux side then, as you avoid the space in
>>>> the "System Folder" in its path, which can cause some problems when
>>>> using the command line.
>>>>
>>
>>
>>>>>> My boot.conf is thus:
>>>>>>
>>>>>> init-message = "\n Welcome to YDL!\Press <TAB> for boot options.\n\n"
>>>>>> timeout = 50
>>>>>>
>>>>>> default = bootYDL
>>>>>>
>>>>>> image = vmlinux-2.4.22-2f
>>>>>> label = bootYDL
>>>>>> root = /dev/hda6
>>>>>> append = "video=valkyriefb3:vmode:14,cmode:8"
>>>>>>
>>>>>> image = vmlinux-2.4.22-2fBOOT
>>>>>> label = install_YDL
>>>>>> initrd = ramdisk.image.gz
>>>>>> initrd-size=16384
>>>>>> root = /dev/ram0
>>>>>> append = "video=valkyriefb3:vmode:14,cmode:8 text"
>>>
>>>
>>>>
>>>>
>>>> Have you tried without any append = "video=..." line? It should work
>>>> without that line. It will usually use 640x480 then, or the settings
>>>> which have been left in the PRAM from the last time you had booted
>>>> into Mac OS. 640x480 is enough to run the installer, after that you
>>>> can try several commands (fbset, nvvideo | read the man pages of those
>>>> two) to tweak video settings and find out about your graphics chip by
>>>> consulting /var/log/dmesg. Also, as already pointed out by another
>>>> poster, the video line should only read valkyriefb and not
>>>> valkyriefb3, in case the machine does have a valkyrie chipset.
>>>>
>>>> Do you get a boot-screen with a landscape and TUX? If so, at least
>>>> some part of miboot has loaded successfully. Increase the "timeout =
>>>> 50" to "timeout = 100" so you'll have 10 secs of boot delay. This
>>>> should suffice in most cases to get the monitor warmed up and to
>>>> display the initial boot screen. Hitting the space bar during that
>>>> first boot scree will get you into a boot menue.
>>>>
>>>> Your problem might also be, that miboot ignores the "default =
>>>> bootYDL" line and will always boot the first set of entries in
>>>> boot.conf after the timeout, which in your case would be the attempt
>>>> to boot an installation that isn't there as of yet (or did you
>>>> allready get YDL installed). From within the boot menue, you will be
>>>> able to choose from your presets in boot.conf and customly add append
>>>> parameters. After installation, put your preferred set of parameters
>>>> as the first set into boot.conf, then automatic boot will start after
>>>> the timeout period.
>>>>
>>>> Also, "root = /dev/hda6" seems a too early partition to hold a linux
>>>> fs to me, as I assume you also have your mibbot partition on the same
>>>> drive. A typical Mac partitioned drive looks as follows:
>>>>
>>>> Partition map (with 512 byte blocks) on '/dev/sda'
>>>> #: type name length base ( size )
>>>> 1: Apple_partition_map Apple 63 @ 1
>>>> 2: Apple_Driver43*Macintosh 54 @ 64
>>>> 3: Apple_Driver43*Macintosh 74 @ 118
>>>> 4: Apple_Driver_IOKit Macintosh 512 @ 192
>>>> 5: Apple_Patches Patch Partition 512 @ 704
>>>> 6: Apple_HFS "Boot_Linux" 204800 @ 1216 (100.0M)
>>>> 7: Apple_UNIX_SVR2 swap 524288 @ 206016 (256.0M)
>>>> 8: Apple_UNIX_SVR2 backup 3448560 @ 730304 ( 1.6G)
>>>> 9: Apple_Free Extra 10 @ 4178864
>>>>
>>>> The the earliest partition, in my above example, to hold a Linux fs
>>>> would be partition 7 and onwards. The root=... line specifies the
>>>> partition which holds the file system that is mounted on / under
>>>> Linux, _not_ the partition that holds the miboot loader. My example
>>>> shows a drive that I only use to boot, hold my secondary swap space
>>>> and a backup partition, as my Linux installation is on an IDE drive
>>>> attached to an IDE controller (Promise Ultra 100 TX2), that is only
>>>> visible to the Linux kernel, but not to the Mac (a PM 7500/100)
>>>> itself. So I am forced to use a SCSI disk to hold my miboot partition.
>>>>
>>>> I hope that helps and "un-hardens" the use of miboot on a PPC/Performa.
>>>>
>>>> BTW, the Performa 6400 is a PCI machine, isn't it? If it is still a
>>>> NuBus architecture machine, you need a different kernel. The kernels
>>>> supplied on the YDL CDs won't work on a NuBus type machine. In that
>>>> case, go to http://nubus-pmac.sf.net to get a kernel. You won't be
>>>> able to follow the "normal" installation procedure though. Feel free
>>>> to contact me in that case. I managed to get YDL-3.0 installed on my
>>>> Performa 5200 from scratch. It needs some tricks though.
>>>>
>>>>
>>>> Greetings,
>>>> Alex
>>>>
>>>>
>>>>
>>>> Alexander Holst
>>>> Pforzheim University of Applied Sciences
>>>> <holst [at] fh-pforzheim [dot] de>
>>>> ph: +49 [0]7231 28-6837
>>>> fx: +49 [0]7231 28-6040
>>>>
>>>>
>>
>>
>>
>> _______________________________________________
>> yellowdog-general mailing list
>> yellowdog-general@lists.terrasoftsolutions.com
>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>> HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
>>
>
>
_______________________________________________
yellowdog-general mailing list
yellowdog-general@lists.terrasoftsolutions.com
http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
--------------040108060005010705040201
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-html" lang="x-western"> I've been looking for that
version all over the place, where can I find
it?<br>
<br>
Daniel Gimpelevich wrote:<br>
<div class="moz-text-plain" wrap="true" graphical-quote="true"
style="font-family: -moz-fixed; font-size: 13px;" lang="x-western">
<pre wrap="">You have not told us which version of miBoot you are using (and saying 1.0a3
means nothing; they're all 1.0a3). Where did you get this miBoot? Is it the
version that comes with YDL? That version does not use boot.conf at all. The
only version that does is the binary-only version that came with LinuxPPC
2000. All other versions must be configured using a resource editor such as
ResEdit.
<div class="moz-txt-sig">--
"No gnu's is good gnu's." --Gary Gnu, "The Great Space Coaster"
</div></pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> </span>From: sadfsdf <<a
class="moz-txt-link-abbreviated" href="mailto:ydl@augustmail.com">ydl@augustmail.com</a>>
<span class="moz-txt-citetags">> </span>Reply-To: <a
class="moz-txt-link-abbreviated"
href="mailto:yellowdog-general@lists.terrasoftsolutions.com">yellowdog-general@lists.terrasoftsolutions.com</a>
<span class="moz-txt-citetags">> </span>Newsgroups: gmane.linux.yellowdog.general
<span class="moz-txt-citetags">> </span>Date: Fri, 30 Jul 2004 11:12:37 -0500
<span class="moz-txt-citetags">> </span>Subject: Re: miboot on a 6400
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>Currently im getting a tux with a red X on there. Ive been reading your
<span class="moz-txt-citetags">> </span>guide from april of last year
<span class="moz-txt-citetags">> </span>(<a
class="moz-txt-link-freetext"
href="http://lists.terrasoftsolutions.com/pipermail/yellowdog-general/2003-April/00">http://lists.terrasoftsolutions.com/pipermail/yellowdog-general/2003-April/00</a>
<span class="moz-txt-citetags">> </span>6938.html)
<span class="moz-txt-citetags">> </span>but nothing seems to work, I press space and nothing happens I press tab
<span class="moz-txt-citetags">> </span>still nothing happens, i do command+alt+shift+del and I get miboot
<span class="moz-txt-citetags">> </span>saying "open error -43"
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>Alexander Holst wrote:
<span class="moz-txt-citetags">> </span>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>>> </span>Message: 10
<span class="moz-txt-citetags">>>> </span>Date: Fri, 30 Jul 2004 09:14:48 +0300
<span class="moz-txt-citetags">>>> </span>Subject: Re: miboot on a 6400
<span class="moz-txt-citetags">>>> </span>From: nathan <<a
class="moz-txt-link-abbreviated" href="mailto:nathan@incirlik.net">nathan@incirlik.net</a>>
<span class="moz-txt-citetags">>>> </span>To: "yellowdog general lists.terrasoftsolutions.com"
<span class="moz-txt-citetags">>>> </span><<a
class="moz-txt-link-abbreviated"
href="mailto:yellowdog-general@lists.terrasoftsolutions.com">yellowdog-general@lists.terrasoftsolutions.com</a>>
<span class="moz-txt-citetags">>>> </span>Reply-To: <a
class="moz-txt-link-abbreviated"
href="mailto:yellowdog-general@lists.terrasoftsolutions.com">yellowdog-general@lists.terrasoftsolutions.com</a>
<span class="moz-txt-citetags">>>> </span>
<span class="moz-txt-citetags">>>> </span>
<span class="moz-txt-citetags">>>> </span>
<span class="moz-txt-citetags">>>> </span>AFAIK, miBoot is really hard to get to work on the PPC/Performa
<span class="moz-txt-citetags">>>> </span>machines.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Not really <span
class="moz-smiley-s3"><span> ;) </span></span> - All my OldWorld Macs (5 in total) boot through it,
<span class="moz-txt-citetags">>> </span>even my beige G3 and my Performa 5200 <span
class="moz-smiley-s1"><span> :) </span></span>
<span class="moz-txt-citetags">>> </span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>>> </span>Why not get a copy of BootX 1.2.x. In my experience it's the easiest to
<span class="moz-txt-citetags">>>> </span>setup and use on the oldworld machines...
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Some people like their machines to be Mac OS free to save some disk
<span class="moz-txt-citetags">>> </span>space and to avoid licence issues <span
class="moz-smiley-s3"><span> ;) </span></span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Hi sadfsdf,
<span class="moz-txt-citetags">>> </span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>>> </span>My directory tree for the miboot partition is like this
<span class="moz-txt-citetags">>>> </span>|-- System Folder (note: Mac OS has blessed the folder)
<span class="moz-txt-citetags">>>> </span>| |-- Finder
<span class="moz-txt-citetags">>>> </span>| |-- System
<span class="moz-txt-citetags">>>> </span>| |-- boot.conf
<span class="moz-txt-citetags">>>> </span>|-- Linux Kernels
<span class="moz-txt-citetags">>>> </span>| |-- vmlinux-2.4.22-2f
<span class="moz-txt-citetags">>>> </span>| |-- vmlinux-2.24.22-2fBOOT
<span class="moz-txt-citetags">>>> </span>|-- ramdisk.image.gz
<span class="moz-txt-citetags">>>> </span>|-- boot.conf
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>You have <span
class="moz-txt-underscore"><span class="moz-txt-tag">_</span>two<span
class="moz-txt-tag">_</span></span> boot.conf files! Use one or the other - I assume miboot
<span class="moz-txt-citetags">>> </span>gets confused which one to use. I usually erase the one in the System
<span class="moz-txt-citetags">>> </span>Folder and use one at the root level of the HFS partition. It is
<span class="moz-txt-citetags">>> </span>easier to manage from the Linux side then, as you avoid the space in
<span class="moz-txt-citetags">>> </span>the "System Folder" in its path, which can cause some problems when
<span class="moz-txt-citetags">>> </span>using the command line.
<span class="moz-txt-citetags">>> </span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>>> </span>My boot.conf is thus:
<span class="moz-txt-citetags">>>> </span>
<span class="moz-txt-citetags">>>> </span>init-message = "\n Welcome to YDL!\Press <TAB> for boot options.\n\n"
<span class="moz-txt-citetags">>>> </span>timeout = 50
<span class="moz-txt-citetags">>>> </span>
<span class="moz-txt-citetags">>>> </span>default = bootYDL
<span class="moz-txt-citetags">>>> </span>
<span class="moz-txt-citetags">>>> </span>image = vmlinux-2.4.22-2f
<span class="moz-txt-citetags">>>> </span>label = bootYDL
<span class="moz-txt-citetags">>>> </span>root = /dev/hda6
<span class="moz-txt-citetags">>>> </span>append = "video=valkyriefb3:vmode:14,cmode:8"
<span class="moz-txt-citetags">>>> </span>
<span class="moz-txt-citetags">>>> </span>image = vmlinux-2.4.22-2fBOOT
<span class="moz-txt-citetags">>>> </span>label = install_YDL
<span class="moz-txt-citetags">>>> </span>initrd = ramdisk.image.gz
<span class="moz-txt-citetags">>>> </span>initrd-size=16384
<span class="moz-txt-citetags">>>> </span>root = /dev/ram0
<span class="moz-txt-citetags">>>> </span>append = "video=valkyriefb3:vmode:14,cmode:8 text"
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Have you tried without any append = "video=..." line? It should work
<span class="moz-txt-citetags">>> </span>without that line. It will usually use 640x480 then, or the settings
<span class="moz-txt-citetags">>> </span>which have been left in the PRAM from the last time you had booted
<span class="moz-txt-citetags">>> </span>into Mac OS. 640x480 is enough to run the installer, after that you
<span class="moz-txt-citetags">>> </span>can try several commands (fbset, nvvideo | read the man pages of those
<span class="moz-txt-citetags">>> </span>two) to tweak video settings and find out about your graphics chip by
<span class="moz-txt-citetags">>> </span>consulting /var/log/dmesg. Also, as already pointed out by another
<span class="moz-txt-citetags">>> </span>poster, the video line should only read valkyriefb and not
<span class="moz-txt-citetags">>> </span>valkyriefb3, in case the machine does have a valkyrie chipset.
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Do you get a boot-screen with a landscape and TUX? If so, at least
<span class="moz-txt-citetags">>> </span>some part of miboot has loaded successfully. Increase the "timeout =
<span class="moz-txt-citetags">>> </span>50" to "timeout = 100" so you'll have 10 secs of boot delay. This
<span class="moz-txt-citetags">>> </span>should suffice in most cases to get the monitor warmed up and to
<span class="moz-txt-citetags">>> </span>display the initial boot screen. Hitting the space bar during that
<span class="moz-txt-citetags">>> </span>first boot scree will get you into a boot menue.
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Your problem might also be, that miboot ignores the "default =
<span class="moz-txt-citetags">>> </span>bootYDL" line and will always boot the first set of entries in
<span class="moz-txt-citetags">>> </span>boot.conf after the timeout, which in your case would be the attempt
<span class="moz-txt-citetags">>> </span>to boot an installation that isn't there as of yet (or did you
<span class="moz-txt-citetags">>> </span>allready get YDL installed). From within the boot menue, you will be
<span class="moz-txt-citetags">>> </span>able to choose from your presets in boot.conf and customly add append
<span class="moz-txt-citetags">>> </span>parameters. After installation, put your preferred set of parameters
<span class="moz-txt-citetags">>> </span>as the first set into boot.conf, then automatic boot will start after
<span class="moz-txt-citetags">>> </span>the timeout period.
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Also, "root = /dev/hda6" seems a too early partition to hold a linux
<span class="moz-txt-citetags">>> </span>fs to me, as I assume you also have your mibbot partition on the same
<span class="moz-txt-citetags">>> </span>drive. A typical Mac partitioned drive looks as follows:
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Partition map (with 512 byte blocks) on '/dev/sda'
<span class="moz-txt-citetags">>> </span>#: type name length base ( size )
<span class="moz-txt-citetags">>> </span>1: Apple_partition_map Apple 63 @ 1
<span class="moz-txt-citetags">>> </span>2: Apple_Driver43*Macintosh 54 @ 64
<span class="moz-txt-citetags">>> </span>3: Apple_Driver43*Macintosh 74 @ 118
<span class="moz-txt-citetags">>> </span>4: Apple_Driver_IOKit Macintosh 512 @ 192
<span class="moz-txt-citetags">>> </span>5: Apple_Patches Patch Partition 512 @ 704
<span class="moz-txt-citetags">>> </span>6: Apple_HFS "Boot_Linux" 204800 @ 1216 (100.0M)
<span class="moz-txt-citetags">>> </span>7: Apple_UNIX_SVR2 swap 524288 @ 206016 (256.0M)
<span class="moz-txt-citetags">>> </span>8: Apple_UNIX_SVR2 backup 3448560 @ 730304 ( 1.6G)
<span class="moz-txt-citetags">>> </span>9: Apple_Free Extra 10 @ 4178864
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>The the earliest partition, in my above example, to hold a Linux fs
<span class="moz-txt-citetags">>> </span>would be partition 7 and onwards. The root=... line specifies the
<span class="moz-txt-citetags">>> </span>partition which holds the file system that is mounted on / under
<span class="moz-txt-citetags">>> </span>Linux, <span
class="moz-txt-underscore"><span class="moz-txt-tag">_</span>not<span
class="moz-txt-tag">_</span></span> the partition that holds the miboot loader. My example
<span class="moz-txt-citetags">>> </span>shows a drive that I only use to boot, hold my secondary swap space
<span class="moz-txt-citetags">>> </span>and a backup partition, as my Linux installation is on an IDE drive
<span class="moz-txt-citetags">>> </span>attached to an IDE controller (Promise Ultra 100 TX2), that is only
<span class="moz-txt-citetags">>> </span>visible to the Linux kernel, but not to the Mac (a PM 7500/100)
<span class="moz-txt-citetags">>> </span>itself. So I am forced to use a SCSI disk to hold my miboot partition.
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>I hope that helps and "un-hardens" the use of miboot on a PPC/Performa.
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>BTW, the Performa 6400 is a PCI machine, isn't it? If it is still a
<span class="moz-txt-citetags">>> </span>NuBus architecture machine, you need a different kernel. The kernels
<span class="moz-txt-citetags">>> </span>supplied on the YDL CDs won't work on a NuBus type machine. In that
<span class="moz-txt-citetags">>> </span>case, go to <a
class="moz-txt-link-freetext" href="http://nubus-pmac.sf.net">http://nubus-pmac.sf.net</a> to get a kernel. You won't be
<span class="moz-txt-citetags">>> </span>able to follow the "normal" installation procedure though. Feel free
<span class="moz-txt-citetags">>> </span>to contact me in that case. I managed to get YDL-3.0 installed on my
<span class="moz-txt-citetags">>> </span>Performa 5200 from scratch. It needs some tricks though.
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Greetings,
<span class="moz-txt-citetags">>> </span>Alex
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>Alexander Holst
<span class="moz-txt-citetags">>> </span>Pforzheim University of Applied Sciences
<span class="moz-txt-citetags">>> </span><holst [at] fh-pforzheim [dot] de>
<span class="moz-txt-citetags">>> </span>ph: +49 [0]7231 28-6837
<span class="moz-txt-citetags">>> </span>fx: +49 [0]7231 28-6040
<span class="moz-txt-citetags">>> </span>
<span class="moz-txt-citetags">>> </span>
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>_______________________________________________
<span class="moz-txt-citetags">> </span>yellowdog-general mailing list
<span class="moz-txt-citetags">> </span><a
class="moz-txt-link-abbreviated"
href="mailto:yellowdog-general@lists.terrasoftsolutions.com">yellowdog-general@lists.terrasoftsolutions.com</a>
<span class="moz-txt-citetags">> </span><a
class="moz-txt-link-freetext"
href="http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general">http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general</a>
<span class="moz-txt-citetags">> </span>HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
<span class="moz-txt-citetags">> </span>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
yellowdog-general mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:yellowdog-general@lists.terrasoftsolutions.com">yellowdog-general@lists.terrasoftsolutions.com</a>
<a class="moz-txt-link-freetext"
href="http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general">http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general</a>
HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
</pre>
</div>
<br>
</div>
</body>
</html>
--------------040108060005010705040201--