search for: 0_

Problem - smbpasswd does not seem to be recognizing my "add user script" option to automatically create Unix users when adding a samba user. I am running Samba version 2.2.8a (from source) on a Linux (Redhat 8.0) system. Relevant lines from smb.conf: [global] server string=Samba Server netbios name = smbpdc security = user domain logons=yes domain master = yes

Now that we can gather diagnostic info, I think I know why our P2Vs kept failing last week. Another one just died right in front of my eyes. I think either the Ethernet or NFS server at this site occasionally "blips" offline when it gets busy and that messes up P2V migrations. The RHEV export domain is an NFS share offered by an old Storagetek NAS, connected over a 10/100 Ethernet.

Hi, I just want to install dovecot 1.0 beta7 from atrpm and noted that it depends on a non official dependency. If you have RHEL4 (Centos) 4.3 fully updated and you try to install: http://dl.atrpms.net/all/dovecot-1.0-0_10.99.beta7.el4.at.i386.rpm You get this error: # rpm -ivh dovecot-1.0-0_10.99.beta7.el4.at.i386.rpm error: Failed dependencies: openssl >= 0.9.7f-4 is needed by dovecot-1.0-0_10.99.beta7.el4.at.i386 The lates official openssl version for RHEL 4.3 is: # rpm -q openssl openssl-0.9.7a-43....

