in reply to Contributions to Linux via PerlMonks

How about a Perl/tk/GTK version of "make xconfig"? AFAIK, right now it's written in tk, but when you do a "make xconfig", you get the following garbage on your terminal:
nooky:/usr/src/linux-2.2.16# make xconfig
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts kconfig.tk
make[1]: Entering directory `/usr/src/linux-2.2.16/scripts'
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkparse.o
+ tkparse.c
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkcond.o 
+tkcond.c
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkgen.o t
+kgen.c
gcc -o tkparse tkparse.o tkcond.o tkgen.o
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
echo "set defaults \"arch/i386/defconfig\"" >> kconfig.tk
echo "set ARCH \"i386\"" >> kconfig.tk
cat tail.tk >> kconfig.tk
chmod 755 kconfig.tk
make[1]: Leaving directory `/usr/src/linux-2.2.16/scripts'
wish -f scripts/kconfig.tk

[download]

How cool would it be to do a perl version? That would remove the gcc compilation necessary, and i'm sure it would simplify the .config file parsing that happens. Anyone else have opinions here?

BlueLines

Disclaimer: This post may contain inaccurate information, be habit forming, cause atomic warfare between peaceful countries, speed up male pattern baldness, interfere with your cable reception, exile you from certain third world countries, ruin your marriage, and generally spoil your day. No batteries included, no strings attached, your mileage may vary.

Replies are listed 'Best First'.
RE (2): Contributions to Linux via PerlMonks
by tilly (Archbishop) on Aug 09, 2000 at 02:02 UTC
    We have been pre-empted by Eric Raymond working in Python.

    The current project is here.

    Personally I think doing a Linux-specific thing in Perl is somewhat silly. What is the point of having an ultra-portable language if the first thing you want to do is try to write unportable code? Just because you like Linux does not mean that kudra or KM shouldn't find it useful on *BSD...

[reply]
      well, the original question asked was regarding a PerlMonks contribution to linux. I do everything but play q3 on openBSD machines, and i wasn't intending to start a holy war over this. But I can't think of anything offhand that could both benefit from being rewritten in perl and is not platform specific. I mean, just because ping/telnet/lsof can be rewritten in perl doesn't necessarily mean they should be...

      how about a gui kernel configuration tool for *BSD?

      BlueLines

      Disclaimer: This post may contain inaccurate information, be habit forming, cause atomic warfare between peaceful countries, speed up male pattern baldness, interfere with your cable reception, exile you from certain third world countries, ruin your marriage, and generally spoil your day. No batteries included, no strings attached, your mileage may vary.
[reply]
        I apologize for not including all other OS's, all the points made were very very accurate. If Perl is meant to be an ultraportable language, then it should cross every platform. Good point all of you. THen I re-word my question: Would it be a viable option for a PerlMonks project that could cross all platforms, be very helpful, and perhaps garnish me some free pie? Okay two out of three ain't bad!

        Nobody expects the The Spanish Inquisition
[reply]

In Section Perl Monks Discussion