I think you'd better use the standard init, which has support for
startup and shutdown scripts. If you customize them, together with a
custom inittab, then you can have your system start just your
application, but still do certain actions upon startup and shutdown.
This seems much
On Thu, Feb 14, 2008 at 2:22 PM, Pravin [EMAIL PROTECTED] wrote:
I think you'd better use the standard init, which has support for
startup and shutdown scripts. If you customize them, together with a
custom inittab, then you can have your system start just your
application, but
On Don, 2008-02-14 at 14:35 +0100, Thomas De Schampheleire wrote:
On Thu, Feb 14, 2008 at 2:22 PM, Pravin [EMAIL PROTECTED] wrote:
[]
But my only concern is that Will it affect the performance.. ??
I mean now I will be having one extra process with my application
which will need some
Hi,
I need to run single application on a linux kernel so that I can get
better performance.
For that I used init=/my_application as kernel parameter
This made sure that kernel will run only this application.
As there are no other processes, my application gets most of the resources,
and hence I
Hi,
On Feb 13, 2008 12:23 PM, Pravin [EMAIL PROTECTED] wrote:
Hi,
I need to run single application on a linux kernel so that I can get
better performance.
For that I used init=/my_application as kernel parameter
This made sure that kernel will run only this application.
As there are no
The problem comes when stopping the system.
The only way to do it is by pressing CTRL+ALT+DEL as CTRL+C does not
work in that mode.
Unfortunately, by using CTRL+ALT+DEL combination, Linux kernel does
the unclean unmounting of root filesystem.
This causes the file-system check on next boot