Hello, i have a problem in my sudo manifest file, because in the variable $name comes sometimes usernames like user.lastname, but i need for sudo (includedir */etc/sudoers.d/*) file names with no dots (like user_lastname). I need a new variable, where is the dots change by underscores. My first try was like this, but it isn''t working well. $name_underscore = "`echo $name | sed

Thanks. I've looked through all the links, and it seems everything is fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, but it didn't help). I'd be glad to provide more details, but the error message is the only info I've got by now. It seems nothing else can be got from syslinux shell without modifiying the code. I've tried to make it load the kernel

...s can't >> be avoided. >> >> Thanks, >> Anton >> > > > A: Because it fouls the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > > 0_ Please avoid top-posting. > > 1_ Beware: YOCTO/OE uses a customized Syslinux. > > 2_ It is still not clear (to me) when exactly the failure occurs. Does > it fail before the bootloader? Is the bootloader itself failing? Is the > _kernel_ not loading, after the bootloader step go...

...nux --install /dev/sdc1 Remember (just in case) that the filesystem should be unmounted before executing the syslinux installer command, or use the extlinux installer instead. To reduce some potential problems, I would suggest using a subdirectory instead of the root of the filesystem, e.g.: 0_ mount the filesystem; 1_ create the "/syslinux/" subdirectory on it; 2_ unmount the filesystem; 3_ syslinux --directory syslinux --install /dev/sdc1 If you want to avoid having to unmount the filesystem just to execute this particular command (e.g. if you need to perform additional ope...

I have used syslinux 4.0x and earlier for many years, with Puppy Linux and more recently Quirky Linux. Though, my knowledge of all the capabilities of syslinux remains rudimentary. I am new to UEFI. I recently got my hands on a win8.1 laptop, 64-bit system, and decided to tackle booting Quirky on it, from a USB stick. I turned off Secure Boot. I wrote /usr/share/syslinux/gptmbr.bin to the flash

...mber (just in case) that the filesystem should be unmounted > before executing the syslinux installer command, or use the extlinux > installer instead. > > To reduce some potential problems, I would suggest using a > subdirectory instead of the root of the filesystem, e.g.: > > 0_ mount the filesystem; > 1_ create the "/syslinux/" subdirectory on it; > 2_ unmount the filesystem; > 3_ syslinux --directory syslinux --install /dev/sdc1 > > If you want to avoid having to unmount the filesystem just to execute > this particular command (e.g. if you nee...

...t behaviors (instead of getting the same consistent error each time) might indicate that perhaps the problem is related to hardware or to the filesystem. Syslinux 6.03 (final) might be only the trigger (or, as you say, it might be the culprit; we don't know yet). Some possible suggestions: 0_ Check whether there is a BIOS (firmware) update available for your hardware. 1_ Wipe the first few MBs of your SD-Card, (warning: data will be erased!). 2_ Create a *new* MBR, partition table, and FAT filessytem. 3_ Use (and post here) an adequate, complete syslinux.cfg (especially if it works w...

...e this is where the problem is. Looks like adding debug prints can't > be avoided. > > Thanks, > Anton > A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? 0_ Please avoid top-posting. 1_ Beware: YOCTO/OE uses a customized Syslinux. 2_ It is still not clear (to me) when exactly the failure occurs. Does it fail before the bootloader? Is the bootloader itself failing? Is the _kernel_ not loading, after the bootloader step got already to the boot promp...

Hi I have tried to install syslinux 4.06 on the SD card again, it works like a charm. I am being very carefull with c32 files from the same version bootloader. No success. I am also unmounting /dev/sdb1 before installing syslinux, as mentioned in the given documentations. In the pasted syslinux.cfg content--- I have also tried using only one DEFAULT directive. No success. syslinux boots

...) to go looking for special CHS values. Using Nx64x32 geometry has its advantages, but it also has cons (and I'd rather not to open now an additional discussion about it). @Ronald, I'll start by taking the UBCD USB drive. If you have relevant data on it please perform a backup. Then: 0_ BEWARE: before proceeding with each step, double-check that you are working on the desired device!. 1_ Check that the partition of the UBCD USB device is not mounted. 2_ zero out the first 5MiB of the drive (I am not just talking about the partition, but about the whole drive, including the MBR...

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'm w...

On 28 Mar 2019, at 10.15, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote: > > error = 0x55e3e2b40ac0 "Fixed index file > /var/mail/piast_efaktury/dovecot.index: log_file_seq 13 -> 15", > nodiskspace = true, This was one of the things I was first wondering, but I'm not sure why it's not logging an error. Anyway, you're using filesystem quota? And this

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?) > > > >

...lib/kubelet/pods/fa4c6540-7dad-11e7-8a44- > 062df200059f/volumes/kubernetes.io~glusterfs/pvc-fa4b2621- > 7dad-11e7-8a44-062df200059f'. > > 5h 32s 151 kubelet, k8s-bootcamp-rbac-np-worker-6263f70 Warning > FailedMount Unable to mount volumes for pod "es-data-log-distributed-0_ > monitoring(fa4c6540-7dad-11e7-8a44-062df200059f)": timeout expired > waiting for volumes to attach/mount for pod "monitoring"/"es-data-log-distributed-0". > list of unattached/unmounted volumes=[es-data] > 5h 32s 163 kubelet, k8s-bootcamp-rbac-np-worker-6263...

...- >>> 062df200059f/volumes/kubernetes.io~glusterfs/pvc-fa4b2621- >>> 7dad-11e7-8a44-062df200059f'. >>> >>> 5h 32s 151 kubelet, k8s-bootcamp-rbac-np-worker-6263f70 Warning >>> FailedMount Unable to mount volumes for pod "es-data-log-distributed-0_ >>> monitoring(fa4c6540-7dad-11e7-8a44-062df200059f)": timeout expired >>> waiting for volumes to attach/mount for pod "monitoring"/"es-data-log-distributed-0". >>> list of unattached/unmounted volumes=[es-data] >>> 5h 32s 163 kubelet,...

Hello List Members, I have a machine that has used extlinux to boot for many years, but the hard disk needs to be replaced. I got a new hard disk and installed it in my system. The old disk is /dev/sda, and the new one is /dev/sdb. I'm using GPT partitioning, and I did (after a day) finally get the legacy bootable flag set on /dev/sdb for the boot partition /dev/sda1. I then formatted out

On Wed, Dec 5, 2018 at 2:21 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > 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 mome...