Natanael Copa schrieb: >> QUESTION: Are there any useful configuration tips for dropbear? > > default dropbear config have just worked for me. OK
>> 6.) Configuration of busybox: busybox provides a lot of tools, but some >> tools should not be used. I have so far identified: >> - start-stop-daemon (provided by baselayout-2) > > I use bb start-stop-daemon (not with baselayout-2 though). It works for > almost all Gentoo scripts. (postgresql is one who does not) In baselayout-2 start-stop-daemon is a link to /sbin/rc . Therefore I should disable it in bb >> QUESTION: Are there any tools I should disable, too? Do I really need >> coreutils (and ncurses, which is pulled in by coreutils) or are the >> busybox tools enough (busybox provides about 69% of the tools in coreutils)? > > I think busybox coreutils should work. If it doesn not, we should fix > busybox. (if you give me a list, I can take a look at it when i get > time) OK, I put coreutils in package.provided. I will see, if this works out. If there are any problems concerning this, I will post it here. > Here below you also say you use sysvinit. Then you can turn off bb init In fact, at first I thought, baselayout-2 just works with sysvinit, but right now I'm not so sure anymore. It would be cool to get rid of sysvinit, but at the moment I will stay with it and see, if it works. I can later switch to bb init. By the way, do you have a bb inittab file, which works like the sysvinit inittab file for gentoo? > i think. (unless you use it in initramfs) Why? I plan to put the complete file system in initramfs and just use it . Are there any problems with sysvinit? > why not just run mdev -s and let mdev create everything. Well, I think, static files are faster than running mdev. The reason for this is, that I'm a genkernel user and every time my desktop pc boots, it "hangs" a second or two at the mdev command, or at least I think so, because this is the last message given by genkernel before the "hang" time. I have not really tested, if this hang is connected to mdev, so if you say, this should be faster, I would be happy to use mdev in my setup. > >> All files I need to fully use my media-pc I will create after booting >> with mdev (from busybox) and copy them to my build machine, since I want >> to use static device files. > > You might want to have a look at my medv config and /lib/mdev/* scripts > shipped in my alpine-baselayout. > > http://dev.alpinelinux.org/alpine/alpine-baselayout/ > > I have also an init.d/mdev script that let me use mdev as an udev > replacement. I will definitely look at this! > >> 8.) System configuration: up to now I have only two QUESTIONs: >> -How do I use locals with uclibc? > > You mean locales? uclibc has locale support but its not good :-( Yes, locales. Not so good means? I want german locales, because my wife will use this pc, too. Can you point to good reading about uclibc and locales? By the way: bb and dropbear provide both a compilation config file in portage/savedconfig and both have the USE flag savedconfig . uclibc does have this USE flag, too, but does not provide a compilation config file. Do you know why? > >> -Do I have to tell baselayout-2, that I use ash as shell? > > I dunno, I think /bin/sh pointing to busybox should be enough. OK. Is busybox sh the shell, which is set in the compilation config (in my case ash)? > >> 9.) install grub. >> >> 10.) Build kernel and initramfs from ROOT >> >> 11.) Boot media-pc with livecd and copy kernel, initramfs and grub files >> to media-pc. QUESTION: Since I have already grub installed on my >> media-pc, grub installation to boot sector is not a problem, but what do >> you do, if you do not have grub installed? Boot with livecd, extract >> initramfs and use installed grub to install grub to boot sector? > > You can use grub on livecd. Ah, OK, have not thought about that! > >> QUESTION: Do you have any remarks? > > You could try busybox-1.7.x. Its a good release. I switched to bb 1.7.1 . Thanks for your input! Marc -- [EMAIL PROTECTED] mailing list
