search for: dpchrist

...be unpacked in a suitable directory by > > tar xvzf block_seq.tgz > > The binary "block_seq" was compiled on Debian Jessie. > If it does not run, do > > cc -o block_seq block_seq.c > > to get a locally compiled binary. Build your code: 2017-03-21 12:31:07 dpchrist at hd-tracy ~ $ cat /etc/debian_version 8.7 2017-03-21 12:33:27 dpchrist at hd-tracy ~ $ uname -a Linux hd-tracy 3.16.0-4-686-pae #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) i686 GNU/Linux 2017-03-21 12:33:29 dpchrist at hd-tracy ~ $ cd sandbox/syslinux/thomas-schmitt/block_seq-20170321-0141/ 2...

Hi, i have uploaded a little gz compressed tarball http://scdbackup.webframe.org/block_seq.tgz containing -rwxr-xr-x thomas/thomas 4552 2017-03-21 09:23 block_seq -rw-r--r-- thomas/thomas 315 2017-03-21 09:22 block_seq.c To be unpacked in a suitable directory by tar xvzf block_seq.tgz The binary "block_seq" was compiled on Debian Jessie. If it does not run, do cc -o

...irectories: $ touch /mnt/z/data/GroupShare/foo $ mkdir /mnt/z/data/GroupShare/bar $ ll /mnt/z/data/GroupShare total 12 drwxrwsrwx+ 3 groupshare groupshare 4096 2013/09/09 16:19:27 ./ drwxr-xr-x 7 root root 4096 2013/09/09 16:18:51 ../ drwxrwsrwx+ 2 dpchrist groupshare 4096 2013/09/09 16:19:27 bar/ -rw-rw-rw-+ 1 dpchrist groupshare 0 2013/09/09 16:19:20 foo However, the directory doesn't work as intended if users copy or move files or directories: $ touch foo2 $ cp foo2 /mnt/z/data/GroupShare/. $ touch foo3 $...

...000000000000000000000 > ... > 00000000000000000000000000000000 Well, this is none of the block contents which was written to the stick. Neither the MBR parts nor the data dummy. Do you get the same result if you fill the entire stick with block_seq by omitting dd option count=647 ? /home/dpchrist/sandbox/syslinux/thomas-schmitt/block_seq-20170321-0141/block _seq | dd iflag=fullblock bs=1M of=/dev/sdb which will end intentionally by i/o error. And then again dd if=/home/dpchrist/src/syslinux/syslinux-6.03+dfsg+dpchrist/bios/mbr/martins_mbr.bin of=/dev/sdb dd if=/mnt/samba/data/dpchrist...

syslinux at zytor.com: I have two older computers with Intel D865GBFLK motherboards (~2003) and Pentium 4 HT CPU's. They both have the latest available BIOS installed. I would like to put Debian on them. I have downloaded: http://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-8.7.1-i386-xfce-CD-1.iso When I put debian-8.7.1-i386-xfce-CD-1.iso on a CD-R, it boots correctly.

...~ # time dd if=/dev/zero of=/dev/sdc bs=1M; sync :195,dd: writing `/dev/sdc': No space left on device 3820+0 records in 3819+0 records out 4004511744 bytes (4.0 GB) copied, 911.198 s, 4.4 MB/s real 15m11.204s user 0m0.000s sys 0m7.888s 2017-03-18 12:40:31 root at cd2533 ~ # cd /var/local/data/dpchrist/iso/debian/8.7.1/i386/ 2017-03-18 12:40:50 root at cd2533 /var/local/data/dpchrist/iso/debian/8.7.1/i386 # grep debian-8.7.1-i386-xfce-CD-1.iso SHA256SUMS a258af89540a64e6d16d6a546ec554a07ef0d46168d74bfc2073cc60d6a9ecde debian-8.7.1-i386-xfce-CD-1.iso 2017-03-18 12:41:06 root at cd2533 /var/local...

...Debian wants/needs on each > system. That's for Debian (and its community) to support (hint: the cfg > files in the ISO image should give you a first clue, and they can > probably be used almost as-is). There is no syslinux.cfg on debian-8.7.1-i386-xfce-CD-1.iso: 2017-03-19 22:39:42 dpchrist at jesse ~ $ find /media/dpchrist/Debian\ 8.7.1\ i386\ 1/ -name syslinux.cfg <nothing> Thanks, everyone, for your patience and assistance. :-) I will try to do an install later, and will report the result. David

