Thank you very much for your job, Liam!
Now I am working in my Final Project of Technical Computer Science Career.
This document will help me much more reading a lot of documents :)
If I have any questions, can I use this same thread to ask? Thanks in advance,
Ozzy - well done, great info. Like Jaymes Driver, I used your process (slightly edited for use in command line only Ubuntu 12.04 LTS) to compile a new kernel with SCSI drivers included, for working with VMWare SAS disk virtual machines. Thanks mate :)
P.S. add a few more screen shots and it’s good for the wiki!
Hello Andy and all the helpful folks in the forums,
This tutorial is great and has me all set up with a generic image. The only issue I am running into right now is that the new Dell machines we are getting in at work don’t have all of their drives in the latest Driver packs.
I looked through their forums and found some tutorials on how to add your own DriverPacks, but they are about 6 years old and I haven’t gotten the steps to work yet, though still working on it. I have found How to add drivers to the existing Driver packs, but thsi means I will have to add the drivers everytime a new DriverPack comes out.
Anyone have any idea how to add my own driver pack so I can put all the missing drivers in it and not have to mess with the driverpacks that can be obtained from the DriverPack site?
If I find the solution myself I will post here.
@jgallo We must be aware of a few things here.
The github site always contains the latest release. So (currently) the files contained are for FOG 1.5.0. If you are working on a down level version of FOG then you need to take the route of extracting the inits. You don’t need to repack the inits, because you only need the file you want to tweak. Once you have the file you want to patch, then you may unmount the loop directory and remove the unpacked init.
The structure of files may change from release to release. In the case of FOS, it was split out into its own branch. The correct path (as of 1.5.0) to the file in question is: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.man.reg (full disclosure, it took me a bit to find the right path too).
The only caution is as newer versions of FOG are released, your patch file may become stale, where you might need to update a newer versions of fog.man.reg as newer versions of FOG are released. The risk is that you might be applying an older version of fog.man.reg over an updated version fog.man.reg breaking FOG without a clue why.
The rest of the instructions by @JGallo are still accurate (at least for 1.5.0). You can still use the post init scripts to “patch” the current FOS image as in the original post.
I think the video would be the best option? Would I be adding in the additional storage node linking to the path.