installing Debian on Cobalt Qube 2

[Sameer Verma]

This is a question about Qube2. I'm looking through
http://www.cyrius.com/debian/cobalt/install.html page. I'm not sure
about the Primary and Secondary eth ports on the Qube2. Which port
gets connected to the "server"? How does the Qube2 get to the 'net?
Via the "server" or via the other eth port?

The Qube is amazing I bought mine 9 years ago.

cheers,
Sameer
--
Dr. Sameer Verma, Ph.D.
Associate Professor, Information Systems
Director, Center for Business Solutions
San Francisco State University
http://verma.sfsu.edu/
http://cbs.sfsu.edu/
http://is.sfsu.edu/


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Martin Michlmayr]

* Sameer Verma <sverma@...> [2009-09-04 19:56]:
> This is a question about Qube2. I'm looking through
> http://www.cyrius.com/debian/cobalt/install.html page. I'm not sure
> about the Primary and Secondary eth ports on the Qube2. Which port
> gets connected to the "server"?

The primary eth port.

--
Martin Michlmayr
http://www.cyrius.com/


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sameer Verma]

On Sat, Sep 5, 2009 at 12:40 AM, Martin Michlmayr<tbm@...> wrote:
> * Sameer Verma <sverma@...> [2009-09-04 19:56]:
>> This is a question about Qube2. I'm looking through
>> http://www.cyrius.com/debian/cobalt/install.html page. I'm not sure
>> about the Primary and Secondary eth ports on the Qube2. Which port
>> gets connected to the "server"?
>
> The primary eth port.
>

OK, I got that far, but how does the Qube2 talk to the Internet if its
talking to the NFS server via Primary port? Do I use the Secondary
port for that? I'm using a laptop with NFS and DHCP to serve /nfsroot
and the laptop is on the Internet via the wireless interface. This is
a bit confusing...perhaps I'm not getting the full picture.

cheers,
Sameer
--
Dr. Sameer Verma, Ph.D.
Associate Professor, Information Systems
Director, Center for Business Solutions
San Francisco State University
http://verma.sfsu.edu/
http://cbs.sfsu.edu/
http://is.sfsu.edu/


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sam Varghese]

On Sun, September 6, 2009 03:23, Sameer Verma wrote:

> On Sat, Sep 5, 2009 at 12:40 AM, Martin Michlmayr<tbm@...> wrote:
>> * Sameer Verma <sverma@...> [2009-09-04 19:56]:
>>> This is a question about Qube2. I'm looking through
>>> http://www.cyrius.com/debian/cobalt/install.html page. I'm not sure
>>> about the Primary and Secondary eth ports on the Qube2. Which port
>>> gets connected to the "server"?
>>
>> The primary eth port.
>>
>
> OK, I got that far, but how does the Qube2 talk to the Internet if its
> talking to the NFS server via Primary port? Do I use the Secondary
> port for that? I'm using a laptop with NFS and DHCP to serve /nfsroot
> and the laptop is on the Internet via the wireless interface. This is
> a bit confusing...perhaps I'm not getting the full picture.

Have a look at the list of possible problems at the bottom of this page
(basically a rehash of Martin's very fine guide), they may be of help:

http://gnubies.com/linux/cobalt_qube2.html

Sam
----
(Sam Varghese)



--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Markus Schröder]

Sam Varghese schrieb:
> Have a look at the list of possible problems at the bottom of this page
> (basically a rehash of Martin's very fine guide), they may be of help:
>
> http://gnubies.com/linux/cobalt_qube2.html
Thanks for the additional link!

I tried to install but got stuck after the Qube got the bootloader from
the NFS/DHCP-Server. Found it out when i changed one of the characters
from the messages of the bootloader and message was displayed on the
Qube, and there is no traffic on my network anyway after the bootloader
is pulled from the Qube.

Is there a way to identify the RAM inside 'cause i believe its only 16MB
and i don't have a serial connector on either the server or my laptop!?

cu...
...Markus...


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sam Varghese]

On Tue, September 8, 2009 01:50, Markus Schröder wrote:

