Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network
I agree with Mark Felder.
2013/8/8 Pavel Timofeev tim...@gmail.com:
I tried to revert mentioned patch, i.e. applied this
--- sendmail/conf.c.orig2013-08-08 12:28:40.0 +0400
+++ sendmail/conf.c 2013-08-08 12:31:17.0 +0400
@@ -4294,12 +4294,7 @@
#else /* (SOLARIS 1 SOLARIS 20400) || (defined(SOLARIS)
SOLARIS 204) || (defined(sony_news) defined(__svr4)) */
int nmaps;
# if NETINET6
-# ifndef SM_IPNODEBYNAME_FLAGS
-/* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */
-# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG
-# endif /* SM_IPNODEBYNAME_FLAGS */
-
- int flags = SM_IPNODEBYNAME_FLAGS;
+ int flags = AI_DEFAULT|AI_ALL;
int err;
# endif /* NETINET6 */
char *maptype[MAXMAPSTACK];
Sendmail started to work
2013/8/7 Gregory Shapiro gshap...@freebsd.org:
I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses Sendmail-8.14.7.
If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS
you won't receive it.
But in same time email passes from FreeBSD 9.1-RELEASE which uses
Sendmail-8.14.5.
The recent release made the following change:
--- sendmail/conf.c 25 Jan 2011 18:31:30 - 8.1168
+++ sendmail/conf.c 5 Apr 2013 17:39:09 - 8.1182
@@ -4726,7 +4726,12 @@
#else /* (SOLARIS 1 SOLARIS 20400) || (defined(SOLARIS)
SOLARIS 204) || (defined(sony_news) defined(__svr4)) */
int nmaps;
# if NETINET6
- int flags = AI_DEFAULT|AI_ALL;
+# ifndef SM_IPNODEBYNAME_FLAGS
+/* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */
+# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG
+# endif /* SM_IPNODEBYNAME_FLAGS */
+
+ int flags = SM_IPNODEBYNAME_FLAGS;
int err;
# endif /* NETINET6 */
char *maptype[MAXMAPSTACK];
Which is described in this release note:
Drop support for IPv4-mapped IPv6 addresses to prevent the MTA
from using a mapped address over a legitimate IPv6 address
and to enforce the proper semantics over the IPv6
connection. Problem noted by Ulrich Sporlein.
It looks like that SERVFAIL from Microsoft's DNS server is getting
in the way of that. I can look at adding this exception to
WorkAroundBroken as a possibility for a future release.
I'd also like to hear feedback on whether the above change (changing
getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went
too far and what the accepted norm is for getipnodebyname().
___
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
missing /boot/menusets.4th
as of now (sorry have no rev#) the file sys/boot/forth/menusets.4th is not being installed, so boot failes! danny ___ 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: missing /boot/menusets.4th
On 08/09/13 10:28, Daniel Braniss wrote: as of now (sorry have no rev#) the file sys/boot/forth/menusets.4th is not being installed, so boot failes! danny ___ 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 Yep, I just recovered from it using fixit and copying the file from src to /boot. FreeBSD 14HELI 9.2-BETA2 FreeBSD 9.2-BETA2 #7: Fri Aug 9 10:43:22 CEST 2013 root@14HELI:/usr/obj/usr/src/sys/JOBBD2 amd64 /Henrik ___ 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: ZFS in jails 9.2-RC1 permission denied
On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrestøl trond.endres...@fagskolen.gjovik.no wrote: On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder f...@freebsd.org wrote: On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: Anybody? Can you provide your jail configuration? I think 9.2 introduces the new /etc/jail.conf functionality and perhaps it somehow it broke the way you were doing it previously? If so, the old method is supposed to be work as well... jail_enable=YES jail_list=jail1 jail_jail1_rootdir=/tank/jails/jail1 jail_jail1_hostname=jail1 jail_jail1_interface=em0 jail_jail1_ip=172.16.154.32 jail_jail1_devfs_enable=YES During my experimentation yesterday, I had to add: jail_jail1_parameters=enforce_statfs=1 allow.mount=1 allow.mount.zfs=1 I wish there was a way of executing a command in the host environment _after_ the jail is created, but _before_ exec.start is run from within the jail environment, exec.prestart is run in the host environment before the jail is created and is of no use for attaching a ZFS dataset to a particular jail with the zfs jail command. Until this issue is resolved, I see no other way than manually attaching a ZFS dataset to a jail, and manually running the mount command from within the jail environment. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++ Excellent, this worked like a charm! Does this means that the sysctl parameters are not honored or they have to be also passed in the jail parameters? Thanks! -- George Kontostanos --- http://www.aisecure.net ___ 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: ZFS in jails 9.2-RC1 permission denied
On Fri, 9 Aug 2013 13:35+0300, George Kontostanos wrote: On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrestøl trond.endres...@fagskolen.gjovik.no wrote: On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder f...@freebsd.org wrote: On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: Anybody? Can you provide your jail configuration? I think 9.2 introduces the new /etc/jail.conf functionality and perhaps it somehow it broke the way you were doing it previously? If so, the old method is supposed to be work as well... jail_enable=YES jail_list=jail1 jail_jail1_rootdir=/tank/jails/jail1 jail_jail1_hostname=jail1 jail_jail1_interface=em0 jail_jail1_ip=172.16.154.32 jail_jail1_devfs_enable=YES During my experimentation yesterday, I had to add: jail_jail1_parameters=enforce_statfs=1 allow.mount=1 allow.mount.zfs=1 I wish there was a way of executing a command in the host environment _after_ the jail is created, but _before_ exec.start is run from within the jail environment, exec.prestart is run in the host environment before the jail is created and is of no use for attaching a ZFS dataset to a particular jail with the zfs jail command. Until this issue is resolved, I see no other way than manually attaching a ZFS dataset to a jail, and manually running the mount command from within the jail environment. Excellent, this worked like a charm! Does this means that the sysctl parameters are not honored or they have to be also passed in the jail parameters? I guess so. Setting the sysctls in /etc/sysctl.conf doesn't seem to propagate to the jail environments at all in 9.2-BETA2. Thanks! You're welcome, and thanks for pushing me to explore jails and ZFS even further. ;-) Maybe the jail people should erect exec.afterprestart, enabling us to attach ZFS datasets to our jails prior to launching the jails. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ 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: ZFS in jails 9.2-RC1 permission denied
On Fri, Aug 9, 2013 at 1:57 PM, Trond Endrestøl trond.endres...@fagskolen.gjovik.no wrote: On Fri, 9 Aug 2013 13:35+0300, George Kontostanos wrote: On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrestøl trond.endres...@fagskolen.gjovik.no wrote: On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder f...@freebsd.org wrote: On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: Anybody? Can you provide your jail configuration? I think 9.2 introduces the new /etc/jail.conf functionality and perhaps it somehow it broke the way you were doing it previously? If so, the old method is supposed to be work as well... jail_enable=YES jail_list=jail1 jail_jail1_rootdir=/tank/jails/jail1 jail_jail1_hostname=jail1 jail_jail1_interface=em0 jail_jail1_ip=172.16.154.32 jail_jail1_devfs_enable=YES During my experimentation yesterday, I had to add: jail_jail1_parameters=enforce_statfs=1 allow.mount=1 allow.mount.zfs=1 I wish there was a way of executing a command in the host environment _after_ the jail is created, but _before_ exec.start is run from within the jail environment, exec.prestart is run in the host environment before the jail is created and is of no use for attaching a ZFS dataset to a particular jail with the zfs jail command. Until this issue is resolved, I see no other way than manually attaching a ZFS dataset to a jail, and manually running the mount command from within the jail environment. Excellent, this worked like a charm! Does this means that the sysctl parameters are not honored or they have to be also passed in the jail parameters? I guess so. Setting the sysctls in /etc/sysctl.conf doesn't seem to propagate to the jail environments at all in 9.2-BETA2. Thanks! You're welcome, and thanks for pushing me to explore jails and ZFS even further. ;-) Maybe the jail people should erect exec.afterprestart, enabling us to attach ZFS datasets to our jails prior to launching the jails. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++ I think that the process of attaching a dataset or a pool to a jail has to be done after the JID has been created. The way I attach them is from the host system: #zfs jail JID pool/dataset Best -- George Kontostanos --- http://www.aisecure.net ___ 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: ZFS in jails 9.2-RC1 permission denied
On Fri, 9 Aug 2013 14:07+0300, George Kontostanos wrote: On Fri, Aug 9, 2013 at 1:57 PM, Trond Endrestøl trond.endres...@fagskolen.gjovik.no wrote: On Fri, 9 Aug 2013 13:35+0300, George Kontostanos wrote: On Fri, Aug 9, 2013 at 8:55 AM, Trond Endrestøl trond.endres...@fagskolen.gjovik.no wrote: On Thu, 8 Aug 2013 19:04+0300, George Kontostanos wrote: On Thu, Aug 8, 2013 at 2:59 PM, Mark Felder f...@freebsd.org wrote: On Thu, Aug 8, 2013, at 6:53, George Kontostanos wrote: Anybody? Can you provide your jail configuration? I think 9.2 introduces the new /etc/jail.conf functionality and perhaps it somehow it broke the way you were doing it previously? If so, the old method is supposed to be work as well... jail_enable=YES jail_list=jail1 jail_jail1_rootdir=/tank/jails/jail1 jail_jail1_hostname=jail1 jail_jail1_interface=em0 jail_jail1_ip=172.16.154.32 jail_jail1_devfs_enable=YES During my experimentation yesterday, I had to add: jail_jail1_parameters=enforce_statfs=1 allow.mount=1 allow.mount.zfs=1 I wish there was a way of executing a command in the host environment _after_ the jail is created, but _before_ exec.start is run from within the jail environment, exec.prestart is run in the host environment before the jail is created and is of no use for attaching a ZFS dataset to a particular jail with the zfs jail command. Until this issue is resolved, I see no other way than manually attaching a ZFS dataset to a jail, and manually running the mount command from within the jail environment. Excellent, this worked like a charm! Does this means that the sysctl parameters are not honored or they have to be also passed in the jail parameters? I guess so. Setting the sysctls in /etc/sysctl.conf doesn't seem to propagate to the jail environments at all in 9.2-BETA2. Thanks! You're welcome, and thanks for pushing me to explore jails and ZFS even further. ;-) Maybe the jail people should erect exec.afterprestart, enabling us to attach ZFS datasets to our jails prior to launching the jails. I think that the process of attaching a dataset or a pool to a jail has to be done after the JID has been created. The way I attach them is from the host system: #zfs jail JID pool/dataset That's why I propose the exec.afterprestart. This is how I imagine it should work: 1. The operator attempts to create a jail: jail -c somejail 2. The exec.prestart is run within the _host_ environment. It is of no concern regarding attaching ZFS datasets to our jail. 3. The jail is actually created, say, with /jails/somejail (zjails/jails/somejail) as it root. 4. The exec.afterprestart is run within the _host_ environment, and in our case is configured to attach some ZFS datasets, say: zfs jail somejail zjails/jaildata/somejail 5. The exec.start is run within the _jail_ environment, typically running /etc/rc. 6. /etc/fstab within the _jail_ environment contains the necessary information to mount zjails/jaildata/somejail as /jaildata. 7. Everything else remains unchanged. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ 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: missing /boot/menusets.4th
On Fri, Aug 09, 2013 at 11:55:01AM +0200, Henrik Lidström wrote: On 08/09/13 10:28, Daniel Braniss wrote: as of now (sorry have no rev#) the file sys/boot/forth/menusets.4th is not being installed, so boot failes! ... Yep, I just recovered from it using fixit and copying the file from src to /boot. FreeBSD 14HELI 9.2-BETA2 FreeBSD 9.2-BETA2 #7: Fri Aug 9 10:43:22 CEST 2013 root@14HELI:/usr/obj/usr/src/sys/JOBBD2 amd64 ... I hit it as well; recovered by booting from one of my alternate boot slices copying as above. Yesterday's stable/9: FreeBSD 9.2-BETA2 #521 r254090M/254091:902501: Thu Aug 8 04:34:52 PDT 2013 root@localhost:/usr/obj/usr/src/sys/CANARY i386 was OK. This morning's -- where I encountered the problem -- was: FreeBSD 9.2-BETA2 #522 r254136M/254137:902501: Fri Aug 9 04:34:36 PDT 2013 root@localhost:/usr/obj/usr/src/sys/CANARY i386 Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp3CE7C9D3vm.pgp Description: PGP signature
[SOLVED] Re: missing /boot/menusets.4th
On Aug 9, 2013, at 2:55 AM, Henrik Lidström wrote: On 08/09/13 10:28, Daniel Braniss wrote: as of now (sorry have no rev#) the file sys/boot/forth/menusets.4th is not being installed, so boot failes! danny ___ 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 Yep, I just recovered from it using fixit and copying the file from src to /boot. FreeBSD 14HELI 9.2-BETA2 FreeBSD 9.2-BETA2 #7: Fri Aug 9 10:43:22 CEST 2013 root@14HELI:/usr/obj/usr/src/sys/JOBBD2 amd64 (raises hand) My fault! I committed SVN r254109/r254113. ... and forgot to merge r242688. And I know why I missed it... Learned a valuable lessen today... *** I did my mergeinfo --show-revs=eligible in sys/boot/forth *** NOTE: Despite the fact that I did svn merge in the proper location, the show-revs was influenced by the fact that I was in a sub-directory ... thus I never caught r242688 because at that sub-directory level, the revision didn't apply (show-revs=eligible didn't list it; and that's the list I was processing). It's not that I wasn't paying close attention to... http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html It's that I didn't know that the rule of getting the list of eligible revs was quite as important as the actual act of merging. I'm very aware now that when you go to synchronize branches... it's imperative that even the show-revs step be done at the right level (but to be fair... I wasn't expecting something like r242688 ... and it had been a _long_ time since I had last broke the build [albeit with the same problem in HEAD]). Much apologies. Merging r242688 immediately to stable/9 to fix the missing file issue. -- Devin _ 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
Re: [SOLVED] Re: missing /boot/menusets.4th
On Aug 9, 2013, at 7:11 AM, Teske, Devin wrote: On Aug 9, 2013, at 2:55 AM, Henrik Lidström wrote: On 08/09/13 10:28, Daniel Braniss wrote: as of now (sorry have no rev#) the file sys/boot/forth/menusets.4th Again, apologies... Patched stable/9 with forgotten MFC of r242688 (see recent SVN r254146). -- Devin _ 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
Re: Sendmail-8.14.7 doesn't work with MS DNS in IPv4 network
Can you put back the original sendmail/conf.c file and try this patch instead
to verify it works? If so, I can plan to commit it to HEAD and MFC to the
various branches (with re permission to the 9.2 branch). This would be a short
term fix until the next sendmail release where we will revisit this section of
code.
--- contrib/sendmail/include/sm/os/sm_os_freebsd.h 2008-08-27
22:53:56.0 -0700
+++ contrib/sendmail/include/sm/os/sm_os_freebsd.h 2013-08-09
10:21:12.0 -0700
@@ -39,3 +39,7 @@
#ifndef SM_CONF_MSG
# define SM_CONF_MSG 1
#endif /* SM_CONF_MSG */
+
+#ifndef SM_IPNODEBYNAME_FLAGS
+# define SM_IPNODEBYNAME_FLAGS AI_DEFAULT|AI_ALL
+#endif /* SM_IPNODEBYNAME_FLAGS */
On Fri, Aug 09, 2013 at 10:34:14AM +0400, Pavel Timofeev wrote:
I agree with Mark Felder.
2013/8/8 Pavel Timofeev tim...@gmail.com:
I tried to revert mentioned patch, i.e. applied this
--- sendmail/conf.c.orig2013-08-08 12:28:40.0 +0400
+++ sendmail/conf.c 2013-08-08 12:31:17.0 +0400
@@ -4294,12 +4294,7 @@
#else /* (SOLARIS 1 SOLARIS 20400) || (defined(SOLARIS)
SOLARIS 204) || (defined(sony_news) defined(__svr4)) */
int nmaps;
# if NETINET6
-# ifndef SM_IPNODEBYNAME_FLAGS
-/* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */
-# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG
-# endif /* SM_IPNODEBYNAME_FLAGS */
-
- int flags = SM_IPNODEBYNAME_FLAGS;
+ int flags = AI_DEFAULT|AI_ALL;
int err;
# endif /* NETINET6 */
char *maptype[MAXMAPSTACK];
Sendmail started to work
2013/8/7 Gregory Shapiro gshap...@freebsd.org:
I found a problem in new FreeBSD 9.2-{BETA2,RC1} which uses
Sendmail-8.14.7.
If you try to send email from FreeBSD 9.2 in IPv4 network with MS DNS
you won't receive it.
But in same time email passes from FreeBSD 9.1-RELEASE which uses
Sendmail-8.14.5.
The recent release made the following change:
--- sendmail/conf.c 25 Jan 2011 18:31:30 - 8.1168
+++ sendmail/conf.c 5 Apr 2013 17:39:09 - 8.1182
@@ -4726,7 +4726,12 @@
#else /* (SOLARIS 1 SOLARIS 20400) || (defined(SOLARIS)
SOLARIS 204) || (defined(sony_news) defined(__svr4)) */
int nmaps;
# if NETINET6
- int flags = AI_DEFAULT|AI_ALL;
+# ifndef SM_IPNODEBYNAME_FLAGS
+/* For IPv4-mapped addresses, use: AI_DEFAULT|AI_ALL */
+# define SM_IPNODEBYNAME_FLAGS AI_ADDRCONFIG
+# endif /* SM_IPNODEBYNAME_FLAGS */
+
+ int flags = SM_IPNODEBYNAME_FLAGS;
int err;
# endif /* NETINET6 */
char *maptype[MAXMAPSTACK];
Which is described in this release note:
Drop support for IPv4-mapped IPv6 addresses to prevent the MTA
from using a mapped address over a legitimate IPv6 address
and to enforce the proper semantics over the IPv6
connection. Problem noted by Ulrich Sporlein.
It looks like that SERVFAIL from Microsoft's DNS server is getting
in the way of that. I can look at adding this exception to
WorkAroundBroken as a possibility for a future release.
I'd also like to hear feedback on whether the above change (changing
getipnodebyname() flags from 'AI_DEFAULT | AI_ALL' to 'AI_ADDRCONFIG' went
too far and what the accepted norm is for getipnodebyname().
___
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: [SOLVED] Re: missing /boot/menusets.4th
On 09.08.13 16:19, Teske, Devin wrote: Again, apologies... Patched stable/9 with forgotten MFC of r242688 (see recent SVN r254146). Accepted! that was the worst outage that hit me since a decade or more. It was really STABLE for longtime ;-) But In that stage of boot i was a bit helpless. Tried half a day to recover. Found some issues with fixit and mounting zfs on root in /mnt could not find menusets.4th on any place in the system. At the end I simply copied the file from http://svnweb.freebsd.org/base/head/sys/boot/forth/menusets.4th?revision=242667view=copathrev=242667 on a usb-drive and copied to /mnt/boot Hope to help others. Now i have to figure out, why |Fixit# zpool import -R /mnt -f poolname| |Fixit# mount -t zfs poolname /mnt| did not worked as expected, and the 9.2-RC1 image was not installable... good night, Beat ___ 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
