Re: I broke my SSH to jails after 7.2-8.0 src upgrade
On Sat, Mar 13, 2010 at 09:33:50PM -0800, Doug Barton wrote: On 03/12/10 02:13, Greg Byshenk wrote: I would put in a word for 'mergemaster -F' (or maybe '-iF') in such cases. At this point the -U option is generally a safer bet. The only time this won't work for you is when upgrading from an older -RELEASE where you've never run mergemaster previously, in which case it will bark loudly that there is no mtree database. You could then run 'mergemaster -Fi' as you suggested, and run 'mergemaster -U' immediately thereafter and you should get as much automation as is possible. I don't actually want as much 'automation' as is possible. Generally I want to know what is being modified, even if it is in a file that I haven't changed. I like '-F' because it allows me to ignore the huge number of files that aren't actually changed -- except the RCS line -- that sometimes arise when moving between versions. -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On Sun, Mar 14, 2010 at 1:11 AM, Greg Byshenk free...@byshenk.net wrote: On Sat, Mar 13, 2010 at 09:33:50PM -0800, Doug Barton wrote: On 03/12/10 02:13, Greg Byshenk wrote: I would put in a word for 'mergemaster -F' (or maybe '-iF') in such cases. At this point the -U option is generally a safer bet. The only time this won't work for you is when upgrading from an older -RELEASE where you've never run mergemaster previously, in which case it will bark loudly that there is no mtree database. You could then run 'mergemaster -Fi' as you suggested, and run 'mergemaster -U' immediately thereafter and you should get as much automation as is possible. I don't actually want as much 'automation' as is possible. Generally I want to know what is being modified, even if it is in a file that I haven't changed. I like '-F' because it allows me to ignore the huge number of files that aren't actually changed -- except the RCS line -- that sometimes arise when moving between versions. Excellent point. People who use FreeBSD don't want automation necessarily -- if they wanted a software developer to make all of the decisions for them, there's always OSX or Windows. FreeBSD users (in general) appreciate the completeness and simplicity in the OS design, but wherever possible if unnecessary noise can be avoided, all the better. Just a thought... Cheers, -Garrett ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On Sat, Mar 13, 2010 at 9:30 PM, Doug Barton do...@freebsd.org wrote: On 03/11/10 20:33, Garrett Cooper wrote: I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. It would be really great if you could submit a proper bug report for this. If there are underlying problems with mergemaster I want to fix them. Meanwhile, mergemaster doesn't have an 'automatic merging logic' of its own. It either uses mtree for the -U option, or sdiff if you merge by hand. Without more information, it's hard to provide more useful assistance. I'll definitely provide more helpful feedback when I have more helpful data and steps to reproduce the `issues' that I'm seeing. -a doesn't actually do any merging though, FWIW: Thanks for helping the user with this information. :) Np... thanks for the help automating things ;)... -Garrett ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 03/14/10 01:11, Greg Byshenk wrote: On Sat, Mar 13, 2010 at 09:33:50PM -0800, Doug Barton wrote: On 03/12/10 02:13, Greg Byshenk wrote: I would put in a word for 'mergemaster -F' (or maybe '-iF') in such cases. At this point the -U option is generally a safer bet. The only time this won't work for you is when upgrading from an older -RELEASE where you've never run mergemaster previously, in which case it will bark loudly that there is no mtree database. You could then run 'mergemaster -Fi' as you suggested, and run 'mergemaster -U' immediately thereafter and you should get as much automation as is possible. I don't actually want as much 'automation' as is possible. Generally I want to know what is being modified, even if it is in a file that I haven't changed. I like '-F' because it allows me to ignore the huge number of files that aren't actually changed -- except the RCS line -- that sometimes arise when moving between versions. Ok, fair enough; that's why there are two options. :) Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 03/11/10 19:18, Steve Bertrand wrote: On 2010.03.11 22:14, Xin LI wrote: Looks like you have a stale configuration. DId you done mergemaster? Yes. I performed it as such: # mergemaster -Uia The -a option is incompatible with -U AND -i (and -F for that matter). However, it's my mistake that this issue has never previously been addressed in the code. I just committed a fix for this, which I'll MFC ASAP. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 03/11/10 20:33, Garrett Cooper wrote: I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. It would be really great if you could submit a proper bug report for this. If there are underlying problems with mergemaster I want to fix them. Meanwhile, mergemaster doesn't have an 'automatic merging logic' of its own. It either uses mtree for the -U option, or sdiff if you merge by hand. Without more information, it's hard to provide more useful assistance. -a doesn't actually do any merging though, FWIW: Thanks for helping the user with this information. :) Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 03/12/10 02:13, Greg Byshenk wrote: I would put in a word for 'mergemaster -F' (or maybe '-iF') in such cases. At this point the -U option is generally a safer bet. The only time this won't work for you is when upgrading from an older -RELEASE where you've never run mergemaster previously, in which case it will bark loudly that there is no mtree database. You could then run 'mergemaster -Fi' as you suggested, and run 'mergemaster -U' immediately thereafter and you should get as much automation as is possible. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On Thu, Mar 11, 2010 at 08:33:29PM -0800, Garrett Cooper wrote: I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. -a doesn't actually do any merging though, FWIW: [...] I would put in a word for 'mergemaster -F' (or maybe '-iF') in such cases. It doesn't try to automate much, but it allows one to concentrate on actual differences by automating the handling of those files where only the VCS Id is different. -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ 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
I broke my SSH to jails after 7.2-8.0 src upgrade
Hi all, please forgive the verbosity, but I wanted to include as much detail as possible (without including config files) up front. Summary: SSH works to the jail box host OS, but not to the jails themselves. On a box that is dedicated to jails, I source upgraded from 7.2 to: FreeBSD jail.eagle.ca 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Mar 11 13:22:59 EST 2010 r...@jail.eagle.ca:/usr/obj/usr/src/sys/JAIL i386 I then proceeded to update each jail by `make installworld DESTDIR=$JAILDIR', followed by (for most, but not quite all jails), a `mergemaster -Uia'. During the upgrade of the host OS, I know I rebooted here: - after the `installkernel' phase of the host OS - after the `installworld' phase of the host OS ...in between the above stages, I performed a `mergemaster -Uia' Now, I can SSH into the host, but not the jails it contains. I have been Googling for hours trying to figure this out. I've honestly exhausted all of the possibilities I could find regarding the issue, even some that dated back to the good ol' 4.x days. It seemingly has something to do with tty/pts, but I just can't figure it out. When trying to SSH to a jail from the resident host OS: %ssh acct.eagle.ca Password: PTY allocation request failed on channel 0 Warning: no access to tty (Bad file descriptor). Thus no job control in this shell. ...and when I attempt SSH to a jail from a remote box, the connection drops immediately after I enter the password. In both cases, the following is logged into /var/log/messages within the jail host: Mar 11 21:35:40 acct sshd[8175]: error: openpty: No such file or directory Mar 11 21:35:40 acct sshd[8178]: error: session_pty_req: session 0 alloc failed A listing of the dev directory on the jail doesn't show pts (but it does on the host OS): %ll /usr/jails/acct/dev total 1 dr-xr-xr-x 2 root wheel 512 Mar 11 17:12 fd lrwxr-xr-x 1 root wheel14 Mar 11 17:12 log - ../var/run/log crw-rw-rw- 1 root wheel0, 7 Mar 11 21:11 null crw-rw-rw- 1 root wheel0, 12 Mar 11 12:10 random lrwxr-xr-x 1 root wheel 4 Mar 11 17:12 stderr - fd/2 lrwxr-xr-x 1 root wheel 4 Mar 11 17:12 stdin - fd/0 lrwxr-xr-x 1 root wheel 4 Mar 11 17:12 stdout - fd/1 lrwxr-xr-x 1 root wheel 6 Mar 11 17:12 urandom - random crw-rw-rw- 1 root wheel0, 8 Mar 11 17:10 zero ...and I've tried to make Google-advised changes to the /etc/defaults/devfs.rules file to no avail. ;) All other services within the host OS and the jails are operating perfectly. I'm just missing my tty's. Can someone hit me with the cluebat, because I really feel that I've missed something. Thanks, Steve ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
Sounds like you have something wrong with devfs.rules in jail section? On Mar 11, 2010 6:46 PM, Steve Bertrand st...@ibctech.ca wrote: Hi all, please forgive the verbosity, but I wanted to include as much detail as possible (without including config files) up front. Summary: SSH works to the jail box host OS, but not to the jails themselves. On a box that is dedicated to jails, I source upgraded from 7.2 to: FreeBSD jail.eagle.ca 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Mar 11 13:22:59 EST 2010 r...@jail.eagle.ca:/usr/obj/usr/src/sys/JAIL i386 I then proceeded to update each jail by `make installworld DESTDIR=$JAILDIR', followed by (for most, but not quite all jails), a `mergemaster -Uia'. During the upgrade of the host OS, I know I rebooted here: - after the `installkernel' phase of the host OS - after the `installworld' phase of the host OS ...in between the above stages, I performed a `mergemaster -Uia' Now, I can SSH into the host, but not the jails it contains. I have been Googling for hours trying to figure this out. I've honestly exhausted all of the possibilities I could find regarding the issue, even some that dated back to the good ol' 4.x days. It seemingly has something to do with tty/pts, but I just can't figure it out. When trying to SSH to a jail from the resident host OS: %ssh acct.eagle.ca Password: PTY allocation request failed on channel 0 Warning: no access to tty (Bad file descriptor). Thus no job control in this shell. ...and when I attempt SSH to a jail from a remote box, the connection drops immediately after I enter the password. In both cases, the following is logged into /var/log/messages within the jail host: Mar 11 21:35:40 acct sshd[8175]: error: openpty: No such file or directory Mar 11 21:35:40 acct sshd[8178]: error: session_pty_req: session 0 alloc failed A listing of the dev directory on the jail doesn't show pts (but it does on the host OS): %ll /usr/jails/acct/dev total 1 dr-xr-xr-x 2 root wheel 512 Mar 11 17:12 fd lrwxr-xr-x 1 root wheel14 Mar 11 17:12 log - ../var/run/log crw-rw-rw- 1 root wheel0, 7 Mar 11 21:11 null crw-rw-rw- 1 root wheel0, 12 Mar 11 12:10 random lrwxr-xr-x 1 root wheel 4 Mar 11 17:12 stderr - fd/2 lrwxr-xr-x 1 root wheel 4 Mar 11 17:12 stdin - fd/0 lrwxr-xr-x 1 root wheel 4 Mar 11 17:12 stdout - fd/1 lrwxr-xr-x 1 root wheel 6 Mar 11 17:12 urandom - random crw-rw-rw- 1 root wheel0, 8 Mar 11 17:10 zero ...and I've tried to make Google-advised changes to the /etc/defaults/devfs.rules file to no avail. ;) All other services within the host OS and the jails are operating perfectly. I'm just missing my tty's. Can someone hit me with the cluebat, because I really feel that I've missed something. Thanks, Steve ___ 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 ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 21:49, Xin LI wrote: Sounds like you have something wrong with devfs.rules in jail section? Did I miss or fsck something up by not reading UPDATING properly? Here is what I have on the host OS: %cat /etc/defaults/devfs.rules | grep -v ^# [devfsrules_hide_all=1] add hide [devfsrules_unhide_basic=2] add path null unhide add path zero unhide add path crypto unhide add path random unhide add path urandom unhide [devfsrules_unhide_login=3] add path 'ptyp*' unhide add path 'ptyq*' unhide add path 'ptyr*' unhide add path 'ptys*' unhide add path 'ptyP*' unhide add path 'ptyQ*' unhide add path 'ptyR*' unhide add path 'ptyS*' unhide add path 'ttyp*' unhide add path 'ttyq*' unhide add path 'ttyr*' unhide add path 'ttys*' unhide add path 'ttyP*' unhide add path 'ttyQ*' unhide add path 'ttyR*' unhide add path 'ttyS*' unhide add path 'pts/*' unhide add path 'pty/*' unhide add path fd unhide add path 'fd/*' unhide add path stdin unhide add path stdout unhide add path stderr unhide [devfsrules_jail=4] add include $devfsrules_hide_all add include $devfsrules_unhide_basic add include $devfsrules_unhide_login ...and on a jail OS: %cat /usr/jails/devel/etc/defaults/devfs.rules | grep -v ^# [devfsrules_hide_all=1] add hide [devfsrules_unhide_basic=2] add path null unhide add path zero unhide add path crypto unhide add path random unhide add path urandom unhide [devfsrules_unhide_login=3] add path 'ptyp*' unhide add path 'ptyq*' unhide add path 'ptyr*' unhide add path 'ptys*' unhide add path 'ptyP*' unhide add path 'ptyQ*' unhide add path 'ptyR*' unhide add path 'ptyS*' unhide add path 'ttyp*' unhide add path 'ttyq*' unhide add path 'ttyr*' unhide add path 'ttys*' unhide add path 'ttyP*' unhide add path 'ttyQ*' unhide add path 'ttyR*' unhide add path 'ttyS*' unhide add path 'pts/*' unhide add path 'pty/*' unhide add path fd unhide add path 'fd/*' unhide add path stdin unhide add path stdout unhide add path stderr unhide add path pts unhide [devfsrules_jail=4] add include $devfsrules_hide_all add include $devfsrules_unhide_basic add include $devfsrules_unhide_login Thanks for such a quick response LI, Steve ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
Looks like you have a stale configuration. DId you done mergemaster? Cheers, -- Xin LI delp...@delphij.net http://www.delphij.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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 22:14, Xin LI wrote: Looks like you have a stale configuration. DId you done mergemaster? Yes. I performed it as such: # mergemaster -Uia under the host OS, and then subsequently within each jail. I'm not very familiar with mergemaster, so could my use of the args been incorrect? Steve ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 22:14, Steve Bertrand wrote: I had even used diff(8) earlier, err, diff(1) ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 21:49, Xin LI wrote: Sounds like you have something wrong with devfs.rules in jail section? Heh, Thanks Xin LI, I knew the cluebat would work ;) This line: add path pts unhide ...I had added to the jails, but NOT to the host /etc/defaults/devfs.rules. It took me sending a cat of each file to realize I was missing it in the host OS file. I had even used diff(8) earlier, but that must have been after much eye-strain. Although I have no idea what add path pts unhide actually does, after adding it into the proper location within the host OS filesystem, I'm all back up and rolling ;) Absolute kudos to Richard Bader who started me down the right path in this thread: http://www.mail-archive.com/freebsd-j...@freebsd.org/msg01061.html The only thing that I didn't get from it was that the add path pts unhide is required in /etc/defaults/devfs.rules file on the HOST OS. Thanks much! 7.2-8.0 source upgrade with jails is 100% successful! Good work dev team! Steve ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Weird, it seems that RELENG_8_0 do contain the correct file... What does 'ident /etc/defaults/devfs.rules' show? Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLmbsOAAoJEATO+BI/yjfBYWwH/jLink3OiDf1Rth8Id+BZL8B P8I2+0jgCny3DjDltRqy0s1+rzF0hjQjpUrUR/T/lPIBRqi2CgQ6RuKe4fHjlZ5c JR2p7AI0BnrU6gpJmVyhoROUZAEEMIrqxXji00N/o+ZuRvuVO+YfVYnuJrMcp78+ vll0bWrHp1xevXf6cH4FcTaurKsexZAZbBvHnrWL6v8WWK1+CtuRmbWjStaNg2tK 6SSOE3P2IEXVW3LNQ9iHV0GycgnbdnsYTTOjsQG2BQTpNRozMvQk3f9oiVMHDn2F a2vBewVkWkzfTX9IBX6o6aYbIInRQo0TYitj5nnP8vI+nF4WI/hnAebv9dO4ymQ= =6LSi -END PGP SIGNATURE- ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 22:54, Xin LI wrote: Weird, it seems that RELENG_8_0 do contain the correct file... What does 'ident /etc/defaults/devfs.rules' show? ...not necessarily 8_0: %grep tag /etc/supfile *default tag=RELENG_8 fwiw: %ident /etc/defaults/devfs.rules /etc/defaults/devfs.rules: $FreeBSD: src/etc/defaults/devfs.rules,v 1.4.2.1.6.1 2009/04/15 03:14:26 kensmith Exp $ ...again... perhaps my arg list to mergemaster was the issue. If it was, it would be good to know ;) Otherwise, it was a standard src upgrade. Let me know if you need anything further. I can simulate the procedure on other hardware tomorrow to isolate the issue if you feel that this may affect others, or if it can prove that I was just sleeping on the job. Steve ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2010/03/11 20:26, Steve Bertrand wrote: On 2010.03.11 22:54, Xin LI wrote: Weird, it seems that RELENG_8_0 do contain the correct file... What does 'ident /etc/defaults/devfs.rules' show? ...not necessarily 8_0: %grep tag /etc/supfile *default tag=RELENG_8 Oh that shouldn't a problem :) fwiw: %ident /etc/defaults/devfs.rules /etc/defaults/devfs.rules: $FreeBSD: src/etc/defaults/devfs.rules,v 1.4.2.1.6.1 2009/04/15 03:14:26 kensmith Exp $ This is a old version which comes from 7.2, so that's the problem... ...again... perhaps my arg list to mergemaster was the issue. If it was, it would be good to know ;) Otherwise, it was a standard src upgrade. Let me know if you need anything further. I can simulate the procedure on other hardware tomorrow to isolate the issue if you feel that this may affect others, or if it can prove that I was just sleeping on the job. Could you please check ident on /usr/src/etc/defaults/devfs.rules? Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLmcNoAAoJEATO+BI/yjfBnQwH/jN//MTEruj3TSPOcQBqmEJd ii9wFhqQfZOHboAAkzNeARX+obGpDhJSEtwSpf4MpoK5jq9i5fEhHaE1uIGmlt+4 ZM9oZkN3elTnTrscU4v9CddPgPXrjSfZMavWQUk/gmoksRrXKAmsdSfAubZBqC9m BpcNaR5+V/DmMfLQqvG3Clfh7/yooyb/X+t6zgcEWNZXGXk/xEwglho7njdQF/LS IFNF9aaPqn+kSucQyVPBKGpQXN98dn4aKjDDu9/Vz4CvDVHNoAL7uNuiZgAC0JD9 Jj5UIYOz7xXzDqNx37jgoMPnqQlxAtsUAQDDxerBcKdIgRlSunpyc5i2W+2lA1o= =dr6j -END PGP SIGNATURE- ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On Thu, Mar 11, 2010 at 8:26 PM, Steve Bertrand st...@ibctech.ca wrote: On 2010.03.11 22:54, Xin LI wrote: Weird, it seems that RELENG_8_0 do contain the correct file... What does 'ident /etc/defaults/devfs.rules' show? ...not necessarily 8_0: %grep tag /etc/supfile *default tag=RELENG_8 fwiw: %ident /etc/defaults/devfs.rules /etc/defaults/devfs.rules: $FreeBSD: src/etc/defaults/devfs.rules,v 1.4.2.1.6.1 2009/04/15 03:14:26 kensmith Exp $ ...again... perhaps my arg list to mergemaster was the issue. If it was, it would be good to know ;) Otherwise, it was a standard src upgrade. Let me know if you need anything further. I can simulate the procedure on other hardware tomorrow to isolate the issue if you feel that this may affect others, or if it can prove that I was just sleeping on the job. I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. -a doesn't actually do any merging though, FWIW: -a Run automatically. This option will leave all the files that differ from the installed versions in the temporary directory to be dealt with by hand. If the temproot directory exists, it creates a new one in a previously non-existent directory. This option unsets the verbose flag, but other than -U it is compatible with all other options. Setting -a makes -w superfluous. Also, add path pts unhide unmasks all psuedo TTY dev nodes so that applications that use openpty(3) and friends (like sshd) can allocate them at login. Thanks, -Garrett ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 23:30, Xin LI wrote: On 2010/03/11 20:26, Steve Bertrand wrote: On 2010.03.11 22:54, Xin LI wrote: Weird, it seems that RELENG_8_0 do contain the correct file... What does 'ident /etc/defaults/devfs.rules' show? ...not necessarily 8_0: %grep tag /etc/supfile *default tag=RELENG_8 Oh that shouldn't a problem :) fwiw: %ident /etc/defaults/devfs.rules /etc/defaults/devfs.rules: $FreeBSD: src/etc/defaults/devfs.rules,v 1.4.2.1.6.1 2009/04/15 03:14:26 kensmith Exp $ This is a old version which comes from 7.2, so that's the problem... ...again... perhaps my arg list to mergemaster was the issue. If it was, it would be good to know ;) Otherwise, it was a standard src upgrade. Let me know if you need anything further. I can simulate the procedure on other hardware tomorrow to isolate the issue if you feel that this may affect others, or if it can prove that I was just sleeping on the job. Could you please check ident on /usr/src/etc/defaults/devfs.rules? %uname -a FreeBSD jail.eagle.ca 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Mar 11 13:22:59 EST 2010 r...@jail.eagle.ca:/usr/obj/usr/src/sys/JAIL i386 %ident /usr/src/etc/defaults/devfs.rules /usr/src/etc/defaults/devfs.rules: $FreeBSD: src/etc/defaults/devfs.rules,v 1.6.2.2 2010/01/11 18:42:29 jhb Exp $ Steve ps. I can see that I did something wrong ;) ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2010/03/11 20:33, Garrett Cooper wrote: I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. -a doesn't actually do any merging though, FWIW: -a Run automatically. This option will leave all the files that differ from the installed versions in the temporary directory to be dealt with by hand. If the temproot directory exists, it creates a new one in a previously non-existent directory. This option unsets the verbose flag, but other than -U it is compatible with all other options. Setting -a makes -w superfluous. Also, add path pts unhide unmasks all psuedo TTY dev nodes so that applications that use openpty(3) and friends (like sshd) can allocate them at login. Yes that's right. Thanks for posting, perhaps we can document it in FAQ? Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLmcX6AAoJEATO+BI/yjfB4lgIAKF4XMGFSU0VsvmfUD2WIWoE N5UQTKiew4cyytk80SS0ProGemMnWykAfZIDyhovCxp7WRAPJMmrqhulcYXHi+hW DBP4Dx8AsHu/pQ0edauIfnEXYy4gd9g9D6yRIS8407izYTPYs1FvfW0GeftLwEfn Ngm/bYggw1g/Nc5ercqc3AV1vXJJSZ6c3VL8r1ohlsiCRlybMaXBxQrU/KSjDFoz /xI4TOJ5+L+gCpfFB8Tvso8IueZ/YqVSPKnC95bOwGR16sERmACZ7rRUIg7zXyhA VhKttjqfLrHRn6yp905OvS3rkmtCWBfpqIM8Ia34owjSlZbTUK7i0phiDw3uADE= =IXRh -END PGP SIGNATURE- ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 23:33, Garrett Cooper wrote: On Thu, Mar 11, 2010 at 8:26 PM, Steve Bertrand st...@ibctech.ca wrote: On 2010.03.11 22:54, Xin LI wrote: Weird, it seems that RELENG_8_0 do contain the correct file... What does 'ident /etc/defaults/devfs.rules' show? ...not necessarily 8_0: %grep tag /etc/supfile *default tag=RELENG_8 fwiw: %ident /etc/defaults/devfs.rules /etc/defaults/devfs.rules: $FreeBSD: src/etc/defaults/devfs.rules,v 1.4.2.1.6.1 2009/04/15 03:14:26 kensmith Exp $ ...again... perhaps my arg list to mergemaster was the issue. If it was, it would be good to know ;) Otherwise, it was a standard src upgrade. Let me know if you need anything further. I can simulate the procedure on other hardware tomorrow to isolate the issue if you feel that this may affect others, or if it can prove that I was just sleeping on the job. I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. -a doesn't actually do any merging though, FWIW: heh. Then this explains it. ...at least my own idiocy (or perhaps lack thereof for trying too hard) keeps me at the OS troubleshooting level ;) So long as the OS I'm troubleshooting doesn't have a gui, I'm ok with it. I'm obviously going to get a better understanding of mergemaster. More importantly, I have a colleague who wanted to help this afternoon, but I didn't know how to describe the problem. This thread will help. Thanks! Steve ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On 2010.03.11 23:41, Xin LI wrote: On 2010/03/11 20:33, Garrett Cooper wrote: I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. -a doesn't actually do any merging though, FWIW: -a Run automatically. This option will leave all the files that differ from the installed versions in the temporary directory to be dealt with by hand. If the temproot directory exists, it creates a new one in a previously non-existent directory. This option unsets the verbose flag, but other than -U it is compatible with all other options. Setting -a makes -w superfluous. Also, add path pts unhide unmasks all psuedo TTY dev nodes so that applications that use openpty(3) and friends (like sshd) can allocate them at login. Yes that's right. Thanks for posting, perhaps we can document it in FAQ? Well, if anything, the FAQ should simply say read the damn handbook and follow it. If I had of followed the same procedure that I've been using for the last 7 years (at least) instead of trying to 'automate' (-a) prior to reading the man page thoroughly, I would have been ok. Sorry for the noise, but thanks for the help ;) Cheers, Steve ___ 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: I broke my SSH to jails after 7.2-8.0 src upgrade
On Thu, Mar 11, 2010 at 8:41 PM, Xin LI delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2010/03/11 20:33, Garrett Cooper wrote: I've done a few RELENG_8_0 to STABLE-8 to 9-CURRENT upgrades lately and mergemaster was goofing up the contents a bit based on the RCS versions. I had to hand-edit a crapload of stuff going from 8 to 9, and I still don't trust mergemaster's automatic merging logic because it goofs up on /etc/group // /etc/passwd still (doesn't merge anything, discards my info, etc) for starters. -a doesn't actually do any merging though, FWIW: -a Run automatically. This option will leave all the files that differ from the installed versions in the temporary directory to be dealt with by hand. If the temproot directory exists, it creates a new one in a previously non-existent directory. This option unsets the verbose flag, but other than -U it is compatible with all other options. Setting -a makes -w superfluous. Also, add path pts unhide unmasks all psuedo TTY dev nodes so that applications that use openpty(3) and friends (like sshd) can allocate them at login. Yes that's right. Thanks for posting, perhaps we can document it in FAQ? Unfortunately this doesn't really fit in a FAQ because it could be any of the failures caused by openpty failure: ERRORS The openpty() function may fail and set the global variable errno for any of the errors specified for the grantpt(3), posix_openpt(3), ptsname(3), and unlockpt(3) functions and the revoke(2) system call. In addition to this, forkpty() may set it to any value as described for fork(2). Note how openpty(3) isn't descriptive in terms of _what_ individual failures can be reported by it, but instead point to other manpages :)... I've run into whacky ass issues with /var/run permissions in the past, etc, which is why I don't suggest putting this into a FAQ -- the bucket is way too huge to deal with. Steve's right though -- if you're willing to use an option and the documentation clearly states the exact behavior and caveats, you are responsible for the results of any failure through misuse of the tool (exceptions being IMO NUL pointer exceptions, abort(3) calls not thrown by assert(3)s, etc). You're more than welcome to make suggestions on how things can be improved, but as I've discovered in some areas, some of the suggestions one makes aren't necessarily accepted with open minds. Excessive and/or redundant documentation (as I'm starting to understand after playing the opposite side for a while) is no better than little or no documentation; complete and concise documentation is what's needed more than anything else. Thanks, -Garrett ___ 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
