similar to: smbd crashes on Debian Lenny if using Debian's

I'm hoping to find the CentOS version of Debian's /etc/apt/sources.list "yum install program" isn't running properly on one server, and I'm wondering if the repositories (or whatever the yum equivalent is) are pointing to good places. Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, For those who run tinc on Debian or Debian-based distributions like Ubuntu and Knoppix, be advised that the following security issue affects tinc as well: http://www.debian.org/security/2008/dsa-1571 In short, if you generated public/private keypairs for tinc between 2006 and May 7th of 2008 on a machine running Debian or a derivative, they may have been generated without a properly

Hello, For those who run tinc on Debian or Debian-based distributions like Ubuntu and Knoppix, be advised that the following security issue affects tinc as well: http://www.debian.org/security/2008/dsa-1571 In short, if you generated public/private keypairs for tinc between 2006 and May 7th of 2008 on a machine running Debian or a derivative, they may have been generated without a properly

I have watched the discussions about the size of the R user base with much interest. One more source of data that might help is the voluntary data capture in Debian. If you are a Debian user, you should volunteer information. It's very easy: as root, say: # apt-get install popularity-contest The results are found at: http://popcon.debian.org/main/math/by_inst This shows that of the

> Now it is just dd, mkfs and copy in the files we need. > One less thing to worry about keeping versions consistent. > > > I just noticed those 2 files that were added by > > > syslinux -i boot.img > > > (right?) > > > > > > Yes, those 2 files came from your 'syslinux' command (in your other > > email). We don't want anything

Here are some comments and questions for you. > I want to eufi boot this image: > http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz I am going to assume that by "boot this image" you don't mean something like memdisk or equivalent, but rather that you want to transfer that image using "dd" to your

On Wed, Aug 24, 2011 at 6:36 PM, Marc J. Driftmeyer <mjd at reanimality.com> wrote: > I've got a simple workaround which obviously everyone will figure out: > > mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crti.o crti.o > mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crt1.o crt1.o > mdriftmeyer at horus:/usr/lib$ sudo ln -s

> > When booting in UEFI x64 mode in your next test, you should see a boot > > menu. > > Nope: > > *** Press enter to boot the default label *** > Failed to load libcom32.c32 > Failed to load COM32 file SYSLINUX/EFI64/vesamenu.c32 > boot: > > > I'd like to ask you to test all the entries in the menu and > > report the results for each. If,

> it works. (boots into the d-i installer, I don't care if the installer > is missing stuff, booting it is all we care about here. OK, so let's add complexity (but not the whole thing, not yet). We already have: target ??? EFI ? ??? BOOT ? ? ??? BOOTX64.EFI ? ? ??? LDLINUX.E64 ? ? ??? SYSLINUX.CFG ? ??? syslinux ??? initrd.gz ??? linux The

After some discussion/debugging behind the scenes, we are back on track, with updated Debian packages. 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted in "target" (or "$target", or some similar notation), and the version of Syslinux-related packages in the OS should be "6.04~git20171011.af7e95c3+dfsg1-6" or newer. At the moment

> > > I think add some lines around here: > > > > > > https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/x86.cfg#L113-115 > > > > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/vesamenu.c32 > > > ::vesamenu.c32; \ > > > mcopy -i$(TEMP_BOOT) /usr/lib/syslinux/modules/bios/libcom32.c32 > >

Seeing as GCC 4.6 works without breaking to build LLVM instead of Clang I think I'm going to bug the Debian proper to make it easier for Clang/LLVM to get the linker update changes. After all, Debian's breaking an awful lot of stuff lately so it seems reasonable for them to add this to their To Do List. - Marc On 08/24/2011 07:15 PM, Eli Friedman wrote: > On Wed, Aug 24, 2011 at

> > _ target/EFI/BOOT/SYSLINUX.CFG > > I don't think that exists? (see list below) In our "first test" (simple boot prompt), we created "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ "target/EFI/BOOT/SYSLINUX/EFI64/SYSLX64.CFG". Part of my intention was to test whether it actually reaches one cfg or the other.

Debian's response I enclose to see if this helps out: > reassign 639214 general > forcemerge 637232 639214 > quit > > Hi Marc, > > Marc J. Driftmeyer wrote: > >> With the most recent changes of moving the object files under >> /usr/lib/x86_64-linux-gnu/ the linker to build Clang/LLVM breaks. >> >> A workaround is to add symlinks for crt1.o,

> On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > Here are some comments and questions for you. > > > > Thanks. > > I've have my scripts to a better state, including installing/using > qemu to uefi and legacy boot the usb stick for testing. > > It mostly works for me, but the "wget a tarball of

I've got a simple workaround which obviously everyone will figure out: mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crti.o crti.o mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crt1.o crt1.o mdriftmeyer at horus:/usr/lib$ sudo ln -s x86_64-linux-gnu/crtn.o crtn.o My real question concerns whether or not I should file a bug report against Debian not having a

I want to eufi boot this image: http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz there is a bug against it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913523 I'd like to fix the resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

On Fri, Nov 30, 2018 at 9:56 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I have a proposal for you here (in the Syslinux mailing list): let's > first find out _what_ exactly is required in order to boot in UEFI > mode, and then you can take the info downstream. Whether "downstream" > means your own personal customized boot.img, or