Hi all. New to sisela, but have linux experience, including source based distro sorcerer. Anyway, I was wondering how hard it would be to add packages to the build process of this distribution. I have built a small computer whos main purpose should be to function as a wireless DSL router, but I also want to run samba, cups,httpd and squid on it. I realize that the main objective of this distro is to be tiny, but I am interested in extending it for myself pretty much... It would also be nice if I could include the madwifi wireless drivers for my card, but they are curretly available only by cvs. Thanks in advance, MixMatch
On Wed, Jan 28, 2004 at 02:52:51AM -0500, MixMatch wrote:
I was wondering how hard it would be to add packages to the build process of this distribution.
It's fairly straightforward in principle.
Get and build the source, then try to make your new package compile correctly with the uClibc tools and uClibc/kernel source from the Sisela build tree. When it seems to work, copy your binaries to the appropriate place in build/install, delete the old rootfs and rootfs.bz2, and run make in the Sisela tree again to build a new image.
It would also be nice if I could include the madwifi wireless drivers for my card, but they are curretly available only by cvs.
Build the modules against the Linux source in your Sisela tree, copy them to build/modules and re-run the build as above.
Same goes for anyone else wanting drivers added - I'm also willing to do special builds on request if people tell me what they want and it's feasible :-)
Martin
Hi Martin and all,
I had GREAT luck with 0.2 :)). Basically I used it until I was able to find another dist. that worked on my old laptop. I just followed the GREAT directions and had it building on my RH8.0 machine. 0.3 doesn't seem to come up from the floppy and I haven't gotten into the sources enough to figure out what is happening.
By using sisela 0.2 with a friends wireless AP, I was finally able to download iso files. That's how I got my first copy of DamnSmall Linux, which is what I am now using on it.
A real floppy Linux is MOST NICE so sisela is in my tool kit :))
I would love to have the Atmel wireless usb driver working with sisela. That and kismet would make a great war driving box.
regards, john
On Wed, 28 Jan 2004, Martin Ling wrote:
On Wed, Jan 28, 2004 at 02:52:51AM -0500, MixMatch wrote:
I was wondering how hard it would be to add packages to the build process of this distribution.
It's fairly straightforward in principle.
Get and build the source, then try to make your new package compile correctly with the uClibc tools and uClibc/kernel source from the Sisela build tree. When it seems to work, copy your binaries to the appropriate place in build/install, delete the old rootfs and rootfs.bz2, and run make in the Sisela tree again to build a new image.
It would also be nice if I could include the madwifi wireless drivers for my card, but they are curretly available only by cvs.
Build the modules against the Linux source in your Sisela tree, copy them to build/modules and re-run the build as above.
Same goes for anyone else wanting drivers added - I'm also willing to do special builds on request if people tell me what they want and it's feasible :-)
Martin
-- http://the.earth.li/~martin/
Sisela mailing list Sisela@earth.li http://www.earth.li/cgi-bin/mailman/listinfo/sisela
On Thu, Jan 29, 2004 at 06:01:59AM -0500, jmh2 wrote:
0.3 doesn't seem to come up from the floppy and I haven't gotten into the sources enough to figure out what is happening.
Where does it seem to get stuck?
1.68MB disks are problematic - not usually in reading them, but in writing them. The easiest thing to do is to try writing the disk in another drive. It's also worth trying the formatting with superformat, which will attempt to autodetect any deviation in the alignment of your drive and compensate.
superformat /dev/fd0 sect=21
should apply the appropriate formatting.
I would love to have the Atmel wireless usb driver working with sisela. That and kismet would make a great war driving box.
Kismet is *big*, sorry :-) - but people seem to keep asking me for a Sisela-like disk for wardriving, so I'll have a go at some point.
I can build you a version with the Atmel USB driver, if you tell me which device you have from:
http://at76c503a.berlios.de/devices.html
The reason I need to know is that the firmware images are different for each variant, and I can't fit all of them on.
Martin
Hi Martin,
I would suggest a 2nd disk for things like kismet, ethereal and drivers. Just mount it after sisela gets going and load/execute from it.
Only one Atmel driver worked for me. I couldn't find it again on the web this afternoon, so I will have to keep looking. The others crash the kernel (with messages) (RH8.0). So once I get it going again I'll let you know which one works.
I think a floppy war driving set is a good idea. Incidently 1.680 seems to work OK here. But I would suggest multiple floppies make more sense to me. Maybe there is already a dist. that is close enough that it's drivers and programs can be used as is?
Regards war driving, the linksys usb is on a 6 foot cable so it could be plugged into laptop inside whilst antenna is on the roof :)
regards, john
On Thu, 29 Jan 2004, Martin Ling wrote:
On Thu, Jan 29, 2004 at 06:01:59AM -0500, jmh2 wrote:
0.3 doesn't seem to come up from the floppy and I haven't gotten into the sources enough to figure out what is happening.
Where does it seem to get stuck?
1.68MB disks are problematic - not usually in reading them, but in writing them. The easiest thing to do is to try writing the disk in another drive. It's also worth trying the formatting with superformat, which will attempt to autodetect any deviation in the alignment of your drive and compensate.
superformat /dev/fd0 sect=21
should apply the appropriate formatting.
I would love to have the Atmel wireless usb driver working with sisela. That and kismet would make a great war driving box.
Kismet is *big*, sorry :-) - but people seem to keep asking me for a Sisela-like disk for wardriving, so I'll have a go at some point.
I can build you a version with the Atmel USB driver, if you tell me which device you have from:
http://at76c503a.berlios.de/devices.html
The reason I need to know is that the firmware images are different for each variant, and I can't fit all of them on.
Martin
-- http://the.earth.li/~martin/
Sisela mailing list Sisela@earth.li http://www.earth.li/cgi-bin/mailman/listinfo/sisela