Thanks for all. my problem was solved, I explain how,
For some reason I had my login.conf, empty. then, as could copy and paste the java based remote console kvm. wrote the contents of the file "login.conf" to not take me much wrote without comments. This file gave me the mistakes I mentioned in previous post. better then turned to repeat the upgrade process with install59.iso and finish before running the reboot command, I headed to "/mnt/etc/" and download the login.conf that comes by default in OpenBSD 5.9. *#cd /mnt/etc/login.conf#rm login.conf* *#ftp http://my-server-upload-file/login.conf.txt <http://my-server-upload-file/login.conf.txt>* *#mv login.conf.txt login.conf* *#reboot* Previously it had obtained from the /src of openbsd because I realized that no longer exists etc59.tar.gz with this file that comes by default it worked perfectly, I think the login.conf file does not work without the first line or comments, or I had some syntax error'll never know something like that happened to someone in this thread the which along with their answers of you helped me solve it. http://openbsd-archive.7691.n7.nabble.com/Reconfiguration-for-chrome-browser- broke-login-capability-td38508.html Thank you for all 2016-04-25 17:31 GMT-05:00 Ultramedia Libertad <meloa...@gmail.com>: > Thanks for all. > > my problem was solved, I explain how, > > For some reason I had my login.conf, empty. > > then, as could copy and paste the java based remote console kvm. > wrote the contents of the file "login.conf" to not take me much wrote without > comments. > > This file gave me the mistakes I mentioned in previous post. > > better then turned to repeat the upgrade process with install59.iso and > finish before running the reboot command, I headed to "/mnt/etc/" and > download the login.conf that comes by default in OpenBSD 5.9. > > > *#cd /mnt/etc/login.conf#rm login.conf* > > *#ftp http://my-server-upload-file/login.conf.txt > <http://my-server-upload-file/login.conf.txt>* > > *#mv login.conf.txt login.conf* > *#reboot* > > Previously it had obtained from the /src of openbsd because I realized > that no longer exists etc59.tar.gz > > with this file that comes by default it worked perfectly, I think the > login.conf file does not work without the first line or comments, or I had > some syntax error'll never know something like that happened to someone in this > thread the which along with their answers of you helped me solve it. > > > http://openbsd-archive.7691.n7.nabble.com/Reconfiguration-for-chrome-browser- broke-login-capability-td38508.html > > Thank you for all > > 2016-04-23 12:27 GMT-05:00 Ultramedia Libertad <meloa...@gmail.com>: > >> if I enter the installation shell with the option install59.iso and press >> S (shell). >> I mount my partitions and then as I can download that login.conf? to >> overwrite the one I have. >> wget does not work because me and I can not write everything in VI that the >> console does not bring the characters and want to rule out human error while >> writing. >> I can not do copy / paste with the remote console. >> >> Thank you >> >> 2016-04-23 14:50 GMT+02:00 Nick Holland <n...@holland-consulting.net>: >> >>> If you don't have any other OpenBSD machines, you can either build one >>> out of a junk machine laying in the scrap pile, or just download the >>> file from cvsweb: >>> >>> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc/etc.amd64/login.conf >>> >>> However, as I indicated, you appear to have had an "event" happen to >>> your system, and you don't seem to know what or when it happened, you >>> really are a prime candidate for a reinstall, or you might be fighting >>> "oddities" for a long time. >>> >>> Nick. >>> >>> >>> On 04/23/16 00:57, Ultramedia Libertad wrote: >>> > How could you use the default login.conf the version 5.9 from the >>> shell >>> > upgrade? o from the single user mode? >>> > >>> > thanks, if this does not work I'll go for the option to install new but >>> > not as support now from single user or intall59.iso >>> > >>> > thanks again, I hope you solve I can, without reaching a new >>> installation. >>> > >>> > 2016-04-22 22:05 GMT-05:00 Nick Holland <n...@holland-consulting.net >>> > <mailto:n...@holland-consulting.net>>: >>> > >>> > On 04/22/16 17:27, Ultramedia Libertad wrote: >>> > > for some reason, the file "/etc/login.conf" was blank >>> > >>> > the date on that file would shed a clue as to when it happened. >>> > >>> > > now I put this old file 5.7, which had a backup: >>> > >>> > closer, but that's still two releases old. >>> > ... >>> > >>> > > and now new errors: >>> > > /(failed) sshdsu couldn't resolve "tc"/ >>> > > /(failed) smtpdsu couldn't resolve "tc" >>> > >>> > "sshdsu"??? smtpdsu?? >>> > you have a very messed up system there. And I'd guess it has to >>> do with >>> > the /etc directory. >>> > >>> > If you can't clean it up easily (maybe with the help of a clean and >>> > fresh 5.9 install), I'd suggest a reload, as obviously something >>> > seriously wrong happened on this system (and as I indicated, I >>> suspect >>> > it was unrelated to the upgrade), and trying to fix it may be very >>> > difficult if you don't know what happened. >>> > >>> > > ....... >>> > > / >>> > > >>> > > Thank for all >>> > > 2016-04-22 19:28 GMT+02:00 Ultramedia Libertad < >>> meloa...@gmail.com <mailto:meloa...@gmail.com> >>> > > <mailto:meloa...@gmail.com <mailto:meloa...@gmail.com>>>: >>> > > >>> > > many thanks, >>> > > >>> > > His answer reminds me that two days ago ago, update OpenBSD >>> 5.7 to >>> > > 5.8 and then packages: >>> > > /pkg_add -u/ >>> > > and then made a >>> > > /sysmerge/ >>> > > >>> > > There was understood that after OpenBSD 5.7 to 5.8 upgrade is >>> > > sysmerge first and then pkg_add -u. >>> > >>> > no. NOTHING NEW here. it has always been complete your base >>> system >>> > upgrade, THEN upgrade packages. sysmerge upgrades the base system. >>> > >>> > AFTER the base system is upgraded, THEN you can do your pkg_add -u. >>> > Think about it, it only makes sense. And it is all we've ever >>> > suggested. >>> > >>> > Now...if you make your own procedure and you get away with it and >>> it >>> > breaks for a new release, that's not an OpenBSD problem. :) >>> > >>> > > >>> > > Another aspect that pkg_add -u in OpenBSD 5.8 dovecot some >>> > > /etc/login.conf wonder, then surely I chose something wrong >>> here. >>> > >>> > I do not believe pkg_add ever touches login.conf, though many >>> > applications will make suggestions of changes to login.conf -- but >>> you >>> > have to make them. >>> > >>> > Nick. >>> > >>> > >>> > > and order a remote console to my datacenter to enter and >>> verify the >>> > > file /etc/login.conf >>> > > >>> > > Thanks, I will report what happens with this. >>> > > >>> > > 2016-04-22 6:28 GMT-05:00 Nick Holland < >>> n...@holland-consulting.net <mailto:n...@holland-consulting.net> >>> > > <mailto:n...@holland-consulting.net >>> > <mailto:n...@holland-consulting.net>>>: >>> > > >>> > > On 04/21/16 21:25, Ultramedia Libertad wrote: >>> > > > hello >>> > > > >>> > > > I am upgrade OpenBSD 5.8 to 5.9 and after to reboot >>> > > > >>> > > > i have follow errors in remote console : >>> > > >>> > > ...[deleting big block of blank lines]... >>> > > >>> > > > *init: daemon: unknown class (failed)syslogdsu: daemon: >>> > unknown class >>> > > > (failed)pflogdsu: daemon: unknown class (failed)ntpdsu: >>> > daemon: unknown >>> > > > class (failed)starting RPC daemons:.savecore: no core >>> > dumpcheckin quotas: >>> > > > done.clearing /tmpkern.securelevel: 0 -> 1creating >>> > runtime link editor >>> > > > directory cache.preserving editor files.startings >>> > networks daemons: sshdsu: >>> > > > daemon: unknown class (failed)smtpdsu: daemon: unknown >>> class >>> > > > (failed)sndiodsu: daemon: unknown class >>> (failed).....Thu apr >>> > > 21 20:06:24 >>> > > > CDI 2016* >>> > > > >>> > > > >>> > > > y more >>> > > > >>> > > > please help me attach image >>> > > >>> > > both the lists and I block images images... >>> > > >>> > > > [demime 1.01d removed an attachment of type image/png >>> > which had a name of Screenshot_2016-04-21_21-14-18.png] >>> > > > >>> > > >>> > > sounds like somewhere along the line you deleted or >>> > mangled your >>> > > /etc/login.conf file. I'm guessing it had nothing to do >>> > with the >>> > > upgrade, but probably more with the reboot (i.e., you >>> > hosed the file >>> > > some time ago, if you had rebooted without an upgrade, >>> you >>> > would >>> > > have >>> > > seen the same problem). >>> > > >>> > > sysmerge may help. >>> > > >>> > > Nick. >>> > > >>> > > >>> > > >>> > > >>> > > -- >>> > > editor de sueños >>> > > >>> > > >>> > > >>> > > >>> > > -- >>> > > editor de sueños >>> > >>> > >>> > >>> > >>> > -- >>> > editor de sueños >>> >>> >> >> >> -- >> editor de sueños >> > > > > -- > editor de sueños > -- editor de sueños
