Re: Bug#161931: kernel-image-2.4.19-k7: VESA driver for console

Jason Gunthorpe [EMAIL PROTECTED] wrote: This explains the very strong technical reason why vesafb and fbcon have to be compiled in statically. Basically, the VESA spec defines a set of real mode BIOS calls to do mode switching and interrogate some information about the new video mode. These

Re: Bug#161931: kernel-image-2.4.19-k7: VESA driver for console

#include hallo.h * Herbert Xu [Sun, Nov 03 2002, 10:29:54PM]: The calls cannot be made _ever_ once the kernel has been booted unless you resort to such trickery as using a BIOS emulator like Gerg alluded too. The kernel simply has no mechanism for calling real mode x86 BIOS code. The

Bug#164889: md5sum FILE produces spurious ` -' in output

I would like to refer bugs #164591 and #164889 (these are merged, and I'm the submitter of the latter) to the committee. Below you'll find my summary of the issue. (In the summary, `you' refers to the package maintainer.) I sent Adam (via the BTS) this summary on the 25th of October, and asked

Processed: refer this one

Processing commands for [EMAIL PROTECTED]: reopen 164889 Bug#164889: md5sum FILE produces spurious ` -' in output Bug is already open, cannot reopen. reassign 164889 tech-ctte Bug#164889: md5sum FILE produces spurious ` -' in output Bug#164591: dpkg: md5sum output changed, breaks innocent