similar to: Unable to build appliance

On Fri, May 14, 2010 at 11:02:36PM -0400, Aron Griffis wrote: > Hi again Rich, > > I'm trying to use febootstrap to install either rawhide or f13, > but my attempts are failing. > > $ sudo febootstrap fedora-13 /mnt/jubjub-f > ... > Running rpm_check_debug > ERROR with rpm_check_debug vs depsolve: > libc.so.6()(64bit) is needed by procmail-3.22-25.fc12.x86_64

Systems such as Debian (and thus Ubuntu) operate with 64-bit programs in /lib, with /lib64 a symlink to it: as a result, they apply a patch to their glibc adjusting the default search path of the 64-bit dynamic loader (only used if the library is not found in ld.so.cache) to look in /lib, and instruct the 32-bit one to look in /lib32. Because fakechroot is implemented via LD_PRELOAD, it ends up

As part of the oVirt Node[1] project, I'm going to P.O.C. a version of the node using febootstrap 2.x instead of livecd-creator. The main reasons in doing this is for allowing a r/w root filesystem without some hacky overlayfs and just to see if it can be done. On IRC, rwmjones mentioned a few issues he ran into with febootstrap 2.x where some rpms had %post scripts which aren't really

I spent the last couple of days rethinking how we go about building the appliance, and the difficulties we have porting that to other Linux distros. I've come up with a much better way that works better and faster on (so far) Fedora and Debian (probably on Ubuntu too, not tried it), and should be much simpler to port to other distros. The current way is to do: +------------------+

[PATCH 1/3] Add a core_pattern debug command The first patch is just a rework of Rich's earlier core dump patch. It turns it into a debug subcommand so it can be called at any time. This also has the advantage of explicitly labelling an extremely untidy API as debug. [PATCH 2/3] Call sync after guestfsd exits The second patch seems to be required for cores to be dumped reliably. I was able to

$SUBJECT, basically. :) -- Matthew Miller • Hosted and Interactive Experience Architect Fedora Cloud Architect ☁ ☁ ☁ <mattdm@fedoraproject.org>

Hello - any help is greatly appreciated. I am trying to compile zaptel on debian 2.4.26-1-386. I have a single X100P card installed. When I run '/usr/src/zaptel/make clean;make install' I get the following: depmod: *** Unresolved symbols in /lib/modules/2.4.26-1-386/misc/torisa.o depmod: *** Unresolved symbols in /lib/modules/2.4.26-1-386/misc/zaptel.o /sbin/depmod -a depmod: ***

Hello people, Went to IRC and zoa helped a bit by saying me to Do a insmod zaptel and insmod wcusb When I did the insmod zaptel it worked fine, but when I did the wcusb it said asterisk:/usr/src/zaptel# insmod wcusb Using /lib/modules/2.4.24/misc/wcusb.o /lib/modules/2.4.24/misc/wcusb.o: unresolved symbol usb_submit_urb_R3d6f870e /lib/modules/2.4.24/misc/wcusb.o: unresolved

Hello, What's wrong ? make install ..... options torisa base=0xd0000 alias char-major-196 torisa alias wcfxs wctdm alias wct2xxp wct4xxp if [ -d /etc/modutils ]; then \ /sbin/update-modules ; \ fi depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-386/misc/wctdm24xxp.o depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-386/misc/zaptel.o depmod: *** Unresolved symbols in

Hello, What can I do when attempting to run depmod with these options: -Ae -b base -F System.map to prevent depmod from appending the following path: lib/modules/2.6.18-53.1.14.el5/modules.dep.temp to the specified base? I am specifying a base as: -b ./lib/modules/2.6.16.23-custom So depmod errors/fails with: FATAL: Could not open

I am trying to compile 2.4.10-ac11 w/ the ext3-2.4-0.9.12-2410ac11 patch. I'm getting unresolved symbols w/ ext3 module: cd /lib/modules/2.4.10-ac11; \ mkdir -p pcmcia; \ find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.10-ac11; fi depmod: *** Unresolved symbols in

Phil Perry wrote: > On 27/09/17 16:49, m.roth at 5-cent.us wrote: >> Hi, folks, >> >> Well, still more fun (for values of fun approaching zero): >> >> 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. >> Even though I installed the 9 repo, all that I get is 8. I've >> used their webform, and an waiting on a

Hi, Still trying to get libguestfs appliance test to work on Ubuntu Lucid. I figured out my umask was causing problems and fixed that. now I'm on to a new problem. libguestfs-test-tool reports the following: febootstrap: mounting new root on /root febootstrap: chroot /proc/uptime: No such file or directory execl: /init: No such file or directory febootstrap: debug: listing directory /

Could anyone help me out, i've got a situation here. :-) I already contacted RTLinux users with no success, I hope ext3 users can help! I have a 2.2.19 kernel patched with RTLinux 3.1, clean and working. I found and applied the ext3 for 2.2.19 kernel patch. Patch went fine (like in README). I was able to tune2fs -j /dev/hda1 (activate the journal). And it actually works. 1) I was not able

Hi, folks, Well, still more fun (for values of fun approaching zero): 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. Even though I installed the 9 repo, all that I get is 8. I've used their webform, and an waiting on a reply. 2. I remove all nvidia packages. 3. It appears that the kmod-nvidia is what I need; that's what nvidia-detect

Hi all. I've been lurking here for a couple weeks just trying to get an idea of how to install asterisk. I'm running Debian with a custom kernel version 2.4.18. I think I've got all the dependencies installed - debian packages readline4 and openssl are installed. It's a very barebones install with only the packages relevant to building a kernel and asterisk installed. The

Hello all, I downloaded the linux-2.6.16.16.tar.bz2 (www.kernel.org) and xen-3.0.2-src.tgz. I tried on Debian: # tar -xvzf xen-3.0.2-src.tgz # tar -xvjf linux-2.6.16.16.tar.bz2 # cd xen-3.0.2-2 # mkbuildtree ../../linux-2.6.16.16 # cd ../../linux-2.6.16.16 # make menuconfig (I made a basic configuration) # make-kpkg --append-to-version=-686-xen --revision=1.0 -us -uc kernel_image However

Hello- I've been trying to scour both * and linux user group archives for a solution to this particular problem, but I am just plan stuck. I got the latest zaptel sources from cvs, uncommented ztdummy.o in Makefile, ran make; make install then, did depmod -a. All is well up until now. When i do modprobe ztdummy, i get this error: dv@sidetrack:/usr/local/src/zaptel# depmod -a

Hi all, Please let me know if this is not the right place to ask this question. I was trying to compile and build kernel 3.2.0, by following <Linux Administration - A Beginner's Guide> written by Wale Soyinka. Error occurs after running the following command: # new-kernel-pkg -v --mkinitrd --depmod --install 3.2.0-custom initrdfile is /boot/initrd-3.2.0-custom.img

Hello, i have downloaded the kernel 2.4.14 and the correspondig ext3 patch ext3-2.4-0.9.15-2414.gz. After this i extract the archiv at /usr/src, renamed the dir linux to linux-2.4.14 and made a symlink linux-2.4. I changed to the directory linux-2.4 and add the patch as decsribed on the website gunzip < ~/ext3-2.4-0.9.15-2414.gz | patch -p1. There was no error and the patch was successful.