Red Hat / Fedora :: Mkinitrd - What Does [$(uname -r).img $(uname -r) Mean
Jun 25, 2010# mkinitrd -v /boot/initrd-$(uname -r).img $(uname -r) what does it [$(uname -r).img $(uname -r) mean?
View 2 Replies# mkinitrd -v /boot/initrd-$(uname -r).img $(uname -r) what does it [$(uname -r).img $(uname -r) mean?
View 2 RepliesI got this message after a update some weeks ago and am now on a permissive opening.
Fedora 11
gnome 2.26.3
I would like to know how to change the uname -a result in my server, i mean if the attacker upload a phpshell in any website for my customer, how could i have a fake uname -a for him?
View 7 Replies View RelatedYou know, I thought I had my Broadcom issues all figured out, I have a simple list of installing the RPM Fusion repos do a yum update and yum install kmod-wl and everything works.However, this time it didn't work. I am installing a new fedora 14 for a friend who is totally fed up with windows and I get this error: (Yes I have searched the internet and Fedora forums for an answer)
[code]...
I have tried the two yum suggestions and they don't work I have tried updating the kernel and have installed kernel-devel-'uname -r' (suggested by another site) I have tried installing broadcom-wl and b43-openfwwf which only knocked out the card entirely
Some instructions say to put 'uname -r' into terminal commands. Is this supposed to be automatically converted by the system to something else? It doesn't get converted to anything on my system. uname -r only works by itself but not as a program argument.
View 1 Replies View Relatedany one knows the difference between the uname -m, -p and -i?
Code:
uname -m
i686
uname -p
i686
uname -i
i386
[Code]...
i gt this from man. does it mean that the machine is a i686 machine that is running on a i386 OS?
I want to change my servers node name which is the output of "#uname -n"Server is CentOS 5I searched but couldn't find. There was some search results about /etc/nodename but I don't have a file at that path. Also some said uname -S which doesn't work.
View 8 Replies View RelatedHow would I prevent printing the kernel version after logging in? I cannot find any relevant setting in login.defs
View 4 Replies View RelatedI use Debian testing and when I run this
Code: Select alluname -a
I see these
Code: Select allLinux debian-mfaridi 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64 GNU/Linux
I run the uname -m command and the output is i686.What does it mean ???
View 3 Replies View RelatedI am having issues trying to compile the alsa-linuxtant module and I am getting errors about not being able to find some files and the source needing to be reconfigured. Anyway the developers told me to try compiling on a pristine source to see if I could compile that way. When I went looking at kernel.org I did not find a 2.6.32-5 version. So I did some checking and to see just what version I have.
$ uname -r
2.6.32-5-amd64
$ dpkg --list | grep linux-image
ii linux-image-2.6-amd 64 2.6.32+27 Linux 2.6 for 64-bit PCs (meta-package)
ii linux-image-2.6.26-2-amd64 2.6.26-24 Linux 2.6.26 image on AMD64
ii linux-image-2.6.32-5-amd64 2.6.32-15 Linux 2.6.32 for 64-bit PCs
So the actual package that is installed is 2.6.32-15 but uname -r reports 2.6.32-5 as the kernel version.
Fedora 11 update released today creates a dependency issue in my x86-64 system: Processing Dependency: kernel-uname-r = 2.6.29.5-191.fc11.x86_64 for package: kmod-wl-2.6.29.5-191.fc11.x86_64-5.10.91.9-3.fc11.1.x86_64 # yum info kernel-uname-r produces "no matching packages to list" the yum info pack tells me kmod-wl is: Metapackage which tracks in wl kernel module for newest kernel so it seems important to have it up to date. What should I do?
View 5 Replies View RelatedI am writing a script inside i need to get the values of uname -n like... var = uname -n. how to do it in shell script ?
View 1 Replies View RelatedI am an openSuSE user for many years. My current installation is openSuSE 11.2. However, my first was SuSE 6.4 and I have been _constantly_ upgrading since then until reaching the current openSuSE 11.2. The technical issue I have been facing lately is with the kernel version of my current system: although it should be 2.6.31.5-0.1-desktop, as this is the one I have chosen via the online update mechanism and the yast2 system boot-loader procedure, grub shows it as preselected, the boot procedure in the end greets me mentioning this very kernel version, _but_ when I issue the command: uname -a in a command prompt, I am informed of using linux kernel version: 2.6.18.2-34-default #1 SMP PREEMPT
I am really quite puzzled, since I _cannot_ find any such vmlinuz file under /boot/ ! Could it be that my system properly runs with the expected kernel version, but uname mistakes it with a different one? Is there a way to determine the actual version of the linux kernel that my system currently runs with? If it's a problem with uname, have you got any suggestions that could potentially shed some light towards the origin/cause of the reported issue?
I did apply the updates on 11.1 32bit and upgraded the kernel from 2.6.27.45 to 2.6.27.56.
Now:
Code:
> uname -a
Linux myhost 2.6.27.45-0.1-default #1 SMP 2010-12-01 16:57:58 +0100 i686 i686 i386 GNU/Linux
but:
Code:
> cat /proc/version
Linux version 2.6.27.56-0.1-pae (geeko@buildhost) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP 2010-12-01 16:57:58 +0100
I'm booting kernel 2.6.34.7-0.4 (opensuse 11.3), but "uname -r" says version:2.6.34.7-0.3-default. What's wrong?
View 1 Replies View RelatedI install fedora on my usb-hdd. Sometimes i boot it from real machine, sometimes i boot from virtual machine (kvm). When I boot from real machine, hdd driver is usb-storage, when i boot from virtual machine hdd drivers are ata_generic and pata_acpi.
Everytime i update kernel, mkinitrd only create initrd image contains only hdd driver current running, and I must recreate initrd manual with all preload hdd driver. How to config fedora to everytime update kernel, mkinitrd can make initrd image with all hdd driver I need?
I am using ubuntu 10.04 version. # mkinitrd -o initrd.img-2.6.25 2.6.25 it give the result as mkinitrd: commong not found. what should i do now. I tried to install the package initrd-tools, but actually i could not.
View 9 Replies View RelatedI'm trying to recompile my linux kernel -2.6.32.5 version in Centos OS platform and when I type these commands:
Quote:
depmod 2.6.30.5-fogonacaixadagua
Quote:
mkinitrd -v /boot/initrd-2.6.30.5-fogonacaixadagua.img 2.6.30.5-fogonacaixadagua
This is the link of the Guide that I'm trying to follow:
Quote:
[URL]
is there any packages in order for me use depmod and mkinitrd?or download it using yum?
since an update to the latest -current version, it comes to an error inside the init script from the initrd.gz on my system, shortly behind the scan for encrpyted devices inside lvm containers.
The message is
Code:
mdadm: No arrays found in config file
1 logical volume(s) in volume group "vg" now activeash: missing ] mount: mounting crypt-vg-root on /mnt/failed: No such file or directory ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead. You can try to fix it. Type "exit" when things are done. If i then unlock the crypted root device within the lvm, boot continues. I think this is a bug, because configuration did not change, and it worked before the update.
I've installed opensuse 11.4 by doing a network install, (boot off kernel + initrd, everything else is fetched off network) and i skipped the bootloader part because i've already got two other linux systems set up with grub2 on my computer. I picked the minimal server install (text mode) and didn't make any other software selectiono changes.
My partition layout is as follows
ssd drive contains / partitions for distributions (GPT layout) hdd drive contains encrypted lvm PV (PV on a luks partition). inside that PV is a VG with volumes for /home and /var (and other), where each distribution has its own /var.
The problem is that i cannot get initrd to open the luks properly. i tried chrooting, rebuilding the image with mkinitrd -f "lvm2 luks" ( i saw that somewhere on opensuse wiki, i think ) and adding boot parameters like this : lvm_box=/dev/disk/by-uuid/<luks partiiton UUID> lvm="box" (where box is the name of the lvm array).
[Code]...
Do I need to add any special options to mkinitrd for AHCI configuration?
mkinitrd -c -k 2.6.37.6-smp -m ext4
Does it know I'm not in legacy PATA mode or do I have to add something to load AHCI module with it?
Recently I updated to centos 5.5 , every thing is fine , but the mkinitrd can't updated
When try:
yum clean all
yum update
The output :
Loading mirror speeds from cached hostfile
* addons: mirror.cogentco.com
* base: pubmirrors.reflected.net
* extras: mirror.highspeedweb.net
* updates: mirror.cogentco.com
Excluding Packages in global exclude list
Finished
Setting up Update Process .....
Error unpacking rpm package mkinitrd-5.1.19.6-61.el5_5.1.i386
error: unpacking of archive failed on file /lib/bdevid/ata.so: cpio: rename
Failed:
mkinitrd.i386 0:5.1.19.6-61.el5_5.1
Complete!
Make the code work when RESUMEDEV is a symbolic link which has a relative path.
[Code]....
We are running SLES 10.3, I am running Novell's support advisor and it is reporting some old hardware that is failing on bootup, one being a QLogic card and another being flex net network adapter. I was looking around for where the file or directory is that holds the list of modules to be loaded when compiling the kernel but SLES does not seem to match other Linux distro's, at least from the other posts I read for where to find these.
View 3 Replies View RelatedI want a new kernel RPM in my custom CentOS 5 kickstart distro. I built the kernel, got a nice kernel RPM out, and replaced it in my ks.cfg. The install goes fine until the very end, where Anaconda prints some spurious stuff about mkinitrd failing.I get why it might fail -the kernel version argument to mkinitrd was no doubt for the old kernel. But I have no idea where this is -it's not in the ks.cfg afaict, and so I don't quite get where Anaconda / mkinitrd gets it from.
I'd eventually like to use this kernel for the installer as well, but I think I understand that process much better.How do I tell kickstart / Anaconda / mkinitrd to use the new kernel version number?
After installing Slack 13.37 on one of my systems while using my own (non-standard) kernel it refused to boot as the harddisk couldn't be found anymore. Investigation yielded that the ahci.ko driver wasn't loaded (but libahci.ko was). However I listed both ahci.ko and libahci.ko in the mkinitrd -m parameter so there had to be an error in the new /sbin/mkinitrd script. It turned out that a grep at the end of the script weeded out my ahci.ko module as the searchterm "ahci.ko" was already detected in the modprobe line for libahci.ko.
I decided to fix it in an easy way : I just prepend a "space" in front of the module name at the line where the grep is called :
[Code]....
I used mkinitrd to build an initrd from the slackware 2.6.37.6 sources. Lilo throws the following: "Warning: The initial RAM disk is too big to fit between the kernel a the 15M-16M memory hole. It will be loaded in the highest memory as though the configuration file specified "large-memory" and it will be assumed that the BIOS supports memory moves above 16M."
Also, I am running swap, / and home on an encrypted volume group. When the initrd boots (but prior to mounting the encrypted vg) I get a message saying that no modules are found-sounds like a daft question but is this expected? I expect that this is because initrd is looking for modules, but can't find them because the relevant partition isn't mounted.
I'd like to use a keymap not present in slackware "fr-dvorak-bepo" with mkinitrd because my root partition is encrypted by luks. So how can I generate a .bmap file from a classic .map file for mkinitrd ?
View 2 Replies View RelatedI am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/2.6.33.4-smp kernel modules tree found for kernel "2.6.33.4-smp"
I tried to look into the directory and there was only modules under 2.6.44.3. So I tried to change the command into: Quote: mkinitrd -c -k 2.6.33.4 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
[Code]....