linuxdc-dev — Developer discussion list

Re: [linuxdc-dev]Some basic questions and Linux DC + NFS

[M. R. B. <mr...@0x...>]

* Danny Rodriguez <me...@op...> on Sun, Oct 14, 2001:

>=20
[...]

Currently Bill's article [1] is the best guide to getting started, Karl and=
 I
are working on the content of linuxdc.org (still down) as I write this.
We'll be providing binaries of the tools at that point as well.

I couldn't really forsee anyone having problems with Bill's article, since =
he
covers all of the bases and leaves no room for error :).  If you do start
getting into other problems (i.e. NFS mounting etc.) don't hesitate to ask
about them here.

[1] http://linuxdevices.com/articles/AT7466555948.html

M. R.

RE: [linuxdc-dev]Some basic questions and Linux DC + NFS

[Danny R. <me...@op...>]

I apologize for my idiocy. I just wasn't thinking.

-Danny

> -----Original Message-----
> From: lin...@li... [mailto:linuxdc-dev-
> ad...@li...] On Behalf Of M. R. Brown
> Sent: Sunday, October 14, 2001 12:58 PM
> To: Danny Rodriguez
> Cc: ad...@mc...; 'Paul Mundt'; linuxdc-
> de...@li...
> Subject: Re: [linuxdc-dev]Some basic questions and Linux DC + NFS
> 
> * Danny Rodriguez <me...@op...> on Sun, Oct 14, 2001:
> 
> > Okay, I'm using Adrian's config with NFS enabled. But I'm getting
the
> > same errors as before.
> >
> > Steps taken :
> >
> > make ARCH=sh config with current .config file
> > make ARCH=sh CROSS_COMPILE=sh-elf-
> > (errors)
> >
> 
> sh-elf?  Are you kidding me?
> 
> Read Bill Gatliff's Linux/Dreamcast article on LinuxDevices.com, and
don't
> come back until you run into *real* problems.
> 
> M. R.

Re: [linuxdc-dev]Some basic questions and Linux DC + NFS

[M. R. B. <mr...@0x...>]

* Danny Rodriguez <me...@op...> on Sun, Oct 14, 2001:

> Okay, I'm using Adrian's config with NFS enabled. But I'm getting the
> same errors as before.
>=20
> Steps taken :
>=20
> make ARCH=3Dsh config with current .config file
> make ARCH=3Dsh CROSS_COMPILE=3Dsh-elf-
> (errors)
>=20

sh-elf?  Are you kidding me?

Read Bill Gatliff's Linux/Dreamcast article on LinuxDevices.com, and don't
come back until you run into *real* problems.

M. R.

RE: [linuxdc-dev]Some basic questions and Linux DC + NFS

[Danny R. <me...@op...>]

Okay, I'm using Adrian's config with NFS enabled. But I'm getting the
same errors as before.

Steps taken :

make ARCH=sh config with current .config file
make ARCH=sh CROSS_COMPILE=sh-elf-
(errors)

I edited the Makefile to do ARCH=sh and CROSS_COMPILE=sh-elf- (which are
in my path).

When I do make dep, or make ARCH=sh CROSS_COMPILE=/usr/local/bin/sh-elf-
dep
(both are equivalent errors)... I get this :

