Where would i find the list of distribution codes.For example.Code:samba-32bit-3.4.2 -1.1.3.1.x8664.rpmIn above rpm file it is indicated that its release is 1.1.3.1 .The rpm is meant to be run for opensuse.Where would i get the linking of release number and In simple words How would i guess distribution by merely looking at rpm name?
I have several terminals opened at once to monitor the logs. It would be helpful to choose different basic color for text (and maybe for background) for each terminal so I can quickly locate the one I need. Anyone know how to do this or perhaps point me to right direction?
I'm writing a script for asterisk to monitor trunk failure, i do a loop for every trunk it got nad would like to name variable like server1=, server2= naming the server upgoing as the trunk is. here is the scripts:
[Code]....
what i would like to do is name the variable server, username and status with the count variable, like this server$COUNT to have server1 when on trunk one, bu as soon as i add the $COUNT after the server, it seems to try to make it a command, it says that:
Code: ./test.sh: line 45: server1=74.63.41.218: command not found
How can I export my Ubuntu terminal's color scheme for use on other computers?I've set up a color scheme that I like and I'd like to put it in a git repo for easy loading from other machines. Any strategy that would make it work in other terminal apps too, such as Konsole?
I am trying to do Multi_key composition...But not able to find which is my character encoding scheme under /usr/share/X11/locale/ I have several direcotries under this folder...How can i come to kno which is my character encoding scheme..Any command for this ?
I have gone over the thread "Learn The DD Command Revised" (It was Fantastic) in the search for a solution to my query.
I have seen posted elsewhere that this code is supposed to be able to change the UUID number of NTFS partitions (useful when multi-booting with Grub2 and cloning partitions). Here is the code:
Code: sudo dd if=/dev/urandom bs=80 count=1 | xxd -l 80 -c 8 | tail -1 | xxd -r - /dev/sda1 This is assuming that I want to change the UUID on the 1st partition on the 1st hard drive >>>sda1<<< If I was trying to modify the 2nd partition on the 1st hard drive it would be >>>sda2<<<
[Code].....
NOTE: I was doing this while booting from Ubuntu's Live CD version 10.04.1 LTS (In case that is a factor)
Someone (not me) recently installed some new distros on my HD. It seems that during the installation my swap partition was reformatted and a new UUID was assigned to it. I have the following questions:
1. I know that I have to change the swap partition UUID in /etc/fstab and /boot/grub/menu.lst of the affected distros. Is there anything else that needs to be changed? 2. I presume a similar change has to be made to the Grub 2 configuration, for those distros that use Grub 2. I have no experience using Grub 2 so how do I make the change or where can I find instructions to do it?
Simple. UUID is apparently limited to a single UUID to be defined. Example UUID="DEB0-0001","3338-3164" separated with a comma is not working.
What could be the linux alternatives for pluging several UUID disks? How to bypass when there is a CF card and a reader box, since blkid gives no UUID ?
I realized that my understanding of UUIDs in Linux to specifying hard disk partitions may be erroneous.
The proverbial wisdom is that one should not use hard-coded device specifications in fstab and in the boot menu.lst, such as /dev/sda1 etc. The reason normally given is that if hard disk order changes or the order of partitions change, then the entries will be incorrect since they are hardcoded to partitions following a specific order.
So my understanding was that using hard disk labels, in the form of LABEL=xxxx, or UUIDs in the form of UUID=some-uuid, would prevent these problems when disk order or partition order changed.
I decided to avoid the use of LABEL in case I wanted to change the LABEL on a partition to make the names of partitions more easily identifiable. I then thought that UUID was ideal since it never changed for a partition no matter even if I moved that partition to another drive or added another hard drive and thus changes the order of hard drives on my computer. I essentially thought that once UUID was determined for a partition, it never changed but was somehow part of the partition in the hardware of my computer.
Then I became curious of how a UUID was determined. I did this because I often make backups of partitions on external SATA drives and wanted to make sure that somehow the backup would not duplicate whatever Linux considers the UUID of a partition and present a Linux distribution with two UUIDS which are somehow the same and therefore confuse the Linux distribution to the point that I could not use it. I am aware that UUID means a unique id, but I wanted to make sure I understand how that unique id is determined in Linux. This is especially true since the tool I use to make backups of an entire partition is a Windows application, and not a Linux application, and I wanted to make sure that the backup partition UUID would not duplicate that of an existing partition.
In my very brief research in how a UUID is generated under Linux it appears that it is not something that is part of the hardware of the partition itself but rather a number generated by some parameters of the partition, one of which is the partition order.
If it is, it means to me that if I move a partition from one place to another, even on the same hard drive, or to another hard drive, a Linux distribution will no longer find the partition based on the UUID. In that case it seems as if the UUID is subject to the same weakness as the device specification in fstab and menu.lst in that the order of a partition or the placement of a partition on a particular hard drive will cause the designation to no longer refer to the same partition. In which case it appears to me that only the LABEL parameter is not subject to this weakness and as long as I keep distinct labels for all partitions on my hard drive I could theoretically move them around at will and a Linux distribution will find them correctly. I am aware of course that my computer must always find the boot partition to be able to boot a Linux distribution, so moving Linux parttions where I want them is subject to the ability of my computer to find them from the MBR of my hard drives. But in the main it now appears to me that the best way to insure that moving partitions does not keep a Linux distribution from botting correctly is to use LABEL, and not UUID, in fstab and menu.lst, and of course to make sure that if I decide to change the LABEL of a partition that I must change its entry in fstab and possibly menu.lst before rebooting that distribution.
If I have been wrong in my latest surmises I would appreciate being corrected, as the information I found on UUIDs and how they are generated may not be correct. Also if there is more exact information on exactly how partition UUIDs are generated in Linux I would appreciating anyone pointing it out to me.
I've got the latest version of Ubuntu on my machine.My Linux partition is ext4, so I need to use a Linux boot loader capable of booting from ext4.Also, I want to be able to use the UUID of my partition instead of specifying "/dev/sda3".Right now I'm using the Grub2 (or whatever the f*** it's called) that comes with Ubuntu. It's the ugliest boot loader you'll ever see, the configuration file is disgusting.So with that in mind, I'd like to change boot loader.Lilo would be OK but I can't seem to get it to boot from ext4.The older version of Grub was fine too but again I don't think it can boot from ext4.
Using Linux, I have several backup levels. One of them is a periodical sector by sector copy (using dd) of my laptop harddisk to an external USB disk. Yes, I have other backups too, like remote rsync. This approach (the disk dd) is OK when cloning a HDD with no LVM volumes, since I can plug the external disk anytime and mount the partitions simply mounting /dev/sdb* instead of /dev/sda*. Trivial and handy.
Today I moved ALL my harddisk (including the /boot) to LVM. Everything works fine. I will stress it for a couple of days, and then I will do a sector by sector copy to my external harddisk. Now I have a problem, I guess.
If in the future I plug the external USB HDD to recover any file, the OS will detect a duplicate LVM configuration, with the same name and the same UUID. Even doing a vgrename (which LVM would be renamed, the internal HDD or the external HDD?), the cloned UUID will not change. Is there any command to change name and UUID? Ideally I would clone the HDD and then change the LVM group name and its UUID, but I don't know how to do it. Another related issue would be... In the past I have booted my laptop using the external disk, using the BIOS boot menu and changing GRUB entries manually to boot from /dev/sdb instead of /dev/sda. But now my current GRUB configuration boots directly from a LVM logical volume, something like: set root='(LVM-root)' in my grub.cfg. So... What is going to happen with duplicated volumes?
How can I make workspaces have names under 10.04? Under 9.10 I can given different workspaces different names, under 10.04 I can't. Workspace-switcher-preferences has less options.
I have a number of partitions, each having an icon on the Desktop.However, they are only referred to by size of partition. What I would like to do is give them a relevant name, e.g. photos, MP3s, etc.My fstab uses UUIDs. Can I change the names while using these to refer to the partitions?
I have 4 SATA hard drives, and they are named sda, sdb, sdc and sdd. My problem is that the drives always randomly switch between these names when I restart my system. It is not really a problem as far as mounting, because I use the UUID option. I'm using the sensors applet to monitor the temps of the hard drives, and I can never tell which one is which, because the drive names are always changing.Is there any way to have the drives named the same way every time?
I'm running Ubuntu 11.04 on my desktop and the 70-persistent-net.rules file seems to be ignored. The ethernet interfaces are randomly shuffled around on boot (i have 4 interfaces). The original one was configured to have a static IP address (eth0). Is there anything that prevents the /etc/udev/rules.d/70-persistent-net.rules from being applied/used?
I have got a question about some terms in Debian package name, for example: 1:9.6.ESV.R3+dfsg-0+lenny1 What do ESV, R3 and lenny1 mean? I can't find information about it anywhere...
I have scanner working nicely, but...When I launch xsane, the scanning for devices upsets my tv-tuner.Xsane accepts a device name in the command line, but how to put it there?sane-find-scanner gives:found USB scanner (vendor=0x04e8, product=0x341b) at libusb:003:003found USB scanner (vendor=0x0c45, product=0x602d) at libusb:002:002
After upgrade to 10.04, my disks are randomly named (sda, sdb, sdc) at each boot. My drive labeled "XP" is sometimes named "sdb" and sometimes "sdc", while my other drive "DATA" is respectively "sdc" or "sdb". This wasn't the case before upgrade with KUbuntu 9.10.
Due to this random naming, my auto-mount in fstab often fail at boot time !
Any solution for this (not found here by myself) ?
Is this linked to Grub troubles reported many times here ?
During installation when i set the partitions i have to provide a Name and a Label. What is the difference of these? It looks like only one should be needed. Any problems of using the same name for both?
I'm doing a few tests with fedora 15. I'm surprised because they changed the naming way on network devices. eth0 is now called em1.At every fedora I have found the configuration files in /etc/sysconfig/network-scripts, but today I can't find them.
Need help on how the scsi and multipathing works in Linux. From the docs i have read, i understand that by the use of multipathing we can assign multiple paths to a SAN partition. If there is a problem then one path will failover to other path.However, i am not clear on how linux recognizes the SAN partitions using the multipath drivers. For e.g. I have a HP Proliant server on which we have the following mounts:
Filesystem Size Used Avail Use% Mounted on /dev/cciss/c0d0p3 59G 11G 46G 20% / /dev/cciss/c0d0p1 494M 27M 443M 6% /boot
I have a problem defining persistent device naming on a Debian Lenny server.I have:RAID1 controller on the server machine with two SCSI disks.external storage with RAID5. I have / mount on the first partition on the server SCSI disk and /storage mount on the external storage.
I'm experiencing a problem: The system recognizes the system disk (RAID 1), as sda or sdb - randomly.I want: To control the recognition, and tell the system that sda (sda1) will always be the system disk.The motivation: GRUB is configured to work with sda, and when the system disk doesn't, boot process fails, and I end up in the initramfs shell-like interface.
Booting the kernel . . . mount:mounting /dev on /root/dev failed: No such file or directory mount:mounting /sys on /root/sys failed: No such file or directory