Displaying 4 results from an estimated 4 matches for "ndisability".
Did you mean:
  disability
  
2005 Jun 13
2
[PATCH] fix x86_64 initrd support
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 =====
---
2007 May 30
0
Headers munged into RAW_POST_DATA
...roller"=>"ad_keywords", "Connection: Keep-Alive\r
\nad_keyword"=>{"smart_keywords"=>"Non Emergency Transport \r\nNon
Emergency Transportation\r\nTransportation for Disabled\r\nTransport
for Disabled\r\nHandicap Transportation\r\nHandicap Transport\r
\nDisability Transportation\r\nDisability Transport\r\nMedical
Transportation Service\r\nMedical Transport Service\r\nMedical
Transportation \r\nMedical Transport \r\nMedical Transportation Vans\r
\nMedical Transport Vans\r\nMedical Patient Transportation \r\nMedical
Patient Transport"}, "cid"=&g...
2007 May 29
1
Headers munged into RAW_POST_DATA
..."=>"ad_keywords", "Connection: Keep-Alive\r\nad_keyword"=> 
{"smart_keywords"=>"Non Emergency Transport \r\nNon Emergency  
Transportation\r\nTransportation for Disabled\r\nTransport for  
Disabled\r\nHandicap Transportation\r\nHandicap Transport\r 
\nDisability Transportation\r\nDisability Transport\r\nMedical  
Transportation Service\r\nMedical Transport Service\r\nMedical  
Transportation \r\nMedical Transport \r\nMedical Transportation Vans\r 
\nMedical Transport Vans\r\nMedical Patient Transportation \r 
\nMedical Patient Transport"}, "cid&q...
2025 Feb 10
1
Installing and running NUT on OpenBSD
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