search for: mfsroot

On Thu, Nov 28, 2013 at 02:48:38PM +0100, Pino Toscano wrote: > Check for /boot/loader.rc as "install disc" detection, using it to mark > FreeBSD install discs. > Also, check for /mfsroot.gz to see whether such disc is also a live one. > > See also RHBZ#1033207. > --- > src/inspect-fs-cd.c | 19 ++++++++++++++++++- > src/inspect-fs.c | 3 ++- > 2 files changed, 20 insertions(+), 2 deletions(-) > > diff --git a/src/inspect-fs-cd.c b/src/inspect-fs-cd.c...

...ng to get FreeBSD 7.2 booting using mboot module from syslinux 3.82. Unfortunately it doesn't seem to work. Here is my pxelinux config: === 8< === label freebsd72-i386-mboot kernel mboot.c32 append /kernels/freebsd/7.2/i386/boot/kernel/kernel single --- /kernels/freebsd/7.2/i386/boot/mfsroot === 8< === Here is the error message I get on boot: === 8< === Loading /kernels/freebsd/7.2/i386/boot/kernel/kernel... ok Loading /kernels/freebsd/7.2/i386/boot/mfsroot... ok Memory segment at 0xc0400034 (len 0x000000a0) is unavailable === 8< === After adding some debug to the source cod...

...rote: > Doing ls -al on pxeboot.0 shows 157696. This is the generic > "pxeboot" program from FreeBSD 4.8. > pxeboot's operation is very similar to pxelinux, but more simple: > pxeboot simply finds and loads a FreeBSD kernel, then a FreeBSD filesystem > called "mfsroot". Access to the kernel and mfsroot is (in my case) over > NFS-- but I'm not even getting that far. pxeboot relies on the "option > root-path" DHCP parameter for access to the NFS filesystem. > pxeboot may access the kernel/mfsroot with TFTP, but that option > must...

Check for filesystem.squashfs also in /live, since it is where live-build places it. --- src/inspect-fs-cd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/inspect-fs-cd.c b/src/inspect-fs-cd.c index 407e4f8..eaeaa6f 100644 --- a/src/inspect-fs-cd.c +++ b/src/inspect-fs-cd.c @@ -429,7 +429,8 @@ guestfs___check_installer_root (guestfs_h *g, struct inspect_fs *fs) *

Hello, I hope this doesn't bounce again... I'm having trouble passing control of the PXE process from PXELINUX to the FreeBSD "pxeboot" program. I tried invoking "pxeboot" from the PXELINUX "boot:" prompt. This causes an error "Invalid or corrupt kernel image." I named pxeboot "pxeboot.0" and tried invoking pxeboot.0 from the

Check for /boot/loader.rc as "install disc" detection, using it to mark FreeBSD install discs. Also, check for /mfsroot.gz to see whether such disc is also a live one. See also RHBZ#1033207. --- src/inspect-fs-cd.c | 19 ++++++++++++++++++- src/inspect-fs.c | 3 ++- 2 files changed, 20 insertions(+), 2 deletions(-) diff --git a/src/inspect-fs-cd.c b/src/inspect-fs-cd.c index eaeaa6f..fff0629 100644 --- a/src/...

Check for /boot/loader.rc as "install disc" detection, using it to mark FreeBSD install discs. Also, check for /mfsroot.gz to see whether such disc is also a live one. See also RHBZ#1033207. --- src/inspect-fs-cd.c | 8 +++++++- src/inspect-fs.c | 3 ++- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/src/inspect-fs-cd.c b/src/inspect-fs-cd.c index eaeaa6f..45d7bb5 100644 --- a/src/inspect-fs-cd....

A few hours ago I downloaded .../i386/ISO-IMAGES/4.9-RC1-i386-disc1.iso and made kern/mfsroot floppies from it. If I enable my ICH5R SATA controller in "native" mode, the 4.9-RC1 GENERIC kernel hangs solidly (only the system reset button can unwedge it) during device configuration. The last line of bootstrap monologue written by the kernel is: plip0" <PLIP network inter...

Any progress here? Does anyone know if this will be fixed in 7.1 latest, or should we start looking for different backup solution (in this case I would suggest to remove dump from the source tree - having a backup tool that doesn't work is worse than having none). After upgrading we basically cannot backup our servers. Shouldn't this issue be on

...far, subnet x.x.x.x netmask 255.255.255.0 { range x.x.x.x x.x.x.x ; ##For PXE BSD 4.11 get it from pxe1 next-server x.x.x.x ; option root-path "x.x.x.x:/usr/local/export/pxe"; filename "pxelinux.cfg"; } My tftp directory: [root at pxe]# ls -F boot/ grub/ mfsroot pxelinux.0 freebsd/ kernel.gz* pxeboot pxelinux.bin@ freebsd.0 menu.lst pxeboot.0 pxelinux.cfg and most importantly, my pxelinux.cfg which is where I believe my troubles are, default freebsd label freebsd kernel pxeboot.0 append ramdisk_size=1000...

...ork. > It wasn''t an anticipated use. I guess somewhere either in FreeBSD GNATS or > xen''s bugzilla there should be i386-xen FreeBSD bugs filed for me to track. I intend to file a bug report sooner or later, but in the meantime I decided to toy around with the kernel and the mfsroot from 5.3-release, and I did eventually come up with something suitable. By a combination of stripping down both the DOMU kernel and the sysinstall floppy, I managed to get the pair together in a size that works and doesn''t caush an immediate crash under Xen. I''ve FTP installed 10...

...rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.3-20080505-SNAP #0: Mon May 5 11:42:32 UTC 2008 root@fbsdbuild.1822direkt.com:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc1051000. Preloaded mfs_root "/boot/mfsroot" at 0xc10511e8. Preloaded elf module "/boot/modules/acpi.ko" at 0xc105122c. MP Configuration Table version 1.4 found at 0xc009dd71 Table 'FACP' at 0xcff68e48 Table 'APIC' at 0xcff68ebc MADT: Found table at 0xcff68ebc APIC: Using the MADT enumerator. MADT: Found CPU AP...

...ontain the same, but larger file). We - * need to unpack this and look inside to tell the difference. - */ - if (guestfs_is_file (g, "/casper/filesystem.squashfs") > 0 || - guestfs_is_file (g, "/live/filesystem.squashfs") > 0 || - guestfs_is_file (g, "/mfsroot.gz") > 0) - fs->is_live_disk = 1; - - /* Debian/Ubuntu. */ - if (guestfs_is_file (g, "/.disk/info") > 0) { - if (check_debian_installer_root (g, fs) == -1) - return -1; - } - - /* Fedora CDs and DVD (not netinst). */ - else if (guestfs_is_file (g, "/.tre...

Hi, I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have

v9 was here: https://www.redhat.com/archives/libguestfs/2017-July/msg00139.html This depends on these three series (the first two being single minor patches): https://www.redhat.com/archives/libguestfs/2017-July/msg00207.html https://www.redhat.com/archives/libguestfs/2017-July/msg00209.html https://www.redhat.com/archives/libguestfs/2017-July/msg00215.html There is no substantive change. I

This depends on the patch series "[PATCH 00/27] Reimplement many daemon APIs in OCaml." (https://www.redhat.com/archives/libguestfs/2017-July/msg00098.html) v8 was posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00274.html v9: - I split up the mega-patch into a more reviewable series of smaller, incremental patches. There are some other changes vs v8, but

This fixes almost everything. Note that it adds an extra commit which fixes the whole utf8/iconv business. It's probably better to list what isn't fixed: (1) I didn't leave the osinfo code around because I'm still haven't looked too closely at virt-builder-repository. Can't we just fetch this code from the git history when we need it? (2) I didn't change the way

v10: https://www.redhat.com/archives/libguestfs/2017-July/msg00245.html No actual change here, but I rebased and retested. Also this series now does not depend on any other patch series since everything else needed is upstream. Rich.

v6 was posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html and this requires the utilities refactoring posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html Inspection is now complete[*], although not very well tested. I'm intending to compare the output of many guests using old & new virt-inspector to see if I can find any

v7 was: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html I believe this addresses all comments received so far. Also it now passes a test where I compared about 100 disk images processed with old and new virt-inspector binaries. The output is identical in all cases except one which is caused by a bug in blkid