search for: successfully_

...: root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. _ldap._tcp.[domain].work has no SRV record Then I run: root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp SRV '[dchost].[domain].work 8080 0 100' -Uadministrator Password for [WKDOM\administrator]: Record _added successfully_ And I am still getting: root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. _ldap._tcp.[domain].work has no SRV record If I run the "add" again, I get: root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp SRV '[dchost].[domain].work 8080 0 100' -Uadministr...

...ap._tcp.[domain].work has no SRV record >> >> Then I run: >> >> root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp >> SRV '[dchost].[domain].work 8080 0 100' -Uadministrator >> Password for [WKDOM\administrator]: >> Record _added successfully_ >> >> And I am still getting: >> >> root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. >> _ldap._tcp.[domain].work has no SRV record >> >> If I run the "add" again, I get: >> >> root@[dchost]:~# samba-tool dns add [dchost] [domain]...

...quot; core module load. This latter assumption is not trivial, as the FAT fs is not "real", but an image located on another (ISO9660) volume. Would 'syslinux.efi' be able to do whatever (and everything) it needs to do under these conditions? Could any kernel be _completely and successfully_ booted under these conditions? Rhetorical question: And then what? Syslinux would have access to the FAT volume (usually less than 32MiB), but it would not be able to access the whole ISO9660 file system (or, in other words, the rest of the optical media, outside the FAT image). Remember, as of...

> Hi, > > Ady wrote: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed