RE: [lcd4linux] rpl_malloc?

[Luis.F.Correia <Lui...@se...>]

Michael, 

> 
> Hi Luis,
> 
> >>Hmm... I looked things up on the internet, and found this a little 
> >>glitch or bug in the autoconf area.
> >>
> >>Could you please try to comment out the "AC_FUNC_MALLOC" line from 
> >>configure.in?
> > 
> > I did commented out the #define malloc rpl_malloc in config.h, and
> > all went well
> 
> Fine. But I'd really like you to test my suggestion, because config.h 
> will be newly created with a 'configure'-run.

I'll do so later on.
My devel sys is stabler at home ;)

> 
> > Our firewall's filesystem is in RAM and is rebuilt on every boot.
> > Meaning that all /dev entries must be created also.
> > 
> > I need some help here, to use parport.o and to have the device
> > correctly created, what do I need to do?
> 
> Are you using devfs? THen all /dev entries will be created 
> automagically.
> 

No, we are not (yet) using devfs...

> Without devfs, you'll have to create the device manually. I'm 
> not shure 
> whats the correct name, but I'd suggest:
> 
> c 99 0 /dev/parport0
> c 99 1 /dev/parport1
> c 99 2 /dev/parport2
> 

That is done with mknod, right?
And when the parport module is loaded (which is not built in the kernel),
all will work?

> Of course you have to change the "Port" entry in the lcd4linux.conf.

I thought so...