Re: Authorisation Errors on 9.2
On 14/10/2013 06:37, Beeblebrox wrote: Hi, I Inadvertently posted the gnome-keyring bit. That's almost standard error message on FreeBSD-Gnome. The relevant bit for the error is in fact: slim: gkr-pam: no password is available for user However, the user cannot login on a tty without providing a password. For ssh, the same error and dropped connection occurs for all users. sshd was modified to allow root login. All users have valid home directories defined. From /etc/passwd; I wonder if this has anything to do with it? sshd:*:22:22:Secure Shell Daemon:/var/empty:/usr/sbin/*nologin* Could it be a dud /root/.tcshrc? Or /etc/login.conf? The accounts which try to ssh login also login on host proper and do not have any login issues when logging-in directly on host - so I think we can eliminate these problems. I'm now really guessing - I've not tried 9.2-RELEASE. Given these things are usually really obvious when you finally spot them (it happens to me a lot, anyway), here are a few obvious things you could think of in case it helps. First off, ssh is different from a console login so what's in sshd_config matters. That said, the defaults generally work (or used to). In no particular order, in sshd_config: PasswordAuthentication must be "yes" KerberosOrLocalPasswd probably "yes" AllowUsers, AllowGroups, DenyUsers and DenyGroups need to be set correctly. ChrootDirectory - this could cause fun if it's set to something. Other things that might be interesting are UseLogin and UsePAM. If this was a fundamental problem with changed defaults in 9.2, I'm sure a lot more people would have complained. Regards, Frank. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Authorisation Errors on 9.2
Hi, I Inadvertently posted the gnome-keyring bit. That's almost standard error message on FreeBSD-Gnome. The relevant bit for the error is in fact: slim: gkr-pam: no password is available for user However, the user cannot login on a tty without providing a password. For ssh, the same error and dropped connection occurs for all users. sshd was modified to allow root login. All users have valid home directories defined. From /etc/passwd; I wonder if this has anything to do with it? sshd:*:22:22:Secure Shell Daemon:/var/empty:/usr/sbin/*nologin* >> Could it be a dud /root/.tcshrc? Or /etc/login.conf? The accounts which try to ssh login also login on host proper and do not have any login issues when logging-in directly on host - so I think we can eliminate these problems. Thanks and Regards ----- FreeBSD-9.2-stable_amd64_root-on-zfs_clang-only-world -- View this message in context: http://freebsd.1045724.n5.nabble.com/Authorisation-Errors-on-9-2-tp5851543p5851636.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adoble Flash troubles on 9.2-RELEASE
On 10/12/13 20:37, Ralf Mardorf wrote: On Sat, 2013-10-12 at 11:52 +0200, David Demelier wrote: I don't like much chrome but I'll give a try to see. +1 It's not a browser I like. Since I'm using my computer for audio production my FreeBSD isn't maintained, I need to use Linux, so I don't know if Chrome is available for FreeBSD. When I google (resp. startpage.com search) for FreeBSD and Chrome, it seems to be that the hits aren't about Chrome, but Chromium instead. Chromium doesn't include Adobe Flash, https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome . Sorry for the noise. At least we could use Adobe Flash by Chrome with FreeBSD in a virtual machine running a Linux instead of a Windows guest. Or is Chrome available for FreeBSD too? Perhaps you should post the links that don't work with the latest Linux version of Adobe Flash, so others could test if the issue is really caused by Flash Player and not by something else. To add more confusion to this fray, although it may not help with gray screen issue, the only reason chromium works (yes, just install the nspluginwrapper as per the handbook) is that it is better suited to the new pepper style Adobe is going with now. FWIW, I did put in a port to fix drm issues on any site which was stopping videos playing (again, not your specific issue, but what appears to be in discussion here) and which allows flash to work using any browser - uses linux dbus libraries (weird). Not sure of the status though. Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Authorisation Errors on 9.2
On 13/10/2013 18:08, Beeblebrox wrote: I have two strange errors but I am not sure whether they are related. ERROR-1: Slim allows login without checking for password. /var/log/auth.log shows: Oct 13 11:44:57: slim: gkr-pam: no password is available for user Oct 13 11:44:57: gnome-keyring-daemon[1225]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk ERROR-2: sshd disconnects (drops) client connections immediately after login. This happens when trying from host its self or some other client. Testing from host (162.168.1.10 is host's IP) $ ssh root@192.168.1.10 Password for root@server.freebsd: Last login: Sun Oct 13 13:02:09 2013 Welcome to myNetwork (the motd message) csh: No such file or directory Connection to 192.168.1.10 closed. /var/log/auth.log for ssh shows: Oct 13 19:41:37: Server listening on 0.0.0.0 port 22. Oct 13 19:42:37: Accepted keyboard-interactive/pam for root from 192.168.1.10 port 33248 ssh2 Oct 13 19:42:37: Received disconnect from 192.168.1.10: 11: disconnected by user Thanks for any advice on how to resolve these two issues. The gnome keyring demon does that. I believe it's only warning and I've never dug in to the source to find out more but I think it's something it can only do on Linux. I'm sure someone will be along in a minute with something to say about that. As to the second problem - csh: No such file or directory. At the risk of pointing out the trivial, is root's home directory valid? Why not post /etc/passwd and we'll check :-) Could it be a dud /root/.tcshrc? Or /etc/login.conf? I assume you've configured sshd to allow direct root logins. If you hadn't I think you get a different rejection message (but who knows with 9.2?) Regards, Frank. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Authorisation Errors on 9.2
I have two strange errors but I am not sure whether they are related. ERROR-1: Slim allows login without checking for password. /var/log/auth.log shows: Oct 13 11:44:57: slim: gkr-pam: no password is available for user Oct 13 11:44:57: gnome-keyring-daemon[1225]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk ERROR-2: sshd disconnects (drops) client connections immediately after login. This happens when trying from host its self or some other client. Testing from host (162.168.1.10 is host's IP) $ ssh root@192.168.1.10 Password for root@server.freebsd: Last login: Sun Oct 13 13:02:09 2013 Welcome to myNetwork (the motd message) csh: No such file or directory Connection to 192.168.1.10 closed. /var/log/auth.log for ssh shows: Oct 13 19:41:37: Server listening on 0.0.0.0 port 22. Oct 13 19:42:37: Accepted keyboard-interactive/pam for root from 192.168.1.10 port 33248 ssh2 Oct 13 19:42:37: Received disconnect from 192.168.1.10: 11: disconnected by user Thanks for any advice on how to resolve these two issues. - FreeBSD-9.2-stable_amd64_root-on-zfs_clang-only-world -- View this message in context: http://freebsd.1045724.n5.nabble.com/Authorisation-Errors-on-9-2-tp5851543.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adoble Flash troubles on 9.2-RELEASE
On Sat, 2013-10-12 at 11:52 +0200, David Demelier wrote: > I don't like much chrome but I'll give a try to see. +1 It's not a browser I like. Since I'm using my computer for audio production my FreeBSD isn't maintained, I need to use Linux, so I don't know if Chrome is available for FreeBSD. When I google (resp. startpage.com search) for FreeBSD and Chrome, it seems to be that the hits aren't about Chrome, but Chromium instead. Chromium doesn't include Adobe Flash, https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome . Sorry for the noise. At least we could use Adobe Flash by Chrome with FreeBSD in a virtual machine running a Linux instead of a Windows guest. Or is Chrome available for FreeBSD too? Perhaps you should post the links that don't work with the latest Linux version of Adobe Flash, so others could test if the issue is really caused by Flash Player and not by something else. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adoble Flash troubles on 9.2-RELEASE
On 12.10.2013 11:02, Ralf Mardorf wrote: > If you really need to visit sites that need Adobe Flash, you perhaps > should use the google-chrome browser. For some websites with flash > content, we don't need flash anymore, just modern HTML5 capable web > browsers. For *nix there never will be a current version for flashplayer > again. > Yes I know that adobe flash player for *nix is gone but I'm guessing why it worked well so much before.. I don't like much chrome but I'll give a try to see. Thanks for the hint! > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adoble Flash troubles on 9.2-RELEASE
If you really need to visit sites that need Adobe Flash, you perhaps should use the google-chrome browser. For some websites with flash content, we don't need flash anymore, just modern HTML5 capable web browsers. For *nix there never will be a current version for flashplayer again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Adoble Flash troubles on 9.2-RELEASE
Hi, The current linux-f10-flashplugin-11.2r202.310 version has some troubles on my machine (with Firefox). Sometimes, when a flash component is displayed and you scroll a bit the window the flash break and goes grey, you're forced to reload the page. I'm using the Intel new KMS driver if that matters, note that it never happened on my 9.1-RELEASE. Is anyone having a similar issue? Regards, David. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD 9.2-RELEASE doesn't correctly detect USB mouse/keyboard
I am running vanilla 9.2-RELEASE on an HP Z230. Strangely, my USB keyboard and mouse don't work. When I attach, here is what shows: Oct 11 12:36:39 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:39 waridi kernel: ugen0.2: at usbus0 (disconnected) Oct 11 12:36:39 waridi kernel: uhub_reattach_port: could not allocate new device Oct 11 12:36:48 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:48 waridi kernel: ugen0.2: at usbus0 (disconnected) Oct 11 12:36:48 waridi kernel: uhub_reattach_port: could not allocate new device Oct 11 12:36:55 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:55 waridi kernel: ugen0.2: at usbus0 (disconnected) Oct 11 12:36:55 waridi kernel: uhub_reattach_port: could not allocate new device $ uname -a FreeBSD waridi.kihingovillage.com 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj /usr/src/sys/GENERIC amd64 I am wondering if there is something obvious I am missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 "I can't hear you -- I'm using the scrambler." ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Victor Sudakov wrote: > > I have several Supermicro-based servers with the mpt RAID adapter: > > # mptutil show adapter > mpt0 Adapter: >Board Name: UNUSED >Board Assembly: > Chip Name: C1068E > Chip Revision: UNUSED > RAID Levels: none > # > > The problem is, I cannot configure any RAIDs (please see output > below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD > still sees them as separate physical discs. What am I doing wrong? > > I cannot use gmirror with these servers because a) if no MPT RAID is > configured in BIOS setup, it cannot boot from HDD and b) if an MPT > RAID *is* configured in BIOS setup, it occupies the last sector and > prevents GEOM from working with these drives. > > Any help please? (or redirect me to a more appropriate maillist). After many unsuccessful trials and googling, we had to reconfigure the adapter from RAID mode to IT mode. It required flashing the adapter's BIOS from a Supermicro-supplied image and changing a jumper setting on the motherboard. Now as the adapter is in IT mode, it is a plain HBA the BIOS can boot from, and I have set up a gmirror on the SAS disks. After flashing the adapter BIOS, don't forget to enter its setup (Ctrl-C) and enable hotplugging of disks (called "Removable Media Support" in the menu, off by default). People come across similar problems and solutions on other OSes, like http://ubuntuforums.org/archive/index.php/t-973912.html -- Victor Sudakov Tomsk, Russia Russian Barefoot FAQ at http://www.barefooters.ru/barefoot.txt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Upgrade 9.1 -> 9.2
I used 'freebsd-update upgrade -r 9.2-RELEASE' to upgrade a test system. All went well, until the point at which it said: Kernel updates have been installed. Please reboot and run "/usr/sbin/freebsd-update install" again to finish installing updates. Stupidly, I did NOT reboot, but started the "/usr/sbin/freebsd-update install" without rebooting first. As soon as I realised my mistake (a few minutes later), I issued ctrl-c to exit, rebooted and ran "/usr/sbin/freebsd-update install" again. It appeared to finish successfuly. Have I screwed up my system, or am I OK? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 8 October 2013, at 16:40, Polytropon wrote: > On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: >> I tried downloading the src with: >> >> svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src >> >> I didn't get Release 9.2. The first entry in UPDATING is: >> >> 20130705: >>hastctl(8)'s `status' command output changed to terse one-liner >> format. >>Scripts using this should switch to `list' command or be rewritten. >> >> >> There is an entry earlier for Release 9.1. but no entry for Release 9.2. > > You could try downloading and extracting the "src" distribution: > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz Before I saw this I built from the src obtained via svn. The system now boots. I still have no idea what was preventing it from booting. It was something between displaying the Beastie menu and waiting for user input. There had to be at least 2 issues as the messages changed after the first attempt to rebuild the system. I tried to chase down the boot code for the first error message and it appears to be generated when there is a problem with a directory. I couldn't find any further diagnostic info to identify the directory. I have not yet tried to chase down the second set of messages in the source. The system now says its 9.2. UPDATING still looks the same. Interestingly enough, on another system that I updated earlier to 9.2 via freebsd-update, UPDATING there is identical to the one on this system. There is no 9.2 entry. Also of note is that most of the ports/packages are still present. However SASL2 vanished without a trace. Its easily replaced, but why is certainly interesting. I have no ideas at this point. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
Polytropon wrote: > On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: >> I tried downloading the src with: >> >> svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src >> >> I didn't get Release 9.2. The first entry in UPDATING is: >> >> 20130705: >> hastctl(8)'s `status' command output changed to terse one-liner >> format. >> Scripts using this should switch to `list' command or be rewritten. >> >> >> There is an entry earlier for Release 9.1. but no entry for Release 9.2. > > You could try downloading and extracting the "src" distribution: > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz > > > > Yes, that might have been simpler. Knew there had to be some other way. :) -- c...@sdf.org SDF Public Access UNIX System - http://sdf.org -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: > I tried downloading the src with: > > svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src > > I didn't get Release 9.2. The first entry in UPDATING is: > > 20130705: > hastctl(8)'s `status' command output changed to terse one-liner > format. > Scripts using this should switch to `list' command or be rewritten. > > > There is an entry earlier for Release 9.1. but no entry for Release 9.2. You could try downloading and extracting the "src" distribution: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
Doug Hardie wrote: >>> The Thick Plottens… >>> I received the drives and installed them on a working system. The >>> failed system is structured with a single partition for the system and >>> another for swap. For some unknown reason, the BIOS got left >>> configured to boot the extra disk if its powered up. That turns out >>> to be handy. I can boot a working system with the corrupt drive >>> powered off. >>> Booting from the corrupt drive yields the normal hardware info >>> followed by the Beastie image and immediately by a multitude of lines >>> (repeated many times): >>> Consoles: internal video/keyboard serial port >>> BIOS drive C: is disk0 >>> BIOS drive D: is disk1 >>> BIOS 639kB/1037824kB available memory >>> FreeBSD/x86 bootstrap loader, Revision 1.1 >>> (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) >>> Can't work out which disk we are booting from. >>> Guessed BIOS device 0x not found by probes, defaulting to disk0: >>> I was able to capture these by using a serial console connected to >>> another computer. The lines only appear on the serial console once. >>> They scroll by on the real console many time - all too fast to read >>> anything. Then after a few seconds of that, the screen goes black, >>> and the system reboots. The cycle then repeats… Pressing any key >>> does nothing. I even filled the keyboard buffer with spaces hoping to >>> stop boot, but nothing seems to stop it. >>> I checked and the freebsd-update.conf include world sys and src. I >>> rebuild everything after removing /obj just for grins and giggles. I >>> have installed the kernel and world using DESTDIR to put it on the >>> corrupt drive. Same messages again. >>> I now have the corrupt drive mounted on /mnt and am trying to update >>> the src again. Using: >>> freebsd-update -b /mnt fetch >>> updated files list show /usr/src/sys… >>> and updating to 9.1-RELEASE-p7 >>> freebsd-update -b /mnt install >>> This is running slower than molasses in January. Its run for almost >>> 30 minutes and only 3 files have been updated. There must be network >>> issues between me and the server. I'll let it run tonight but I am >>> going to crash now. Long day. More tomorrow. >>> -- Doug >> >> Have you checked the dmesg output, specifically to see if there are any disk >> errors, perhaps the hard drive is about dead. If you are planning to >> rebuild world and kernel form source, why not just use svn or extract the >> source from the 9.2-RELEASE disk onto the system. > > There are no hardware errors logged. The drive is only a couple months old. > Smart drive status is good. > > I tried downloading the src with: > > svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src > > I didn't get Release 9.2. The first entry in UPDATING is: > > 20130705: > hastctl(8)'s `status' command output changed to terse one-liner > format. > Scripts using this should switch to `list' command or be rewritten. > > > There is an entry earlier for Release 9.1. but no entry for Release 9.2. > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > > Hello Doug, Here is a more recent version of the file on svn: http://svnweb.freebsd.org/base/stable/9/UPDATING?revision=255900&view=markup Earlier today I also checked out base for releng/9.2 from the same mirror, svn0.us-west. My UPDATING file is outdated too. Time of the last entry is 20130705. The mirror told me that I had checked out revision 256150. When running "freebsd-update upgrade -r RELEASE-9.2" last night it gave : > WARNING: This system is running a "customcl" kernel, which is not a kernel configuration distributed as part of FreeBSD 9.1-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "/usr/sbin/freebsd-update install". > That might have been expected, but I have read on this list that freebsd-update will sometimes automatically replace a custom kernel with a generic, and in /etc/freebsd-update.conf I had the line: Components src world kernel . HTH, Cary -- c...@sdf.org SDF Public Access UNIX System - http://sdf.org -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 8 October 2013, at 06:22, dweimer wrote: > On 10/08/2013 4:27 am, Doug Hardie wrote: >> On 5 October 2013, at 05:08, Polytropon wrote: >>> On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: >>>> On 4 October 2013, at 20:03, Polytropon wrote: >>>>> On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: >>>>>> On 4 October 2013, at 19:08, Polytropon wrote: >>>>>>> On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: >>>>>>>> The exact sequence was: >>>>>>>> Step 1: freebsd-update from 9.1 to 9.2 >>>>>>> Have you verified in /etc/freebsd-update.conf that "src" >>>>>>> is definitely part of what should be updated? >>>>>> System is not bootable - can't verify anything… >>>>> Does the system (or better, its "enclosure", software-wise) >>>>> allow booting a rescue system or an emergency media, such >>>>> as a FreeBSD v9 live system? >>>> Yes - but there is no one there who can successfully be told >>>> how to run it. >>> Not even inserting a USB stick (with the FreeBSD memstick data) >>> or a CD? >>>> We have serious communications issues - they want to use back >>>> slashes and have no idea what a slash is. >>> Maybe that is the result of many years of "administration" on >>> "Windows" PCs. :-) >>>> Even if you tell them which key to use, they know better and >>>> use a back slash cause thats what Windoze uses. >>> Uh... "knowing better" would disqualify them as maintainers of >>> a server installation. The inability to learn (or even to read >>> and follow instructions) is a dangerous thing. >>>> The disk should be in the mail to me now. I will be able to >>>> work with it when it arrives. >>> Okay, that's also a possible alternative. To be honest, that's >>> the first time I hear about this procedure. But doable. >>>>> The file /etc/freebsd-update.conf should contain the line >>>>> Components src world kernel >>>>> if you want to make sure the source is properly updated, >>>>> along with the world and kernel (GENERIC). >>>> As indicated before, I don't think all the source got updated. >>>> The kernel showed 9.2 after recompilation. However UPDATING >>>> was not updated. Thats as much as I could check before. >>> I assume that this could be possible by inconsistently updated >>> sources. It would be a good start to remove /usr/src and download >>> the sources of the correct version via SVN _or_ freebsd-update >>> again. Before the next installation attempt, /usr/obj should be >>> removed as well, just to be sure. >>>>>>>> Step 5: reboot >>>>>>> Attention: Into single-user mode. >>>>>> Not possible since the system is located over 100 miles away. >>>>>> Everything has to be done via remote console. >>>>> Does this mean "SSH only" or do you have a _real_ console >>>>> transmission by which you can access the system _prior_ to >>>>> the OS providing the SSH access? I'm mentioning this because >>>>> the traditional approach requires (few) steps done in the >>>>> single-user mode where no SSH connectivity is provided in >>>>> the "normal" way… >>>> I have a telnet box that has serial connections to the console >>>> ports. That approach has been used without any issues since >>>> FreeBSD 2.5. I do disable all ports during the process via an >>>> reduced rc.conf file. >>> A serial console should also work, but even though I've been >>> using serial consoles (and _real_ serial terminals), one thing >>> I'm not sure about: Is it possible to interrupt (!) the boot >>> process at an early stage to get to the loader prompt and >>> boot into single user mode from there? >>> Ok >>> boot -s >>> If not, do you have the "beastie menu" (or whatever it is called >>> today) enabled to go to SUM to perform the "make installworld" step? >>> Anyway, if you can install everything is required with the disk >>> at home, and then send it back to that "datacenter" (according >>> to your characterization, the quotes are deserved), that should >>> solve the problems and make sure everything works as i
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
Yeah!!! 96.47.72.120 works! Thanks! > Depends. Where are your other installed packages from? I'd probably > re-install all of them from the pkg-test repository just to be safe. I installed 9.1 on new node and compiled from ports. It took a long time, which I want to avoid right now. Here is what I consider as steps for 9.2: freebsd-update upgrade -r 9.2-RELEASE freebsd-update install nextboot -k GENERIC freebsd-update install portsnap fetch portsnap extract do all pkg steps freebsd-update install kernel rebuild reboot I might be making some misunderstandings in order of this? Best regards Zoran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
On Tue, Oct 8, 2013, at 10:58, Zoran Kolic wrote:
> > Use PACKAGESITE=http://pkg-test.freebsd.org/pkg-test-${ABI}/latest
> >
> > That's the kit that will form the official FreeBSD package repository;
> > it just lacks the crypto bits for signing the packages, which is why
> > it's calling itself 'pkg-test'
> >
> > Oh -- there isn't an A record in the DNS for pkg-test.freebsd.org --
> > look up a SRV record for _http._tcp.pkg-test.freebsd.org instead.
>
> Well, I still have no idea what the address of the server is.
> Could someone post it (i.e. 123.456.789.123 or alike)?
# dig _http._tcp.pkg-test.freebsd.org SRV
; <<>> DiG 9.9.3-P2 <<>> _http._tcp.pkg-test.freebsd.org SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8634
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;_http._tcp.pkg-test.freebsd.org. INSRV
;; ANSWER SECTION:
_http._tcp.pkg-test.freebsd.org. 120 IN SRV 10 10 80
pkg1.nyi.freebsd.org.
;; ADDITIONAL SECTION:
pkg1.nyi.freebsd.org. 3600IN A 96.47.72.120
pkg1.nyi.freebsd.org. 3600IN 2610:1c1:1:6300::16:78
;; Query time: 374 msec
;; SERVER: 192.168.93.251#53(192.168.93.251)
;; WHEN: Tue Oct 08 11:24:41 CDT 2013
;; MSG SIZE rcvd: 144
> After having it set as PACKAGESITE, I assume running pkg, pkg2ng,
> pkg update, pkg upgrade -fy enough?
> Best regards all
>
Depends. Where are your other installed packages from? I'd probably
re-install all of them from the pkg-test repository just to be safe.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
> Use PACKAGESITE=http://pkg-test.freebsd.org/pkg-test-${ABI}/latest
>
> That's the kit that will form the official FreeBSD package repository;
> it just lacks the crypto bits for signing the packages, which is why
> it's calling itself 'pkg-test'
>
> Oh -- there isn't an A record in the DNS for pkg-test.freebsd.org --
> look up a SRV record for _http._tcp.pkg-test.freebsd.org instead.
Well, I still have no idea what the address of the server is.
Could someone post it (i.e. 123.456.789.123 or alike)?
After having it set as PACKAGESITE, I assume running pkg, pkg2ng,
pkg update, pkg upgrade -fy enough?
Best regards all
Zoran
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 10/08/2013 4:27 am, Doug Hardie wrote: On 5 October 2013, at 05:08, Polytropon wrote: On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: On 4 October 2013, at 20:03, Polytropon wrote: On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: On 4 October 2013, at 19:08, Polytropon wrote: On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that "src" is definitely part of what should be updated? System is not bootable - can't verify anything… Does the system (or better, its "enclosure", software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. Not even inserting a USB stick (with the FreeBSD memstick data) or a CD? We have serious communications issues - they want to use back slashes and have no idea what a slash is. Maybe that is the result of many years of "administration" on "Windows" PCs. :-) Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. Uh... "knowing better" would disqualify them as maintainers of a server installation. The inability to learn (or even to read and follow instructions) is a dangerous thing. The disk should be in the mail to me now. I will be able to work with it when it arrives. Okay, that's also a possible alternative. To be honest, that's the first time I hear about this procedure. But doable. The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. I assume that this could be possible by inconsistently updated sources. It would be a good start to remove /usr/src and download the sources of the correct version via SVN _or_ freebsd-update again. Before the next installation attempt, /usr/obj should be removed as well, just to be sure. Step 5: reboot Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. Does this mean "SSH only" or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the "normal" way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. A serial console should also work, but even though I've been using serial consoles (and _real_ serial terminals), one thing I'm not sure about: Is it possible to interrupt (!) the boot process at an early stage to get to the loader prompt and boot into single user mode from there? Ok boot -s If not, do you have the "beastie menu" (or whatever it is called today) enabled to go to SUM to perform the "make installworld" step? Anyway, if you can install everything is required with the disk at home, and then send it back to that "datacenter" (according to your characterization, the quotes are deserved), that should solve the problems and make sure everything works as intended. The Thick Plottens… I received the drives and installed them on a working system. The failed system is structured with a single partition for the system and another for swap. For some unknown reason, the BIOS got left configured to boot the extra disk if its powered up. That turns out to be handy. I can boot a working system with the corrupt drive powered off. Booting from the corrupt drive yields the normal hardware info followed by the Beastie image and immediately by a multitude of lines (repeated many times): Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kB/1037824kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: I was able to capture these by using a serial console connected to another computer. The lines only appear on the serial console once. They scroll by on the real console many time - all too fast to read anything. Then after a few seconds of that, the screen goes black, and the system reboots. The cycle then repeats… Pressin
Re: 9.1 - 9.2 upgrade
On 5 October 2013, at 05:08, Polytropon wrote: > On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: >> >> On 4 October 2013, at 20:03, Polytropon wrote: >> >>> On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: >>>> >>>> On 4 October 2013, at 19:08, Polytropon wrote: >>>> >>>>> On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: >>>>>> The exact sequence was: >>>>>> >>>>>> Step 1: freebsd-update from 9.1 to 9.2 >>>>> >>>>> Have you verified in /etc/freebsd-update.conf that "src" >>>>> is definitely part of what should be updated? >>>> >>>> System is not bootable - can't verify anything… >>> >>> Does the system (or better, its "enclosure", software-wise) >>> allow booting a rescue system or an emergency media, such >>> as a FreeBSD v9 live system? >> >> Yes - but there is no one there who can successfully be told >> how to run it. > > Not even inserting a USB stick (with the FreeBSD memstick data) > or a CD? > > > >> We have serious communications issues - they want to use back >> slashes and have no idea what a slash is. > > Maybe that is the result of many years of "administration" on > "Windows" PCs. :-) > > > >> Even if you tell them which key to use, they know better and >> use a back slash cause thats what Windoze uses. > > Uh... "knowing better" would disqualify them as maintainers of > a server installation. The inability to learn (or even to read > and follow instructions) is a dangerous thing. > > > >> The disk should be in the mail to me now. I will be able to >> work with it when it arrives. > > Okay, that's also a possible alternative. To be honest, that's > the first time I hear about this procedure. But doable. > > > >>> The file /etc/freebsd-update.conf should contain the line >>> >>> Components src world kernel >>> >>> if you want to make sure the source is properly updated, >>> along with the world and kernel (GENERIC). >> >> As indicated before, I don't think all the source got updated. >> The kernel showed 9.2 after recompilation. However UPDATING >> was not updated. Thats as much as I could check before. > > I assume that this could be possible by inconsistently updated > sources. It would be a good start to remove /usr/src and download > the sources of the correct version via SVN _or_ freebsd-update > again. Before the next installation attempt, /usr/obj should be > removed as well, just to be sure. > > > >>>>>> Step 5: reboot >>>>> >>>>> Attention: Into single-user mode. >>>> >>>> Not possible since the system is located over 100 miles away. >>>> Everything has to be done via remote console. >>> >>> Does this mean "SSH only" or do you have a _real_ console >>> transmission by which you can access the system _prior_ to >>> the OS providing the SSH access? I'm mentioning this because >>> the traditional approach requires (few) steps done in the >>> single-user mode where no SSH connectivity is provided in >>> the "normal" way… >> >> I have a telnet box that has serial connections to the console >> ports. That approach has been used without any issues since >> FreeBSD 2.5. I do disable all ports during the process via an >> reduced rc.conf file. > > A serial console should also work, but even though I've been > using serial consoles (and _real_ serial terminals), one thing > I'm not sure about: Is it possible to interrupt (!) the boot > process at an early stage to get to the loader prompt and > boot into single user mode from there? > > Ok > boot -s > > If not, do you have the "beastie menu" (or whatever it is called > today) enabled to go to SUM to perform the "make installworld" step? > > Anyway, if you can install everything is required with the disk > at home, and then send it back to that "datacenter" (according > to your characterization, the quotes are deserved), that should > solve the problems and make sure everything works as intended. The Thick Plottens… I received the drives and installed them on a working system. The failed system is structured with a single partition for the system and another for swap. For some unknown reason, the BIOS got left configured to boot t
mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Colleagues, I have several Supermicro-based servers with the mpt RAID adapter: # mptutil show adapter mpt0 Adapter: Board Name: UNUSED Board Assembly: Chip Name: C1068E Chip Revision: UNUSED RAID Levels: none # The problem is, I cannot configure any RAIDs (please see output below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD still sees them as separate physical discs. What am I doing wrong? I cannot use gmirror with these servers because a) if no MPT RAID is configured in BIOS setup, it cannot boot from HDD and b) if an MPT RAID *is* configured in BIOS setup, it occupies the last sector and prevents GEOM from working with these drives. Any help please? (or redirect me to a more appropriate maillist). # mptutil clear Are you sure you wish to clear the configuration on mpt0? [y/N] y mpt0: Configuration cleared # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # mptutil show drives mpt0 Physical Drives: da0 ( 558G) ONLINE SCSI-6 bus 0 id 0 da1 ( 558G) ONLINE SCSI-6 bus 0 id 1 da2 ( 558G) ONLINE SCSI-6 bus 0 id 2 da3 ( 558G) ONLINE SCSI-6 bus 0 id 3 # # mptutil create raid1 -v da2,da3 mptutil: Reading config page header failed: Invalid configuration page Added drive da2 with PhysDiskNum 0 mptutil: Reading config page header failed: Invalid configuration page # # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD 9.2 - does not appear to support the 'dc' PCMCIA NIC driver
I have a Netgear FA511 PCMCIA NIC that worked fine under 9.1. Under 9.2 I get the following message: Oct 6 21:38:11 monitor4 kernel: dc0: port 0x1100-0x11ff irq 19 at device 0.0 on cardbus0 Oct 6 21:38:11 monitor4 kernel: dc0: attaching PHYs failed This used to work under 9.1, does anyone know what happened? Thanks. Kent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Best 10Gbit/s card for FB 9.2
Le 06/10/2013 à 18:24:27-0400, ill...@gmail.com a écrit > On 6 October 2013 10:47, Albert Shih wrote: > > Hi, > > > > I would like to known what is the best 10 Gbits/s copper ethernet card for > > FreeBSD 9.2 on Dell hardware : > > > > I got on the Dell's website > > > > > > > > Broadcom 57800 2x10Gb BT + 2x1Gb BT Network Daughter Card > > > > Broadcom 57810 DP 10Gb BT Converged Network Adapter > > > > Intel Ethernet X540 10Gb BT DP + i350 1Gb BT DP Network Daughter Card > > > > Intel Ethernet X540 DP 10GBASE-T Server Adapter, Low Profile > > > > It looks like (from grepping around) that the BCE578xx are only > supported on FreeBSD 10 (bxe(4)). The Intel adapter looks to be > supported on 9.2 as ixgbe(4) which is in the GENERIC kernel & so > should (cross fingers) work "out of the box". Lots of thanks. When I got my server I send here the result to confirm (or not) the support. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: lun 7 oct 2013 10:06:00 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Best 10Gbit/s card for FB 9.2
On 6 October 2013 10:47, Albert Shih wrote: > Hi, > > I would like to known what is the best 10 Gbits/s copper ethernet card for > FreeBSD 9.2 on Dell hardware : > > I got on the Dell's website > > > > Broadcom 57800 2x10Gb BT + 2x1Gb BT Network Daughter Card > > Broadcom 57810 DP 10Gb BT Converged Network Adapter > > Intel Ethernet X540 10Gb BT DP + i350 1Gb BT DP Network Daughter Card > > Intel Ethernet X540 DP 10GBASE-T Server Adapter, Low Profile > It looks like (from grepping around) that the BCE578xx are only supported on FreeBSD 10 (bxe(4)). The Intel adapter looks to be supported on 9.2 as ixgbe(4) which is in the GENERIC kernel & so should (cross fingers) work "out of the box". -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Best 10Gbit/s card for FB 9.2
Hi, I would like to known what is the best 10 Gbits/s copper ethernet card for FreeBSD 9.2 on Dell hardware : I got on the Dell's website Broadcom 57800 2x10Gb BT + 2x1Gb BT Network Daughter Card Broadcom 57810 DP 10Gb BT Converged Network Adapter Intel Ethernet X540 10Gb BT DP + i350 1Gb BT DP Network Daughter Card Intel Ethernet X540 DP 10GBASE-T Server Adapter, Low Profile Best regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: dim 6 oct 2013 16:43:45 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem completing a 9.1 release to 9.2 release upgrade
On 06/10/2013 04:51, Eric Feldhusen wrote:
> I figured I'd walk through those steps from start to finish and just
> correct my main problem and any other little glitches I might have.
>
> I'm on step 6 and when I run mergemaster -p, I get the following error.
>
> *** Creating the temporary root environment in /var/tmp/temproot
> *** /var/tmp/temproot ready for use
> *** Creating and populating directory structure in /var/tmp/temproot
>
> /usr/bin/install: Undefined symbol "gid_from_group"
>
> *** FATAL ERROR: Cannot copy files to the temproot environment
>
> I found this thread on the Freebsd forums
> http://forums.freebsd.org/showthread.php?t=41779 with the same error and if
> I do the same diagnostic steps of
>
> truss install -d -g wheel ~/testdirectory
>
> I find an error of
>
> lstat("/usr/local/etc/libmap.d",0x7fffb990) ERR#2 'No such file or
> directory'
>
> Any suggestions? Thank you for the help thus far.
The 'undefined symbol' error means you have a binary which is somehow
not dynamically linking against the shared libraries it was compiled to
use. As install(1) has pretty simple dynamic library usage -- just
libmd and libc:
# ldd /usr/bin/install
/usr/bin/install:
libmd.so.5 => /lib/libmd.so.5 (0x800822000)
libc.so.7 => /lib/libc.so.7 (0x800a33000)
... and libmd.so just contains code for computing various checksums,
nothing to do with groups and GIDs. This suggests that your libc.so is
somehow incompatible with your /usr/bin/install. Which really shouldn't
be the case given that you'ld previously used freebsd-update to upgrade
your userland to 9.2-RELEASE.
Things to double check:
* you haven't been faffing about with /etc/libmap.conf -- that file
or any file it includes should basically be empty except in quite
unusual circumstances. Remember folks: libmap is not your
solution of choice. It's what you turn to when there are no other
viable alternatives.
* Your freebsd-update really has been updating the source tree you
attempted to upgrade from. Check /etc/freebsd-update.conf. By
default it contains:
# Components of the base system which should be kept updated.
Components src world kernel
If you don't have src in there your buildworld procedure will at
best be trying to take you back down to 9.1-RELEASE-p???, and at
worst trying to create some unholy mixture of 9.2 kernel with
earlier bits of the system.
I think you should be able to recover to a system managed via
freebsd-update by something like:
# vi /etc/freebsd-update.conf
{ Make sure you're getting 'src world kernel' components as shown
above }
# freebsd-update fetch
# freebsd-update install
but I haven't tested that so ICBW. In any case, this should get you
back to the state where you have a 9.2-RELEASE world but your modified
9.1-RELEASE kernel. If you still need a custom kernel then you can
build and install it like so:
# cd /usr/src
# make KERNCONF=MYKERNEL buildkernel
# make KERNCONF=MYKERNEL installkernel
and reboot. Otherwise, I'm not sure exactly how you'ld revert from a
custom kernel to the standard generic kernel you'ld normally get via
freebsd-update. What I'd try is moving aside my customized kernel and
re-running freebsd-update:
# cd /boot
# mv kernel kernel-MYKERNEL
# freebsd-update install
If that creates a new /boot/kernel and populates with a new kernel and
many loadable modules then you're golden. If not, move your saved
kernel back into place (mv kernel-MYKERNEL kernel) and ask here again.
The 'no such file or directory' error for /usr/local/etc/libmap.d thing
is a false problem: /usr/local/etc/libmap.d is an optional directory --
all you are seeing is install(1) trying to open it and discovering that
it doesn't exist.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk
signature.asc
Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
On Sun, 06 Oct 2013 08:08:42 +0100, Matthew Seaman wrote: > On 05/10/2013 21:41, Polytropon wrote: > > On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: > >> I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just > >> be able to do a > >> > >> cd /usr/src > >> make buildworld > >> make installworld > >> reboot > >> > >> and I'll be running up on the 9.2 kernel and then I'll be all set? > > > > No. You should follow the procedure mentioned in the > > comment header of /usr/src/Makefile. From my (old) > > b-STABLE system: > > > > # 1. `cd /usr/src' (or to the directory containing your source > > tree). > > # 2. `make buildworld' > > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is > > GENERIC). > > # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is > > GENERIC). > > # [steps 3. & 4. can be combined by using the "kernel" target] > > # 5. `reboot'(in single user mode: boot -s from the loader > > prompt). > > # 6. `mergemaster -p' > > # 7. `make installworld' > > # 8. `make delete-old' > > # 9. `mergemaster'(you may wish to use -i, along with -U or > > -F). > > # 10. `reboot' > > # 11. `make delete-old-libs' (in case no 3rd party program uses them > > anymore) > > > > Pick what you need to do. When kernel and world sources are > > in sync, a new kernel can always be installed in multi-user > > mode. To install world, you should drop to single-user mode > > to avoid interferences with a full-featured system running > > in the "background". This procedure (or parts of it) will > > also work when you have been using freebsd-update to modify > > your kernel, world, and sources. > > > > Errrmm... The OP is maintaining his system using freebsd-update -- just > building and installing a replacement kernel from the source tree > installed via freebsd-update is in fact perfectly OK and a supported way > to manage a FreeBSD system. That is true. But if I understand the question (as quoted above) correctly, installing world from source has been involved, that's why my suggestion of following the instructions (or a subset of them, as it applies). > While you are quoting the official instructions from /usr/src/UPDATING > here (so they are completely correct in that sense) these are the > instructions to do something rather different to what the OP intended. I've copied the the instructions from the comment header of /usr/src/Makefile (at least on my outdated system at home they're there). Of course if the _only_ problem of the initial question is to install a custom kernel, with an otherwise updated system using freebsd-update (with world, kernel and sources in sync), just installing a custom kernel from within multi-user mode is fully supported by the system. This implies that only a small subset of the quoted instructions would apply here (steps 1 and 3 - 5), after freebsd-update has been finished successfully. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 21:41, Polytropon wrote: > On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: >> I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just >> be able to do a >> >> cd /usr/src >> make buildworld >> make installworld >> reboot >> >> and I'll be running up on the 9.2 kernel and then I'll be all set? > > No. You should follow the procedure mentioned in the > comment header of /usr/src/Makefile. From my (old) > b-STABLE system: > > # 1. `cd /usr/src' (or to the directory containing your source tree). > # 2. `make buildworld' > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > # [steps 3. & 4. can be combined by using the "kernel" target] > # 5. `reboot'(in single user mode: boot -s from the loader prompt). > # 6. `mergemaster -p' > # 7. `make installworld' > # 8. `make delete-old' > # 9. `mergemaster'(you may wish to use -i, along with -U or -F). > # 10. `reboot' > # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) > > Pick what you need to do. When kernel and world sources are > in sync, a new kernel can always be installed in multi-user > mode. To install world, you should drop to single-user mode > to avoid interferences with a full-featured system running > in the "background". This procedure (or parts of it) will > also work when you have been using freebsd-update to modify > your kernel, world, and sources. > Errrmm... The OP is maintaining his system using freebsd-update -- just building and installing a replacement kernel from the source tree installed via freebsd-update is in fact perfectly OK and a supported way to manage a FreeBSD system. While you are quoting the official instructions from /usr/src/UPDATING here (so they are completely correct in that sense) these are the instructions to do something rather different to what the OP intended. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
I figured I'd walk through those steps from start to finish and just
correct my main problem and any other little glitches I might have.
I'm on step 6 and when I run mergemaster -p, I get the following error.
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
/usr/bin/install: Undefined symbol "gid_from_group"
*** FATAL ERROR: Cannot copy files to the temproot environment
I found this thread on the Freebsd forums
http://forums.freebsd.org/showthread.php?t=41779 with the same error and if
I do the same diagnostic steps of
truss install -d -g wheel ~/testdirectory
I find an error of
lstat("/usr/local/etc/libmap.d",0x7fffb990) ERR#2 'No such file or
directory'
Any suggestions? Thank you for the help thus far.
Eric
On Sat, Oct 5, 2013 at 4:41 PM, Polytropon wrote:
> On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote:
> > I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should
> just
> > be able to do a
> >
> > cd /usr/src
> > make buildworld
> > make installworld
> > reboot
> >
> > and I'll be running up on the 9.2 kernel and then I'll be all set?
>
> No. You should follow the procedure mentioned in the
> comment header of /usr/src/Makefile. From my (old)
> b-STABLE system:
>
> # 1. `cd /usr/src' (or to the directory containing your source
> tree).
> # 2. `make buildworld'
> # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is
> GENERIC).
> # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is
> GENERIC).
> # [steps 3. & 4. can be combined by using the "kernel" target]
> # 5. `reboot'(in single user mode: boot -s from the loader
> prompt).
> # 6. `mergemaster -p'
> # 7. `make installworld'
> # 8. `make delete-old'
> # 9. `mergemaster'(you may wish to use -i, along with -U or
> -F).
> # 10. `reboot'
> # 11. `make delete-old-libs' (in case no 3rd party program uses them
> anymore)
>
> Pick what you need to do. When kernel and world sources are
> in sync, a new kernel can always be installed in multi-user
> mode. To install world, you should drop to single-user mode
> to avoid interferences with a full-featured system running
> in the "background". This procedure (or parts of it) will
> also work when you have been using freebsd-update to modify
> your kernel, world, and sources.
>
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem completing a 9.1 release to 9.2 release upgrade
On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: > I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just > be able to do a > > cd /usr/src > make buildworld > make installworld > reboot > > and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. & 4. can be combined by using the "kernel" target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the "background". This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem completing a 9.1 release to 9.2 release upgrade
Ah, yes, when this particular box was a 9.0-release, I had compiled a custom kernel to enable ipsec. When I check the strings, it's a 9.1 release kernel. I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? Thanks for the help. Eric On Sat, Oct 5, 2013 at 3:34 PM, Matthew Seaman wrote: > On 05/10/2013 20:11, Eric Feldhusen wrote: > > I have a server that was/is running 9.1 release that I tried to upgrade > to > > 9.2 release. I missed the step of updating to the latest 9.1 patches by > > doing > > > > freebsd-update fetch > > freebsd-update install > > > > I went right to > > > > freebsd-update upgrade -r 9.2-RELEASE > > freebsd-update install > > > > rebooot > > > > freebsd-update install > > > > reboot again > > > > But my system still comes up as 9.1 release. > > > > Any suggestions on the steps to fix my goof? > > Did you replace the generic kernel from 9.1-RELEASE with something you > compiled yourself? If so, you may well have caused freebsd-update to > ignore any modifications to the kernel. > > You can fix that by re-compiling a kernel using the 9.2-RELEASE sources > and basically the same kernel configuration as for 9.1 (you will need to > check for 9.2 related differences to the configuration, but these are > likely to be pretty minor or not needed at all.) > > If you aren't using a customized kernel, then has the kernel in the > standard location on your system actually been updated? You can tell if > it's a 9.2 kernel by running strings(1) against the kernel binary, like so: > ># strings /boot/kernel/kernel | grep RELEASE > > If that's clearly a 9.2 kernel, then are you actually booting up from a > different kernel somewhere else on your system? First of all, are > there any other copies of FreeBSD kernels around anywhere -- on > memsticks, or on split mirrors perhaps? You may need to fiddle with the > bios settings or interrupt the boot sequence and type things directly at > the loader if so. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 20:11, Eric Feldhusen wrote: > I have a server that was/is running 9.1 release that I tried to upgrade to > 9.2 release. I missed the step of updating to the latest 9.1 patches by > doing > > freebsd-update fetch > freebsd-update install > > I went right to > > freebsd-update upgrade -r 9.2-RELEASE > freebsd-update install > > rebooot > > freebsd-update install > > reboot again > > But my system still comes up as 9.1 release. > > Any suggestions on the steps to fix my goof? Did you replace the generic kernel from 9.1-RELEASE with something you compiled yourself? If so, you may well have caused freebsd-update to ignore any modifications to the kernel. You can fix that by re-compiling a kernel using the 9.2-RELEASE sources and basically the same kernel configuration as for 9.1 (you will need to check for 9.2 related differences to the configuration, but these are likely to be pretty minor or not needed at all.) If you aren't using a customized kernel, then has the kernel in the standard location on your system actually been updated? You can tell if it's a 9.2 kernel by running strings(1) against the kernel binary, like so: # strings /boot/kernel/kernel | grep RELEASE If that's clearly a 9.2 kernel, then are you actually booting up from a different kernel somewhere else on your system? First of all, are there any other copies of FreeBSD kernels around anywhere -- on memsticks, or on split mirrors perhaps? You may need to fiddle with the bios settings or interrupt the boot sequence and type things directly at the loader if so. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Problem completing a 9.1 release to 9.2 release upgrade
I have a server that was/is running 9.1 release that I tried to upgrade to 9.2 release. I missed the step of updating to the latest 9.1 patches by doing freebsd-update fetch freebsd-update install I went right to freebsd-update upgrade -r 9.2-RELEASE freebsd-update install rebooot freebsd-update install reboot again But my system still comes up as 9.1 release. Any suggestions on the steps to fix my goof? Eric Feldhusen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Failure to build FreeBSD 9.2
2013/10/5 Polytropon > On Sat, 5 Oct 2013 09:40:31 +0300, Juris Kaminskis wrote: > > i recompiled my kernel with more verbose output and I see following > errors > > before it stops: > > > > procfs registered > > panic: No usable event timer found! > > cpuid=0 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > panic() at panic+0x1d8/frame > > initclocks() > > mi_startup() > > btext() ... > > KDB: enter: panic > > [thread pid 0 tid 10] > > Stopped at kdb_enter+0x3b: moxq > > > > can someone help me to explain what this means and what to do next? > > In many cases, this indicates a problem introduced by the > computer's BIOS settings or ACPI. Make sure ACPI is enabled > and the BIOS is configured properly (e. g. no timer settings > modified or features deactivated). You could also check if > a newer version of the BIOS is available. > > Update to new BIOS did the trick! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Failure to build FreeBSD 9.2
On Sat, 5 Oct 2013 09:40:31 +0300, Juris Kaminskis wrote: > i recompiled my kernel with more verbose output and I see following errors > before it stops: > > procfs registered > panic: No usable event timer found! > cpuid=0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x1d8/frame > initclocks() > mi_startup() > btext() ... > KDB: enter: panic > [thread pid 0 tid 10] > Stopped at kdb_enter+0x3b: moxq > > can someone help me to explain what this means and what to do next? In many cases, this indicates a problem introduced by the computer's BIOS settings or ACPI. Make sure ACPI is enabled and the BIOS is configured properly (e. g. no timer settings modified or features deactivated). You could also check if a newer version of the BIOS is available. In addition, there's the suggestion to add the line debug.acpi.disabled="hostres" to /boot/loader.conf and reboot. Source: http://www.freebsd.org/releases/9.0R/errata.html -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Failure to build FreeBSD 9.2
i recompiled my kernel with more verbose output and I see following errors before it stops: procfs registered panic: No usable event timer found! cpuid=0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x1d8/frame initclocks() mi_startup() btext() ... KDB: enter: panic [thread pid 0 tid 10] Stopped at kdb_enter+0x3b: moxq can someone help me to explain what this means and what to do next? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 21:49:18 -0700, Doug Hardie wrote: > > On 4 October 2013, at 20:03, Polytropon wrote: > > > On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: > >> > >> On 4 October 2013, at 19:08, Polytropon wrote: > >> > >>> On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: > >>>> The exact sequence was: > >>>> > >>>> Step 1: freebsd-update from 9.1 to 9.2 > >>> > >>> Have you verified in /etc/freebsd-update.conf that "src" > >>> is definitely part of what should be updated? > >> > >> System is not bootable - can't verify anything… > > > > Does the system (or better, its "enclosure", software-wise) > > allow booting a rescue system or an emergency media, such > > as a FreeBSD v9 live system? > > Yes - but there is no one there who can successfully be told > how to run it. Not even inserting a USB stick (with the FreeBSD memstick data) or a CD? > We have serious communications issues - they want to use back > slashes and have no idea what a slash is. Maybe that is the result of many years of "administration" on "Windows" PCs. :-) > Even if you tell them which key to use, they know better and > use a back slash cause thats what Windoze uses. Uh... "knowing better" would disqualify them as maintainers of a server installation. The inability to learn (or even to read and follow instructions) is a dangerous thing. > The disk should be in the mail to me now. I will be able to > work with it when it arrives. Okay, that's also a possible alternative. To be honest, that's the first time I hear about this procedure. But doable. > > The file /etc/freebsd-update.conf should contain the line > > > > Components src world kernel > > > > if you want to make sure the source is properly updated, > > along with the world and kernel (GENERIC). > > As indicated before, I don't think all the source got updated. > The kernel showed 9.2 after recompilation. However UPDATING > was not updated. Thats as much as I could check before. I assume that this could be possible by inconsistently updated sources. It would be a good start to remove /usr/src and download the sources of the correct version via SVN _or_ freebsd-update again. Before the next installation attempt, /usr/obj should be removed as well, just to be sure. > >>>> Step 5: reboot > >>> > >>> Attention: Into single-user mode. > >> > >> Not possible since the system is located over 100 miles away. > >> Everything has to be done via remote console. > > > > Does this mean "SSH only" or do you have a _real_ console > > transmission by which you can access the system _prior_ to > > the OS providing the SSH access? I'm mentioning this because > > the traditional approach requires (few) steps done in the > > single-user mode where no SSH connectivity is provided in > > the "normal" way… > > I have a telnet box that has serial connections to the console > ports. That approach has been used without any issues since > FreeBSD 2.5. I do disable all ports during the process via an > reduced rc.conf file. A serial console should also work, but even though I've been using serial consoles (and _real_ serial terminals), one thing I'm not sure about: Is it possible to interrupt (!) the boot process at an early stage to get to the loader prompt and boot into single user mode from there? Ok boot -s If not, do you have the "beastie menu" (or whatever it is called today) enabled to go to SUM to perform the "make installworld" step? Anyway, if you can install everything is required with the disk at home, and then send it back to that "datacenter" (according to your characterization, the quotes are deserved), that should solve the problems and make sure everything works as intended. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 4 October 2013, at 20:03, Polytropon wrote: > On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: >> >> On 4 October 2013, at 19:08, Polytropon wrote: >> >>> On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: >>>> The exact sequence was: >>>> >>>> Step 1: freebsd-update from 9.1 to 9.2 >>> >>> Have you verified in /etc/freebsd-update.conf that "src" >>> is definitely part of what should be updated? >> >> System is not bootable - can't verify anything… > > Does the system (or better, its "enclosure", software-wise) > allow booting a rescue system or an emergency media, such > as a FreeBSD v9 live system? Yes - but there is no one there who can successfully be told how to run it. We have serious communications issues - they want to use back slashes and have no idea what a slash is. Even if you tell them which key to use, they know better and use a back slash cause thats what Windoze uses. The disk should be in the mail to me now. I will be able to work with it when it arrives. > > The file /etc/freebsd-update.conf should contain the line > > Components src world kernel > > if you want to make sure the source is properly updated, > along with the world and kernel (GENERIC). As indicated before, I don't think all the source got updated. The kernel showed 9.2 after recompilation. However UPDATING was not updated. Thats as much as I could check before. > > > >>>> Step 5: reboot >>> >>> Attention: Into single-user mode. >> >> Not possible since the system is located over 100 miles away. >> Everything has to be done via remote console. > > Does this mean "SSH only" or do you have a _real_ console > transmission by which you can access the system _prior_ to > the OS providing the SSH access? I'm mentioning this because > the traditional approach requires (few) steps done in the > single-user mode where no SSH connectivity is provided in > the "normal" way… I have a telnet box that has serial connections to the console ports. That approach has been used without any issues since FreeBSD 2.5. I do disable all ports during the process via an reduced rc.conf file. > > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 19:42:15 -0700, Doug Hardie wrote: > > On 4 October 2013, at 19:08, Polytropon wrote: > > > On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: > >> The exact sequence was: > >> > >> Step 1: freebsd-update from 9.1 to 9.2 > > > > Have you verified in /etc/freebsd-update.conf that "src" > > is definitely part of what should be updated? > > System is not bootable - can't verify anything… Does the system (or better, its "enclosure", software-wise) allow booting a rescue system or an emergency media, such as a FreeBSD v9 live system? The file /etc/freebsd-update.conf should contain the line Components src world kernel if you want to make sure the source is properly updated, along with the world and kernel (GENERIC). > >> Step 5: reboot > > > > Attention: Into single-user mode. > > Not possible since the system is located over 100 miles away. > Everything has to be done via remote console. Does this mean "SSH only" or do you have a _real_ console transmission by which you can access the system _prior_ to the OS providing the SSH access? I'm mentioning this because the traditional approach requires (few) steps done in the single-user mode where no SSH connectivity is provided in the "normal" way... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 4 October 2013, at 19:08, Polytropon wrote: > On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: >> The exact sequence was: >> >> Step 1: freebsd-update from 9.1 to 9.2 > > Have you verified in /etc/freebsd-update.conf that "src" > is definitely part of what should be updated? System is not bootable - can't verify anything… > > > >> Step 2: make buildworld >> Step 3: make build_kernel KERNCONF=LAFN >> Step 4: make install_kernel KERNCONF=LAFN > > I assume the correct targets "buildkernel" and "installkernel" > have been used. ;-) > Yes > > >> Step 5: reboot > > Attention: Into single-user mode. Not possible since the system is located over 100 miles away. Everything has to be done via remote console. > > > >> Step 6: mergemaster -p >> Step 7: make installworld >> Step 8: mergemaster -i >> Step 9: make delete-old >> Step 10: reboot > > Into multi-user mode again. > > > >> oops, something went wrong.. >> >> After step 5, uname -a still showed 9.2 but now it listed the >> kernel I built rather than generic. > > Again, verify your configuration. Compare your steps with the > comment header of /usr/src/Makefile which illustrates the > exact procedure; from a (dated) 8-STABLE installation: > > 1. `cd /usr/src' (or to the directory containing your source tree). > 2. `make buildworld' > 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > [steps 3. & 4. can be combined by using the "kernel" target] > 5. `reboot'(in single user mode: boot -s from the loader prompt). > 6. `mergemaster -p' > 7. `make installworld' > 8. `make delete-old' > 9. `mergemaster'(you may wish to use -i, along with -U or -F). > 10. `reboot' > 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On Fri, 4 Oct 2013 18:58:52 -0700, Doug Hardie wrote: > The exact sequence was: > > Step 1: freebsd-update from 9.1 to 9.2 Have you verified in /etc/freebsd-update.conf that "src" is definitely part of what should be updated? > Step 2: make buildworld > Step 3: make build_kernel KERNCONF=LAFN > Step 4: make install_kernel KERNCONF=LAFN I assume the correct targets "buildkernel" and "installkernel" have been used. ;-) > Step 5: reboot Attention: Into single-user mode. > Step 6: mergemaster -p > Step 7: make installworld > Step 8: mergemaster -i > Step 9: make delete-old > Step 10: reboot Into multi-user mode again. > oops, something went wrong.. > > After step 5, uname -a still showed 9.2 but now it listed the > kernel I built rather than generic. Again, verify your configuration. Compare your steps with the comment header of /usr/src/Makefile which illustrates the exact procedure; from a (dated) 8-STABLE installation: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. & 4. can be combined by using the "kernel" target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster'(you may wish to use -i, along with -U or -F). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 4 October 2013, at 09:22, dweimer wrote: > On 10/04/2013 1:36 am, Doug Hardie wrote: >> On 3 October 2013, at 11:48, Doug Hardie wrote: >>> On 3 October 2013, at 10:49, Doug Hardie wrote: >>>> I just did an upgrade using freebsd-update to 9.2. This system uses a >>>> custom kernel so I am rebuilding everything after the update completed. >>>> However, I noticed that /usr/src/UPDATING has not been updated. The first >>>> entry still says: 9.1-RELEASE. Is this correct? >>> Well, it just got worse - The last reboot now fails: I am using a remote >>> console and it shows: >>> --> Press a key on the console to reboot <-- >>> Rebooting... >>> Consoles: internal video/keyboard serial port >>> BIOS drive A: is disk0 >>> BIOS drive C: is disk1 >>> BIOS 639kB/2087360kB available memory >>> FreeBSD/x86 bootstrap loader, Revision 1.1 >>> (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) >>> Can't work out which disk we are booting from. >>> Guessed BIOS device 0x not found by probes, defaulting to disk0: >>> panic: free: guard1 fail @ 0x7f481ed0 from >>> /usr/src/sys/boot/i386/loader/../../common/module.c:1004 >>> --> Press a key on the console to reboot <-- >>> I can enter a string as it doesn't try to reboot again till the return is >>> entered. I've tried b disk1, but it still only tries disk0. The system >>> rebooted fine after the reboot after make kernel. Mergemaster didn't seem >>> to affect anything dealing with boot. Don't know what make delete-old does >>> but the descriptions lead me to not believe it could cause this. This >>> system is on the other side of LA from me so its a major trip timewise. >>> Any ideas how this can be recovered remotely? >> Booting off the live CD didn't find anything obviously wrong. I >> replaced the kernel with the old one and still the same error. I am >> having the drive mailed to me and will work with it here. However, it >> appears a new install is going to be required. The old sysinstall had >> the capability to skip over the formatting of the disk by just >> entering quit. It would then just replace the system components and >> leave everything else alone. I don't see any obvious way to do the >> same thing with bsdinstall. Is there a way to do that. I don't want >> to have to completely rebuild the drive, but just replace the system. >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > Just want to clarify the steps that started this > > if I read everything right: > > Step 1: freebsd-update from 9.1 to 9.2 > Step 2: compile from source ? Was this world, or just the custom kernel?? > Step 3: make delete-old > Step 4: mergemaster > Step 5: reboot > oops, something went wrong.. > > If my suspicions are correct, the source was still 9.1 patch 7, but the > system was running 9.2 from the binary update. This may have caused the make > delete-old to delete things it shouldn't have > > The very first thing I would do is bring the disk up in another system and > make a backup copy of the data. > > I have never tried this process, I am basically just taking the steps I use > for updating a zfs system using boot environments, and applying them in order > to build a new kernel and world to an alternate directory, as a method of > recovering the system. > > The next step I would take is to then mount the file systems in an alternate > location, /mnt for example > > make MAKEOBJDIRPREFIX /mnt/usr/obj > make DESTDIR /mnt > cd /mnt/usr/src > rm -r * .svn > rm -r /usr/obj/* > svn co https://svn0.us-west.freebsd.org/base/releng/9.2 > make buildwolrd > make buildkernel > make installkernel > make installworld > make -DBATCH_DELETE_OLD_FILES delete-old > make -DBATCH_DELETE_OLD_FILES delete-old-libs > mergemaster -Ui /mnt/usr/src -D /mnt > > With some luck the file system will now contain a boot-able FreeBSD install, > that will still have all the settings in place, except it will be the generic > kernel. You should then just be able to build and install the custom kernel, > from the booted system as you normally would. > The exact sequence was: Step 1: freebsd-update from 9.1 to 9.2 Step 2: make buildworld Step 3: make build_kernel KERNCONF=LAFN Step 4: make install_kernel KERNCONF=LAFN Step 5: reboot Step 6: mergemaster -p Step 7: make installworld Step 8: mergemaster -i Step 9: make delete-old Step 10: reboot oops, something went wrong.. After step 5, uname -a still showed 9.2 but now it listed the kernel I built rather than generic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Failure to build FreeBSD 9.2
Hello, I am desperate trying to build FreeBSD 9.2. The same happens with FreeBSD-Current. When I build 9.1 kernel without building world everything is ok. My svn info Path: . Working Copy Root Path: /usr/src URL: http://svn0.eu.freebsd.org/base/release/9.2.0 Repository Root: http://svn0.eu.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 255954 Node Kind: directory Schedule: normal Last Changed Author: gjb Last Changed Rev: 255898 Last Changed Date: 2013-09-26 21:28:11 +0300 (Thu, 26 Sep 2013) When I do standard process: make buildworld make buildkernel make installkernel reboot my kernel hangs up and does not respond. I have tried a lot of things but nothing works. my new kernel hangs right after: pci1: on pcib1 my uname -a FreeBSD station 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 and my dmesg output: Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2211.11-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40fb2 Family = f Model = 4b Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f real memory = 2147483648 (2048 MB) avail memory = 2045505536 (1950 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) unknown: memory range not supported unknown: memory range not supported unknown: memory range not supported acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ff0 (3) failed cpu0: on acpi0 cpu1: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 3.0 on pci0 pcib1: failed to allocate initial memory window: 0xffb0-0xffbf pci1: on pcib1 vgapci0: port 0x9800-0x98ff mem 0xc000-0xcfff irq 19 at device 0.0 on pci1 hdac0: irq 16 at device 0.1 on pci1 pcib2: at device 6.0 on pci0 pci2: on pcib2 re0: port 0xa800-0xa8ff mem 0xffcff000-0xffcf irq 18 at device 0.0 on pci2 re0: Using 1 MSI message re0: Chip rev. 0x3800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:19:db:f6:72:d0 ahci0: port 0xe800-0xe807,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd80f mem 0xffeffc00-0xffef irq 22 at device 18.0 on pci0 ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ohci0: mem 0xffefe000-0xffefefff irq 16 at device 19.0 on pci0 usbus0 on ohci0 ohci1: mem 0xffefd000-0xffefdfff irq 17 at device 19.1 on pci0 usbus1 on ohci1 ohci2: mem 0xffefc000-0xffefcfff irq 18 at device 19.2 on pci0 usbus2 on ohci2 ohci3: mem 0xffefb000-0xffefbfff irq 17 at device 19.3 on pci0 usbus3 on ohci3 ohci4: mem 0xffefa000-0xffefafff irq 18 at device 19.4 on pci0 usbus4 on ohci4 ehci0: mem 0xffeff800-0xffeff8ff irq 19 at device 19.5 on pci0 ehci0: AMD SB600/700 quirk applied usbus5: EHCI version 1.0 usbus5 on ehci0 pci0: at device 20.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: at channel 0 on atapci0 hdac1: mem 0xffef4000-0xffef7fff irq 16 at device 20.2 on pci0 isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 fwohci0: port 0xbc00-0xbc7f mem 0xffdff800-0xffdf irq 20 at device 2.0 on pci3 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:dc:10:00:01:2d:cc:8b f
Re: 9.1 - 9.2 upgrade
On 10/04/2013 1:36 am, Doug Hardie wrote: On 3 October 2013, at 11:48, Doug Hardie wrote: On 3 October 2013, at 10:49, Doug Hardie wrote: I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: --> Press a key on the console to reboot <-- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 --> Press a key on the console to reboot <-- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? Booting off the live CD didn't find anything obviously wrong. I replaced the kernel with the old one and still the same error. I am having the drive mailed to me and will work with it here. However, it appears a new install is going to be required. The old sysinstall had the capability to skip over the formatting of the disk by just entering quit. It would then just replace the system components and leave everything else alone. I don't see any obvious way to do the same thing with bsdinstall. Is there a way to do that. I don't want to have to completely rebuild the drive, but just replace the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Just want to clarify the steps that started this if I read everything right: Step 1: freebsd-update from 9.1 to 9.2 Step 2: compile from source ? Was this world, or just the custom kernel?? Step 3: make delete-old Step 4: mergemaster Step 5: reboot oops, something went wrong.. If my suspicions are correct, the source was still 9.1 patch 7, but the system was running 9.2 from the binary update. This may have caused the make delete-old to delete things it shouldn't have The very first thing I would do is bring the disk up in another system and make a backup copy of the data. I have never tried this process, I am basically just taking the steps I use for updating a zfs system using boot environments, and applying them in order to build a new kernel and world to an alternate directory, as a method of recovering the system. The next step I would take is to then mount the file systems in an alternate location, /mnt for example make MAKEOBJDIRPREFIX /mnt/usr/obj make DESTDIR /mnt cd /mnt/usr/src rm -r * .svn rm -r /usr/obj/* svn co https://svn0.us-west.freebsd.org/base/releng/9.2 make buildwolrd make buildkernel make installkernel make installworld make -DBATCH_DELETE_OLD_FILES delete-old make -DBATCH_DELETE_OLD_FILES delete-old-libs mergemaster -Ui /mnt/usr/src -D /mnt With some luck the file system will now contain a boot-able FreeBSD install, that will still have all the settings in place, except it will be the generic kernel. You should then just be able to build and install the custom kernel, from the booted system as you normally would. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 3 October 2013, at 11:48, Doug Hardie wrote: > > On 3 October 2013, at 10:49, Doug Hardie wrote: > >> I just did an upgrade using freebsd-update to 9.2. This system uses a >> custom kernel so I am rebuilding everything after the update completed. >> However, I noticed that /usr/src/UPDATING has not been updated. The first >> entry still says: 9.1-RELEASE. Is this correct? > > Well, it just got worse - The last reboot now fails: I am using a remote > console and it shows: > > --> Press a key on the console to reboot <-- > Rebooting... > Consoles: internal video/keyboard serial port > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS 639kB/2087360kB available memory > > FreeBSD/x86 bootstrap loader, Revision 1.1 > (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) > Can't work out which disk we are booting from. > Guessed BIOS device 0x not found by probes, defaulting to disk0: > > panic: free: guard1 fail @ 0x7f481ed0 from > /usr/src/sys/boot/i386/loader/../../common/module.c:1004 > --> Press a key on the console to reboot <-- > > > I can enter a string as it doesn't try to reboot again till the return is > entered. I've tried b disk1, but it still only tries disk0. The system > rebooted fine after the reboot after make kernel. Mergemaster didn't seem to > affect anything dealing with boot. Don't know what make delete-old does but > the descriptions lead me to not believe it could cause this. This system is > on the other side of LA from me so its a major trip timewise. Any ideas how > this can be recovered remotely? Booting off the live CD didn't find anything obviously wrong. I replaced the kernel with the old one and still the same error. I am having the drive mailed to me and will work with it here. However, it appears a new install is going to be required. The old sysinstall had the capability to skip over the formatting of the disk by just entering quit. It would then just replace the system components and leave everything else alone. I don't see any obvious way to do the same thing with bsdinstall. Is there a way to do that. I don't want to have to completely rebuild the drive, but just replace the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 3 October 2013, at 11:58, dweimer wrote: > On 10/03/2013 1:48 pm, Doug Hardie wrote: >> On 3 October 2013, at 10:49, Doug Hardie wrote: >>> I just did an upgrade using freebsd-update to 9.2. This system uses a >>> custom kernel so I am rebuilding everything after the update completed. >>> However, I noticed that /usr/src/UPDATING has not been updated. The first >>> entry still says: 9.1-RELEASE. Is this correct? >> Well, it just got worse - The last reboot now fails: I am using a >> remote console and it shows: >> --> Press a key on the console to reboot <-- >> Rebooting... >> Consoles: internal video/keyboard serial port >> BIOS drive A: is disk0 >> BIOS drive C: is disk1 >> BIOS 639kB/2087360kB available memory >> FreeBSD/x86 bootstrap loader, Revision 1.1 >> (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) >> Can't work out which disk we are booting from. >> Guessed BIOS device 0x not found by probes, defaulting to disk0: >> panic: free: guard1 fail @ 0x7f481ed0 from >> /usr/src/sys/boot/i386/loader/../../common/module.c:1004 >> --> Press a key on the console to reboot <-- >> I can enter a string as it doesn't try to reboot again till the return >> is entered. I've tried b disk1, but it still only tries disk0. The >> system rebooted fine after the reboot after make kernel. Mergemaster >> didn't seem to affect anything dealing with boot. Don't know what >> make delete-old does but the descriptions lead me to not believe it >> could cause this. This system is on the other side of LA from me so >> its a major trip timewise. Any ideas how this can be recovered >> remotely? >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > I wonder if your source update didn't correctly download, mine starts with: > > Updating Information for FreeBSD current users > ...[snip]... > Items affecting the ports and packages system can be found in > /usr/ports/UPDATING. Please read that file before running portupgrade. > > 20130705: >hastctl(8)'s `status' command output changed to terse one-liner format. >Scripts using this should switch to `list' command or be rewritten. > > 20130618: >Fix a bug that allowed a tracing process (e.g. gdb) to write > ...[snip]... > 20121218: >With the addition of auditdistd(8), a new auditdistd user is now >depended on during installworld. "mergemaster -p" can be used to add >the user prior to installworld, as documented in the handbook. > > 20121205: >9.1-RELEASE. > ...[snip]... > > I haven't a clue how to fix your non booting system short of booting off a > FreeBSD disc, going to live CD, mounting the filesystems in a temp location > and doing a buildworld/kernel over again with correct source tree. I have been using freebsd-update for quite awhile now and this is the first time it has failed. However, I am not convinced the kernel is bad. It never gets to the point of trying to load the kernel. Something has failed in the bootstrap process itself and I have not figured out what is the right thing to enter at that prompt. Being on-site is not a viable alternative… ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 10/03/2013 1:48 pm, Doug Hardie wrote: On 3 October 2013, at 10:49, Doug Hardie wrote: I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: --> Press a key on the console to reboot <-- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 --> Press a key on the console to reboot <-- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I wonder if your source update didn't correctly download, mine starts with: Updating Information for FreeBSD current users ...[snip]... Items affecting the ports and packages system can be found in /usr/ports/UPDATING. Please read that file before running portupgrade. 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. 20130618: Fix a bug that allowed a tracing process (e.g. gdb) to write ...[snip]... 20121218: With the addition of auditdistd(8), a new auditdistd user is now depended on during installworld. "mergemaster -p" can be used to add the user prior to installworld, as documented in the handbook. 20121205: 9.1-RELEASE. ...[snip]... I haven't a clue how to fix your non booting system short of booting off a FreeBSD disc, going to live CD, mounting the filesystems in a temp location and doing a buildworld/kernel over again with correct source tree. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade
On 3 October 2013, at 10:49, Doug Hardie wrote: > I just did an upgrade using freebsd-update to 9.2. This system uses a custom > kernel so I am rebuilding everything after the update completed. However, I > noticed that /usr/src/UPDATING has not been updated. The first entry still > says: 9.1-RELEASE. Is this correct? Well, it just got worse - The last reboot now fails: I am using a remote console and it shows: --> Press a key on the console to reboot <-- Rebooting... Consoles: internal video/keyboard serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/2087360kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (d...@zool.lafn.org, Thu Oct 3 04:23:13 PDT 2013) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x7f481ed0 from /usr/src/sys/boot/i386/loader/../../common/module.c:1004 --> Press a key on the console to reboot <-- I can enter a string as it doesn't try to reboot again till the return is entered. I've tried b disk1, but it still only tries disk0. The system rebooted fine after the reboot after make kernel. Mergemaster didn't seem to affect anything dealing with boot. Don't know what make delete-old does but the descriptions lead me to not believe it could cause this. This system is on the other side of LA from me so its a major trip timewise. Any ideas how this can be recovered remotely? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
9.1 - 9.2 upgrade
I just did an upgrade using freebsd-update to 9.2. This system uses a custom kernel so I am rebuilding everything after the update completed. However, I noticed that /usr/src/UPDATING has not been updated. The first entry still says: 9.1-RELEASE. Is this correct? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.1 - 9.2 upgrade, clang question
03.10.2013 17:36, dweimer wrote: When upgrading from 9.1 to 9.2 using source, is there any benefit to rebuilding twice, due to the clang version change? So that the second buildworld/kernel is done from the updated clang 3.3, instead of the clang 3.1 that was in FreeBSD 9.1? During the buildworld first new compiler is built and then this new compiler is used to build everything else. There may be other reasons to double build though... Maybe after cleaning system with `make delete-old`/`make delete-old-libs`? -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
9.1 - 9.2 upgrade, clang question
When upgrading from 9.1 to 9.2 using source, is there any benefit to rebuilding twice, due to the clang version change? So that the second buildworld/kernel is done from the updated clang 3.3, instead of the clang 3.1 that was in FreeBSD 9.1? -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
On 02/10/2013 21:07, Winston wrote:
> Summary:
>
> Where is the (U.S.) pkg(ng) repository for amd64 9.2-RELEASE (i.e.,
> what's the right URI for PACKAGESITE in pkg.conf)?
>
>
> Things I tried that didn't work:
>
> * pkg_add -r pkg didn't create /usr/local/etc/pkg.conf
>
> * pkg.conf.sample suggests "http://pkg.freebsd.org/${ABI}/latest";,
> but the host name pkg.freebsd.org does not DNS resolve for me.
>
> * URLs using pkgbeta.FreeBSD.org didn't work, and
> http://pkgbeta.FreeBSD.org/ itself says
> "Currently this site only contains pkg bootstrap files!"
Yeah -- and the bootstrap pkg on pkgbeta is severely out of date and has
some problems with the up to date DB schema.
Use PACKAGESITE=http://pkg-test.freebsd.org/pkg-test-${ABI}/latest
That's the kit that will form the official FreeBSD package repository;
it just lacks the crypto bits for signing the packages, which is why
it's calling itself 'pkg-test'
Oh -- there isn't an A record in the DNS for pkg-test.freebsd.org --
look up a SRV record for _http._tcp.pkg-test.freebsd.org instead.
(Yes, this is counter to RFC 2616.
https://github.com/freebsd/pkg/issues/550 There are moves afoot to
change to a new set of URL schemes: pkg+http://, pkg+https://,
pkg+ssh:// etc. but these are still under development)
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Where is pkg repository for 9.2-RELEASE (amd64)?
Summary:
Where is the (U.S.) pkg(ng) repository for amd64 9.2-RELEASE (i.e.,
what's the right URI for PACKAGESITE in pkg.conf)?
Things I tried that didn't work:
* pkg_add -r pkg didn't create /usr/local/etc/pkg.conf
* pkg.conf.sample suggests "http://pkg.freebsd.org/${ABI}/latest";,
but the host name pkg.freebsd.org does not DNS resolve for me.
* URLs using pkgbeta.FreeBSD.org didn't work, and
http://pkgbeta.FreeBSD.org/ itself says
"Currently this site only contains pkg bootstrap files!"
Thanks!
-WBE
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2-RELEASE stability?
On Tue, Oct 1, 2013, at 18:54, ot...@ahhyes.net wrote: > > * I run powerdns recursor for resolution of domain names. Despite > having the recursor as being one of the first things > in rc.conf to start (certainly before ntpdate), ntpdate decides to run > before the recursor has started. This causes the lookup of the ntp > server > hostname to fail (using -b ip.ip.ip.ip as a flag to ntpdate rather than > a host is a way to work around the issue). > Create in rc script in /usr/local/etc/rc.d that does nothing but set the REQUIRE and BEFORE fields. You can use that to re-order the startup scripts. Use the `service` command to see the new startup order -- there's a flag that will give you that output. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2-RELEASE stability?
On Mon, Sep 30, 2013, at 14:01, Brett Glass wrote: How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. very frustrated at the moment... I've had some very strange issues crop up since upgrading from 9.1-RELEASE to 9.2-RELEASE. I'm using FreeBSD on a Xen HVM instance. My previous install was a system with a custom kernel (includes Xen HVM options) (entire base and kernel compiled with Clang 3.1 (base clang)). The system worked flawlessly. A "rinse and repeat" upgrade (build from source) with 9.2 is giving me some very strange issues: * Randomly when I start the VM, there is no network connectivity. I first noticed DHCP was timing out. The link appeared to be up on the xn0 interface but no data flow at all. Attempted manual interface configuration. Zilch, couldn't even get a response from the default gateway when pinging (both ipv4 and ipv6). A reboot of the machine and suddenly network connectivity is restored. Subsequently with no predictability, another reboot = no network again. No errors in dmesg or /var/log/messages. * /usr/ports/net/net-im/jabber (which appears not to have changed versions between my system upgrade) randomly aborts with signal 10 (bus error). * Programs that rely on mysql (installed percona 5.5 server) (such as jabber, powerdns etc) spew a bunch of errors saying they are unable to connect to the mysql server via /tmp/mysql.sock, after I log in and look, mysql is running just fine, and the programs that were complaining about mysql being unreachable are all operating correctly... (i have mysql set to start in /etc/rc.d before any of the programs that require it are started) -- never saw these issues in 9.1 * I run powerdns recursor for resolution of domain names. Despite having the recursor as being one of the first things in rc.conf to start (certainly before ntpdate), ntpdate decides to run before the recursor has started. This causes the lookup of the ntp server hostname to fail (using -b ip.ip.ip.ip as a flag to ntpdate rather than a host is a way to work around the issue). This was a clean build. I cleared up old libraries and rebuilt all my installed ports from scratch, I left no kruft lingering on the system to the best of my knowledge. Normally I would put something like the jabber server issue just being bad code that clang is happy to compile.. But the random network issue has the alarm bells ringing. Perhaps there is an issue with clang 3.3 generating faulty code? I havent had any kernel panics or machine freezes. This has to be a first for me with freebsd, I almost never ever have an issue after upgrading from RELEASE to RELEASE. I can probably rebuild it all again with the base gcc compiler, but clang is much much faster than the dinosaur gcc included in base and produces better code. Up in the air with this one. I might go back to 9.1, had none of these issues with it. /my 10 cents worth. BR, Alex. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2-RELEASE stability?
On Tue, Oct 1, 2013 at 3:53 PM, Mark Felder wrote: > On Mon, Sep 30, 2013, at 14:01, Brett Glass wrote: >> How stable are folks finding FreeBSD 9.2-RELEASE to be? For me freebsd-update from 9.1 to 9.2 went smooth on my workstation laptop, the userland works fine :-) I remember myself "Nakatomi BSD 9.2" on the movie (in the reception hall scene), I was su suprised back then to see BSD in this kind of movie :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2-RELEASE stability?
On Mon, Sep 30, 2013, at 14:01, Brett Glass wrote: > How stable are folks finding FreeBSD 9.2-RELEASE to be? The > improvements are welcome, but there have been a few troubling > messages about kernel panics and VM issues on the various mailing > lists. It's never clear until the release drops whether these are > actual problems with the software or hardware defects in individual > systems, so I am eager to hear how the new release is working for > everyone. > I upgraded our two main backup servers which are doing I/O via rsync/rsnapshot and sending ZFS snapshots to the other remote site every 15 minutes. I had several instances where the machines went unresponsive. They didn't panic, and they did respond to CTRL+ALT+DEL on the console, but they lost all networking and wouldn't do anything else. The only change was I enabled zfs prefetch which I previously had disabled for performance reasons. It never caused this issue on 9.1 when I had it enabled, though. The fix definitely was turning off prefetch again which doesn't bother me too much, but I can't use this environment to try to help debug it as it's important production data. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2-RELEASE stability?
Le Mon, 30 Sep 2013 13:01:26 -0600, Brett Glass a écrit : Hello, > How stable are folks finding FreeBSD 9.2-RELEASE to be? The > improvements are welcome, but there have been a few troubling > messages about kernel panics and VM issues on the various mailing > lists. It's never clear until the release drops whether these are > actual problems with the software or hardware defects in individual > systems, so I am eager to hear how the new release is working for > everyone. I've seen two problems if you use poudriere (on ZFS only?) which occur in some loads (ie desktop running gvfsd). One fix is in 9-STABLE and the other one should be mfced soon. May be there will be an errata for 9.2-RELEASE for this ? I think that would be nice because 9.2 is stable as a Windows 3.11 with my load :-) Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
9.2
Hi! I have to used FreeBSD 10.0-ALPHA1 for a while but it was to difficult for me. I run FreeBSD on iMac 11,1 which has: Chipset Model: ATI Radeon HD 4850 Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 512 MB Vendor: ATI (0x1002) Device ID:0x944a Revision ID: 0x ROM Revision: 113-B9110C-425 EFI Driver Version: 01.00.383 Displays: iMac: Display Type: LCD Resolution: 2560 x 1440 Pixel Depth: 32-Bit Color (ARGB) Main Display: Yes Mirror: Off Online: Yes Built-In: Yes Connection Type: DisplayPort On FreeBSD 10.0-ALPHA1 it worked very good but for me 3D is not important. I installed FreeBSD 9.2 one hour ago without problem and run "portsnap fetch extrac"t and I like to install Xorg and KDE. Do I need to have in make.conf "with_new_xorg=yes", please? Does xorg t need hal?. Does anyone has Radeon 4850 GPU type, please and it works? I had problems with sound settings on CURRENT and I note that will be better now. Thank you very much. Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2-RELEASE stability?
On 9/30/2013 15:01, Brett Glass wrote: How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. --Brett Glass Just upgraded a system running in KVM, working like a charm. -- staticsafe O< ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. It is not logical. Please don't CC me! I'm subscribed to whatever list I just posted on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD 9.2-RELEASE stability?
How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with 9.2-RC3
On Wed, 25 Sep 2013 19:46:39 -0300, Joseph Mingrone wrote: > Walter Hurry writes: > >> Running 9.2-RC4 in a VirtualBox VM, I am having a few problems. >> >> FreeBSD freebsd.vm 9.2-RC3 FreeBSD 9.2-RC3 #1 r254965: Wed Aug 28 >> 04:17:40 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM4 amd64 >> >> At this stage I am reluctant to file PRs, as doubtless some of these >> are of my own making. >> >> The first is that I cannot get port devel/xdg-utils to install. The >> error is: >> >> ===> Installing for xdg-utils-1.0.2.20130919 ===> Registering >> installation for xdg-utils-1.0.2.20130919 pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- >> desktop-icon.1): No such file or directory pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- >> desktop-menu.1): No such file or directory pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- email.1): No >> such file or directory pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- >> icon-resource.1): No such file or directory pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- mime.1): No >> such file or directory pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- open.1): No >> such file or directory pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- >> screensaver.1): No such file or directory pkg-static: >> lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- settings.1): >> No such file or directory *** [fake-pkg] Error code 74 >> >> What have I done wrong? It seems fine on 9.1 and 10.0. >> >> > There were some staging problems with ports. Update your ports tree > then upgrade ports-mgmt/pkg and the problem should resolve itself. Thanks! I cleared down the ports tree, did a fresh 'portsnap fetch extract', and all is now well in this regard. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with 9.2-RC3
Walter Hurry writes: > Running 9.2-RC4 in a VirtualBox VM, I am having a few problems. > > FreeBSD freebsd.vm 9.2-RC3 FreeBSD 9.2-RC3 #1 r254965: Wed Aug 28 > 04:17:40 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM4 amd64 > > At this stage I am reluctant to file PRs, as doubtless some of these are > of my own making. > > The first is that I cannot get port devel/xdg-utils to install. The error > is: > > ===> Installing for xdg-utils-1.0.2.20130919 > ===> Registering installation for xdg-utils-1.0.2.20130919 > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > desktop-icon.1): No such file or directory > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > desktop-menu.1): No such file or directory > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > email.1): No such file or directory > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > icon-resource.1): No such file or directory > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > mime.1): No such file or directory > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > open.1): No such file or directory > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > screensaver.1): No such file or directory > pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- > settings.1): No such file or directory > *** [fake-pkg] Error code 74 > > What have I done wrong? It seems fine on 9.1 and 10.0. > There were some staging problems with ports. Update your ports tree then upgrade ports-mgmt/pkg and the problem should resolve itself. Joseph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problems with 9.2-RC3
Running 9.2-RC4 in a VirtualBox VM, I am having a few problems. FreeBSD freebsd.vm 9.2-RC3 FreeBSD 9.2-RC3 #1 r254965: Wed Aug 28 04:17:40 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM4 amd64 At this stage I am reluctant to file PRs, as doubtless some of these are of my own making. The first is that I cannot get port devel/xdg-utils to install. The error is: ===> Installing for xdg-utils-1.0.2.20130919 ===> Registering installation for xdg-utils-1.0.2.20130919 pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-icon.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-menu.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- email.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- icon-resource.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- mime.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- open.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- screensaver.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- settings.1): No such file or directory *** [fake-pkg] Error code 74 What have I done wrong? It seems fine on 9.1 and 10.0. Other issues will follow as separate threads. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: New system - go for 9.1+upgrade - or go for 9.2-RC4?
On Wed, Sep 25, 2013 at 09:16:01AM +0200, Terje Elde wrote: > > Two options: > ... Thanks - helps alot. -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: New system - go for 9.1+upgrade - or go for 9.2-RC4?
On 25. sep. 2013, at 09.00, Ewald Jenisch wrote: o) Will upgrading kernel/system using > svn co svn://svn.freebsd.org/base/stable/9/ /usr/src > bring a 9.2-RC4 installed system up to date once 9.2 final is released? Two options: base/stable/9 - track 9-STABLE base/releng/9.2 - track 9.2-security branch The former is more of a moving target, while the latter is 9.2-RELEASE, but gets security updates. Also, rather than using svn://, I'd use https://, and pick a server from this list: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn-mirrors.html Terje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
New system - go for 9.1+upgrade - or go for 9.2-RC4?
Hi, Since I'm about to set up a new system from scratch I'm thinking whether I should install 9.1 and upgrade it to 9-STABLE or to install 9.2-RC4 right away. To be specific: o) Will upgrading kernel/system using svn co svn://svn.freebsd.org/base/stable/9/ /usr/src bring a 9.2-RC4 installed system up to date once 9.2 final is released? o) Is it possible to install ports using "portsnap fetch extract" and "pkg_add -r..." on a system that was installed using the 9.2-RC4-CDs? Thanks much in advance for your help, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: The logo at boot (Nakatomi Socrates BSD 9.2)
On 05.09.2013 14:59, Patrick Dung wrote:
>
>
>
>
> On Wed, 4 Sep 2013, Lowell Gilbert wrote: >Patrick Dung yahoo.com.hk> writes: >>>Do you know what is this logo means, or the story
> behind it? >>I thought the BSD daemon (logo) has been around for many years
> in the past. >>It's a movie reference ("Die Hard"). >>The Beastie logo is
> still there, in the /boot directory, if you want it. Or the standard "orb",
> by setting it in /boot/loader.conf:
> loader_logo="orb"
>
> Thanks for the info.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
Yes it's a joke for 9.2 RELEASE, some (including me) explained our
disappointment about this but we must keep it for other users for
"surprise" :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: The logo at boot (Nakatomi Socrates BSD 9.2)
On Wed, 4 Sep 2013, Lowell Gilbert wrote: >Patrick Dung writes: >>>Do you know what is this logo means, or the story
behind it? >>I thought the BSD daemon (logo) has been around for many years in
the past. >>It's a movie reference ("Die Hard"). >>The Beastie logo is still
there, in the /boot directory, if you want it. Or the standard "orb", by
setting it in /boot/loader.conf:
loader_logo="orb"
Thanks for the info.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: The logo at boot (Nakatomi Socrates BSD 9.2)
On Wed, 4 Sep 2013, Lowell Gilbert wrote:
Patrick Dung writes:
Do you know what is this logo means, or the story behind it?
I thought the BSD daemon (logo) has been around for many years in the past.
It's a movie reference ("Die Hard").
The Beastie logo is still there, in the /boot directory, if you want it.
Or the standard "orb", by setting it in /boot/loader.conf:
loader_logo="orb"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: The logo at boot (Nakatomi Socrates BSD 9.2)
Oh I see. I have found that the logo was mentioned in news group
org.freebsd.freebsd-chat back in 1997.
From: Lowell Gilbert
To: Patrick Dung
Cc: "freebsd-questions@freebsd.org"
Sent: Wednesday, September 4, 2013 11:45 PM
Subject: Re: The logo at boot (Nakatomi Socrates BSD 9.2)
Patrick Dung writes:
> Do you know what is this logo means, or the story behind it?
> I thought the BSD daemon (logo) has been around for many years in the past.
It's a movie reference ("Die Hard").
The Beastie logo is still there, in the /boot directory, if you want it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: The logo at boot (Nakatomi Socrates BSD 9.2)
Patrick Dung writes:
> Do you know what is this logo means, or the story behind it?
> I thought the BSD daemon (logo) has been around for many years in the past.
It's a movie reference ("Die Hard").
The Beastie logo is still there, in the /boot directory, if you want it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: The logo at boot (Nakatomi Socrates BSD 9.2)
2013/9/4 Patrick Dung > Hello, > > Do you know what is this logo means, or the story behind it? > I thought the BSD daemon (logo) has been around for many years in the past. > > Thanks and regards, > Patrick Dung > http://en.wikipedia.org/wiki/BSD_Daemon -- - (°> Dhénin Jean-Jacques / ) 48, rue de la Justice 78300 Poissy ^^ dhe...@gmail.com - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
The logo at boot (Nakatomi Socrates BSD 9.2)
Hello, Do you know what is this logo means, or the story behind it? I thought the BSD daemon (logo) has been around for many years in the past. Thanks and regards, Patrick Dung ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Shared library not found after upgrade to 9.2-PRERELEASE
I recently upgraded a system to FreeBSD t42.umpquanet.com 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254977: Wed Aug 28 19:58:37 PDT 2013 r...@t42.umpquanet.com:/usr/obj/usr/src/sys/GENERIC i386 I then deleted all the installed ports, and am rebuilding the ones I still use. I've encountered several instances where although a required port is already installed, a dependent port build will claim that the required library isn't found, and attempt a (re-)install of that port. In this example, jbig2dec claims that shared library libpng15.so is not found, although 'ls' says it is in /usr/local/lib, and 'make missing' reports no uninstalled dependencies. What can I do to remedy this, short of setting FORCE_PKG_REGISTER and spending a lot of time rebuilding ports that are already installed? Please Cc: me on replies. Thank you! Jim # cd /usr/ports/graphics/jbig2dec # ls -l /usr/local/lib/libpng15* -rw-r--r-- 1 root wheel 202762 Sep 1 16:10 /usr/local/lib/libpng15.a lrwxr-xr-x 1 root wheel 14 Sep 1 16:10 /usr/local/lib/libpng15.so@ -> libpng15.so.15 -rwxr-xr-x 1 root wheel 175596 Sep 1 16:10 /usr/local/lib/libpng15.so.15* # make clean ===> Cleaning for png-1.5.17 ===> Cleaning for jbig2dec-0.11_1 # make missing # make ===> License GPLv3 accepted by the user ===> Found saved configuration for jbig2dec-0.11 ===> Fetching all distfiles required by jbig2dec-0.11_1 for building ===> Extracting for jbig2dec-0.11_1 => SHA256 Checksum OK for jbig2dec-0.11.tar.xz. ===> Patching for jbig2dec-0.11_1 ===> Applying extra patch /usr/ports/graphics/jbig2dec/files/simpler-test-patch ===> Applying FreeBSD patches for jbig2dec-0.11_1 /usr/bin/sed -i.bak -E 's|SHA1_Final\( *([^,]+), *([^\)]+)\)|SHA1_Final(\2, \1)|' /usr/ports/graphics/jbig2dec/work/jbig2dec-0.11/jbig2dec.c /usr/ports/graphics/jbig2dec/work/jbig2dec-0.11/sha1.c ===> jbig2dec-0.11_1 depends on shared library: libpng15.so - not found ===>Verifying for libpng15.so in /usr/ports/graphics/png ===> Found saved configuration for png-1.5.12 ===> Fetching all distfiles required by png-1.5.17 for building ===> Extracting for png-1.5.17 => SHA256 Checksum OK for libpng-1.5.17.tar.xz. => SHA256 Checksum OK for libpng-1.5.17-apng.patch.gz. /bin/cp /usr/ports/distfiles//libpng-1.5.17-apng.patch.gz /usr/ports/graphics/png/work/libpng-1.5.17/ /usr/bin/gzip -nf -9 -d /usr/ports/graphics/png/work/libpng-1.5.17/libpng-1.5.17-apng.patch.gz ===> Patching for png-1.5.17 ===> Applying extra patch /usr/ports/graphics/png/work/libpng-1.5.17/libpng-1.5.17-apng.patch ===> Applying FreeBSD patches for png-1.5.17 /usr/bin/sed -i.bak -e 's|RELEASE}.0|RELEASE}|' -e 's|LIBDIR}/pkgconfig|LIBDIR}data/pkgconfig|' /usr/ports/graphics/png/work/libpng-1.5.17/CMakeLists.txt ===> png-1.5.17 depends on file: /usr/local/bin/cmake - found ===> Configuring for png-1.5.17 ===> Performing in-source build /bin/mkdir -p /usr/ports/graphics/png/work/libpng-1.5.17 -- The C compiler identification is GNU 4.2.1 ... snip ... [100%] Built target pngvalid /usr/local/bin/cmake -E cmake_progress_start /usr/ports/graphics/png/work/libpng-1.5.17/CMakeFiles 0 Running tests... /usr/local/bin/ctest --force-new-ctest-process Test project /usr/ports/graphics/png/work/libpng-1.5.17 Start 1: pngtest 1/2 Test #1: pngtest .. Passed0.02 sec Start 2: pngvalid 2/2 Test #2: pngvalid . Passed 43.20 sec 100% tests passed, 0 tests failed out of 2 Total Test time (real) = 43.23 sec ===> Installing for png-1.5.17 ===> Generating temporary packing list ===> Checking if graphics/png already installed ===> png-1.5.17 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of graphics/png without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/graphics/png. *** [lib-depends] Error code 1 Stop in /usr/ports/graphics/jbig2dec. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2
http://forums.macrumors.com/showthread.php?t=1619404 It is helpful too… On Aug 15, 2013, at 4:14 PM, Doug Hardie wrote: > > On 15 August 2013, at 06:37, ajtiM wrote: > >> >> How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is >> it supported? >> >> I try Linux Mint and it works perfect. I am downloading live CD for NetBSD >> (jibbed) and I will see how is works but I like to install FreeBSD (not >> double boot, just FreeBSD). >> > > See: http://docs.freebsd.org/cgi/mid.cgi?28915479-B712-4ED0-A041-B75F2F59FECA > > Thats not a complete answer as I don't use any of the user interface stuff. > However, it will give a starting point for you. I have updated my two newest > minis to run 9.2 (latest candidate). > > Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
buildworld breaks at xinstall (9.2)
When I svnup and make buildworld, I get a failure at xinstall. THings Any chance that FreeBSD will be fixed to allow upgrading in place from 9.1? http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/181344 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd 9.2 via svn
On Mon, 19 Aug 2013 04:22:15 +0100, John wrote: > > If you don't use a custom kernel, why not use freebsd-update > > and follow the 9.2-RELEASE path with the security updates? > > Not sure if this is logic or "religon", but freebsd-update makes me > nervous. I'm allergic to automatic anything unless I've written it. The only > times I've run generic is when installing a new system, to see what I > need and what I don't. Maybe I'm just old. You demonstrated a valid argument for building from source. Using freebsd-update, a binary method is used for updating the _default_ system and the GENERIC kernel. If you have custom settings and therefore _intend_ to build from source, changing the version in your "svn co" command to the new -RELEASE-pX branch (security update branch) is safe. I've been using a similar approach with CVS to follow the -STABLE branch with a custom kernel and custom settings for building the system. If this makes me old, I should deserve several birthday parties per year. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd 9.2 via svn
On Mon, Aug 19, 2013 at 04:17:02AM +0200, Polytropon wrote: > 9.2-RELEASE hasn't been released yet. :-) well yes, there is that I suppose ;) > If you don't use a custom kernel, why not use freebsd-update > and follow the 9.2-RELEASE path with the security updates? Not sure if this is logic or "religon", but freebsd-update makes me nervous. I'm allergic to automatic anything unless I've written it. The only times I've run generic is when installing a new system, to see what I need and what I don't. Maybe I'm just old. thanks for the input, -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd 9.2 via svn
On Mon, 19 Aug 2013 02:28:25 +0100, John wrote: > Is it "safe" to start using 9.2 in the svn repos? I have a line like > this in a daily crontab: > > svn co svn://svn.us-east.freebsd.org/base/releng/9.1 /usr/src > > Can I change that 9.1 to 9.2 now, or should I wait? I aim to follow > 9.2-R with security updates. 9.2-RELEASE hasn't been released yet. :-) http://www.freebsd.org/releases/9.2R/schedule.html If you don't use a custom kernel, why not use freebsd-update and follow the 9.2-RELEASE path with the security updates? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
freebsd 9.2 via svn
Hello list, Is it "safe" to start using 9.2 in the svn repos? I have a line like this in a daily crontab: svn co svn://svn.us-east.freebsd.org/base/releng/9.1 /usr/src Can I change that 9.1 to 9.2 now, or should I wait? I aim to follow 9.2-R with security updates. thanks, -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2
Thank you very much. I will wait for 9.2 release or switch to Linux which works but it is not hat I want it… On Aug 15, 2013, at 4:14 PM, Doug Hardie wrote: > > On 15 August 2013, at 06:37, ajtiM wrote: > >> >> How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is >> it supported? >> >> I try Linux Mint and it works perfect. I am downloading live CD for NetBSD >> (jibbed) and I will see how is works but I like to install FreeBSD (not >> double boot, just FreeBSD). >> > > See: http://docs.freebsd.org/cgi/mid.cgi?28915479-B712-4ED0-A041-B75F2F59FECA > > Thats not a complete answer as I don't use any of the user interface stuff. > However, it will give a starting point for you. I have updated my two newest > minis to run 9.2 (latest candidate). > > Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
failure of libGL to compile on 9.2-PRERELEASE
i'm having trouble compiling libGL on 9.2-PRERELEASE using portmaster. firefox requires it. here's how the compile log file that i created ends: gmake[3]: Nothing to be done for `default'. gmake[3]: Leaving directory `/usr/ports/graphics/libGL/work/Mesa-8.0.5/src/mesa/x86' cc -c -o main/api_exec_es1.o main/api_exec_es1.c -DFEATURE_GL=1 -DHAVE_POSIX_MEMALIGN -DUSE_XCB -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DHAVE_ALIAS -I../../include -I../../src/glsl -I../../src/mesa -I../../src/mapi -I../../src/gallium/include -I../../src/gallium/auxiliary -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmiss ing-prototypes -std=c99 -fno-strict-aliasing -fno-builtin-memcmp -O2 -pipe -fno-strict-aliasing -fPIC -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -fvisibility=hidden python2 -t -O -O ../../src/mapi/glapi/gen/gl_table.py -f ../../src/mapi/glapi/gen/gl_and_es_API.xml -m remap_table -c es2 > main/api_exec_es2_dispatch.h gmake[2]: Leaving directory `/usr/ports/graphics/libGL/work/Mesa-8.0.5/src/mesa' gmake[1]: Leaving directory `/usr/ports/graphics/libGL/work/Mesa-8.0.5/src' *** [do-build] Error code 1 Stop in /usr/ports/graphics/libGL. i'm not clear exactly what the error is nor, therefore, how to correct it, nor how to work around it. suggestions, please. david coder daco...@dcoder.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9.2
On 15 August 2013, at 06:37, ajtiM wrote: > > How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is > it supported? > > I try Linux Mint and it works perfect. I am downloading live CD for NetBSD > (jibbed) and I will see how is works but I like to install FreeBSD (not > double boot, just FreeBSD). > See: http://docs.freebsd.org/cgi/mid.cgi?28915479-B712-4ED0-A041-B75F2F59FECA Thats not a complete answer as I don't use any of the user interface stuff. However, it will give a starting point for you. I have updated my two newest minis to run 9.2 (latest candidate). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD 9.2
Hi! I did stop using FreeBSD three months ago and with to iMac computer (older one) but I like start using FreeBSD again - I like it more. My computer is: iMac 27-inch, Late 2009 Processor 2.8 GHz Intel Core i7 Memory 8GB and graphics cars is ATI Radeon: Chipset Model: ATI Radeon HD 4850 Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 512 MB Vendor: ATI (0x1002) How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is it supported? I try Linux Mint and it works perfect. I am downloading live CD for NetBSD (jibbed) and I will see how is works but I like to install FreeBSD (not double boot, just FreeBSD). Thanks in advance. Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On Tue, 13 Aug 2013 18:22:33 +0200 Terje Elde wrote: > On 13. aug. 2013, at 16:30, "O. Hartmann" > wrote: > > What is going wrong? > > Are you unable to connect, or do you get an error message? If you do, > what is it? > > Terje I always get this message: psql postgres pgsql Password for user pgsql: XX psql: FATAL: password authentication failed for user "pgsql" signature.asc Description: PGP signature
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On 13. aug. 2013, at 16:30, "O. Hartmann" wrote: > What is going wrong? Are you unable to connect, or do you get an error message? If you do, what is it? Terje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On Tue, 13 Aug 2013 17:55:06 +0300 Volodymyr Kostyrko wrote: > > 13.08.2013 17:30, O. Hartmann wrote: > >> For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT > >> successfully. But by now, out of the blue, login as the database's > >> supervisor "pgsql" remotely isn't possible any more. > >> > >> The appropriate lines in pg_hba.conf are: > >> > >> local all pgsql md5 > >> hostssl all pgsql 0.0.0.0/0 md5 > >> > >> The funny thing is: when login locally without providing a password > >> (swap md5 to trust in the "local" line) and setting the password > >> for the role "pgsql" via > >> > >> ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; > > > > I guess ENCRYPTED means you are substituting FooMe with md5 hashed > > password correctly salted with role name as postgresql requires? > > Silly me, that's wrong. ENCRYPTED only means that password will be > stored encrypted on the disk. There's a side note about using > ENCRYPTED password with postgres in the docs though: > > "Note that older clients might lack support for the MD5 > authentication mechanism that is needed to work with passwords that > are stored encrypted." > Well, even if not ENCRYPTED it doesn't work anymore and prior to this failure, the passwords were stored md5 hashed via pgadmin3 all the time - and it worked. I made now another test. On a FreeBSD 9.2 box which is also running PostgreSQL 9.2 and to which I have access the way that is now rejected by the others, I did a login as the supervisor (pgsql) successfully and then set the password for that supervisor again with alter role pgsql with encrypted password 'FooMe'; (FooMe was the passowrd used before on the same system, it worked definitely) and - booom - I can not login anymore onto that machine! Something is definitely wrong. I have no idea what is wrong here. signature.asc Description: PGP signature
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
13.08.2013 17:30, O. Hartmann wrote: For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT successfully. But by now, out of the blue, login as the database's supervisor "pgsql" remotely isn't possible any more. The appropriate lines in pg_hba.conf are: local all pgsql md5 hostssl all pgsql 0.0.0.0/0 md5 The funny thing is: when login locally without providing a password (swap md5 to trust in the "local" line) and setting the password for the role "pgsql" via ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; I guess ENCRYPTED means you are substituting FooMe with md5 hashed password correctly salted with role name as postgresql requires? Silly me, that's wrong. ENCRYPTED only means that password will be stored encrypted on the disk. There's a side note about using ENCRYPTED password with postgres in the docs though: "Note that older clients might lack support for the MD5 authentication mechanism that is needed to work with passwords that are stored encrypted." -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
13.08.2013 17:30, O. Hartmann wrote: For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT successfully. But by now, out of the blue, login as the database's supervisor "pgsql" remotely isn't possible any more. The appropriate lines in pg_hba.conf are: local all pgsql md5 hostssl all pgsql 0.0.0.0/0 md5 The funny thing is: when login locally without providing a password (swap md5 to trust in the "local" line) and setting the password for the role "pgsql" via ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; I guess ENCRYPTED means you are substituting FooMe with md5 hashed password correctly salted with role name as postgresql requires? or doing the same via pgadmin3 from remotely by also swapping md5 to trust in the line "hostssl" for global network, it seems I could alter/change the password for the supervisor pgsql. But restoring the password check by setting back "md5" leaves me locked out! By the way, this strange behaviour occurs on ALL(!) PostgreSQL 9.2 servers running on FreeBSD 10.0-CURRENT boxes. Ports databases/postgresql-XXX as well as FreeBSD is as of the latest sources and up to date. What is going wrong? -- Sphinx of black quartz, judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT successfully. But by now, out of the blue, login as the database's supervisor "pgsql" remotely isn't possible any more. The appropriate lines in pg_hba.conf are: local all pgsql md5 hostssl all pgsql 0.0.0.0/0 md5 The funny thing is: when login locally without providing a password (swap md5 to trust in the "local" line) and setting the password for the role "pgsql" via ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; or doing the same via pgadmin3 from remotely by also swapping md5 to trust in the line "hostssl" for global network, it seems I could alter/change the password for the supervisor pgsql. But restoring the password check by setting back "md5" leaves me locked out! By the way, this strange behaviour occurs on ALL(!) PostgreSQL 9.2 servers running on FreeBSD 10.0-CURRENT boxes. Ports databases/postgresql-XXX as well as FreeBSD is as of the latest sources and up to date. What is going wrong? Please CC me. Regards, Oliver signature.asc Description: PGP signature
Re: 9.2-RC1: Problem with Kernel
On Tue, 13 Aug 2013 05:14:52 +0200, Polytropon wrote: > On Mon, 12 Aug 2013 21:01:14 + (UTC), Walter Hurry wrote: >> Sorry again. Anyway, I have it nailed down now. For anyone who is >> interested, the missing entry was: >> >> options ATA_CAM > > Correct. Line 84 and 264 have it commented out. This is the "new" method > of talking to disk devices, similarly as the acd interface for optical > media has been trans- formed into "SCSI over ATA" (ex device atapicam). > So the disk drive has not been recognized by the kernel, therefore: No > soup for you (i. e., no boot device). :-) Thanks, Polytropon! I have changed the controller (this is a VM, remember) to which the (same) virtual hard drive is attached, from ISA to SATA and "options ATA_CAM" is no longer needed. So I have learned a few things. Thanks again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.2-RC1: Problem with Kernel
On Mon, 12 Aug 2013 21:01:14 + (UTC), Walter Hurry wrote: > Sorry again. Anyway, I have it nailed down now. For anyone who is > interested, the missing entry was: > > options ATA_CAM Correct. Line 84 and 264 have it commented out. This is the "new" method of talking to disk devices, similarly as the acd interface for optical media has been trans- formed into "SCSI over ATA" (ex device atapicam). So the disk drive has not been recognized by the kernel, therefore: No soup for you (i. e., no boot device). :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.2-RC1: Problem with Kernel
On Sun, 11 Aug 2013 22:47:36 +1000, Ian Smith wrote:
> In freebsd-questions Digest, Vol 479, Issue 8, Message: 10 On Sun, 11
> Aug 2013 09:43:57 + (UTC) Walter Hurry
> wrote:
> > On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote:
> >
> > > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote:
> > >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching
> > >> the source from releng/9.2 and rebuilding kernel and world).
> > >>
> > >> The kernel compiles and runs fine using the supplied GENERIC, but
> > >> when I try to use my custom kenel config file, on reboot I get
> > >> this:
> > >>
> > >> Mounting from ufs:/dev/ada0p2 failed with error 19
> > >>
> > >> What module(s) have I missed?
> > >
> > > Diff against the GENERIC kernel. Maybe "device xhci"?
> > > What bootable media is listed when you type "?" at the mountroot
> > > prompt?
> > > If GENERIC boots and your kernel doesn't, there should be a
> > > significant difference regarding the config file's content. :-)
> >
> > Thanks for the reply. When I type "?" at the mountroot prompt I get:
> >
> > List of GEOM managed disk devices:
> >
> > with nothing shown.
> >
> > After restoring the GENERIC kernel, the output from 'gpart list' is:
> >
> > Geom name: ada0
> [..]
> > Consumers:
> > 1. Name: ada0
> >Mediasize: 21474836480 (20G)
> >Sectorsize: 512 Mode: r2w2e3
> >
> > (This is a small VirtualBox VM.)
> >
> > Kernel config is at http://paste2.org/h17Ih0PD
>
> Please Walter, it's not fair to make us do the work of figuring out what
> you've changed from GENERIC in that, when all you need to provide is:
>
> # diff -uw /path/to/GENERIC /path/to/YOURKERNEL
>
> More ideal for custom kernel configs - for just these occasions - is:
>
> include GENERIC ident YOURKERNEL # custom {no,}device and {no,}options
> statements
>
Sorry again. Anyway, I have it nailed down now. For anyone who is
interested, the missing entry was:
options ATA_CAM
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-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-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.2-RC1: Problem with Kernel
On Sun, 11 Aug 2013 22:47:36 +1000, Ian Smith wrote:
> In freebsd-questions Digest, Vol 479, Issue 8, Message: 10 On Sun, 11
> Aug 2013 09:43:57 + (UTC) Walter Hurry
> wrote:
> > On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote:
> >
> > > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote:
> > >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching
> > >> the source from releng/9.2 and rebuilding kernel and world).
> > >>
> > >> The kernel compiles and runs fine using the supplied GENERIC, but
> > >> when I try to use my custom kenel config file, on reboot I get
> > >> this:
> > >>
> > >> Mounting from ufs:/dev/ada0p2 failed with error 19
> > >>
> > >> What module(s) have I missed?
> > >
> > > Diff against the GENERIC kernel. Maybe "device xhci"?
> > > What bootable media is listed when you type "?" at the mountroot
> > > prompt?
> > > If GENERIC boots and your kernel doesn't, there should be a
> > > significant difference regarding the config file's content. :-)
> >
> > Thanks for the reply. When I type "?" at the mountroot prompt I get:
> >
> > List of GEOM managed disk devices:
> >
> > with nothing shown.
> >
> > After restoring the GENERIC kernel, the output from 'gpart list' is:
> >
> > Geom name: ada0
> [..]
> > Consumers:
> > 1. Name: ada0
> >Mediasize: 21474836480 (20G)
> >Sectorsize: 512 Mode: r2w2e3
> >
> > (This is a small VirtualBox VM.)
> >
> > Kernel config is at http://paste2.org/h17Ih0PD
>
> Please Walter, it's not fair to make us do the work of figuring out what
> you've changed from GENERIC in that, when all you need to provide is:
>
> # diff -uw /path/to/GENERIC /path/to/YOURKERNEL
>
> More ideal for custom kernel configs - for just these occasions - is:
>
> include GENERIC ident YOURKERNEL # custom {no,}device and {no,}options
> statements
>
Sorry. A diff wouldn't have helped much, as every line had changed due to
my reformatting. Never mind, I'll work it out for myself by a process of
elimination - and I'll post the answer here just in case anyone else is
interested.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.2-RC1: Problem with Kernel
In freebsd-questions Digest, Vol 479, Issue 8, Message: 10
On Sun, 11 Aug 2013 09:43:57 + (UTC) Walter Hurry
wrote:
> On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote:
>
> > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote:
> >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the
> >> source from releng/9.2 and rebuilding kernel and world).
> >>
> >> The kernel compiles and runs fine using the supplied GENERIC, but when
> >> I try to use my custom kenel config file, on reboot I get this:
> >>
> >> Mounting from ufs:/dev/ada0p2 failed with error 19
> >>
> >> What module(s) have I missed?
> >
> > Diff against the GENERIC kernel. Maybe "device xhci"?
> > What bootable media is listed when you type "?" at the mountroot prompt?
> > If GENERIC boots and your kernel doesn't, there should be a significant
> > difference regarding the config file's content. :-)
>
> Thanks for the reply. When I type "?" at the mountroot prompt I get:
>
> List of GEOM managed disk devices:
>
> with nothing shown.
>
> After restoring the GENERIC kernel, the output from 'gpart list' is:
>
> Geom name: ada0
[..]
> Consumers:
> 1. Name: ada0
>Mediasize: 21474836480 (20G)
>Sectorsize: 512
>Mode: r2w2e3
>
> (This is a small VirtualBox VM.)
>
> Kernel config is at http://paste2.org/h17Ih0PD
Please Walter, it's not fair to make us do the work of figuring out what
you've changed from GENERIC in that, when all you need to provide is:
# diff -uw /path/to/GENERIC /path/to/YOURKERNEL
More ideal for custom kernel configs - for just these occasions - is:
include GENERIC
ident YOURKERNEL
# custom {no,}device and {no,}options statements
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.2-RC1: Problem with Kernel
On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote: > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote: >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the >> source from releng/9.2 and rebuilding kernel and world). >> >> The kernel compiles and runs fine using the supplied GENERIC, but when >> I try to use my custom kenel config file, on reboot I get this: >> >> Mounting from ufs:/dev/ada0p2 failed with error 19 >> >> What module(s) have I missed? > > Diff against the GENERIC kernel. Maybe "device xhci"? > What bootable media is listed when you type "?" at the mountroot prompt? > If GENERIC boots and your kernel doesn't, there should be a significant > difference regarding the config file's content. :-) Thanks for the reply. When I type "?" at the mountroot prompt I get: List of GEOM managed disk devices: with nothing shown. After restoring the GENERIC kernel, the output from 'gpart list' is: Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 41943006 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ada0p1 Mediasize: 65536 (64k) Sectorsize: 512 Stripesize: 0 Stripeoffset: 17408 Mode: r0w0e0 rawuuid: c5ae2f8e-f5e1-11e2-92dd-08002755f0f7 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 65536 offset: 17408 type: freebsd-boot index: 1 end: 161 start: 34 2. Name: ada0p2 Mediasize: 20401029120 (19G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 82944 Mode: r1w1e1 rawuuid: c5ba5d2c-f5e1-11e2-92dd-08002755f0f7 rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: (null) length: 20401029120 offset: 82944 type: freebsd-ufs index: 2 end: 39845921 start: 162 3. Name: ada0p3 Mediasize: 1073707008 (1G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 3221242880 Mode: r1w1e0 rawuuid: c5ccb46a-f5e1-11e2-92dd-08002755f0f7 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 1073707008 offset: 20401112064 type: freebsd-swap index: 3 end: 41943005 start: 39845922 Consumers: 1. Name: ada0 Mediasize: 21474836480 (20G) Sectorsize: 512 Mode: r2w2e3 (This is a small VirtualBox VM.) Kernel config is at http://paste2.org/h17Ih0PD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
