search for: systemversion

...e contains: * .VolumeIcon.icns - icon for EFI boot image in macosx * EFI/BOOT/BOOTX64.efi * EFI/BOOT/grub.cfg * mach_kernel - dummy kernel required for boot * System/Library/CoreServices/boot.efi - basically a blessed BOOTX64.efi * System/Library/CoreServices/grub.cfg * System/Library/CoreServices/SystemVersion.plist You can look at mkefiboot.py from fedora's lorax package to see how this was generated. I have a customized copy which generates the macboot.img without the shim support. After you've done generating the iso image with xorriso you can just run: isohybrid --uefi --mac image.iso then...

...lbox Trash { special_use = \Trash } prefix = } passdb { args = session=yes dovecot driver = pam } ssl_cert = </usr/pkg/etc/openssl/certs/dovecot.pem ssl_key = </usr/pkg/etc/openssl/private/dovecot.pem userdb { driver = passwd } $ defaults read "/System/Library/CoreServices/SystemVersion" ProductVersion 10.10.1 Dec 30 13:21:47 my.host.name dovecot[49247]: auth: Debug: auth client connected (pid=49289) Dec 30 13:21:51 my.host.name dovecot[49247]: auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=3bBdlHULNgAAAAAAAAAAAAAAAAAAAAAB lip=::1 rip=::1...

...tion worked, but left with the same problem. There were some errors in the installation log from the installation on this new user: Jul 3 20:58:12 Macintosh-102 Installer[474]: JS: Package Authoring Error: Exception thrown while running volume check. TypeError: Result of expression 'my.target.systemVersion' [undefined] is not an object. and also a series of: Jul 3 20:59:10 Macintosh-102 Software Update[440]: Package Authoring Error: installation-check results requires a message Throughout all of this (except when I created a new user), whenever I re-installed R and started it up, it would sta...

...TALLVER} ${LDCONFIG_PLIST} ${LDCONFIG_RUNLIST} Actually, the way that _PORTDIRNAME is set is inefficient. I think you may be able to use make's variable substitution rather than making a (slow) call to ${BASENAME}. Given that BSDPORTMKVERSION is stuck back in the year 2000, I suspect that SYSTEMVERSION may no longer be used. I couldn't find it in any port Makefiles. This isn't as important as it used to be since bsd.port.mk doesn't rely on recursive ${MAKE} processes as much anymore. All the same, I do measure a significant speed improvement for 'make readme'. It is probab...

I've been using various versions of syslinux as the boot loader for the g4l project that I have been the maintainer of since 2004. It was already using syslinux, so I've just updated it over the years, and currently have it use 5.10 version, but have done test builds with the 6.x versions. Recently had request from to users about EFI support, and one suggested that virtualbox has

...ntavista-linux" "/usr/bin/../lib/i686-montavista-linux" "/usr/bin/../lib/gcc/i386-unknown-freebsd9.2" "/usr/bin/../lib/i386-unknown-freebsd9.2/gcc/i386-unknown-freebsd9.2" "/usr/bin/../lib/i386-unknown-freebsd9.2" [...] "/System/Library/CoreServices/SystemVersion.plist" [...]