> On 03/19/2017 04:03 PM, David Christensen wrote: > > [ 0.600883] ---[ end Kernel panic - not syncing: VFS: Unable to mount > > root fs on unkonwn-block(0,0) > > Similar kernel panic when booted on Intel DQ67SW i7-2600S. > > > David > That's because your syslinux.cfg is "wrong", but the behavior just proves that SYSLINUX is indeed

...block 0, you may mount it too > > mount /dev/sdc1 /mnt/iso Or, using a loop device and the *.iso file: 2017-03-18 17:31:22 root at cd2533 ~ # mkdir /mnt/iso 2017-03-18 17:48:16 root at cd2533 ~ # losetup -d /dev/loop0 2017-03-18 17:51:32 root at cd2533 ~ # losetup -r -f /var/local/data/dpchrist/iso/debian/8.7.1/i386/debian-8.7.1-i386-xfce-CD-1.iso 2017-03-18 17:52:13 root at cd2533 ~ # losetup -a /dev/loop0: [fe02]:126616474 (/var/local/data/dpchrist/iso/debian/8.7.1/i386/debian-8.7.1-i386-xfce-CD-1.iso) 2017-03-18 17:52:48 root at cd2533 ~ # mount /dev/loop0 /mnt/iso mount: block devi...

...I interpreted: https://www.debian.org/releases/jessie/i386/ch04s03.html.en#usb-copy-flexible If you used an hd-media image, you should now copy the ISO file of a Debian ISO image[4] onto the stick. When you are done, unmount the USB memory stick (umount /mnt). As: # cp -ip /mnt/samba/data/dpchrist/iso/debian/8.7.1/i386/debian-8.7.1-i386-xfce-CD-1.iso /mnt/usb/. >> Should I be asking on the debian-boot or debian-cd mailing lists? > > Yep, debian-cd at lists.debian.org should be the right one. > I'd tell briefly what i did to set up the stick. If i had to equip a .cfg &gt...

Debian Users, Cygwin, & Rsync: I'm having trouble with rsync invoked on Debian 5.0.3 pulling files from Windows XP SP3/ Cygwin 1.5.25. I posted to the Debian User and Cygwin mailing lists [1] and thought I was done two days ago, but I wasn't -- after several hours of use of the Windows machine, rsync would again hang on Debian. To summarize, rsync pulls in perhaps 1,000 files from

...primary fat16 0% 100% Information: You may need to update /etc/fstab. # parted /dev/sdb set 1 boot on Information: You may need to update /etc/fstab. # install-mbr /dev/sdb # mkdosfs /dev/sdb1 mkfs.fat 3.0.27 (2014-11-12) # syslinux /dev/sdb1 # mkdir /mnt/iso # mount /mnt/samba/data/dpchrist/iso/debian/8.7.1/i386/debian-8.7.1-i386-xfce-CD-1.iso /mnt/iso # mkdir /mnt/usb # mount /dev/sdb1 /mnt/usb # cp -ip /mnt/iso/install.386/vmlinuz /mnt/usb/. # cp -ip /mnt/iso/install.386/initrd.gz /mnt/usb/. # echo "default vmlinuz" >> /mnt/usb/syslinux.cfg # echo "append...

Package: xcp-xapi Version: 1.3-16 Severity: normal Tags: patch Dear Maintainer, Path to "xe" program in /usr/lib/xcp/bin/xe-mount-iso-sr should be: XE="/usr/bin/xe" HTH, David -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)

On 03/19/2017 11:28 PM, David Christensen via Syslinux wrote: > I will try to do an install later, and will report the result. Booting the USB flash drive I prepared, the Debian installer runs: Select a language English Select your location United States Configure the keyboard American English Detect and mount CD-ROM Incorrect CD-ROM detected The CD-ROM drive contains a CD which

On 03/19/2017 04:03 PM, David Christensen wrote: > [ 0.600883] ---[ end Kernel panic - not syncing: VFS: Unable to mount > root fs on unkonwn-block(0,0) Similar kernel panic when booted on Intel DQ67SW i7-2600S. David

On 03/19/2017 09:05 AM, Ady Ady via Syslinux wrote: > Now, besides this whole discussion and with no reference to anyone in > particular nor offense intended, I have to admit that I am a little bit > tired of answering questions related to how an ISO image either fails > or succeeds when booting from USB (we both have been part of these > discussions during the last few years) . I

On 03/19/2017 09:42 PM, Martin Str|mberg via Syslinux wrote: > David Christensen wrote: >> This is how I prepared an ADATA USB Flash Drive 4 GB: > ... > install-mbr /dev/sdb > ... > [Rest of very clear description snipped.] > > What's that? That desn't exist in the Debian I'm running. > Otherwise you gave a very good description of what you're doing.

On 03/19/2017 01:12 AM, Ady Ady via Syslinux wrote: > Regarding distros for older computers, there are several. The > problem, at least at this point, is bootability. Although Antix is > for older computers, it is also based on Debian and the latest > ISOLINUX will also be bigger than 32KiB. Perhaps Knoppix or some (of > the many) PuppyLinux would still use ISOLINUX 4.xx or older.

On 03/18/2017 04:15 PM, Ady Ady via Syslinux wrote: > >> On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: >>> _ With the USB device connected to (one of) the problematic >>> computer(s), power up the system and get into the BIOS setup. In >>> the BIOS setup screen(s), change the boot order in such way that >>> the USB device is recognized as first