Sisela

sisela@earth.li

68 discussions

shutdown and reboot
by Mike Zimmerman 13 May '09

13 May '09

How would I go about rebooting? I have sisela running at a few off-sites and need to reboot through ssh, have no physical access. I tried "shutdown -r now" like you would on debian based distros but it was command not recognized. Thanks, Mike

2 1

PPPOE
by Nyitrai István 27 Oct '07

27 Oct '07

Hi! Can you or I pack-in an PPPoE handler program into sisela? If yes, how can I do this? Thank you for your help. sisela is a very great job, keep up the good work! -- Istvan Nyitrai

1 0

insert executable
by Prda Prdic 08 Oct '07

08 Oct '07

Hello Martin I have problem with inserting executable in sisela-0.3 floppy image. Need to put "wlanconfig" executable in rootfs and make it executable. My kernel is compailed with atheros drivers and I need "wlanconfig" to manipulate it. Can you help me? Greetings

2 1

Static Leases in udhcpd
by John Goodwin 19 Dec '06

19 Dec '06

Hi, I was wondering if it would be too much trouble to update the udhcpd portion of Sisela to include static leases. If not, do you have any information on compiling Sisela? I looked in the source, and did not find very much other than some patches. I don't see the source code baseline. -- Thanks, John Goodwin

2 1

wf 511 driver
by Stipe 15 Oct '06

15 Oct '06

If it is not a problem can you add drivers for wf 511 wifi card to sisela for floppy and send it on my email? Thanks a lot. newb

1 0

ndiswrapper
by Larry Cohen 04 Jun '06

04 Jun '06

I have just downloaded sisela-0.3. It boots perfectly on the old hardware I want to use. Only one problem - no ndiswrapper. Don't want to buy a new wireless card and the one I have is broadcom based. Can anyone advise an easy way to add that to the CD version (the floppy would be better). I would like to avoid building from scratch, if possible. I am using a Zenwalk (Slack) system and would not like to fool around with Debian. Help would be much appreciated. Best Regards, Larry

3 2

Boot option attempts...
by Chris Scott 18 May '06

18 May '06