> Sam Varghese schrieb:
>> Have a look at the list of possible problems at the bottom of this page
>> (basically a rehash of Martin's very fine guide), they may be of help:
>>
>> http://gnubies.com/linux/cobalt_qube2.html
> Thanks for the additional link!
>
> I tried to install but got stuck after the Qube got the bootloader from
> the NFS/DHCP-Server. Found it out when i changed one of the characters
> from the messages of the bootloader and message was displayed on the
> Qube, and there is no traffic on my network anyway after the bootloader
> is pulled from the Qube.
>
> Is there a way to identify the RAM inside 'cause i believe its only 16MB
> and i don't have a serial connector on either the server or my laptop!?

Hi Markus

If the machine is not booting up due to lack of RAM, then you will
definitely get a kernel panic message.

To find out the hardware specs of your Qube, you'll have a specific set of
commands which you can issue after getting into the BIOS, depending on
whether it is a Qube 1/2 or a Qube 3. You can find these in the manual for
the model in question.

Qube 2 manual - http://docs.sun.com/app/docs/doc/816-1804
Qube 3 manual - http://docs.sun.com/app/docs/doc/816-1807


HTH.

Sam
----
(Sam Varghese)



--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sameer Verma]

On Sat, Sep 5, 2009 at 5:45 PM, Sam Varghese<sam@...> wrote:

> On Sun, September 6, 2009 03:23, Sameer Verma wrote:
>> On Sat, Sep 5, 2009 at 12:40 AM, Martin Michlmayr<tbm@...> wrote:
>>> * Sameer Verma <sverma@...> [2009-09-04 19:56]:
>>>> This is a question about Qube2. I'm looking through
>>>> http://www.cyrius.com/debian/cobalt/install.html page. I'm not sure
>>>> about the Primary and Secondary eth ports on the Qube2. Which port
>>>> gets connected to the "server"?
>>>
>>> The primary eth port.
>>>
>>
>> OK, I got that far, but how does the Qube2 talk to the Internet if its
>> talking to the NFS server via Primary port? Do I use the Secondary
>> port for that? I'm using a laptop with NFS and DHCP to serve /nfsroot
>> and the laptop is on the Internet via the wireless interface. This is
>> a bit confusing...perhaps I'm not getting the full picture.
>
> Have a look at the list of possible problems at the bottom of this page
> (basically a rehash of Martin's very fine guide), they may be of help:
>
> http://gnubies.com/linux/cobalt_qube2.html
>
> Sam
> ----
> (Sam Varghese)
>
>
>
> --
> To UNSUBSCRIBE, email to debian-mips-REQUEST@...
> with a subject of "unsubscribe". Trouble? Contact listmaster@...
>
>

Hi Sam,
Thank you for the clarifications via the link...it makes a lot more
sense now. I had switched from Sun's Cobalt release (the last update
they did before killing Cobalt) to Debian a long time ago, and I
vaguely remember using a set of Debian 3.0 CDs on a laptop to install
Debian on the Qube2. This method is using netinstall, so that makes
sense.

I'm stumped on something new though. My laptop runs Jaunty and I am
using its wlan0 as the interface to the outside, while the eth0
interface offers NFS, DHCP etc. via a crossover to the Qube2. The
trouble is that I simply cannot get the interfaces to forward at all.
This has me stumped because I've done this a thousand times on
machines several years ago, but haven't done so lately, and I am at a
complete loss. does Jaunty have something that would prevent the
forwarding? cat /proc/sys/net/ipv4/ip_forward reports 1

Is NetworkManager getting in the way?

cheers,
Sameer
--
Dr. Sameer Verma, Ph.D.
Associate Professor, Information Systems
Director, Center for Business Solutions
San Francisco State University
http://verma.sfsu.edu/
http://cbs.sfsu.edu/
http://is.sfsu.edu/


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sameer Verma]

On Tue, Sep 8, 2009 at 7:56 PM, Sameer Verma <sverma@...> wrote:

