search for: ndisable

Looks like x86_64 never quite handled initrd''s. This brings x86_64 in line with i386 in that it doesn''t check LOADER_TYPE (which will be zero anyway). Now initrd is working fine for me on x86_64. Signed-off-by: Chris Wright <chrisw@osdl.org> ===== linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/setup.c 1.6 vs edited ===== ---

Hi, we''re seeing a really weird problem in our production environment. "Connection: Keep-Alive\r\n" is being pre-pended to the RAW_POST_DATA, which makes requests error out. This bug is seen infrequently and *seems* to be browser-related, although I can''t reproduce it using the browser reported in HTTP_USER_AGENT. Set up is a apache 2.2 -> hardware load balancer

Hi, we''re seeing a really weird problem in our production environment. "Connection: Keep-Alive\r\n" is being pre-pended to the RAW_POST_DATA, which makes requests error out. This bug is seen infrequently and *seems* to be browser-related, although I can''t reproduce it using the browser reported in HTTP_USER_AGENT. Set up is a hardware load balancer (NetScaler)

Hello, sorry and puzzled to hear about that. My guess would be permissions - while nut-scanner remains `root` (if started as one) and sees everything, drivers default to dropping privileges and may not see the devfs nodes (not sure OTOH which paths are involved on OpenBSD). One experimental workaround can be adding `user=root` to `ups.conf` entry for the device. But properly - tame whichever