search for: next_entri

Booting a fedora 19 domU failed because a it could not properly parse the grub.cfg file. This was cased by set default="${next_entry}" This statement actually is within an ''if'' statement, so maybe it would be better to skip code within if/fi blocks... But this patch seems to work fine. --- tools/pygrub/src/GrubConf.py | 2 ++ 1 files changed, 2 insertions(+), 0

This grub.cfg from a default fedora 19 Beta install caused pygrub failures.The previous pygrub commit fixed taht. So this example file added for reference. Signed-off-by: Marcel Mol <marcel@mesa.nl> --- tools/pygrub/examples/fedora-19.grub2 | 117 +++++++++++++++++++++++++++++++++ 1 files changed, 117 insertions(+), 0 deletions(-) create mode 100644 tools/pygrub/examples/fedora-19.grub2

I''m trying to run Xen on Arch Linux with UEFI boot. I followed the steps for Xen in the Arch Linux Wiki https://wiki.archlinux.org/index.php/Xen I get the following when attempting to boot: Loading Xen 4.2.2 ... WARNING: no console will be available to the OS Loading Linux linux ... Loading initial ramdisk ... Unfortunately there is no console so I cannot determine what has gone wrong,

Hi all, I''m trying to link to the "Next Entry >>" from the current entry page (in show.html.erb). Any one know how I would do it? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send

Hello When using readdir() on a directory with many files or long file names it can happen that it returns the same file name twice. Attached is a program that demonstrates this. I have traced this problem back to linux-2.6.10-rc1-bk18 and all kernels after this one are effected. linux-2.6.10-rc1-bk17 is still okay. If I reverse the following patch in linux-2.6.10-rc1-bk18, readdir() works again

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Improve readdir. Now returns C struct stat st_mode compatible data in DX rather than the raw data from a FAT filesystem or C struct dirent d_mode compatible data. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- If I return something that's compatible with the C struct stat st_mode member, this can be used for more

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/04/15 10:45, Bastian Blank wrote: > Hi Daniel > > On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote: >> This should probably be released in an update to wheezy. > > Well, if you can pursuade the release team. We have grub2 for Xen > in Jessie now and it can be used on Wheezy as well. > Can you be

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Fh, 0020h, 0021h and 0022h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Fh will return a valid value for all variants. INT22h, AX= 0020h, 0021h, and 0022h are only

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Eh, 001Fh, 0020h and 0021h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Eh will return a valid value for all variants. INT22h, AX= 001Fh, 0020h, and 0021h are only

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012