The reason for the three operating systems on the same hard drive (FreeBSD 10.0, Debian kfreebsd-i386, Debian vanilla i386) is to eventually migrate to a root-on-zfs with Debian kfreebsd-i386.
I should emphasize that this behavior occurs when I''m running Debian kfreebsd-i386. That's why the bug submission puts kfreebsd-i386 in the title. The behavior is normal with the Linux kernel. Under the vanilla Linux kernel, the command line: eject /dev/cdrom ejects the tray with the DVD. There is something wrong regarding the kfreebsd-i386 eject command . Either eject isn't supposed to work and I should be using something else, or there is a bug in the eject executable thats sending the wrong ioctl to the Freebsd kernel. I'll download the xorriso program and use scp to copy it to the Debian kfreebsd-i386 system. It will be a useful test. Look for an email tomorrow. On Mon, Oct 20, 2014 at 11:32 PM, Thomas Schmitt <scdbac...@gmx.net> wrote: > Hi, > > (cc'ing debian-bsd@lists.debian.org again) > > Urm ... before we dig deeper with burn programs: > Is your laptop drive physically able to eject, at all ? > > Many laptop drives need the mechanical power of the user > to come out. I.e. if you have to press the eject button > with some force and if no electric motor is to hear, > then probably it cannot eject on its own. > > -------------------------------------------------------- > Only if it does have a motor to eject the tray, it is > worth to try on: > > DAVID Henderson <dghkd...@gmail.com> wrote: > > > Your programs dont seem to work. > > wodim is not by me. :)) > > > I've got the HP laptop system connected to a network with only local > > access, so I can't install packages not in the wheezy 7.6.0/update > > DVD set. > > ... > > root@hpdkfre:~# aptitude install cdrskin > > No candidate version found for cdrskin > > ... > > root@hpdkfre:~# aptitude install xorriso > > No candidate version found for xorriso > > I am clueless how to install the packages without internet > access. Maybe one of the bystanders can help. > > If you can get somehow > > http://www.gnu.org/software/xorriso/xorriso-1.3.8.tar.gz > > and transport it somehow to your machine, you may > put xorriso-1.3.8.tar.gz into your $HOME directory > and do: > > cd $HOME > tar xzf xorriso-1.3.8.tar.gz > cd xorriso-1.3.8 > ./configure --prefix=/usr > make > xorriso/xorriso -version > > If the last of these commands tells you: > > GNU xorriso 1.3.8 : RockRidge filesystem manipulator, libburnia project. > ... > There is NO WARRANTY, to the extent permitted by law. > > then you are ready for the eject test: > > $HOME/xorriso/xorriso -outdev /dev/cd0 -eject all > > (Note that xorriso is not installed at this moment but > already can used by its absolute file address. > All its files are contained in $HOME/xorriso-1.3.8. > So you may easily remove them by removing that file tree.) > > If xorriso says that no device is usable, then have a look > at the file permissions of /dev/cd0 : > > ls -l /dev/cd0 > > You need rw-permission for the user who wants to operate > the drive. Most liberal and insecure would be this setting: > > chmod a+rw /dev/cd0 > > This chmod setting is supposed to vanish when you reboot. > > Maybe the kFreeBSD experts here can tell you whether the > following permanent permission setting receipe for FreeBSD 8 > is valid on Debian/kFreeBSD too: > > --------------------------------------------------------- > Edit /etc/devfs.rules and make sure to have these lines > [localrules=10] > add path 'acd*' mode 0664 group floppy > add path 'cd*' mode 0664 group floppy > add path 'pass*' mode 0664 group floppy > add path 'xpt*' mode 0664 group floppy > [localrules=5] > add path 'pass*' mode 0664 group floppy > add path 'cd*' mode 0664 group floppy > add path 'xpt*' mode 0664 group floppy > add path 'acd*' mode 0664 group floppy > > Edit /etc/rc.conf and add the following line if missing > devfs_system_ruleset="localrules" > > This gets into effect by reboot or by command > /etc/rc.d/devfs start > --------------------------------------------------------- > > If setting of permissions does not help, learn xorriso's > absulute file path: > > echo "absolute path: $HOME/xorriso/xorriso" > > become superuser (aka user name "root") and execute > > ...above.absolute.path.to.xorriso... -devices > > to learn about available drive addresses. > > > Have a nice day :) > > Thomas > >
