Ccomp5950
Member
- Reaction score
- 13
- Location
- Marshall, Texas
So I'm trying to roll my own Linux. So far I've run in to quite a few problems. I'm not following a walkthrough, this is all trial and error.
The reason I want to roll my own is because I want to learn mainly. But also I'll turn around and probably sell the "application". I've posted how I use a network install of linux to run antivirus. I use my server to autoupdate (every six hours it runs a version of this script) and maintain versions of certain programs that are ran in windows afterwards but I want to move this onto the "application" (that's the code name of this endevor until I come up with something snazzier).
1.) Run a S.M.A.R.T. check using smartctl and if problems are shown stop the process now.
2.) The computer boots into Linux using either PXE or a bootcd and automounts the windows partition and begins scanning using Avira. A pro license is required for this and if I turn around and sell this the CD / PXE images will have to be built on the go with the user uploading this license file.
3.) Once scanning is complete make a directory and push tools on it such as tdsskiller and malwarebytes or spybot. Also a batch file that installs(if applicable) and runs these tools. This directory will also contain the log file from avira.
4.) Add a RunOnce entry to the registry so the batch file runs when windows first comes up.
5.) Reboot and when windows comes up the tools run.
6.) Reboot once the tools are done and run notepad to display the log entries for tdsskiller and avira.
So first things first I started with this (out of date) walkthrough in mind to give me the basic scafolding for what I intended.
http://www.viaarena.com/build-your-own-linux-distro---part-i.aspx?ID=10&MCatID=3
I've deviated it and decided to use Bash instead of Busybox, mainly because I'm used to Bash. This brought some issues.
Because I'm not using Busybox I have to also include Init (Sys V Init), Coreutils, Linux-Utils, NetUtils.
Since I'm using a newer Kernel I also have to use udevd instead of the devfs he is planning on using.
I'm in a trial and error period with getty and init currently.
Lessons learned so far:
1.) If you use cramfs as your initial root disk image you have to compile cramfs support into the kernel (not module). Otherwise good luck mounting that "disk"
2.) You have to have init. Yep, I forgot to get init when I changed to bash instead of busybox (busybox builds in a version of init)
3.) You have to create /dev/console.
4.) Takes more then a day to trial and error your way through this.
The reason I want to roll my own is because I want to learn mainly. But also I'll turn around and probably sell the "application". I've posted how I use a network install of linux to run antivirus. I use my server to autoupdate (every six hours it runs a version of this script) and maintain versions of certain programs that are ran in windows afterwards but I want to move this onto the "application" (that's the code name of this endevor until I come up with something snazzier).
1.) Run a S.M.A.R.T. check using smartctl and if problems are shown stop the process now.
2.) The computer boots into Linux using either PXE or a bootcd and automounts the windows partition and begins scanning using Avira. A pro license is required for this and if I turn around and sell this the CD / PXE images will have to be built on the go with the user uploading this license file.
3.) Once scanning is complete make a directory and push tools on it such as tdsskiller and malwarebytes or spybot. Also a batch file that installs(if applicable) and runs these tools. This directory will also contain the log file from avira.
4.) Add a RunOnce entry to the registry so the batch file runs when windows first comes up.
5.) Reboot and when windows comes up the tools run.
6.) Reboot once the tools are done and run notepad to display the log entries for tdsskiller and avira.
So first things first I started with this (out of date) walkthrough in mind to give me the basic scafolding for what I intended.
http://www.viaarena.com/build-your-own-linux-distro---part-i.aspx?ID=10&MCatID=3
I've deviated it and decided to use Bash instead of Busybox, mainly because I'm used to Bash. This brought some issues.
Because I'm not using Busybox I have to also include Init (Sys V Init), Coreutils, Linux-Utils, NetUtils.
Since I'm using a newer Kernel I also have to use udevd instead of the devfs he is planning on using.
I'm in a trial and error period with getty and init currently.
Lessons learned so far:
1.) If you use cramfs as your initial root disk image you have to compile cramfs support into the kernel (not module). Otherwise good luck mounting that "disk"
2.) You have to have init. Yep, I forgot to get init when I changed to bash instead of busybox (busybox builds in a version of init)
3.) You have to create /dev/console.
4.) Takes more then a day to trial and error your way through this.
