similar to: OT: piped greps with regex

Hello All, We would appreciate your advice on the following issue. We have created a full virtualized Xen guest that its disk is an image file of 4GB. We want to use this image file as a template for creating Xen guests which their disk will be an LVM device. The disk image file is of type: file /var/lib/xen/images/rhel52.img /var/lib/xen/images/rhel52.img: x86 boot sector;

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync'd files from root partition of physical

On Mon, Feb 03, 2014 at 09:14:09PM +0000, Richard W.M. Jones wrote: > On Mon, Feb 03, 2014 at 03:29:37PM -0500, Andre Goree wrote: > > Ahhh, understood. I do have have an image I can provide that was > > installed onto and MBR layout (seemed the easiest for libguestfs to > > understand, GPT is preferred if libguestfs works well with it, but > > that's another matter

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the

Hello , everyone I am a newcomer to xen , which i study in recent months . I have deploy the xen-4.1.2 on dell server , centos as dom0 , now , i use the vhd format to be the virtual hard disk , after i execute " xm new ***.cfg" , this vm generate the vm in "xm list" , but when i execute " xm start *** ", "Error: Boot loader didn''t return any data

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync''d files from root partition of

I installed Centos 6.x 64 bit with the minimal ISO and used two disks in RAID 1 array. Filesystem Size Used Avail Use% Mounted on /dev/md2 97G 918M 91G 1% / tmpfs 16G 0 16G 0% /dev/shm /dev/md1 485M 54M 407M 12% /boot /dev/md3 3.4T 198M 3.2T 1% /vz Personalities : [raid1] md1 : active raid1 sda1[0] sdb1[1] 511936 blocks super 1.0

On Tuesday 04 February 2014 09:54:58 Richard W.M. Jones wrote: > On Mon, Feb 03, 2014 at 09:14:09PM +0000, Richard W.M. Jones wrote: > > On Mon, Feb 03, 2014 at 03:29:37PM -0500, Andre Goree wrote: > > > Ahhh, understood. I do have have an image I can provide that was > > > installed onto and MBR layout (seemed the easiest for libguestfs > > > to > > >

I've been able to successfully kickstart CentOS 3.9 from the base repo, but no such luck after merging os and updates. I think I did everything right - updated base/comps.xml and regenerated hdlist/hdlist2. Updated the yum repo as well although I'm pretty sure it's not used by anaconda. This is difficult to debug. The setup is running under kvm on a CentOS 6.4 host, and for some

On 02/03/2014 3:16 pm, Richard W.M. Jones wrote: > On Mon, Feb 03, 2014 at 03:12:28PM -0500, Andre Goree wrote: >> I'm wondering whether or not anyone has tried to use guestmount on >> an image with a ZFS partition (MBR partition table). I can't seem >> to find much on the internet regarding it, but I do see hints that >> may lead me to a solution. I'm

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Hi Konrad, Does this look at all familiar? There is some more info in the full bug log at http://bugs.debian.org/637234 . In particular, contrary to the message below, the user subsequently confirmed that the issue appears to be Xen specific (doesn''t happen on native or vmware) and that it arose between 2.6.39-2-686-pae and 3.0.0-1-686-pae. Could it be related to edf6ef59ec7e

Hello Group, This is an open-ended question. Quite fascinated by the things I can do and the control I have on my activities since I started using R. I basically have been using this for analytical related work off my desktop. My experience has been quite good and most issues where I need to investigate and solve are typical items more related to data errors, format corruption, etc... not

Hello, I was looking for a way to detect the installed boot loader of an image and I found this: https://github.com/arvidjaar/bootinfoscript This script will inspection a lot of things on a running system and will output a Report. The most interesting part is that it uses known Master and Volume Boot Record byte-patterns to determine the installed boot loader:

I was browsing through the SAMBA workgroups defined here: E51-CAE, E51-WAAS, etc... everything looked fine (well, with the exception of subnet browsing) until I displayed the properties of the machines in the workgroups. Select a SAMBA host, right-click on the hostname and select 'Properties' from an NT4 machine displays the domain as "E51"; everything from the dash onward

Hi I recently started working with somba on my Slackware box, and got it going with file sharing. However, I need a little more functionality out of it. I'll start with my situation, and what I need to do. I run a webserver on IIS 5.0 on a Win 2000 box. It is strictly a LAN webserver and only accessable from thos on the inside. People access from their browser via my Win 2000

On Fri, Jun 19, 2015 at 01:53:13PM +0300, Nikos Skalkotos wrote: > Hello, > > I was looking for a way to detect the installed boot loader of an image > and I found this: https://github.com/arvidjaar/bootinfoscript > This script will inspection a lot of things on a running system and will > output a Report. The most interesting part is that it uses known Master > and Volume

In article <5c2439dc6351659900b0c7ef421ae3f1e7b84fe4.camel at biggs.org.uk>, Pete Biggs <pete at biggs.org.uk> wrote: > > > > > is what is annoying me. That seems to be what I would expect if I > > piped it to less. I checked a fedora 31 and another centos 8 box and > > am seeing the same behaviour. Am I missing something? > > > > The

> > is what is annoying me. That seems to be what I would expect if I > piped it to less. I checked a fedora 31 and another centos 8 box and > am seeing the same behaviour. Am I missing something? > The environment variable $PAGER determines what pager to use. The default is 'less'. User export PAGER=more to use 'more' instead. Or export PAGER= to not

Starting off, it is important not to loose any dhcp messages, especially during log rotation. My first thought on this would be to add a fifo to syslog.conf and slup from it, like: # perl -ne 'm/.../ && WWW::Curl ...' < /var/log/messages.fifo Does anyone see a more proper way? tail -F / -f could both miss messages during log rotation (please correct me if I am wrong) What