> On Sat, Sep 5, 2009 at 5:45 PM, Sam Varghese<sam@...> wrote:
>> On Sun, September 6, 2009 03:23, Sameer Verma wrote:
>>> On Sat, Sep 5, 2009 at 12:40 AM, Martin Michlmayr<tbm@...> wrote:
>>>> * Sameer Verma <sverma@...> [2009-09-04 19:56]:
>>>>> This is a question about Qube2. I'm looking through
>>>>> http://www.cyrius.com/debian/cobalt/install.html page. I'm not sure
>>>>> about the Primary and Secondary eth ports on the Qube2. Which port
>>>>> gets connected to the "server"?
>>>>
>>>> The primary eth port.
>>>>
>>>
>>> OK, I got that far, but how does the Qube2 talk to the Internet if its
>>> talking to the NFS server via Primary port? Do I use the Secondary
>>> port for that? I'm using a laptop with NFS and DHCP to serve /nfsroot
>>> and the laptop is on the Internet via the wireless interface. This is
>>> a bit confusing...perhaps I'm not getting the full picture.
>>
>> Have a look at the list of possible problems at the bottom of this page
>> (basically a rehash of Martin's very fine guide), they may be of help:
>>
>> http://gnubies.com/linux/cobalt_qube2.html
>>
>> Sam
>> ----
>> (Sam Varghese)
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-mips-REQUEST@...
>> with a subject of "unsubscribe". Trouble? Contact listmaster@...
>>
>>
>
>
> Hi Sam,
> Thank you for the clarifications via the link...it makes a lot more
> sense now. I had switched from Sun's Cobalt release (the last update
> they did before killing Cobalt) to Debian a long time ago, and I
> vaguely remember using a set of Debian 3.0 CDs on a laptop to install
> Debian on the Qube2. This method is using netinstall, so that makes
> sense.
>
> I'm stumped on something new though. My laptop runs Jaunty and I am
> using its wlan0 as the interface to the outside, while the eth0
> interface offers NFS, DHCP etc. via a crossover to the Qube2. The
> trouble is that I simply cannot get the interfaces to forward at all.
> This has me stumped because I've done this a thousand times on
> machines several years ago, but haven't done so lately, and I am at a
> complete loss. does Jaunty have something that would prevent the
> forwarding? cat /proc/sys/net/ipv4/ip_forward reports 1
>
> Is NetworkManager getting in the way?
>
> cheers,
> Sameer
> --
> Dr. Sameer Verma, Ph.D.
> Associate Professor, Information Systems
> Director, Center for Business Solutions
> San Francisco State University
> http://verma.sfsu.edu/
> http://cbs.sfsu.edu/
> http://is.sfsu.edu/
>

Found the culprit. Ubuntu Jaunty needs dnsmasq for ipmasquerading to
work. http://brainstorm.ubuntu.com/idea/10427/ Installation is going
on smoothly as I write this.

cheers,
Sameer
--
Dr. Sameer Verma, Ph.D.
Associate Professor, Information Systems
Director, Center for Business Solutions
San Francisco State University
http://verma.sfsu.edu/
http://cbs.sfsu.edu/
http://is.sfsu.edu/


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Martin Michlmayr]

* Markus Schröder <m.schroeder@...> [2009-09-07 17:50]:
> I tried to install but got stuck after the Qube got the bootloader
> from the NFS/DHCP-Server. Found it out when i changed one of the
> characters from the messages of the bootloader and message was
> displayed on the Qube, and there is no traffic on my network anyway
> after the bootloader is pulled from the Qube.
>
> Is there a way to identify the RAM inside 'cause i believe its only
> 16MB and i don't have a serial connector on either the server or my
> laptop!?

IIRC CoLo (the 2nd stage boot loader that's loaded via the network)
will display the amount of RAM when it starts.
--
Martin Michlmayr
http://www.cyrius.com/


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Markus Schröder]

Martin Michlmayr schrieb:

