gnaservicesinc
December 14th, 2011, 10:17 PM
Often it seem their are more then one way to do something but one best way. I am attempting something and I believe I have found a way but I'm not sure if it is the best way. So what I am going to do is layout what I need to do, how I have found to do it and then if somebody knows a better way or has feedback please reply.
I am planning on installing a minimal install of Ubuntu + snort on a computer that has no hard disk drive but rather it has a compact flash card that is seen as a HDD because it connects via the IDE port. It is important that everything loads into ram because obviously the CF over IDE is very slow. So I want to load everything into ram and not write back to the CF.
My plan is to, on my current Ubuntu desktop to follow the steps for a customised live cd from scratch (https://help.ubuntu.com/community/LiveCDCustomizationFromScratch) and use debootstrap to create a chroot, install everything I need and nothing more. Then when making the iso set up "toram" in the boot options. Then dd the image onto the CF card. Then when I want to update the system, I will go back into the chroot, update, and then remake the image and then DD that onto the card.
I have never done something like this before so I am not sure if that will work or if that is the best way to go about this. It might even be a really BAD way to go about it, IDK that is just what I have come up with in my search. It is also possible that I am being dumb and I have missed some well know method to do this. :D
So any feedback, suggestions, links to other methods, etc will all be welcome.
Also as more background: The system that will be booting from the CF has lots of ram, 8GB, a fast 3.6Gzh quad core CPU, and three PCI Express Intel PRO/1000 Server Adaptors (NIC cards)
Again, the goal is to make an image of a Ubuntu + Snort etc. Install that is all pre configured (The snort and networking configurations have already been created and turned into debs for easy install) The hard part being the image needs to not write back and stay in ram for speed because not only is the CF over IDE (So thats like what 133 MByte/s.) the CF card it's self would be like 20 MByte/s) so it would be a bad idea to be writing back.
Thanks!
I am planning on installing a minimal install of Ubuntu + snort on a computer that has no hard disk drive but rather it has a compact flash card that is seen as a HDD because it connects via the IDE port. It is important that everything loads into ram because obviously the CF over IDE is very slow. So I want to load everything into ram and not write back to the CF.
My plan is to, on my current Ubuntu desktop to follow the steps for a customised live cd from scratch (https://help.ubuntu.com/community/LiveCDCustomizationFromScratch) and use debootstrap to create a chroot, install everything I need and nothing more. Then when making the iso set up "toram" in the boot options. Then dd the image onto the CF card. Then when I want to update the system, I will go back into the chroot, update, and then remake the image and then DD that onto the card.
I have never done something like this before so I am not sure if that will work or if that is the best way to go about this. It might even be a really BAD way to go about it, IDK that is just what I have come up with in my search. It is also possible that I am being dumb and I have missed some well know method to do this. :D
So any feedback, suggestions, links to other methods, etc will all be welcome.
Also as more background: The system that will be booting from the CF has lots of ram, 8GB, a fast 3.6Gzh quad core CPU, and three PCI Express Intel PRO/1000 Server Adaptors (NIC cards)
Again, the goal is to make an image of a Ubuntu + Snort etc. Install that is all pre configured (The snort and networking configurations have already been created and turned into debs for easy install) The hard part being the image needs to not write back and stay in ram for speed because not only is the CF over IDE (So thats like what 133 MByte/s.) the CF card it's self would be like 20 MByte/s) so it would be a bad idea to be writing back.
Thanks!