similar to: why no /dev/loop0 in install chroot system?

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 Al, Here's a set of patches that: (1) Provides a convenience member in struct fs_context that is OR'd into sb->s_iflags by sget_fc(). (2) Provides a convenience vfs_init_pseudo_fs_context() helper function for doing most of the work in mounting a pseudo filesystem. (3) Converts all the trivial filesystems that have no arguments to fs_context. (4) Converts

Have been trying some things, but something isn't working at least with using Virtual Box with EFI option. With it off, the cd boots as normal, and works, but with EFI on, it has an error that flashes on screen, and then it drops to a shell prompt. I'm hoping it is just a dumb mistake I am making, and can be resolved. Perhaps I've named the directories incorrectly, or there is a

This is probably a known issue, but just in case. On my Desktop, I am running SELinux in Permissive mode. When I restart the system, or shut it down, I notice this message: "Stopping setroubleshootd failed". Notice at the end of the dmseg output below, regarding SELinux, there are three (3) identical lines. I don't know if that is normal or not. [lanny at dell2400 ~]$ dmesg |more

Hello, I was using a bunch of cpios in initramfs as a working system, and wondering why the unused files weren't being paged out to swap. So I reread ramfs-rootfs-initramfs.txt and now I know. So I wrote the attached utility. It creates a tmpfs, moves all files on the initramfs, moves / and executes the real init. It works, even with hardlinks, but it isn't the correct approach. Have

Hi Al, Here's a set of patches that converts a bunch (but not yet all!) to the new mount API. To this end, it makes the following changes: (1) Provides a convenience member in struct fs_context that is OR'd into sb->s_iflags by sget_fc(). (2) Provides a convenience helper function, vfs_init_pseudo_fs_context(), for doing most of the work in mounting a pseudo filesystem.

After supermin has finished running, the initramfs files sit around occupying swappable memory but serving no further purpose. This saves a little memory, at the cost of about 1ms of extra boot time. --- init/init.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 48 insertions(+), 2 deletions(-) diff --git a/init/init.c b/init/init.c index 733d66e..5ac53e9 100644 ---

Subject of Hint: How to create a Bootable Live CD/DVD from your Linux From Scratch (LFS) build Good day from Singapore, I am Mr. Turritopsis Dohrnii Teo En Ming, based in Singapore. I have recently *successfully* created my own custom Linux distribution called Teo En Ming Linux 2020.03 (FINAL), which is based on Linux From Scratch 20200302-systemd book and Linux Kernel 5.5.7, on 12 March

I'm using the same CD's that I've used to install CentOS on my other systems. After the first failure I had the installation verify the install media just in case. It passed. I've tried the default install (used for all previous installs) and the i586 option (after googling). They both fail in the same way. Here is a transcript of what is output to the screen: Running

Hi All I was wondering if anyone has installed CentOS 4.x on the following configuration? Our specs for the server are ASUS P5VD2-VM Motherboard, Intel Core2Duo processor, 2 x 250GB Seagate SATA HDD with 2GB RAM. I am currently trying to install SME Server 7.1 on this configuration. The SME forum has recommended I post here as well to see if anybody can help. The message I am getting is:

I just recently posted a patch to the linux-kernel mailing list to move rootfs/initramfs from ramfs to tmpfs. Now I'd like to test this out better. Currently I'm only using initramfs to store data so I'm new the this klibc thing. Tommorrow I'm going to try to get klibc working to run some programs in early-userspace. From what I've read so far, i'll need a swapon

Hi, Here's a try at writing an initramfs HOWTO. This is basically a write-up of a number of interesting emails I collected over time. It could probably use an editor, more fact-checking and a bunch of other good things, but it should be better than nothing ;-) Daniel -------------- next part -------------- INITRAMFS HOWTO 0) What are klibc and initramfs? Initramfs is a ramfs into which

I earlier this week upgraded from Debian woody to sarge on a machine that does a nightly backup to another machine via a samba share. Since then I have had some issues with accessing that share with I believe are a result of the upgrade. I upgraded the kernel at the same time to 2.4.27-1-686 #1 via apt-get, which might be the related to the problem. Smbfs is version 3.0.6-3

Harcoding default content of initramfs in the gen_initramfs_list.sh script seems ackward. Move it to a file named: usr/initramfs.default This also fixes a small bug when no arguments was passed to CONFIG_INITRAMFS_SOURCE (-d was passed twice to the script) Idea and bug report from: "H. Peter Anvin" <hpa@zytor.com> Signed-off-by: Sam Ravnborg <sam@ravnborg.org> ---

This is most exceedingly weird boot/shutdown sequence that I used once, and can't find a way to adapt to initramfs. Since you guys are trying to adapt all mechanisms that use initrd to using initramfs, this should interest you. initrd has (all binaries static): /bin: init halt mount poweroff pivot_root reboot sh umount /etc: fstab haltrc /dev: null zero tty tty0 tty1 console->tty0 hda1

Was it intentional feature, or it is a bug? Bug, because if, say initramfs `init` has # chroot /rootfs /bin/sh -i <>/rootfs/dev/tty2 1>&0 2>&0 # without any prior `cd`, then current directory will be one of the `init`, even if it is displayed by tools as `/' inside the chroot. ____

Generate dependencies almost like done by fixdep in the kernel. This teaches make to rebuild cpio image when content has changed. Also restructured usr/Kbuild a little so we better utilise parallel makes (dash, gzip, utils and kinit are now build in parallel). Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- patch is on top of hpa's linux tree, so path differ if applied to the klibc

Hey all, I've downloaded the latest CentOS 5.0 and the md5sums look good. I loop-back mounted the ISOs and pulled all of the RPMs out into a single dir. I have an existing PXE environment with several different distros to which I added 5.0. RPMs are served from my HTTPS server. I used the isolinux.cfg that was provided and all *looks* good. The problem is that on 4 *very* different

Fix usr/Kbuild so it utilise the new gen_initramfs.sh script which will rebuild initramfs when the content has changed. Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- usr/Kbuild | 74 +++++++++++++++++++---------------------------------------------- 1 file changed, 22 insertions(+), 52 deletions(-) This patch shall not be applied until my kbuild.git tree is merged upstream. Or it

gen_initramfs_list.sh failed to generate a dependency list when it was supplied the -d option. Restructured gen_initramfs_list.sh to support dependency info with -d. This also fixes a bug where we did not properly process when more than one dir was specified. Finally update dependency info for the -d case (list_default_initramfs) In usr/Kbuild remove "" around CONFIG_RAMFS_SOURCE so the