search for: graff97

In message <CAL9Ac2TasS6RfoC5i-oeOh32r+h0QBpVCSNhQMG1MN_KmAr6mw at mail.gmail.com> Dean Graff <graff97 at gmail.com> wrote: ># I think this qualifies as a bootloader, sort of ># sincerely hope it helps address Mr. Guilmette curiousity Yes. Thank you. It had not occurred to me that ye good olde BIOS is/was still there, and that it could actually be relied upon to do useful things, you kn...

On Sun, Feb 2, 2014 at 4:43 PM, Dean Graff <graff97 at gmail.com> wrote: > [ ... ] And Thomas, that 8 partition live OS sounds right up my alley, and > I will definitely check it out. > oops. Mattias, I got you guys confused as you both helped so much. This live system you described sounds fascinating. I really want syslinux + partitio...

btw, that works with mkfs.vfat as well. just have to use syslinux with a syslinux.cfg file instead of extlinux with an extlinux.conf. On Tue, Jan 21, 2014 at 11:58 AM, Dean Graff <graff97 at gmail.com> wrote: > the closest i have gotten to a consistent way to test a MS-DOS filesystem > setup is: > > dd if=/dev/zero of=binary.img bs=1M count=500 > i="$(losetup -f --show binary.img )" > parted binary.img mklabel msdos -s -m > dd if=/usr/lib/syslinux/...

the closest i have gotten to a consistent way to test a MS-DOS filesystem setup is: dd if=/dev/zero of=binary.img bs=1M count=500 i="$(losetup -f --show binary.img )" parted binary.img mklabel msdos -s -m dd if=/usr/lib/syslinux/mbr.bin of="${i}" parted binary.img mkpart primary -a optimal -s -m 0% 100% parted binary.img set 1 boot on mkfs.ext4 $(kpartx -savu "${i}"

> > Both sticks show very unusual factors for heads and sectors > > which are hardly intentional. If BIOS gets confused like fdisk, > > then the failure to find files is quite plausible. > > > > ------------------------------------------------------------- > > > > Could you please exercise what is described for Linux in > >

#!/bin/bash # a small shell script to: # 1) make a simple asm program # 2) compile that program with `nasm' # 3) convert resulting .bin to a .img with `dd' # 4) boot the reulting "hello.img" with qemu/kvm # I think this qualifies as a bootloader, sort of # sincerely hope it helps address Mr. Guilmette curiousity # -chris graff printf ' BITS 16 jmp

I got this figured out much faster than I thought I would. Thanks to all of your help, Peter, Mattias, Thomas and Helmut. And Thomas, that 8 partition live OS sounds right up my alley, and I will definitely check it out. The second partition is working well with `parted' and `fdisk', so I am quite pleased. Below is, again, "what I came up with". I tried to integrate each of your

cmon, it is not that ugly. before parted, and kpartx it was even worse. On Tue, Jan 21, 2014 at 1:54 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 01/21/2014 11:13 AM, Thomas Schmitt wrote: > > > > My current theory is that vendors prefer to record > > a cylinder aligned end CHS address over recording > > an end CHS address which exploits the whole capacity.

Could i get an example to make a binary hard disk image with `mkdiskimage', populate it and install syslinux please? Preferably with a single FAT partition. On Wed, Jan 22, 2014 at 9:20 AM, Rich Mahn <rich at lat.com> wrote: > > > > Both sticks show very unusual factors for heads and sectors > > > which are hardly intentional. If BIOS gets confused like fdisk,

I played with `mkdiskimage' some last night, here is what i came up with: mkdiskimage -z -F binary.img 1000 i="$(losetup -f --show binary.img)" j="$(kpartx -savu "${i}" | awk '{print "/dev/mapper/"$3 }')" mount "${j}" /mnt cp /usr/lib/syslinux/vesamenu.c32 /mnt cat > /mnt/syslinux.cfg <<EOF UI vesamenu.c32 DEFAULT linux LABEL

I saw this name, https://github.com/syslinux available. And jumped at it. If you guys want it for official business just let me know. I plan to host upstream stable syslinux for my distro (statix) from it, in the case you guys don't want to use the name. As syslinux is one of the most important packages i work with. Give me the word and i will delete it and or hand it over to Peter. Sincerely

On Sun, Feb 2, 2014 at 2:31 AM, Thomas Schmitt <scdbackup at gmx.net> wrote: > Hi, > > > # Most linux distros dont have `mkisofs' ( > > Or they have genisoimage under the name "mkisofs". > (e.g. Debian, Archlinux) > ... > I would add option -R or -r for Rock Ridge names and file attributes. > This will make appear the files with their original

I am working with multiboot module "mboot.c32". I have had luck using it to boot NetBSD and the Hurd kernel. The problem with booting the Hurd kernel is apparently connected to the extended syntax passed along to it by grub. Grub passes Hurd kernel approximately 4 files, some of which are modules, and another ten (or so) boot arguments, which correspond to those modules and kernel. The

On Sun, Feb 2, 2014 at 6:27 AM, Mattias Schlenker <ms at mattiasschlenker.de>wrote: [...] > Build a recent xorriso - this can be run from the build directory without > installing (thanks, Thomas!): > > ./configure --enable-static > > Thank you for pointing this out, I tried desperately to statically compile `mkisofs' yesterday, to no avail. To hear that xorriso is

I have not looked into it all that much. But seems that UEFI basically allows booting without a bootloader. Here is some gentoo wiki info in it: http://wiki.gentoo.org/wiki/EFI_stub_kernel And Greg Kroah-Hartman talking about it a bit: http://kroah.com/log/blog/2013/09/02/booting-a-self-signed-linux-kernel/ I am looking forward to making a little HOWTO, for this subject and also for using

Could someone help me get the syntax for `genisoimage' and/or `xorriso' correct? Apparently it is not in many linux distros so below my little HOWTO shows how to compile it. ( which adds tons of crap that can go wrong) mkdir -p ISO_root/isolinux cp /usr/lib/syslinux/[i,m,v]* ISO_root/isolinux cat > ISO_root/isolinux/isolinux.cfg << EOF UI menu.c32 label isolinuxtests EOF # Most