Hello, On Thursday 19 July 2007 23:25, Raymond Luong wrote: > Sorry to bother you but I really need to know if there is a solution to > this.
Yes, I saw your bug report on this yesterday. > > > It seems the bacula-rescue code does not come with usb support. Doesn't > matter what version of bacula-rescue I use. Once I get to the login prompt, > I lose my usb keyboard. When I us a pc with ps2 keyboard, everything work > fine. Unfortunately all my server only has usb and no ps2. I'm not too surprised, but it is a bit of a shame. > > Is there anyway I can fix or overcome this problem. I really need to get the > rescue cd working. Well, I've come to realize that regardless of the importance I place on the rescue cd, it is very difficult to maintain due to the different ways that distros handle booting (they sometimes change from version to version) and to the rapid evolution of devices that are supported. Each device typically requires some specific code to get it working, and that code is often different on each distro. The only solutions I see to this are: 1. devote a huge amount of time to working on the rescue cd (something I can unfortunately not do). 2. Find some package that does this so that the package maintainer will resolve all these issues when they come up. There are several out there, but as far as I can tell, it will take a good amount of work to convert. The future prospects are looking quite good though as there are more and more LiveCDs which do essentially what we want, and they are becoming common with almost all major distros. Probably the most promising is the KIWI Image System (openSUSE). However, this will require someone with some time and engery. 3. Rely on contributions from users such as yourself. For the moment, I've been doing a bit of all the above, I even previously converted it to use a 3rd party package. However, for the moment, I rely mostly on item 3 (user contributions). If you wait long enough (6 months), the problem will hit me (all my new machines have USB keyboards), and I will fix it. If you want to fix it sooner, you can do it yourself. First read the README. It gives you a good feeling about how the process works, particularly the booting. Then for your distro, figure out how it brings up the keyboard by looking at the output of dmesg. It is probably a USB HID device, and the output should show you what driver is needed. Ensure the correct driver is saved by Bacula (probably), then make sure it is explicitly loaded in the Bacula boot sequence, and make sure that the appropriate startup calls are made. This you can do by looking at your distros startup scripts and making sure that Bacula does the same thing. To speed up development and testing use qemu to test the new boot images. If you get it working, be sure to send us a patch. That's about all I can do to help you. Implementing this stuff is a bit tricky and frustrating, because during the boot sequence if something breaks, usually not much info is printed, and you are left in a state where you can do nothing ... Good luck, Kern > > > > I would really appreciate any help you can provide. > > > > Raymond > > > > Raymond Luong > > IT Department > > Mocana Corporation > > 350 Sansome st. Ste. 210 > > San Francisco, Ca. 94104 > > (415) 617-0055 x3016 > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