I sent this reply to ChrisM off-list but in reflection I'm sending it to the list to help people in future who search the archives requiring similar help. Chris ---------- Forwarded message ---------- From: Chris Scott <chrisjscott(a)gmail.com> Date: 18-May-2006 13:54 Subject: Re: [sisela] Boot option attempts... To: chris.mooney(a)kelleylog.com Hi If /floppy is empty then it sounds like you haven't mounted the floppy drive to this point and I don't recall Sisela doing that automatically but I could be wrong. Run something like: "mount /dev/fd0 /floppy" You may need to use; "mount /dev/fd0u1680 /floppy" as the floppy is in the non-standard format. Then run "mount" to see that it is mounted and "ls /floppy" to see the files. If that worked you can then proceed with vi and sync. This is more of a general Linux problem than a Sisela one. There used to be an IRC channel where we would discuss Sisela. If you want more interactive help then bug me and I'll maybe resurrect the channel. It died due to lack of interest but I'm still willing to help others. Hope that helps Chris On 18/05/06, Christopher T. Mooney <chris.mooney(a)kelleylog.com> wrote: > OK, > > Many thanks to you ChrisS and Farmalar for answering... I > tried going to the /floppy directory, running vi to create a boot.sh script, > put my networking commands in it (ifconfig eth0 192.168.0.1 netmask > 255.255.255.0 up), and typing :wq to exit. I do an ls and see boot.sh there > in the floppy directory. Now I do a sync as suggested, and reboot (using > the reboot command, not ctl+alt+del). When sisela comes back up I go to the > /floppy directory and do an ls. The directory is empty... Any Ideas? It > never really seemed to access the floppy when I did the sync. If the > machine was able to read the floppy it should be able to write to it, > correct? > > Thanks again! > > --ChrisM > > BTW: Farmalar, your english is quite good. Don't knock yourself! I > appreciate you even attempting it. :-) > > /** > * Christopher T. Mooney > * Senior Software Engineer > * Kelley's Logistics Support Systems > * > * <mailto:chris.mooney@kelleylog.com> > * <http://www.kelleylog.com> > * > * 937.879.3483 > */ > -----Original Message----- > From: sisela-bounces(a)earth.li [mailto:sisela-bounces@earth.li] On Behalf Of > sisela-request(a)earth.li > Sent: Wednesday, May 17, 2006 07:00 > To: sisela(a)earth.li > Subject: Sisela Digest, Vol 2, Issue 2 > > Send Sisela mailing list submissions to > sisela(a)earth.li > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.earth.li/cgi-bin/mailman/listinfo/sisela > or, via email, send a message with subject or body 'help' to > sisela-request(a)earth.li > > You can reach the person managing the list at > sisela-owner(a)earth.li > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of Sisela digest..." > > > Today's Topics: > > 1. Re: Saving boot options (Chris Scott) > 2. Re: Saving boot options (Farmalar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 May 2006 15:15:21 +0100 > From: "Chris Scott" <chrisjscott(a)gmail.com> > Subject: Re: [sisela] Saving boot options > To: "discussion of the Sisela networking boot disk" <sisela(a)earth.li> > Message-ID: > <9fcc08fd0605160715j47279682w3bcb061a868f0a07(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi > > Did you run "sync" to actually write the file to the floppy? IIRC you can > put BusyBox shell commands into boot.sh on the floppy and it will then > execute them on boot. > > It's been a while since I've run Sisela but if you need better help I could > fire it up and have a look. This list is probably your best shot for > support. > > Cheers > > Chris > > On 15/05/06, Christopher T. Mooney <chris.mooney(a)kelleylog.com> wrote: > > Hello, > > > > I am just getting started with Sisela, and am a mite confused > > about how to save commands to be run on system startup. Sisela tells > > me that if I save a file in the /floppy directory called > > boot.<something> (I can't remember quite what the filename is, and I > > don't have the machine I am testing out Sisela on here at work), then > > Sisela will run those commands upon startup. I tried doing this, but > > after re-boot, the file was gone! Of course this seemed obvious to me > > when I remembered that the root filesystem is a bz2 image, I just > > thought that perhaps sisela would save the boot command file back to > > the compressed image file on shutdown. Is there a way to force sisela > > to do this? Or do I need to build sisela from the sources or just > > create my own filesystem image to load on the boot floppy? Any help I > > can get here would be most appreciated. I think Sisela is ultimately cool > and am really looking forward to using it! > > > > Thanks! > > > > Chris > > > > /** > > * Christopher T. Mooney > > * Senior Software Engineer > > * Kelley's Logistics Support Systems > > * > > * <mailto:chris.mooney@kelleylog.com> > > * <http://www.kelleylog.com> > > * > > * 937.879.3483 > > */ > > > > > > > > _______________________________________________ > > Sisela mailing list > > Sisela(a)earth.li > > http://www.earth.li/cgi-bin/mailman/listinfo/sisela > > > > > -- > Chris Scott > chrisjscott(a)gmail.com > > ------------------------------ > > Message: 2 > Date: Wed, 17 May 2006 07:57:13 -0300 > From: "Farmalar" <farmalar(a)terra.com.br> > Subject: Re: [sisela] Saving boot options > To: "discussion of the Sisela networking boot disk" <sisela(a)earth.li> > Message-ID: <000a01c679a0$a8733a90$0500a8c0@Micro4> > Content-Type: text/plain; charset="iso-8859-1" > > Hello friend! > I4m not expert on linux and I don4t speak English very well too, but I > will tray to explain to you.Ok? > You just need to create a fille in the floppy directory: > vi boot.sh > In my case, I put inside it : > ifconfig eth0 up > ifconfig eth0 192.168.0.1 netmask 255.255.255.0 > and more > > I hope , I could help you and.... > sorry for my bad English.... > > > > > ----- Original Message ----- > From: "Christopher T. Mooney" <chris.mooney(a)kelleylog.com> > To: <sisela(a)earth.li> > Sent: Monday, May 15, 2006 9:49 AM > Subject: [sisela] Saving boot options > > > > Hello, > > > > I am just getting started with Sisela, and am a mite confused about > > how to save commands to be run on system startup. Sisela tells me > > that if > I > > save a file in the /floppy directory called boot.<something> (I can't > > remember quite what the filename is, and I don't have the machine I am > > testing out Sisela on here at work), then Sisela will run those > > commands upon startup. I tried doing this, but after re-boot, the file > was gone! > Of > > course this seemed obvious to me when I remembered that the root > filesystem > > is a bz2 image, I just thought that perhaps sisela would save the boot > > command file back to the compressed image file on shutdown. Is there > > a > way > > to force sisela to do this? Or do I need to build sisela from the > > sources or just create my own filesystem image to load on the boot > > floppy? Any > help > > I can get here would be most appreciated. I think Sisela is > > ultimately > cool > > and am really looking forward to using it! > > > > Thanks! > > > > Chris > > > > /** > > * Christopher T. Mooney > > * Senior Software Engineer > > * Kelley's Logistics Support Systems > > * > > * <mailto:chris.mooney@kelleylog.com> > > * <http://www.kelleylog.com> > > * > > * 937.879.3483 > > */ > > > > > > > > _______________________________________________ > > Sisela mailing list > > Sisela(a)earth.li > > http://www.earth.li/cgi-bin/mailman/listinfo/sisela > > > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.1.392 / Virus Database: 268.5.6/339 - Release Date: > > 14/5/2006 > > > > > > > > > ------------------------------ > > _______________________________________________ > Sisela mailing list > Sisela(a)earth.li > http://www.earth.li/cgi-bin/mailman/listinfo/sisela > > > End of Sisela Digest, Vol 2, Issue 2 > ************************************ > > > > _______________________________________________ > Sisela mailing list > Sisela(a)earth.li > http://www.earth.li/cgi-bin/mailman/listinfo/sisela > -- Chris Scott chrisjscott(a)gmail.com -- Chris Scott chrisjscott(a)gmail.com