make[1]: Entering directory `/home/Danny/kernel/arch/sh/boot'
make[1]: Nothing to be done for `dep'.
make[1]: Leaving directory `/home/Danny/kernel/arch/sh/boot'
scripts/mkdep -- init/*.c > .depend
scripts/mkdep -- `find /home/Danny/kernel/include/asm
/home/Danny/kernel/include
/linux /home/Danny/kernel/include/scsi /home/Danny/kernel/include/net
-name SCCS
 -prune -o -follow -name \*.h ! -name modversions.h -print` > .hdepend
scripts/mkdep: error 22
make: *** [dep-files] Error 2

What am I missing here?

Thanks!

-Danny

-----Original Message-----
From: Adrian McMenamin [mailto:ad...@mc...] 
Sent: Sunday, October 14, 2001 6:04 AM
To: Danny Rodriguez; 'Paul Mundt'
Cc: lin...@li...
Subject: Re: [linuxdc-dev]Some basic questions and Linux DC + NFS

I've sent mine direct to Danny, but should anyone want it - try 
http://www.mcmen.demon.co.uk/linuxdc/config

...and just a reminder that you'll find a BBA supporting (but not NFS
booting 
elf'ed kernel at http://www.mcmen.demon.co.uk/linuxdc - and ther's also
a 
compiled x86 copy of the dc-tool app there too. But no documentation for
any 
of this!


On Sunday 14 October 2001  7:21 am, Danny Rodriguez wrote:
> Do you guys, by any chance, have sample .config files for the DC? One
> that supports the BBA and NFS?
>
> -Danny
>

Re: [linuxdc-dev]Some basic questions and Linux DC + NFS

[Paul M. <pm...@mv...>]

On Sun, Oct 14, 2001 at 02:21:16AM -0400, Danny Rodriguez wrote:
> Do you guys, by any chance, have sample .config files for the DC? One
> that supports the BBA and NFS?
>=20
There's an old one in CVS, but nothing that's really useful. Due to the
straightforward nature of setting up a config for the DC, there's no real n=
eed
for this.. but at the same time I suppose sticking in a standard defconfig
probably couldn't hurt either.. Will see what NIIBE-san thinks about adding
arch/sh/configs (in accordance w/ PPC and MIPS guidelines) and go from ther=
e.

Regards,

--=20
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.

Re: [linuxdc-dev]Some basic questions and Linux DC + NFS

[Adrian M. <ad...@mc...>]

I've sent mine direct to Danny, but should anyone want it - try 
http://www.mcmen.demon.co.uk/linuxdc/config

...and just a reminder that you'll find a BBA supporting (but not NFS booting 
elf'ed kernel at http://www.mcmen.demon.co.uk/linuxdc - and ther's also a 
compiled x86 copy of the dc-tool app there too. But no documentation for any 
of this!


On Sunday 14 October 2001  7:21 am, Danny Rodriguez wrote:
> Do you guys, by any chance, have sample .config files for the DC? One
> that supports the BBA and NFS?
>
> -Danny
>

RE: [linuxdc-dev]Some basic questions and Linux DC + NFS

[Danny R. <me...@op...>]

Do you guys, by any chance, have sample .config files for the DC? One
that supports the BBA and NFS?

-Danny

-----Original Message-----
From: Paul Mundt [mailto:pm...@mv...] 
Sent: Sunday, October 14, 2001 1:30 AM
To: Danny Rodriguez
Cc: lin...@li...
Subject: Re: [linuxdc-dev]Some basic questions and Linux DC + NFS

On Sun, Oct 14, 2001 at 01:13:47AM -0400, Danny Rodriguez wrote:
> Okay guys, it's been a while since I've worked on the LinuxDC project.
I
> downloaded the updated CVS module linux-sh-dc, then copied the files
> into the 2.4.10 kernel codebase.
> 
linux-sh-dc is an _experimental_ CVS module. It's where all the new
development that isn't fit for general consumption goes. All the stuff
you're
looking for is in the linuxsh CVS. See http://sf.net/projects/linuxsh/

> I used the HOWTO's .config then added maple bus support in make
> menuconfig. Now nothing works as far as the HOWTO is concerned. I try
> doing 
> 
HOWTO probably needs to be updated.. the maple stuff in the linux-sh-dc
module
is an experimental work-in-progress at a new implementation of the maple
bus
to behave somewhat more intelligently. If you're interested in
functional, you
want the old maple stuff thats in the LinuxSH CVS.

> 
> Am I missing steps? Also, the menuconfig has no mention of NFS
support,
> or even network support/BBA for that matter.
> 
> What happened to the old linux module?
> 
Most of our changes got pushed into the LinuxSH CVS, and that's where
all the
"stable" stuff goes now. Experimental and new stuff goes in the LinuxDC
CVS.
Unless you're a kernel hacker interested in hacking on new things, stay
away
from the linux-sh-dc module.

Regards,

-- 
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.

Re: [linuxdc-dev]Some basic questions and Linux DC + NFS

[Paul M. <pm...@mv...>]

On Sun, Oct 14, 2001 at 01:13:47AM -0400, Danny Rodriguez wrote:
> Okay guys, it's been a while since I've worked on the LinuxDC project. I
> downloaded the updated CVS module linux-sh-dc, then copied the files
> into the 2.4.10 kernel codebase.
>=20
linux-sh-dc is an _experimental_ CVS module. It's where all the new
development that isn't fit for general consumption goes. All the stuff you'=
re
looking for is in the linuxsh CVS. See http://sf.net/projects/linuxsh/

> I used the HOWTO's .config then added maple bus support in make
> menuconfig. Now nothing works as far as the HOWTO is concerned. I try
> doing=20
>=20
HOWTO probably needs to be updated.. the maple stuff in the linux-sh-dc mod=
ule
is an experimental work-in-progress at a new implementation of the maple bus
to behave somewhat more intelligently. If you're interested in functional, =
you
want the old maple stuff thats in the LinuxSH CVS.

>=20
> Am I missing steps? Also, the menuconfig has no mention of NFS support,
> or even network support/BBA for that matter.
>=20
> What happened to the old linux module?
>=20
Most of our changes got pushed into the LinuxSH CVS, and that's where all t=
he
"stable" stuff goes now. Experimental and new stuff goes in the LinuxDC CVS.
Unless you're a kernel hacker interested in hacking on new things, stay away
from the linux-sh-dc module.

Regards,

--=20
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.

[linuxdc-dev]Some basic questions and Linux DC + NFS

[Danny R. <me...@op...>]

Okay guys, it's been a while since I've worked on the LinuxDC project. I
downloaded the updated CVS module linux-sh-dc, then copied the files
into the 2.4.10 kernel codebase.

I used the HOWTO's .config then added maple bus support in make
menuconfig. Now nothing works as far as the HOWTO is concerned. I try
doing 

$ make ARCH=sh CROSS_COMPILE=/usr/local/bin/sh-elf- dep zImage
make[1]: Entering directory `/home/Danny/linux/arch/sh/boot'
make[1]: Nothing to be done for `dep'.
make[1]: Leaving directory `/home/Danny/linux/arch/sh/boot'
scripts/mkdep -- init/*.c > .depend
scripts/mkdep -- `find /home/Danny/linux/include/asm
/home/Danny/linux/include/l
inux /home/Danny/linux/include/scsi /home/Danny/linux/include/net -name
SCCS -pr
une -o -follow -name \*.h ! -name modversions.h -print` > .hdepend
scripts/mkdep: error 22
make: *** [dep-files] Error 2


Am I missing steps? Also, the menuconfig has no mention of NFS support,
or even network support/BBA for that matter.

What happened to the old linux module?

Also, I finally got a BBA, so no more burning CD's every 5 seconds. Do I
simply use the load+exec feature of DC load on a kernel image? How does
that work?

Thanks guys,

-Danny

Re: [linuxdc-dev]NFSROOT problem (was QT Embedded)

[Adrian M. <ad...@mc...>]

On Saturday 13 October 2001  7:11 pm, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Sat, Oct 13, 2001:
> > Sounds right - but I don't have an /etc/network/interfaces file to
> > disable! The /etc directory on the DC's root partition is empty :-<
>
> If you're using busybox as a base system, setup /etc/inittab and try
> remounting NFS rw from /etc/init.d/rcS, also setup an /etc/fstab with your
> NFS root entry.
>
Thanks, this works - if you leave out the inittab step. Don't ask me why, but 
with /etc/inittab it fails - something to do with the fact that busybox 
appears to be running before inittab is processed, I'd guess.

Re: [linuxdc-dev]NFSROOT problem (was QT Embedded)

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Sat, Oct 13, 2001:

> Sounds right - but I don't have an /etc/network/interfaces file to disabl=
e!=20
> The /etc directory on the DC's root partition is empty :-<
>=20

If you're using busybox as a base system, setup /etc/inittab and try
remounting NFS rw from /etc/init.d/rcS, also setup an /etc/fstab with your
NFS root entry.

Also, I'm a bit confused about your kernel options, why use rarp if you're
specifying an IP address?  Here's my command-line:

  mem=3D16M video=3Dpvr2fb:640x480-16 root=3D/dev/nfs \
  nfsroot=3D192.168.1.11:/home/mrbrown/dcdev/nfs/nfsroot \
  ip=3D192.168.1.21::192.168.1.254:255.255.255.0:blackbox::off

Notice that I've turned IP autoconfiguration off since I'm assigning a
static IP to the DC.

M. R.

Re: [linuxdc-dev]NFSROOT problem (was QT Embedded)

[Adrian M. <ad...@mc...>]

On Saturday 13 October 2001  5:29 pm, Gareth J. Greenaway wrote:
> On Sat, Oct 13, 2001 at 04:41:10PM +0100, Adrian McMenamin wrote:
> > I have been able to successfully (?) set up my DC to mount an NFS
> > partition as root (busybox), but the file system is only being mounted as
> > readonly - which is next to useless. I can't spot any configuration
> > error, maybe somebody here can.
>
> I had this exactly same problem, it took me a a couple days to finally
> figure out what was happening.  The NFS root was being mounted but then
> the way I had it setup the network interface was going and grabbing
> another IP address which caused the root to be remounted readonly.  I
> disabled the network configuration in /etc/network/interfaces and then
> it worked fine.
>
>
> 						Gareth
Sounds right - but I don't have an /etc/network/interfaces file to disable! 
The /etc directory on the DC's root partition is empty :-<

Does this mean some jiggery-pokery with the kernel command line?

Re: [linuxdc-dev]NFSROOT problem (was QT Embedded)

[<ga...@wi...>]

On Sat, Oct 13, 2001 at 04:41:10PM +0100, Adrian McMenamin wrote:
> I have been able to successfully (?) set up my DC to mount an NFS partition 
> as root (busybox), but the file system is only being mounted as readonly - 
> which is next to useless. I can't spot any configuration error, maybe 
> somebody here can.
> 

I had this exactly same problem, it took me a a couple days to finally
figure out what was happening.  The NFS root was being mounted but then
the way I had it setup the network interface was going and grabbing
another IP address which caused the root to be remounted readonly.  I
disabled the network configuration in /etc/network/interfaces and then
it worked fine.


						Gareth

-- 
Gareth J. Greenaway
ga...@wi...

[linuxdc-dev]NFSROOT problem (was QT Embedded)

[Adrian M. <ad...@mc...>]

On Saturday 06 October 2001  4:59 pm, M. R. Brown wrote:
>
> Note: Currently the best way to verify that your DC mouse, keyboard, and
> controller are working is to use the distro provided at m17n.org.  With a
> bit of hacking, you can set this up as your NFSROOT, so you can just move
> apps their when your ready to test.  It comes with all of the /dev nodes
> created (actually it uses devfs).  Do *not* use the kernel supplied with
> that distro, as it's hopelessly out of date.  Do compile IP
> autoconfiguration and NFS root support into your kernel.  I've attached my
> /etc/fstab file.  Here are my kernel command-line args:
>
>   mem=16M video=pvr2fb:640x480-16 root=/dev/nfs \
>   nfsroot=192.168.1.11:/home/mrbrown/dcdev/nfs/nfsroot \
>   ip=192.168.1.21::192.168.1.254:255.255.255.0:blackbox::off
>
> Read linux/Documentation/nfsroot.txt for more info.
>

I have been able to successfully (?) set up my DC to mount an NFS partition 
as root (busybox), but the file system is only being mounted as readonly - 
which is next to useless. I can't spot any configuration error, maybe 
somebody here can.

exports file on ix86 box...
/home/Adrian/nfs/initrd  	dreamy(rw,no_root_squash)  	#Dreamcast shell

kernel command line...
commandline:
	.ascii	"mem=16M video=pvr2fb root=/dev/nfs 
nfsroot=192.168.62.123:/home/Adrian/nfs/initrd 
ip=192.168.62.2:192.168.62.123::255.255.255.0:dreamy::rarp"
	.byte	0

	.end

I'm not using an /etc/fstab file on the DC at the moment - as it makes no 
difference whether I use one or not - it all still mounts as ro.

Any help?

Thanks

Adrian

Re: [linuxdc-dev] Qt Embedded

[Adrian M. <ad...@mc...>]

On Saturday 06 October 2001  4:59 pm, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Sat, Oct 06, 2001:
> > The only device nodes I have set up are /dev/console and /dev/fb0 - could
> > that be it?
>
> Yes, use the MAKEDEV script that I mailed you to create the proper device
> nodes.  You at least want "MAKEDEV std" and "MAKEDEV input".  Make a
> symlink from /dev/input/mice to /dev/psaux (yeah, but QtE expects
> /dev/psaux to be rw, I don't know why it doesn't use /dev/input/mice
> directly).
>
Thanks, problem now appears to be fixed.

Re: [linuxdc-dev] Qt Embedded

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Sat, Oct 06, 2001:

> 
> The only device nodes I have set up are /dev/console and /dev/fb0 - could 
> that be it?
> 

Yes, use the MAKEDEV script that I mailed you to create the proper device
nodes.  You at least want "MAKEDEV std" and "MAKEDEV input".  Make a
symlink from /dev/input/mice to /dev/psaux (yeah, but QtE expects
/dev/psaux to be rw, I don't know why it doesn't use /dev/input/mice
directly).

Of course make sure all of the input core drivers are compiled into the
kernel, as well as the Maple mouse and keyboard support.  Note that these
*cannot* be used as modules, do to a flaw in the Maple driver design.

I'm able to run QtE static, I still can't do shared yet (gcc-3.0.1 issues),
and I'm working on QPE at the moment.  Then, konqueror is next :P.

Note: Currently the best way to verify that your DC mouse, keyboard, and
controller are working is to use the distro provided at m17n.org.  With a
bit of hacking, you can set this up as your NFSROOT, so you can just move
apps their when your ready to test.  It comes with all of the /dev nodes
created (actually it uses devfs).  Do *not* use the kernel supplied with
that distro, as it's hopelessly out of date.  Do compile IP
autoconfiguration and NFS root support into your kernel.  I've attached my
/etc/fstab file.  Here are my kernel command-line args:

  mem=16M video=pvr2fb:640x480-16 root=/dev/nfs \
  nfsroot=192.168.1.11:/home/mrbrown/dcdev/nfs/nfsroot \
  ip=192.168.1.21::192.168.1.254:255.255.255.0:blackbox::off 

Read linux/Documentation/nfsroot.txt for more info.

M. R.

Re: [linuxdc-dev] Qt Embedded

[Adrian M. <ad...@mc...>]

On Friday 05 October 2001  1:39 am, Adrian McMenamin wrote:
> I have successfully compiled and run this for linuxdc. It's bloated, but it
> works.
>
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev

This turns out to be not quite as good as I thought yesterday morning! Maybe 
someone here might be able to help....

All the compiled examples run - the screen flashes up lime green and the 
windows with widgets appear on them - together with a mouse pointer in the 
middle of the screen.

But the apps won't accept any keyboard or mouse input (my mouse is a PS/2 
through an adaptor, but it's a proper DC keyboard).

Keystrokes just result in characters appearing at the bottom of the screen - 
though the app keeps running and writing to the framebuffer at the same time 
if that is required. (Ctrl+C will break the app).

Any ideas? Is this a setup/config problem do you think? Or a problem with 
QtE? My hunch is the former, but I don't know.

The only device nodes I have set up are /dev/console and /dev/fb0 - could 
that be it?

Adrian

[linuxdc-dev] Qt Embedded

[Adrian M. <ad...@mc...>]

I have successfully compiled and run this for linuxdc. It's bloated, but it 
works.

Re: [linuxdc-dev] Newbie questions

[Paul M. <pm...@mv...>]

On Thu, Sep 27, 2001 at 04:08:06PM +0200, edd...@wa... wrote:
> 1) GD-Rom support: I found at some point on the web the information that 
> support was available now, and in the 2.4.10-pre6 kernel you've got some 
> kind of option for GD-Rom support. What is it status? I'd love to get rid 
> of the initrd, actually... :)
> 
There's an ugly hack of a GD-ROM driver in the LinuxSH tree (linuxsh.sf.net)
which is based off an ugly NetBSD driver. It works for the most part, but will
definately be replaced by a cleaner one as time allows. It might be feasible
to use for booting, but I've not tried it, so I can't confirm one way or the
other.

> 2) I'm working with the files used in BG's article, but where can I find 
> new diffs? I guess things move fairly often, do I need to CVS or is there 
> some kind of regular diffs release somewhere?
> 
The way we're doing it now is doing all experimental and new development in
the LinuxDC CVS, then after it's tested and ready to move on, it gets pushed
into the LinuxSH CVS. As far as what's in the LinuxDC CVS, everything is being
done as a drop-in tree, so you need to link it into a stock checkout of the
LinuxSH tree if you really want it. Though new users shouldn't ever be
touching the experimental tree for any reason at all, and we have no intention
of supporting the experimental tree incase a new user has problems with it.

> 3) Do you maintain your own tree for the basic tools 
> (binutils/gcc/libc/kernel) and release from time to time diffs, or are your 
> bug corrections merged inside the main CVS trees?
> 
See above. The only thing that's being maintained is the kernel. The rest of
the stuff just requires occasional patching which generally applies to SH4 in
general, and is better handled through the LinuxSH project.

> 4) A few problems when buiding gcc, for example whent omitting the 
> --with-newlib flag. Hints? BTW, never managed to compile correctly 
> newlib-1.9. Again, hints?
> 
How about posting an error log? What you're implying is -ESOMETHINGWENTWRONG,
which isn't all that useful.

Regards,

-- 
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.

[linuxdc-dev] Newbie questions

[<edd...@wa...>]

Hello everyone


Sorry for bothering you with those questions, but I'm a newbie in the 
LinuxDC arena, and I'd like to get started.

To give it a go, I carefully did everything in Bill Gatliff's article on 
Linuxdevices, and everything went OK. The CD's ready, I don't know if it 
boots cause I'm still waiting for the VGA adaptor (I bought a second hand 
DC just to work on Linux a few days ago :).
I guess I understood what is involved in the process, now I'm willing to 
buid something a tad more sophisticated. So I tried a few things, and here 
are my questions.

1) GD-Rom support: I found at some point on the web the information that 
support was available now, and in the 2.4.10-pre6 kernel you've got some 
kind of option for GD-Rom support. What is it status? I'd love to get rid 
of the initrd, actually... :)

2) I'm working with the files used in BG's article, but where can I find 
new diffs? I guess things move fairly often, do I need to CVS or is there 
some kind of regular diffs release somewhere?

3) Do you maintain your own tree for the basic tools 
(binutils/gcc/libc/kernel) and release from time to time diffs, or are your 
bug corrections merged inside the main CVS trees?

4) A few problems when buiding gcc, for example whent omitting the 
--with-newlib flag. Hints? BTW, never managed to compile correctly 
newlib-1.9. Again, hints?


Thanks a lot for your help.
Ed

Re: [linuxdc-dev] Viruses - off topic, but interesting?

[Adrian M. <ad...@mc...>]

On Wednesday 26 September 2001  1:15 pm, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Wed, Sep 26, 2001:
> > But I've been unsuccesful because every version I've looked at appears to
> > contain the backdoor/IRC-Flood/D virus (I think that's what it was
> > called).
>
> Um .. have you written to the GIMP or GTK+ developers about this?  Seems
> like they would know what's what.
>
> M. R.
Looks like you're right - but it doesn't seem to like 777 either ?!

Re: [linuxdc-dev] Viruses - off topic, but interesting?

[Adrian M. <ad...@mc...>]

On Wednesday 26 September 2001  1:15 pm, M. R. Brown wrote:

The developer has told me it is a false positive.

> * Adrian McMenamin <ad...@mc...> on Wed, Sep 26, 2001:
> > But I've been unsuccesful because every version I've looked at appears to
> > contain the backdoor/IRC-Flood/D virus (I think that's what it was
> > called).
>
> Um .. have you written to the GIMP or GTK+ developers about this?  Seems
> like they would know what's what.
>
> M. R.
>
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev

Re: [linuxdc-dev] Compiling Qt Embedded

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Wed, Sep 26, 2001:

> As those who listen into #linuxdc know, I've been attempting to port Qt 
> Embedded to DC Linux.
> 
> I've learnt alot about NFS and much else on the way!
> 
> But now I can run the examples they report the error "QServerSocket could not 
> bind tp file /tmp/...." etc 
> Anybody know what it means?
> 

Hmm ... just a guess ... but obviously you need a writable /tmp directory.

So create one :P.

M. R.

Re: [linuxdc-dev] Viruses - off topic, but interesting?

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Wed, Sep 26, 2001:

> 
> But I've been unsuccesful because every version I've looked at appears to 
> contain the backdoor/IRC-Flood/D virus (I think that's what it was called).
> 

Um .. have you written to the GIMP or GTK+ developers about this?  Seems
like they would know what's what.

M. R.

[linuxdc-dev] Compiling Qt Embedded

[Adrian M. <ad...@mc...>]

As those who listen into #linuxdc know, I've been attempting to port Qt 
Embedded to DC Linux.

I've learnt alot about NFS and much else on the way!

But now I can run the examples they report the error "QServerSocket could not 
bind tp file /tmp/...." etc 
Anybody know what it means?