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@earth.li [mailto:sisela-bounces@earth.li] On Behalf Of sisela-request@earth.li Sent: Wednesday, May 17, 2006 07:00 To: sisela@earth.li Subject: Sisela Digest, Vol 2, Issue 2
Send Sisela mailing list submissions to sisela@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@earth.li
You can reach the person managing the list at sisela-owner@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@gmail.com Subject: Re: [sisela] Saving boot options To: "discussion of the Sisela networking boot disk" sisela@earth.li Message-ID: 9fcc08fd0605160715j47279682w3bcb061a868f0a07@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@kelleylog.com wrote:
Hello,
I am just getting started with Sisela, and am a mite confusedabout 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@earth.li http://www.earth.li/cgi-bin/mailman/listinfo/sisela
-- Chris Scott chrisjscott@gmail.com
------------------------------
Message: 2 Date: Wed, 17 May 2006 07:57:13 -0300 From: "Farmalar" farmalar@terra.com.br Subject: Re: [sisela] Saving boot options To: "discussion of the Sisela networking boot disk" sisela@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@kelleylog.com To: sisela@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@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@earth.li http://www.earth.li/cgi-bin/mailman/listinfo/sisela
End of Sisela Digest, Vol 2, Issue 2 ************************************