root#akshit-Vostro-1550:/boot# mkinitrd -o initrd.img-2.6.32 2.6.32
mkinitrd: command not found
apt-get install mkinitrd-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package mkinitrd-tools
/initrd images contains device driver which needed to load rest of the operating system later on. Not all computer requires initrd, but it is safe to create one./
After a little research I found out that in Ubuntu mkinitramfs command is used instead of mkinitrd.
Refer to this question
Related
I'm trying to build snappy, but I end up getting the error
error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
When I go look in /lib/gcc/x86_64-redhat-linux/8/ I do find a file libatomic.so
Which has the contents
INPUT ( /usr/lib64/libatomic.so.1.2.0 )
then if I go looking in /usr/lb64/ only these files exist
libatomic_ops_gpl.so.1
libatomic_ops_gpl.so.1.1.2
libatomic_ops.so.1
libatomic_ops.so.1.1.1
I try doing yum install libatomic_ops.x86_64, it says nothing to do. That is the only package that comes up when doing yum search libatomic.
I'm confused with how to solve this issue. Thanks!
For what it matters, this is a redhat 8.6 machine.
This was solved by running dnf install gcc, this updated gcc and allowed for yum install libatomic to work
I have installed apt onto a system built by BitBake by adding the apt package to the IMAGE_INSTALL variable in my recipe.
apt-get and apt-cache now execute on the built system, but if I try to do anything useful with them (such as apt-get update or apt-cache search), I get the following error:
E: Could not open file /var/lib/dpkg/status - open (2: No such file or directory)
E: The package lists or status file could not be parsed or opened
After some preliminary searching, I found this exchange on the Yocto Project mailing list:
Hi,
I have some requirement with apt-get in yocto genearted rootfs.
I built the yocto source code with enabling the apt package.
But after booting the image on my machine and run the "apt-get" command for installing some package it gives the following error.
Could not open the file /var/lib/dpkg/status open(2: no such a file or directory).
The package lists or status files could not be parsed or opened.
This error is because you need to add package-management to EXTRA_IMAGE_FEATURES in local.conf,
PACKAGE_CLASSES ?= "package_deb"
EXTRA_IMAGE_FEATURES = "debug-tweaks package-management"
I've added package-management but don't see any different output.
After a touch /var/lib/dpkg/status, apt-get update returns the following:
Reading package lists...Done
How can I get apt into a functioning state through the use of BitBake metadata?
I have found a similar thread from the NXP website.
You would need to set up your own web server and provide all those packages and add the server URL to the source list. SourceList
In addition, you have to update the package manifest by running bitbake package-index and add PACKAGE_CLASSES ?= " package_deb" to conf/local.conf
I have successfully set up OPKG before. The steps are similar, you can find it here
I am trying to compile the i3 window manager from source, which requires a header file from libsn (#include ).
I cannot find libsn's source package from anywhere and would like help locating it.
Fourth result from typing "libsn" into Google gives this. It's not a "package", but in order to find a package, we'd have to know what kind of package you need - RPM, DEB, tar.gz, ....
You need to locate a current version of the package: startup-notification-devel
I was trying to build i3 on CentOS 7, which includes startup-notification but not startup-notification-devel. My compilation was successful by using the package from RepoForge for CentOS 6. Exact commands will depend on your distribution, but here are the general steps.
Install RPMforge: http://wiki.centos.org/AdditionalResources/Repositories/RPMForge
Quick reference for CentOS 6/7 x86_64:
wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.3-1.el6.rf.x86_64.rpm
rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
rpm -i rpmforge-release-0.5.3-1.el6.rf.*.rpm
Install the package:
yum install --enablerepo=rpmforge-extras startup-notification-devel
If you're not using RHEL/CentOS then you may want to download the source:
http://www.freedesktop.org/software/startup-notification/releases
Instructions to compile the libraries are available at the Linux From Scratch project:
http://www.linuxfromscratch.org/blfs/view/svn/x/startup-notification.html
Installing on Ubuntu 13.06 x64, it's an OpenVZ virtual machine.
Followed the script to the letter, and received a couple errors...
root#dev:/# sudo apt-get install linux-image-extra-`uname -r`
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-image-extra-2.6.32-042stab081.3
E: Couldn't find any package by regex 'linux-image-extra-2.6.32-042stab081.3'
root#dev:/#
though I am able to to:
root#dev:/# uname -r
2.6.32-042stab081.3
root#dev:/#
Then when I attempt to install I receive the following (this is a second attempt, so obviously stripped down)
root#dev:/# sudo apt-get install lxc-docker
Reading package lists... Done
Building dependency tree
Reading state information... Done
lxc-docker is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up lxc (0.9.0-0ubuntu3.4) ...
start: Job failed to start
invoke-rc.d: initscript lxc-net, action "start" failed.
dpkg: error processing lxc (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of lxc-templates:
lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43); however:
Package lxc is not configured yet.
dpkg: error processing lxc-templates (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of lxc-docker-0.6.3:
lxc-docker-0.6.3 depends on lxc; however:
Package lxc is not configured yet.
dpkg: error processing lxc-docker-0.6.3 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of lxc-docker:
lxc-docker depends on lxc-docker-0.6.3; however:
Package lxc-docker-0.6.3 is not configured yet.
dpkg: error processing lxc-docker (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
lxc
lxc-templates
lxc-docker-0.6.3
lxc-docker
E: Sub-process /usr/bin/dpkg returned an error code (1)
root#dev:/#
There are two distinct problems here.
Missing linux-image-extra-$(uname -r) package.
This is because the Docker installation script makes the bold assumption that if you are running kernel e.g. 3.8.0-30, it was installed from the package linux-image-3.8.0-30, and there should be a package linux-image-extra-3.8.0-30 containing extra files (including the AUFS module, which is necessary to run Docker). If you are running a kernel which is not a stock Ubuntu kernel, this assumption will be false, the linux-image-extra-... package won't exist, and the script will fail miserably.
However, if you know that you have AUFS support in your kernel (or that the AUFS module for your kernel is installed one way or another), you can safely skip this step.
Admittedly, the install script should investigate a bit more about your environment, and try to install this -extra- package only when it makes sense.
Cannot install lxc package inside an OpenVZ container.
The postinstall script of the lxc package tries to start the lxc-net service, which tries to setup the lxcbr0 bridge. I don't have an OpenVZ environment here to test this, but I think that you cannot create a bridge within an OpenVZ environment. Therefore, the service fails to start, and the postinstall script reports a failure, and the lxc package cannot be recorded as "installed", and the Docker package (lxc-docker) doesn't want to install if its dependencies are not correctly installed.
You can work around this by preventing the service from starting; for instance by doing:
echo exit 101 | sudo tee /usr/sbin/policy-rc.d
sudo chmod +x /usr/sbin/policy-rc.d
However, I am almost sure that you won't be able to run Docker within OpenVZ, because you won't be able to run containers inside OpenVZ. Again, I don't have an OpenVZ environment to test; but I would be very surprised if that worked.
I strongly suggest to run Docker on a more recent kernel (e.g. 3.8), and not inside OpenVZ.
However, if you absolutely need to run Docker within OpenVZ, there is a way to do it; but it is very hackish. There will be a performance hit, and there might be side-effects. If you want to try anyway, you can check Sekexe. It will let you start arbitrary processes within a user-mode-linux kernel. I have used it successfully to run Docker tests within Travis CI. I wouldn't recommend it for anything else, though.
I was playing a bit with sekexe, but I totally agree with jpetazzo; it's cool but not for production. Instead I started using debootstrap + chrooted jails to have a similar Docker-ish experience (but not as cool as docker of course).
You might want to check this: http://coderofsalvation.github.io/debootstrap-container
I'm using this now on an OpenVZ VPS to separate packages/projects in tidy containers. Disclaimer: I am the author.
Kernel version: 2.6.32-042stab057.1
rpm -qa | grep -i kernel result:
vzkernel-headers-2.6.32-042stab057.1.i686
libreport-plugin-kerneloops-2.0.9-5.el6.centos.i686
vzkernel-firmware-2.6.32-042stab057.1.noarch
abrt-addon-kerneloops-2.0.8-6.el6.centos.i686
vzkernel-devel-2.6.32-042stab057.1.i686
when i send the command make i get this error:
You do not appear to have the sources for the 2.6.32-042stab057.1 kernel installed.
OS: Centos 6.3 Final
I am not very familiar with OpenVZ, but from your provided information, looks like you don't have kernel source. You have kernel-devel and kernel-headers, but not the kernel itself.
You may download kernel here:
http://download.openvz.org/kernel/branches/rhel6-2.6.32/042stab057.1/vzkernel-2.6.32-042stab057.1.i686.rpm
And then: rpm -ivh vzkernel-2.6.32-042stab057.1.i686.rpm
I had the same issue compiling it on my new VPS. I was able to get it all to install from the files found at http://wiki.openvz.org/Download/kernel/rhel6/042stab057.1
Download/install those RPMs and you'll be good to go.
You need
have access to main node, compile asterisk on it
forward dahdi device to container(via container config)
copy from main node kernel-devel package, compile dahdi in container.
Read this
http://openvz.org/Asterisk_from_source