Re: file mounted after debootstrap + udev

[EMAIL PROTECTED] writes: > Hi, > > I've been using debootstrap to produce my live linux based on debian > 2.6.18 . > At first, my system was built with devfs and everything was fine . > Recently, i moved to udev (i added kernel support + udev package) and > although the live linux works just fin

Re: file mounted after debootstrap + udev

On Jul 5, 12:20 pm, Daniel Baumann <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > - How come the build process starts an apache ? i thought it should > > just install it... > > because apache does no detect if he is in a chroot or not; use policy-rc > (see /usr/share/doc/sysv-rc/README.p

Re: file mounted after debootstrap + udev

[EMAIL PROTECTED] wrote: > - How come the build process starts an apache ? i thought it should > just install it... because apache does no detect if he is in a chroot or not; use policy-rc (see /usr/share/doc/sysv-rc/README.policy-rc.d) to avoid that. > - what's the "standard procedure" for build

file mounted after debootstrap + udev

Hi, I've been using debootstrap to produce my live linux based on debian 2.6.18 . At first, my system was built with devfs and everything was fine . Recently, i moved to udev (i added kernel support + udev package) and although the live linux works just fine , after the "build process" - there ar