2 1

Boot option attempts...
by Christopher T. Mooney 18 May '06

18 May '06

OK, Many thanks to you ChrisS and Farmalar for answering... I tried going to the /floppy directory, running vi to create a boot.sh script, put my networking commands in it (ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up), and typing :wq to exit. I do an ls and see boot.sh there in the floppy directory. Now I do a sync as suggested, and reboot (using the reboot command, not ctl+alt+del). When sisela comes back up I go to the /floppy directory and do an ls. The directory is empty... Any Ideas? It never really seemed to access the floppy when I did the sync. If the machine was able to read the floppy it should be able to write to it, correct? Thanks again! --ChrisM BTW: Farmalar, your english is quite good. Don't knock yourself! I appreciate you even attempting it. :-) /** * Christopher T. Mooney * Senior Software Engineer * Kelley's Logistics Support Systems * * <mailto:chris.mooney@kelleylog.com> * <http://www.kelleylog.com> * * 937.879.3483 */ -----Original Message----- From: sisela-bounces(a)earth.li [mailto:sisela-bounces@earth.li] On Behalf Of sisela-request(a)earth.li Sent: Wednesday, May 17, 2006 07:00 To: sisela(a)earth.li Subject: Sisela Digest, Vol 2, Issue 2 Send Sisela mailing list submissions to sisela(a)earth.li To subscribe or unsubscribe via the World Wide Web, visit http://www.earth.li/cgi-bin/mailman/listinfo/sisela or, via email, send a message with subject or body 'help' to sisela-request(a)earth.li You can reach the person managing the list at sisela-owner(a)earth.li When replying, please edit your Subject line so it is more specific than "Re: Contents of Sisela digest..." Today's Topics: 1. Re: Saving boot options (Chris Scott) 2. Re: Saving boot options (Farmalar) ---------------------------------------------------------------------- Message: 1 Date: Tue, 16 May 2006 15:15:21 +0100 From: "Chris Scott" <chrisjscott(a)gmail.com> Subject: Re: [sisela] Saving boot options To: "discussion of the Sisela networking boot disk" <sisela(a)earth.li> Message-ID: <9fcc08fd0605160715j47279682w3bcb061a868f0a07(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Did you run "sync" to actually write the file to the floppy? IIRC you can put BusyBox shell commands into boot.sh on the floppy and it will then execute them on boot. It's been a while since I've run Sisela but if you need better help I could fire it up and have a look. This list is probably your best shot for support. Cheers Chris On 15/05/06, Christopher T. Mooney <chris.mooney(a)kelleylog.com> wrote: > Hello, > > I am just getting started with Sisela, and am a mite confused > about how to save commands to be run on system startup. Sisela tells > me that if I save a file in the /floppy directory called > boot.<something> (I can't remember quite what the filename is, and I > don't have the machine I am testing out Sisela on here at work), then > Sisela will run those commands upon startup. I tried doing this, but > after re-boot, the file was gone! Of course this seemed obvious to me > when I remembered that the root filesystem is a bz2 image, I just > thought that perhaps sisela would save the boot command file back to > the compressed image file on shutdown. Is there a way to force sisela > to do this? Or do I need to build sisela from the sources or just > create my own filesystem image to load on the boot floppy? Any help I > can get here would be most appreciated. I think Sisela is ultimately cool and am really looking forward to using it! > > Thanks! > > Chris > > /** > * Christopher T. Mooney > * Senior Software Engineer > * Kelley's Logistics Support Systems > * > * <mailto:chris.mooney@kelleylog.com> > * <http://www.kelleylog.com> > * > * 937.879.3483 > */ > > > > _______________________________________________ > Sisela mailing list > Sisela(a)earth.li > http://www.earth.li/cgi-bin/mailman/listinfo/sisela > -- Chris Scott chrisjscott(a)gmail.com ------------------------------ Message: 2 Date: Wed, 17 May 2006 07:57:13 -0300 From: "Farmalar" <farmalar(a)terra.com.br> Subject: Re: [sisela] Saving boot options To: "discussion of the Sisela networking boot disk" <sisela(a)earth.li> Message-ID: <000a01c679a0$a8733a90$0500a8c0@Micro4> Content-Type: text/plain; charset="iso-8859-1" Hello friend! I4m not expert on linux and I don4t speak English very well too, but I will tray to explain to you.Ok? You just need to create a fille in the floppy directory: vi boot.sh In my case, I put inside it : ifconfig eth0 up ifconfig eth0 192.168.0.1 netmask 255.255.255.0 and more I hope , I could help you and.... sorry for my bad English.... ----- Original Message ----- From: "Christopher T. Mooney" <chris.mooney(a)kelleylog.com> To: <sisela(a)earth.li> Sent: Monday, May 15, 2006 9:49 AM Subject: [sisela] Saving boot options > Hello, > > I am just getting started with Sisela, and am a mite confused about > how to save commands to be run on system startup. Sisela tells me > that if I > save a file in the /floppy directory called boot.<something> (I can't > remember quite what the filename is, and I don't have the machine I am > testing out Sisela on here at work), then Sisela will run those > commands upon startup. I tried doing this, but after re-boot, the file was gone! Of > course this seemed obvious to me when I remembered that the root filesystem > is a bz2 image, I just thought that perhaps sisela would save the boot > command file back to the compressed image file on shutdown. Is there > a way > to force sisela to do this? Or do I need to build sisela from the > sources or just create my own filesystem image to load on the boot > floppy? Any help > I can get here would be most appreciated. I think Sisela is > ultimately cool > and am really looking forward to using it! > > Thanks! > > Chris > > /** > * Christopher T. Mooney > * Senior Software Engineer > * Kelley's Logistics Support Systems > * > * <mailto:chris.mooney@kelleylog.com> > * <http://www.kelleylog.com> > * > * 937.879.3483 > */ > > > > _______________________________________________ > Sisela mailing list > Sisela(a)earth.li > http://www.earth.li/cgi-bin/mailman/listinfo/sisela > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.392 / Virus Database: 268.5.6/339 - Release Date: > 14/5/2006 > > ------------------------------ _______________________________________________ Sisela mailing list Sisela(a)earth.li http://www.earth.li/cgi-bin/mailman/listinfo/sisela End of Sisela Digest, Vol 2, Issue 2 ************************************

1 0

Saving boot options
by Christopher T. Mooney 17 May '06

17 May '06

Hello, I am just getting started with Sisela, and am a mite confused about how to save commands to be run on system startup. Sisela tells me that if I save a file in the /floppy directory called boot.<something> (I can't remember quite what the filename is, and I don't have the machine I am testing out Sisela on here at work), then Sisela will run those commands upon startup. I tried doing this, but after re-boot, the file was gone! Of course this seemed obvious to me when I remembered that the root filesystem is a bz2 image, I just thought that perhaps sisela would save the boot command file back to the compressed image file on shutdown. Is there a way to force sisela to do this? Or do I need to build sisela from the sources or just create my own filesystem image to load on the boot floppy? Any help I can get here would be most appreciated. I think Sisela is ultimately cool and am really looking forward to using it! Thanks! Chris /** * Christopher T. Mooney * Senior Software Engineer * Kelley's Logistics Support Systems * * <mailto:chris.mooney@kelleylog.com> * <http://www.kelleylog.com> * * 937.879.3483 */

3 2

ftp nat
by jgdsr jgdsr 13 Jun '05

13 Jun '05

How do I make Sisela as a router forward ftp sessions, being how I can't just modprobe ip_nat_ftp.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Sisela