> * Markus Schröder <m.schroeder@...> [2009-09-07 17:50]:
>  
>> I tried to install but got stuck after the Qube got the bootloader
>> from the NFS/DHCP-Server. Found it out when i changed one of the
>> characters from the messages of the bootloader and message was
>> displayed on the Qube, and there is no traffic on my network anyway
>> after the bootloader is pulled from the Qube.
>>
>> Is there a way to identify the RAM inside 'cause i believe its only
>> 16MB and i don't have a serial connector on either the server or my
>> laptop!?
>>    
>
> IIRC CoLo (the 2nd stage boot loader that's loaded via the network)
> will display the amount of RAM when it starts.
>  

I finally bought a serial cable to see whats happening on the Qube², and
128MB Ram when i saw it had only 16MB installed. But i still have the
probs it won't load the bootloader at all.

In the 1st, i connected the Qube², the NFS/DHCP-Server, my regular
desktop machine and the Router/Gateway over a 3com Hub. There was a
serial connection between my regular desktop running HyperTerm and the
Qube, too. IP-Address was assigned to the Qube as i could ping it from
the NFS/DHCP-Server, but it only went to "Installing SSH-Server", not
further. I tried several times using both NFS and TFT boot option, and
one time it got to the "Booting...$IP-Address" message.

 > Cobalt Microserver Diagnostics - 'We serve it, you surf it'
Built Tue Dec 15 04:11:42 PST 1998

 1.LCD Test................................PASS
 2.Controller Test.........................PASS
 5.Bank 0:.................................64M
 6.Bank 1:.................................64M
 7.Bank 2:.................................16M
 8.Bank 3:.................................16M
 9.Serial Test.............................PASS
10.PCI Expansion Slot....................**EMPTY**
12.IDE Test................................PASS
13.Ethernet Test...........................PASS
16.RTC Test................................PASS
Decompressing  done
Decompressing \ done.

[ "CoLo" v1.22 ]
stage2: 89fa0000-8a000000
cpu: clock 250.000MHz
pci: unit type <Qube2>
tulip: #0 device 21143
tulip: #1 device 21143
tulip: {00:10:e0:00:26:e9}
ide: resetting
boot: running boot menu
1> lcd 'Booting...'
1> net
tulip: link up (100Mbps)
net: interface up
dhcp: DISCOVER
dhcp: OFFER 192.168.178.5 <-- 192.168.178.40
dhcp: REQUEST
dhcp: ACK
net: interface down
tulip: link up (100Mbps)
net: interface up
  address     192.168.178.5
  netmask     255.255.255.0
  gateway     192.168.178.1
  name server 192.168.178.1
1> lcd 'Booting...' {ip-address}
1> tftp {dhcp-next-server} {dhcp-boot-file}
no response
script aborted <1>

another time i tried i got this message i copied from the terminal on my
desktop machine:

Cobalt Microserver Diagnostics - 'We serve it, you surf it'
Built Tue Dec 15 04:11:42 PST 1998

 1.LCD Test................................PASS
 2.Controller Test.........................PASS
 5.Bank 0:.................................64M
 6.Bank 1:.................................64M
 7.Bank 2:.................................16M
 8.Bank 3:.................................16M
 9.Serial Test.............................PASS
10.PCI Expansion Slot....................**EMPTY**
12.IDE Test................................PASS
13.Ethernet Test...........................PASS
16.RTC Test................................PASS
Decompressing  done
Decompressing \ done.

[ "CoLo" v1.22 ]
stage2: 89fa0000-8a000000
cpu: clock 250.000MHz
pci: unit type <Qube2>
tulip: #0 device 21143
tulip: #1 device 21143
tulip: {00:10:e0:00:26:e9}
ide: resetting
boot: running boot menu
1> lcd 'Booting...'
1> mount
ide: {ST314220A}
ide: LBA 27853148
ide: supports PIO mode 4
ide: mode 4 timing
ide: partition 1
ext2: revision 1
ext2: has journal (ext3)
1> lcd 'Booting...' /dev/{mounted-volume}
1> -load /boot/default.colo
file not found
(unknown error #1)
1> -script
no script loaded
(unknown error #1)
1> load /boot/vmlinux.gz
file not found
script aborted <1>

I wonder there was no IP-address assigned at all this time, so this
would be the cause why booting failed.

After i spent a complete evening on that prob, i connected the Qube² to
the NFS/DHCP-Server using a crossover cable and the serial to my desktop
running HyperTerm, but doesn't work at all. Started the Qube a few times
with tcpdump running on the server, but i haven't any clue at all what's
going wrong there...

cu...
...Markus...




--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Glyn Astill]

Hi Markus,

> tftp {dhcp-next-server} {dhcp-boot-file}

Are you really trying to use tftp to do the setup?  AFAIK when I did the setup I ran it off of an NFS share - when the qube first boots up the lcd gives you options to choose TFTP, NFS local disk etc and you just use the buttons to choose.

However my attempts ultimately ended in failure, it installed fine, but after half an hour or so of uptime debian just went lazy (the best word I can think to describe it) until it just died. Back to NetBSD I went, and as usual it runs like a dream.

Glyn



--- On Fri, 18/9/09, Markus Schröder <m.schroeder@...> wrote:

> From: Markus Schröder <m.schroeder@...>
> Subject: Re: installing Debian on Cobalt Qube 2
> To: "Martin Michlmayr" <tbm@...>
> Cc: debian-mips@...
> Date: Friday, 18 September, 2009, 3:27 PM
> Martin Michlmayr schrieb:
> > * Markus Schröder <m.schroeder@...>
> [2009-09-07 17:50]:
> >   
> >> I tried to install but got stuck after the Qube
> got the bootloader
> >> from the NFS/DHCP-Server. Found it out when i
> changed one of the
> >> characters from the messages of the bootloader and
> message was
> >> displayed on the Qube, and there is no traffic on
> my network anyway
> >> after the bootloader is pulled from the Qube.
> >>
> >> Is there a way to identify the RAM inside 'cause i
> believe its only
> >> 16MB and i don't have a serial connector on either
> the server or my
> >> laptop!?
> >>     
> >
> > IIRC CoLo (the 2nd stage boot loader that's loaded via
> the network)
> > will display the amount of RAM when it starts.
> >   
> I finally bought a serial cable to see whats happening on
> the Qube², and 128MB Ram when i saw it had only 16MB
> installed. But i still have the probs it won't load the
> bootloader at all.
>
> In the 1st, i connected the Qube², the NFS/DHCP-Server, my
> regular desktop machine and the Router/Gateway over a 3com
> Hub. There was a serial connection between my regular
> desktop running HyperTerm and the Qube, too. IP-Address was
> assigned to the Qube as i could ping it from the
> NFS/DHCP-Server, but it only went to "Installing
> SSH-Server", not further. I tried several times using both
> NFS and TFT boot option, and one time it got to the
> "Booting...$IP-Address" message.
>
> > Cobalt Microserver Diagnostics - 'We serve it, you
> surf it'
> Built Tue Dec 15 04:11:42 PST 1998
>
> 1.LCD Test................................PASS
> 2.Controller Test..........................PASS
> 5.Bank 0:.................................64M
> 6.Bank 1:.................................64M
> 7.Bank 2:..................................16M
> 8.Bank 3:.................................16M
> 9.Serial Test.............................PASS
> 10.PCI Expansion Slot.....................**EMPTY**
> 12.IDE Test.................................PASS
> 13.Ethernet Test...........................PASS
> 16.RTC Test.................................PASS
> Decompressing  done
> Decompressing \ done.
>
> [ "CoLo" v1.22 ]
> stage2: 89fa0000-8a000000
> cpu: clock 250.000MHz
> pci: unit type <Qube2>
> tulip: #0 device 21143
> tulip: #1 device 21143
> tulip: {00:10:e0:00:26:e9}
> ide: resetting
> boot: running boot menu
> 1> lcd 'Booting...'
> 1> net
> tulip: link up (100Mbps)
> net: interface up
> dhcp: DISCOVER
> dhcp: OFFER 192.168.178.5 <-- 192.168.178.40
> dhcp: REQUEST
> dhcp: ACK
> net: interface down
> tulip: link up (100Mbps)
> net: interface up
>  address     192.168.178.5
>  netmask     255.255.255.0
>  gateway     192.168.178.1
>  name server 192.168.178.1
> 1> lcd 'Booting...' {ip-address}
> 1> tftp {dhcp-next-server} {dhcp-boot-file}
> no response
> script aborted <1>
>
> another time i tried i got this message i copied from the
> terminal on my desktop machine:
>
> Cobalt Microserver Diagnostics - 'We serve it, you surf
> it'
> Built Tue Dec 15 04:11:42 PST 1998
>
> 1.LCD Test.................................PASS
> 2.Controller Test.........................PASS
> 5.Bank 0:..................................64M
> 6.Bank 1:..................................64M
> 7.Bank 2:.................................16M
> 8.Bank 3:..................................16M
> 9.Serial Test..............................PASS
> 10.PCI Expansion Slot....................**EMPTY**
> 12.IDE Test................................PASS
> 13.Ethernet Test............................PASS
> 16.RTC Test................................PASS
> Decompressing  done
> Decompressing \ done.
>
> [ "CoLo" v1.22 ]
> stage2: 89fa0000-8a000000
> cpu: clock 250.000MHz
> pci: unit type <Qube2>
> tulip: #0 device 21143
> tulip: #1 device 21143
> tulip: {00:10:e0:00:26:e9}
> ide: resetting
> boot: running boot menu
> 1> lcd 'Booting...'
> 1> mount
> ide: {ST314220A}
> ide: LBA 27853148
> ide: supports PIO mode 4
> ide: mode 4 timing
> ide: partition 1
> ext2: revision 1
> ext2: has journal (ext3)
> 1> lcd 'Booting...' /dev/{mounted-volume}
> 1> -load /boot/default.colo
> file not found
> (unknown error #1)
> 1> -script
> no script loaded
> (unknown error #1)
> 1> load /boot/vmlinux.gz
> file not found
> script aborted <1>
>
> I wonder there was no IP-address assigned at all this time,
> so this would be the cause why booting failed.
>
> After i spent a complete evening on that prob, i connected
> the Qube² to the NFS/DHCP-Server using a crossover cable
> and the serial to my desktop running HyperTerm, but doesn't
> work at all. Started the Qube a few times with tcpdump
> running on the server, but i haven't any clue at all what's
> going wrong there...
>
> cu...
> ...Markus...
>
>
>
>
> -- To UNSUBSCRIBE, email to debian-mips-REQUEST@...
> with a subject of "unsubscribe". Trouble? Contact listmaster@...
>
>

--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Markus Schröder]

Glyn Astill schrieb:
>> tftp {dhcp-next-server} {dhcp-boot-file}
>>    
>
> Are you really trying to use tftp to do the setup?  AFAIK when I did the setup I ran it off of an NFS share - when the qube first boots up the lcd gives you options to choose TFTP, NFS local disk etc and you just use the buttons to choose.
>  
I tried all methods to install given by the menu on the qube, but nothing worked. When i had no success with NFS i tried TFTP to see what happens. And finally the qube² reacted a few times like in the examples, usually it stops after the selftest with a "Decompressing done"

I just figured out that after i've chosen  the "Network (NFS)" option
the qubes primary network interface is set up (green LED on the port
turns off for 1/2 second and lights up again) and i could ping it.

When i now choose the "Install (SSH)" option and "starting the
installer" (both SSH and TTYS) is shown on the display, it seems as the
interface is going down again 'cause the green LED turns off for about
1/2 second and all pings on the qube fails when it lights up after that.
> However my attempts ultimately ended in failure, it installed fine, but after half an hour or so of uptime debian just went lazy (the best word I can think to describe it) until it just died. Back to NetBSD I went, and as usual it runs like a dream.
>  
Think my last chance is to do a manual installation right on the HD,
using the tar ball provided by Martin Michlmayr. But hey, it's weekend
and there's plenty of time for such a quest :) ...


cu...
...Markus...


--
To UNSUBSCRIBE, email to debian-mips-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...