I'm using Kiwi to build a boot CD based on OpenSUSE 13.1. I want the disk ISO image to be as tiny as possible. I managed to get the read-only filesystem down to only 100MB, but for reasons unknown, the initrd file is 80MB on its own. (!!)
Is there some way I can convince Kiwi to produce a smaller initrd?
Is there a way to take the initrd image that Kiwi has produced and shrink it somehow?
Datanaut wrote:I've installed CrunchBang.I'm using CrunchBang.I'm logged into CrunchBang.I'm loving CrunchBang.I'll help CrunchBang by donating, but more importantly, promoting.Enjoy the company, and you can help by washing up your cup after helping yourself to coffee and cake in the crunchbang clubhouse
I have a number of remote branches (each with an IPSec site to site configuration. The main station has a Cisco 5510, the branches are each a Cisco ASA 5505. Works fine. I recently installed the paid version of the Kiwi Syslogd device at the main station and it works fine with the 5510.
Hello Crunchbang(#!) Member,I am a IT student here at philippines. Then our professor has give an OS review. Our group choose CrunchBang . Now my topic for the documentation for Crunchbang(#!) is Process Management. I don't have an idea about Process Management of Crunchbang(#!) . Please Help me to answer this question below about Process Management. 1.
I just installed Kiwi Syslog and have been receiving what intuitively seems like there might be a problem. I immediately started getting over 2000 Kernal.Alert Messages Per Hour and a few hours later it is now almost 6000 MPH.
Hey, I have used #! for about 2 years on my Asus EEE PC 701 netbook. Started with hearing about cruncheee. Searched it, installed it and got used to using crunchbang. Crunchbang is nothing short but a work of art.