FeeBSD 9.2-RC1 sendmail alisases.db missing
Hello :-) On a fresh install of FreeBSD 9.2-RC1 I get this warning: sm-mta[]: SYSERR(root): hash map "Alias0": missing map file /etc/mail/aliases.db: No such file or directory. /etc/mail/aliases.db is missing and probably not generated from /etc/mail/aliases which seems to be on place. Please fix :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FeeBSD 9.2-RC1 sendmail alisases.db missing
Le 12/08/2013 14:27, CeDeROM a écrit : > Hello :-) > > On a fresh install of FreeBSD 9.2-RC1 I get this warning: > > sm-mta[]: SYSERR(root): hash map "Alias0": missing map file > /etc/mail/aliases.db: No such file or directory. > > /etc/mail/aliases.db is missing and probably not generated from > /etc/mail/aliases which seems to be on place. > > Please fix :-) > > Best regards :-) > Tomek > Should'nt we do a cap_mkdp /etc/aliases ? It made the job for me. signature.asc Description: OpenPGP digital signature
Installer on serial-console-only-embedded system
Hello :-) With my friend Jacek we have tried to perform PXE installation of FreeBSD 9 on an i386 embedded system for one project. This required adding "-h" or "comconsole" to the /boot/loader.conf so the input-output is done with serial console port, not video console. However, after installation, on this embedded system with no video console, system seems to be configured to use videoconsole by default... Is it possible to add this nice feature to the new installer that would recognise if installation is done with serial-port-console and then setup the installed system to work with serial-port-console by default not the videoconsole? We could try it out on 9.2-RC2 if possible :-) Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FeeBSD 9.2-RC1 sendmail alisases.db missing
On Mon, Aug 12, 2013 at 02:29:01PM +0200, Florent Peterschmitt wrote: > Le 12/08/2013 14:27, CeDeROM a écrit : > > Hello :-) > > > > On a fresh install of FreeBSD 9.2-RC1 I get this warning: > > > > sm-mta[]: SYSERR(root): hash map "Alias0": missing map file > > /etc/mail/aliases.db: No such file or directory. > > > > /etc/mail/aliases.db is missing and probably not generated from > > /etc/mail/aliases which seems to be on place. > > > > Please fix :-) > > > > Best regards :-) > > Tomek > > > Should'nt we do a cap_mkdp /etc/aliases ? It made the job for me. Uh -- does it? Normally you'ld rebuild the aliases.db using makemap(1) via the handy Makefile in /etc/mail: # cd /etc/mail # make ISTR this used to happen at some point as part of the install process. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk pgpEUFq8N_hUu.pgp Description: PGP signature
Re: Installer on serial-console-only-embedded system
You need to change /etc/ttys to turn off the virtual consoles and turn on a serial terminal. E.g., ttyv0 "/usr/libexec/getty Pc" xterm off secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" xterm off secure ttyv2 "/usr/libexec/getty Pc" xterm off secure ttyv3 "/usr/libexec/getty Pc" xterm off secure ttyv4 "/usr/libexec/getty Pc" xterm off secure ttyv5 "/usr/libexec/getty Pc" xterm off secure ttyv6 "/usr/libexec/getty Pc" xterm off secure ttyv7 "/usr/libexec/getty Pc" xterm off secure ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 "/usr/libexec/getty std.9600" dialup on secure ttyu1 "/usr/libexec/getty std.9600" dialup off secure ttyu2 "/usr/libexec/getty std.9600" dialup off secure ttyu3 "/usr/libexec/getty std.9600" dialup off secure # Dumb console dcons "/usr/libexec/getty std.9600" vt100 off secure On Mon, Aug 12, 2013 at 8:34 AM, CeDeROM wrote: > Hello :-) > > With my friend Jacek we have tried to perform PXE installation of > FreeBSD 9 on an i386 embedded system for one project. This required > adding "-h" or "comconsole" to the /boot/loader.conf so the > input-output is done with serial console port, not video console. > However, after installation, on this embedded system with no video > console, system seems to be configured to use videoconsole by > default... > > Is it possible to add this nice feature to the new installer that > would recognise if installation is done with serial-port-console and > then setup the installed system to work with serial-port-console by > default not the videoconsole? We could try it out on 9.2-RC2 if > possible :-) > > Best regards! :-) > Tomek > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > ___ > freebsd-embed...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Installer on serial-console-only-embedded system
On Mon, Aug 12, 2013 at 2:56 PM, Michael Sierchio wrote: > You need to change /etc/ttys to turn off the virtual consoles and turn > on a serial terminal. > (..) Thank you Michael for the hint! Do you think it would be sensible to put that functionality into a new installer to detect this kind of configuration and apply it over fresh system during install (just as it detects and verifies some partitioning formats)? Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Installer on serial-console-only-embedded system
On Mon, Aug 12, 2013 at 4:00 PM, CeDeROM wrote: > On Mon, Aug 12, 2013 at 2:56 PM, Michael Sierchio wrote: >> You need to change /etc/ttys to turn off the virtual consoles and turn >> on a serial terminal. >> (..) > > Thank you Michael for the hint! Do you think it would be sensible to > put that functionality into a new installer to detect this kind of > configuration and apply it over fresh system during install (just as > it detects and verifies some partitioning formats)? > > Best regards! :-) > Tomek > > -- You can easily detect that the system has a COM port. However, it is very hard to detect that there is a working terminal attached to the port. -Kimmo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Installer on serial-console-only-embedded system
On Mon, Aug 12, 2013 at 3:11 PM, Kimmo Paasiala wrote: > You can easily detect that the system has a COM port. However, it is > very hard to detect that there is a working terminal attached to the > port. > -Kimmo Hey Kimmo :-) Wouldn't "who" or "w" show that what terminal is user/installer running on? :-P Sorry I don't have that device for testing at hand, but try to verify that with some older hardware :-) Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9.2-RC1 rc.firewall workstation type and myservices
Hello :-)
I just have setup some service on 9.2-RC1. I want this service to be
available on WAN but still I want to have stateful firewall running. I
am using workstation firewall type and put the service port on
firewall_myservices. However by default only TCP connections are
accepted, still I need to serve UDP connections. Wouldn't that be more
convenient to change "TCP" into "IP" for default firewall_myservices
and maybe add TCP and UDP for firewall_myservices_{tcp,udp} ? Below is
the script part..
Best regards,
Tomek
# Add permits for this workstations published services below
# Only IPs and nets in firewall_allowservices is allowed in.
# If you really wish to let anyone use services on your
# workstation, then set "firewall_allowservices='any'" in /etc/rc.conf
#
# Note: We don't use keep-state as that would allow DoS of
# our statetable.
# You can add 'keep-state' to the lines for slightly
# better performance if you fell that DoS of your
# workstation won't be a problem.
#
for i in ${firewall_allowservices} ; do
for j in ${firewall_myservices} ; do
${fwcmd} add pass tcp from $i to me $j
done
done
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Installer on serial-console-only-embedded system
sysinstall had the ability to allow you to muck with /etc/ttys before rebooting to your installed OS. This functionality is coming back slowly. In 9.2-R you will be able to (somehow) bow out of the installation process after it's complete (e.g., "Ctrl-C" ??) and then run bsdconfig -- invoking the "TTYs" module, giving you a chance to change the settings before you reboot from your newly installed system. Tighter Integration will follow in the years to come... but replacing a tool that had a 15-year run which did _all_ of this stuff, is/was not an overnight project. Rather, it's a journey! -- Devin On Aug 12, 2013, at 5:56 AM, Michael Sierchio wrote: > You need to change /etc/ttys to turn off the virtual consoles and turn > on a serial terminal. > E.g., > > ttyv0 "/usr/libexec/getty Pc" xterm off secure > # Virtual terminals > ttyv1 "/usr/libexec/getty Pc" xterm off secure > ttyv2 "/usr/libexec/getty Pc" xterm off secure > ttyv3 "/usr/libexec/getty Pc" xterm off secure > ttyv4 "/usr/libexec/getty Pc" xterm off secure > ttyv5 "/usr/libexec/getty Pc" xterm off secure > ttyv6 "/usr/libexec/getty Pc" xterm off secure > ttyv7 "/usr/libexec/getty Pc" xterm off secure > ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure > # Serial terminals > # The 'dialup' keyword identifies dialin lines to login, fingerd etc. > ttyu0 "/usr/libexec/getty std.9600" dialup on secure > ttyu1 "/usr/libexec/getty std.9600" dialup off secure > ttyu2 "/usr/libexec/getty std.9600" dialup off secure > ttyu3 "/usr/libexec/getty std.9600" dialup off secure > # Dumb console > dcons "/usr/libexec/getty std.9600" vt100 off secure > > On Mon, Aug 12, 2013 at 8:34 AM, CeDeROM wrote: >> Hello :-) >> >> With my friend Jacek we have tried to perform PXE installation of >> FreeBSD 9 on an i386 embedded system for one project. This required >> adding "-h" or "comconsole" to the /boot/loader.conf so the >> input-output is done with serial console port, not video console. >> However, after installation, on this embedded system with no video >> console, system seems to be configured to use videoconsole by >> default... >> >> Is it possible to add this nice feature to the new installer that >> would recognise if installation is done with serial-port-console and >> then setup the installed system to work with serial-port-console by >> default not the videoconsole? We could try it out on 9.2-RC2 if >> possible :-) >> >> Best regards! :-) >> Tomek >> >> -- >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >> ___ >> freebsd-embed...@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >> To unsubscribe, send any mail to "freebsd-embedded-unsubscr...@freebsd.org" > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Geom mirror regression in 9.2-RC1
I want to use old gmirror disk, created in 8.0-RELEASE on new 9.2-RC1 machine When I attach this disk, I see only /dev/mirror/gm0, instead of /dev/mirror/gm0 and /dev/mirror/gm0s1 I forced to manually load geom_mbr.ko to use this disk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Change in loader or kernel: won't boot with kfreebsd in grub2
> Hmm I just tested super_grub2_disk_hybrid_2.00s1-beta5.iso from > http://www.supergrubdisk.org/category/download/supergrub2diskdownload/ > if it can boot FreeBSD-9.2-RC1-amd64-memstick.img in qemu and I > had to fix "kfreebsd" spelled as "freebsd" and "kfreebsd_loadenv" > spelled as "frebsd_loadenv", replace /boot/kernel/kernel with > /boot/loader, and I in the loader I then had to set currdev=disk1a > (shown by lsdev) and load /boot/kernel/kernel. qemu was started > like this: > qemu-system-x86_64 -cdrom super_grub2_disk_hybrid_2.00s1-beta5.iso > -hda FreeBSD-9.2-RC1-amd64-memstick.img -m 512 -boot d -monitor stdio > Letting super_grub2_disk_hybrid_2.00s1-beta5.iso boot the kernel > directly via kfreebsd /boot/kernel/kernel fails tho because of a this > bug in the vanilla grub 2.00 code: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002 > (The fix for that bug now is in our sysutils/grub2 port as well as > in debian's grub 2.00 but apparently not yet in the super grub disk > isos.) > So maybe your problem is that loader needs currdev set at least > in this case and in your old 9.0 installation it didn't? HTH, :) > Juergen I still wonder why Super Grub Disk kfreebsd worked until recently. I figure something must have changed in FreeBSD loader or kernel structure since the Super Grub Disk didn't change in that time. For currdev, apparently the big hard drive is just recognized as one big drive with no reference to partitions (lsdev). I could try building grub2 from ports on both the hard-drive installation and the USB-stick amd64 installation, see what possibilities are then available. FreeBSD gpart can create a boot partition, but then the question is how to boot that when there is more than one OS partition. I can't simply put the FreeBSD boot partition at the start of the hard drive as I did with the USB sticks. I had a FreeDOS installation with syslinux on a USB stick that went bad (the USB stick hardware). That would permit me to have various boot images including grub4dos and Super Grub Disk to boot with syslinux without booting into FreeDOS. I'd re-create that, but the FreeDOS installer has proven tricky. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Installer on serial-console-only-embedded system
On Mon, Aug 12, 2013 at 01:53:15PM +, Teske, Devin wrote: | sysinstall had the ability to allow you to muck with /etc/ttys before | rebooting to your installed OS. | | This functionality is coming back slowly. | | In 9.2-R you will be able to (somehow) bow out of the installation process | after it's complete (e.g., "Ctrl-C" ??) and then run bsdconfig -- invoking | the "TTYs" module, giving you a chance to change the settings before you | reboot from your newly installed system. | | Tighter Integration will follow in the years to come... but replacing a | tool that had a 15-year run which did _all_ of this stuff, is/was not an | overnight project. Rather, it's a journey! I also had made changes to sysinstall that if it detected a boot with -h then it did the /etc/tty etc. changes automatically to the installed system. It would be good to see this come back. I'm not sure if Robert's official changes did that. It's fairly easy to check what the console device is and then do the right thing. Thanks, Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Change in loader or kernel: won't boot with kfreebsd in grub2
On Mon, Aug 12, 2013 at 03:39:45PM +, Thomas Mueller wrote: > > Hmm I just tested super_grub2_disk_hybrid_2.00s1-beta5.iso from > > > > > http://www.supergrubdisk.org/category/download/supergrub2diskdownload/ > > > if it can boot FreeBSD-9.2-RC1-amd64-memstick.img in qemu and I > > had to fix "kfreebsd" spelled as "freebsd" and "kfreebsd_loadenv" > > spelled as "frebsd_loadenv", replace /boot/kernel/kernel with > > /boot/loader, and I in the loader I then had to set currdev=disk1a > > (shown by lsdev) and load /boot/kernel/kernel. qemu was started > > like this: > > > qemu-system-x86_64 -cdrom super_grub2_disk_hybrid_2.00s1-beta5.iso > > -hda FreeBSD-9.2-RC1-amd64-memstick.img -m 512 -boot d -monitor stdio > > > Letting super_grub2_disk_hybrid_2.00s1-beta5.iso boot the kernel > > directly via kfreebsd /boot/kernel/kernel fails tho because of a this > > bug in the vanilla grub 2.00 code: > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002 > > > (The fix for that bug now is in our sysutils/grub2 port as well as > > in debian's grub 2.00 but apparently not yet in the super grub disk > > isos.) > > > So maybe your problem is that loader needs currdev set at least > > in this case and in your old 9.0 installation it didn't? > > HTH, :) > > Juergen > > I still wonder why Super Grub Disk kfreebsd worked until recently. > > I figure something must have changed in FreeBSD loader or kernel structure > since the Super Grub Disk didn't change in that time. > > For currdev, apparently the big hard drive is just recognized as one big > drive with no reference to partitions (lsdev). > Hmm that sounds like a problem and would explain why loader cannot boot that install, when it doesn't find the partition... Maybe this is another case of confusion caused by leftover partition table data? In that case you probably can fix this by backing up what you want to keep from that disk, dd'ing /dev/zero over beginning and end of it and then reinstalling everything... (What does gpart show say about that disk now when run from a booted system and also from the 9.2 live system?) > I could try building grub2 from ports on both the hard-drive installation and > the USB-stick amd64 installation, see what possibilities are then available. > > FreeBSD gpart can create a boot partition, but then the question is how to > boot that when there is more than one OS partition. > > I can't simply put the FreeBSD boot partition at the start of the hard drive > as I did with the USB sticks. > > I had a FreeDOS installation with syslinux on a USB stick that went bad (the > USB stick hardware). That would permit me to have various boot images > including grub4dos and Super Grub Disk to boot with syslinux without booting > into FreeDOS. I'd re-create that, but the FreeDOS installer has proven > tricky. > I talked to the super grub disk people yesterday and they want to prepare an updated iso using debian's grub 2.00 (that has the kfreebsd >= 9.1 kernel fix), and with the FreeBSD templates fixed also, _maybe_ that would then help you as well... Good luck, :) Juergen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[SOLVED] how to remove usb-storage devices without CAM errors
2013/8/8 Michael Schuh > H i@list, > > i have a simple wuestion caused by a "device loss". > > is there a special routine for unplugging usb-storage devices? > in the meaning: > may be settle some commends before unplugging the device > other than umount. > according to the handbook there ist no special routine. > unmounting should be enough and pull the USB-Devie out of the bus. > > i could not find anything related by the help of the big oracle. > > > i have some usb-sticks that i need to write with prepared disk-images by > using dd. > two or more drives are already plugged in > and da0 is already finished, da1 or da2 still at writing. > unplugging da0 causes a CAM error and interrupts the ongoing write. > i am not sure if all writes to each different device gets stopped. > this is a reproduceable behaviour thats new to me. > see the listing below. > > let me know if i can and what to do to help to further identify > and investigate this error. > > iirc this happens for the first time this way. > my last upgrade before this was feb./march. > time of svn checkout was 2013-07-22 so its may be already fixed? > > many thanks in advance > > regards > > michael > > === > > ugen3.2: at usbus3 > umass0: on usbus3 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:8:0:-1: Attached to scbus8 > da0 at umass-sim0 bus 0 scbus8 target 0 lun 0 > da0: Removable Direct Access SCSI-6 device > da0: 40.000MB/s transfers > da0: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) > da0: quirks=0x2 > ugen7.2: at usbus7 > umass1: on usbus7 > umass1: SCSI over Bulk-Only; quirks = 0x0100 > umass1:9:1:-1: Attached to scbus9 > da1 at umass-sim1 bus 1 scbus9 target 0 lun 0 > da1: Removable Direct Access SCSI-6 device > da1: 40.000MB/s transfers > da1: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C) > da1: quirks=0x2 > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > ugen3.2: at usbus3 (disconnected) > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > umass0: (da0:at uhub3, port 3, addr 2 (disconnected) > umass-sim0:0:0:0): Retrying command > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Retrying command > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Error 5, Retries exhausted > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 > 00 00 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Retrying command > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 > 00 00 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Error 5, Retries exhausted > (da0:umass-sim0:0:0:0): got CAM status 0x44 > (da0:umass-sim0:0:0:0): fatal error, failed to attach to device > (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 5 refs > (da0:umass-sim0:0:0:0): removing device entry > > > Hi again, the error is gone after a new update from svn. many thanks. greetings m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Change in loader or kernel: won't boot with kfreebsd in grub2
On Mon, Aug 12, 2013 at 09:05:11PM +0200, Juergen Lock wrote: > On Mon, Aug 12, 2013 at 03:39:45PM +, Thomas Mueller wrote: > > > Hmm I just tested super_grub2_disk_hybrid_2.00s1-beta5.iso from > > > > > > > > http://www.supergrubdisk.org/category/download/supergrub2diskdownload/ > > > > > if it can boot FreeBSD-9.2-RC1-amd64-memstick.img in qemu and I > > > had to fix "kfreebsd" spelled as "freebsd" and "kfreebsd_loadenv" > > > spelled as "frebsd_loadenv", replace /boot/kernel/kernel with > > > /boot/loader, and I in the loader I then had to set currdev=disk1a > > > (shown by lsdev) and load /boot/kernel/kernel. qemu was started > > > like this: > > > > > qemu-system-x86_64 -cdrom > > > super_grub2_disk_hybrid_2.00s1-beta5.iso -hda > > > FreeBSD-9.2-RC1-amd64-memstick.img -m 512 -boot d -monitor stdio > > > > > Letting super_grub2_disk_hybrid_2.00s1-beta5.iso boot the kernel > > > directly via kfreebsd /boot/kernel/kernel fails tho because of a this > > > bug in the vanilla grub 2.00 code: > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002 > > > > > (The fix for that bug now is in our sysutils/grub2 port as well as > > > in debian's grub 2.00 but apparently not yet in the super grub disk > > > isos.) > > > > > So maybe your problem is that loader needs currdev set at least > > > in this case and in your old 9.0 installation it didn't? > > > > HTH, :) > > > Juergen > > > > I still wonder why Super Grub Disk kfreebsd worked until recently. > > > > I figure something must have changed in FreeBSD loader or kernel structure > > since the Super Grub Disk didn't change in that time. > > > > For currdev, apparently the big hard drive is just recognized as one big > > drive with no reference to partitions (lsdev). > > > Hmm that sounds like a problem and would explain why loader cannot boot > that install, when it doesn't find the partition... Maybe this is > another case of confusion caused by leftover partition table data? > In that case you probably can fix this by backing up what you want > to keep from that disk, dd'ing /dev/zero over beginning and end of > it and then reinstalling everything... (What does gpart show > say about that disk now when run from a booted system and also from > the 9.2 live system?) > > > I could try building grub2 from ports on both the hard-drive installation > > and the USB-stick amd64 installation, see what possibilities are then > > available. > > > > FreeBSD gpart can create a boot partition, but then the question is how to > > boot that when there is more than one OS partition. > > > > I can't simply put the FreeBSD boot partition at the start of the hard > > drive as I did with the USB sticks. > > > > I had a FreeDOS installation with syslinux on a USB stick that went bad > > (the USB stick hardware). That would permit me to have various boot images > > including grub4dos and Super Grub Disk to boot with syslinux without > > booting into FreeDOS. I'd re-create that, but the FreeDOS installer has > > proven tricky. > > > I talked to the super grub disk people yesterday and they want to > prepare an updated iso using debian's grub 2.00 (that has the > kfreebsd >= 9.1 kernel fix), and with the FreeBSD templates fixed > also, _maybe_ that would then help you as well... > New super grub disk iso is ready: https://forja.cenatic.es/frs/?group_id=204 https://forja.cenatic.es/frs/download.php/file/1587/super_grub2_disk_hybrid_2.00s1-beta6.iso https://forja.cenatic.es/frs/download.php/file/1586/super_grub2_disk_hybrid_2.00s1-beta6.iso.md5 Homepage: http://www.supergrubdisk.org/ Maybe you are lucky and this version works for you already... HTH, :) Juergen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
