Thanks for the reply. I actually did download the ifssystem and get it to compile and everything, but I kept getting an error about register_chrdev_Rsmp_00133218. The module would compile and almost work except for the error. I don't think it is specific to DL, but may just be the module itself that has a problem.

Again, thanks for the help.

-Brad

On Thu, Jan 22, 2009 at 10:34 PM, Serge Leschinsky <fish@infonet.nnov.ru> wrote:
Hi Bradlee,

the easiest way is to have development environment from which DL iso was
produced. Theoretically it should be able to compile one module only in another
(but similar) lfssystem and get it working, but I've never checked it.

If it's really important for you I can download lfssystem and packages for 1.2
and try to compile it.

PS. For ~100k custom code you can create a dir in /etc/ then save configs. The
binary will be saved on configuration media.

--
Serge


Bradlee Landis wrote:
> I tried to run it, and it worked fine, but my program did not work.
> What's the easiest way to compile the driver against the kernel? I
> really don't want to go through the build process. If I sent someone
> the .tar.gz file, could you return me a compiled module (lcm.o) that I
> could use?
>
> If it helps, here's the makefile sent with the driver:
> ------Makefile------
> #
> # Makefile for LCD driver and testprograms
> #
> CC = gcc
> #
> # Uncomment the correct line for your kernel-version!
> #
> #KERNEL = -DKERNEL20
> KERNEL = -DKERNEL21
>
> INSTALLDIR = /lib/modules/`uname -r`/misc/
>
> #
> # If you want some debugging output then add -DDEBUG to the CFLAGS
> # Attention: This will fill your syslog quite fast!
> #
> CFLAGS  =       $(KERNEL) -D__KERNEL__ -I/usr/src/linux-2.4/include -Wall \
>                -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe \
>                -ffixed-8 -DMODULE -DMODVERSIONS -finline-functions \
>                -include /usr/src/linux-2.4/include/linux/modversions.h \
> # -DLCM_DEBUG
> LDLAGS = -O2 -Wall -I/usr/src/linux-2.4/include -Wstrict-prototypes \
> -D__KERNEL__ -DMODULE -Xlinker \
> -include /usr/src/linux-2.4/include/linux/modversions.h
>
> OBJS = lcd_module.o lcd.o
>
> lcm.o: lcm_module.c lcm_module.h lcm.h
> $(CC) $(CFLAGS) -c lcm_module.c -o lcm.o
>
> .PHONY: install clean
>
> install:
> [ -d $(INSTALLDIR) ] || mkdir -p $(INSTALLDIR)
> install -c -m644 lcm.o $(INSTALLDIR)
> clean:
> rm -f *.o
> -------------------------
>
>
> On Wed, Jan 21, 2009 at 9:16 AM, Bradlee Landis <bradleelandis@gmail.com> wrote:
>> Hi,
>>
>> I've been trying to add custom code (about 104K in size) to devil
>> linux (1.2) by remaking the bootcd.iso. When I run mkisofs, the iso is
>> more than twice as big as the original (~580M vs the original 250M). I
>> tried running mkisofs straight and it came out larger. The -z flag
>> (which seems to suggest it compresses the image) only makes it larger.
>>
>> I also attempted to use the information at
>> http://www.linuxfromscratch.org/hints/downloads/files/OLD/bootlfscd.txt,
>> but I have not been able to find the boot.img file needed to make it
>> bootable.
>>
>> Is there a special command that is used to make the original? Can I
>> use the larger file without problems?
>>
>> Thanks,
>> -Brad Landis
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Devil-linux-discuss mailing list
> Devil-linux-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Devil-linux-discuss mailing list
Devil-linux-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss