similar to: chroot....

Hi, I am trying to figure out a poor mans install ... I want to be able to boot CD iso thats on my hard disc .. There is an option to install via hard drive .. but I keep getting VFAT16 files system errors .. I know where copied iso image is ... I can boot kernel but linuxrc will not start LiveCD ... Maybe I could rewrite linuxrc to allow this but as it works from ram I am finding hard to

Hello again, I'm always not able to boot-up my CF-FileSystem. (It works with a 2.4.x Kernel!) See: http://syslinux.zytor.com/archives/2006-June/006942.html I dont't understand, why the kernel can't mount the root-fs on exit of "linuxrc". Before finising "linuxrc" I can work on it, start a "bash"-shell, do all sorts of linux-cmds on the root-fs...

hi ya syslinuxerz - i've been slowly working on a making a custom bootable standalone usb-stick with X11 and kde - it's basically builds itself off of a slackware-10.1 server - create a custom initrd.gz ( /dev/ram0 ) http://linux-boot.net/Bootable/InitRD/ - create a custom rootfs.gz ( /dev/loop0 ) http://linux-boot.net/Bootable/RootFS/ - create X11 and kde loopfiles

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting

I?ve got a 512M machine and a 330M ( uncompressed ) initrd image. How can I mount the ramdisk? Normal booting seems to want to copy the entire initrd image into a Ramdisk, thus requiring 2X the memory. So what happens is the kernel boots correctly and I get, RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 330000 blocks [ 1 disk ] into ram disk And then I never see the light of day after

Hello, I'm trying to fix netbooting and I got quit far. Before this, it reported that it had no root disk, I fixed this by specifying my initrd. Nou it crys's: Kernel panic: I have no root and I want to scream I think I made the mistake whit the creation of the initrd file. What should I put in it except the /linuxrc. I put a echo "TEST" in de /linuxrc to see if it runs, in

Hi! Is there any experience of converting vmware''s vmdk file to a domU image? Maybe via extracting vmdk (how?) -> build tar -> untar in domU? That would be very nice despite replacing the original kernel with a self-built one and worthy to write a script... :) Cheers, Sven. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

I converted my lvm root initrd to an initramfs by putting glibc, lvm, pivot_root, my linuxrc, etc. in my initramfs source file. I use ash compiled against klibc to run my linuxrc Unfortunately - pivot_root . initrd - complains - pivot_root: Invalid argument I suspect this may be because you can't pivot_root using a cpio initramfs root? If so, what should I do instead? Should I

Hi, new to the list, R and rpy. my first post. using rpy, i find this r.X11(height=3, width=6) allows me to preset the size of a subsequent r.plot(x, y) but i've been unable to find documention on related aspects, such as programatic control of the plot window location on the monitor, or programatic resizing of a plot once it is generated. Are these possible? In general I've

Hello, Im a Gentoo kernel maintainer thats trying to fix some bugs on are upcoming 1.4 livecd release that uses IsoLinux. Our isolinux.cfg is pretty standard : ######################################### default gentoo append initrd=initrd acpi=off root=/dev/ram0 init=/linuxrc timeout 300 prompt 1 display boot.msg F1 boot.msg F2 help.msg label livecd kernel gentoo append

hi, i am wondering about how submission of append parameters can be done. i have the following isolinux.cfg: --------------------------------------------------------------------- DEFAULT linux PROMPT 1 TIMEOUT 100 LABEL linux KERNEL vmlinuz APPEND initrd=initrd.gz nomce quiet ---------------------------------------------------------------------- what i want to do is to tell at

> /diskless/pxelinux.cfg/default > --- > DEFAULT /gentoo-x86_64/boot/kernel-3.14.14-gentoo > APPEND ip=dhcp ro rootfstype=nfs root=/dev/nfs > nfsroot=10.0.0.11:/diskless/gentoo-x86_64 > init=/linuxrc That pxelinux.cfg/default seems "tolerable" for older versions, but not for Syslinux 5+. Is this an inadequate copy of the actual content? Or is it really a

I have tried to use isolinux 2.05, and I am running into a problem where it will not boot. I have previously used version 1.66, and the older version works just fine. Changing nothing except dropping the new version in does not work. Below is all of the relevant info, I believe. This occurs on multiple machines with different BIOS. I am currently in process of doing a binary search to find the

Dear useRs, I was asked to produce a survival curve like this: http://www.palug.net/Members/jabba/immaginetta.png/view with the cardinality of the riskset at the bottom. I do not like doing it, because it doesn't add any valuable information and because it doesn't discriminate between died and censored. Nevertheless, is there someone able to tell me how to do it? Currently the only

Hello, I am using with success SYSLINUX-1.48 to boot a CD-Rom in order to realize an automatic installation of Linux. Actually all messages during the boot step are displayed on VGA screen. In the operational version, we have only a VT on COM1. I have tested to modified my syslinux.cfg like the following listing but boot messages are always displayed on VGA screen ! Can you help me, please ? (I

Dear All, I have a following query: - My initrd image is created using ext2 filesystem. - The filesystem type of / is specified as ext3 in /etc/fstab file. - I dont mount the real root during execution of linuxrc because I referred some documents saying that if you dont mount real root from linuxrc the kernel will mount it after linuxrc is finished. - The system boots up successfully, mount

Having fought my PXE config and eventually getting it to work (had to comment out the group { } statments ? I now come across another issue I cannot resolve and would appreciate some help. in my /tftpboot/pxelinux.cfg/default file I have cause to use the APPEND statement to pass options to the kernel being used. Unfortunately this line has now become longer than 255 characters and appears to be

>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>> on Tue, 1 May 2018 16:14:43 +0200 writes: >>>>> G?bor Cs?rdi <csardi.gabor at gmail.com> >>>>> on Tue, 1 May 2018 12:05:32 +0000 writes: >> This is a not too old R-devel on Linux, it already fails >> in R 3.4.4, and on macOS as well.

Hello, sorry for not being clear enough. My problem is represented with the following code, running on OSX: mkdir ~/test ln -s ~/test ~/testlink touch ~/test/foo Rscript -e 'Sys.readlink(c("~/test/foo", "~/testlink/foo")); normalizePath(c("~/test/foo","~/testlink/foo"))' I expected `Sys.readlink` to show the same output as `normalizePath`. Also,

This is a not too old R-devel on Linux, it already fails in R 3.4.4, and on macOS as well. The tar file seems valid, external tar can untar it, so maybe an untar() bug. setwd(tempdir()) dir.create("pkg") cat("foobar\n", file = file.path("pkg", "NAMESPACE")) cat("this: that\n", file = file.path("pkg", "DESCRIPTION"))