Re: Disappointing dependency introduced in 9.1 (from 8-STABLE)
On 12/09/2013 05:53, Michael Sierchio wrote: > Because I build a lot of embedded devices with serial consoles, I was in > the habit of hacking /boot/loader by commenting out a line in a Makefile > that enables terminal emulation > > /sys/boot/i386/libi386/Makefile: > > #CFLAGS+= -DTERM_EMU > > and then in /sys/boot doing a make clean && make > > unfortunately, with 9.X, this breaks the compile. It seems a dependency > was introduced which requires the videoconsole code. I find this extremely > irritating. Of course, there's nothing to stop me (at the moment) from > compiling loader under 8-STABLE and installing it on 9.1 machines, but... > > Is there a better way now to stop the cursor from scribbling illegibly > across the screen? Hmmm... normally you should be controlling build options by setting WITH_FOO style flags in /etc/src.conf, although I can't see anything obviously relevant in src.conf(5). Did you raise a PR about this? Requesting a means to have a loader that only works via a serial console sounds like something that should be supported. 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
Disappointing dependency introduced in 9.1 (from 8-STABLE)
Because I build a lot of embedded devices with serial consoles, I was in the habit of hacking /boot/loader by commenting out a line in a Makefile that enables terminal emulation /sys/boot/i386/libi386/Makefile: #CFLAGS+= -DTERM_EMU and then in /sys/boot doing a make clean && make unfortunately, with 9.X, this breaks the compile. It seems a dependency was introduced which requires the videoconsole code. I find this extremely irritating. Of course, there's nothing to stop me (at the moment) from compiling loader under 8-STABLE and installing it on 9.1 machines, but... Is there a better way now to stop the cursor from scribbling illegibly across the screen? - M ___ 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 stable/9 and LSI controlers?
Both servers work with this patch applied. On Tue, 2013-09-10 at 14:29 -0600, Kenneth D. Merry wrote: > On Tue, Sep 10, 2013 at 12:35:02 -0700, Dennis Glatting wrote: > > On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: > > >>On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >> > > >>>On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > > >>>> > > >>>>Today I updated several systems against stable/9 that had not bee > > >>>>updated > > >>>>in ~five months. Two of the systems are serviced by LSI 2008 controllers > > >>>>with a RAID1 array housing the operating system. > > >>>> > > >>>>These systems no longer properly boot. > > >>>> > > >>>>Specifically, they begin the boot process but bomb when they try to > > >>>>mount > > >>>>root. Neither system sees the GPT partitions of the boot disk at the > > >>>>"mountroot>" prompt. On one system I replaced the hard disks, > > >>>>repartitioned, and reinstalled but the problem continued. > > >>>> > > >>>>I don't see any mention of geom or controller update in UPDATING but I > > >>>>know they have been updated because I saw their revisions fly actross my > > >>>>screen during the svn update. Also, I am running IR vers 16 on my > > >>>>controllers, which is the latest version of LSI firmware. > > >>>> > > >>>>Is there some new action I have to take to sucessfully boot LSI disks > > >>>>against the updated kernel? > > >>> > > >>>Can you try the mpslsi driver from LSI's web site and see if that works? > > >>> > > >>>If it does, then it is a problem we've introduced locally. > > >>> > > >> > > >>I'll give it a shot but just to be clear, I have been running the 16 > > >>firmware for months. > > > > > >The issue is very likely in the driver, not the firmware. I'm just > > >trying to figure out whether it broke in LSI's Phase 16 or in our > > >additional changes in FreeBSD. > > > > > >In any case, I've reproduced the problem, and hopefully I'll know soon > > >where the issue is. > > > > > >So don't worry about trying LSI's driver. Just go back to the previous > > >version of stable/9 that worked for you until we fix it. > > > > > >This only affects RAID volumes, not regular disks. > > > > > > > Thanks. > > > > I downloaded the mpslsi.ko driver from LSI under r255451 and the system > > now boots. > > Okay, try the attached patch with the new driver and see whether it fixes > the problem for you. > > The issue was that with the new rescanning code, we weren't rescanning RAID > volumes that got created. > > It fixes the problem for me with a RAID-1 volume. > > There is still the issue of all of the verbose probe errors that crop up > when an Integrated RAID volume is enabled, but it isn't obvious at the > moment whether we can easily fix that. > > Ken ___ 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 stable/9 and LSI controlers?
On Tue, 10 Sep 2013, John wrote: On Tue, Sep 10, 2013 at 11:21:02AM -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Hi, does it use the mfi driver? Because that has been updated. There was an errata notice about it on the 22nd August concerning mfi in JBOD mode and disks >2TB (typing by hand) mps0: port 0xb-0xb0ff mem mps0: Firmware: 16.00.00.00, Driver: 16.00.00.00-fbsd mps0: IOCCapabilities: 185c The system I am sitting in front of, appears NOT to see the RAID1 disk but does see the two non-RAID disks. All disks are 1TB Seagate ST31000424SS. The second system, which is remote and I cannot view its console from here, has two 250GB disks RAID1. ___ 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 stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > > Today I updated several systems against stable/9 that had not bee updated > in ~five months. Two of the systems are serviced by LSI 2008 controllers > with a RAID1 array housing the operating system. > > These systems no longer properly boot. > > Specifically, they begin the boot process but bomb when they try to mount > root. Neither system sees the GPT partitions of the boot disk at the > "mountroot>" prompt. On one system I replaced the hard disks, > repartitioned, and reinstalled but the problem continued. > > I don't see any mention of geom or controller update in UPDATING but I > know they have been updated because I saw their revisions fly actross my > screen during the svn update. Also, I am running IR vers 16 on my > controllers, which is the latest version of LSI firmware. > > Is there some new action I have to take to sucessfully boot LSI disks > against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. If it doesn't, then LSI needs to fix it. Ken -- Kenneth Merry k...@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: Problems with stable/9 and LSI controlers?
On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. I'll give it a shot but just to be clear, I have been running the 16 firmware for months. The issue is very likely in the driver, not the firmware. I'm just trying to figure out whether it broke in LSI's Phase 16 or in our additional changes in FreeBSD. In any case, I've reproduced the problem, and hopefully I'll know soon where the issue is. So don't worry about trying LSI's driver. Just go back to the previous version of stable/9 that worked for you until we fix it. This only affects RAID volumes, not regular disks. Thanks. I downloaded the mpslsi.ko driver from LSI under r255451 and the system now boots. ___ 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 stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 11:21:02AM -0700, Dennis Glatting wrote: > > Today I updated several systems against stable/9 that had not bee updated > in ~five months. Two of the systems are serviced by LSI 2008 controllers > with a RAID1 array housing the operating system. > > These systems no longer properly boot. > > Specifically, they begin the boot process but bomb when they try to mount > root. Neither system sees the GPT partitions of the boot disk at the > "mountroot>" prompt. On one system I replaced the hard disks, > repartitioned, and reinstalled but the problem continued. > > I don't see any mention of geom or controller update in UPDATING but I > know they have been updated because I saw their revisions fly actross my > screen during the svn update. Also, I am running IR vers 16 on my > controllers, which is the latest version of LSI firmware. > > Is there some new action I have to take to sucessfully boot LSI disks > against the updated kernel? Hi, does it use the mfi driver? Because that has been updated. There was an errata notice about it on the 22nd August concerning mfi in JBOD mode and disks >2TB -- 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: Problems with stable/9 and LSI controlers?
On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 12:35:02 -0700, Dennis Glatting wrote: On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. I'll give it a shot but just to be clear, I have been running the 16 firmware for months. The issue is very likely in the driver, not the firmware. I'm just trying to figure out whether it broke in LSI's Phase 16 or in our additional changes in FreeBSD. In any case, I've reproduced the problem, and hopefully I'll know soon where the issue is. So don't worry about trying LSI's driver. Just go back to the previous version of stable/9 that worked for you until we fix it. This only affects RAID volumes, not regular disks. Thanks. I downloaded the mpslsi.ko driver from LSI under r255451 and the system now boots. Okay, try the attached patch with the new driver and see whether it fixes the problem for you. The issue was that with the new rescanning code, we weren't rescanning RAID volumes that got created. It fixes the problem for me with a RAID-1 volume. The patch worked for one of my servers. I can't test the second server until tonight however the problem is the same. There is still the issue of all of the verbose probe errors that crop up when an Integrated RAID volume is enabled, but it isn't obvious at the moment whether we can easily fix that. ___ 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 stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: > On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > >> > >>Today I updated several systems against stable/9 that had not bee updated > >>in ~five months. Two of the systems are serviced by LSI 2008 controllers > >>with a RAID1 array housing the operating system. > >> > >>These systems no longer properly boot. > >> > >>Specifically, they begin the boot process but bomb when they try to mount > >>root. Neither system sees the GPT partitions of the boot disk at the > >>"mountroot>" prompt. On one system I replaced the hard disks, > >>repartitioned, and reinstalled but the problem continued. > >> > >>I don't see any mention of geom or controller update in UPDATING but I > >>know they have been updated because I saw their revisions fly actross my > >>screen during the svn update. Also, I am running IR vers 16 on my > >>controllers, which is the latest version of LSI firmware. > >> > >>Is there some new action I have to take to sucessfully boot LSI disks > >>against the updated kernel? > > > >Can you try the mpslsi driver from LSI's web site and see if that works? > > > >If it does, then it is a problem we've introduced locally. > > > > I'll give it a shot but just to be clear, I have been running the 16 > firmware for months. The issue is very likely in the driver, not the firmware. I'm just trying to figure out whether it broke in LSI's Phase 16 or in our additional changes in FreeBSD. In any case, I've reproduced the problem, and hopefully I'll know soon where the issue is. So don't worry about trying LSI's driver. Just go back to the previous version of stable/9 that worked for you until we fix it. This only affects RAID volumes, not regular disks. Ken -- Kenneth Merry k...@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: Problems with stable/9 and LSI controlers?
On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. I'll give it a shot but just to be clear, I have been running the 16 firmware for months. ___ 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 stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 12:35:02 -0700, Dennis Glatting wrote: > On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > >On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: > >>On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > >> > >>>On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > >>>> > >>>>Today I updated several systems against stable/9 that had not bee > >>>>updated > >>>>in ~five months. Two of the systems are serviced by LSI 2008 controllers > >>>>with a RAID1 array housing the operating system. > >>>> > >>>>These systems no longer properly boot. > >>>> > >>>>Specifically, they begin the boot process but bomb when they try to > >>>>mount > >>>>root. Neither system sees the GPT partitions of the boot disk at the > >>>>"mountroot>" prompt. On one system I replaced the hard disks, > >>>>repartitioned, and reinstalled but the problem continued. > >>>> > >>>>I don't see any mention of geom or controller update in UPDATING but I > >>>>know they have been updated because I saw their revisions fly actross my > >>>>screen during the svn update. Also, I am running IR vers 16 on my > >>>>controllers, which is the latest version of LSI firmware. > >>>> > >>>>Is there some new action I have to take to sucessfully boot LSI disks > >>>>against the updated kernel? > >>> > >>>Can you try the mpslsi driver from LSI's web site and see if that works? > >>> > >>>If it does, then it is a problem we've introduced locally. > >>> > >> > >>I'll give it a shot but just to be clear, I have been running the 16 > >>firmware for months. > > > >The issue is very likely in the driver, not the firmware. I'm just > >trying to figure out whether it broke in LSI's Phase 16 or in our > >additional changes in FreeBSD. > > > >In any case, I've reproduced the problem, and hopefully I'll know soon > >where the issue is. > > > >So don't worry about trying LSI's driver. Just go back to the previous > >version of stable/9 that worked for you until we fix it. > > > >This only affects RAID volumes, not regular disks. > > > > Thanks. > > I downloaded the mpslsi.ko driver from LSI under r255451 and the system > now boots. Okay, try the attached patch with the new driver and see whether it fixes the problem for you. The issue was that with the new rescanning code, we weren't rescanning RAID volumes that got created. It fixes the problem for me with a RAID-1 volume. There is still the issue of all of the verbose probe errors that crop up when an Integrated RAID volume is enabled, but it isn't obvious at the moment whether we can easily fix that. Ken -- Kenneth Merry k...@freebsd.org //depot/users/kenm/FreeBSD-stable2/9/sys/dev/mps/mps_sas_lsi.c#10 - /usr/home/kenm/perforce4/kenm/FreeBSD-stable2/9/sys/dev/mps/mps_sas_lsi.c *** /tmp/tmp.91039.2Tue Sep 10 14:13:13 2013 --- /usr/home/kenm/perforce4/kenm/FreeBSD-stable2/9/sys/dev/mps/mps_sas_lsi.c Tue Sep 10 14:07:08 2013 *** *** 892,898 --- 892,901 free(lun, M_MPT2); } SLIST_INIT(&targ->luns); + #if ((__FreeBSD_version >= 100) && (__FreeBSD_version < 139)) || \ + (__FreeBSD_version < 902502) if ((sassc->flags & MPSSAS_IN_STARTUP) == 0) + #endif mpssas_rescan_target(sc, targ); mps_dprint(sc, MPS_MAPPING, "RAID target id %d added (WWID = 0x%jx)\n", targ->tid, wwid); ___ 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 stable/9 and LSI controlers?
Whatever changed, happened between r253683 (July 26) and r255451 (today). On Tue, 10 Sep 2013, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? ___ 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"
Problems with stable/9 and LSI controlers?
Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? ___ 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"
Stable/9 from today mpssas_scsiio timeouts
as of stable today im seeing alot of new mps time outs 9.1-STABLE FreeBSD 9.1-STABLE #0 r253035M: Mon Jul 8 16:34:28 UTC 2013 root@:/usr/obj/nas/usr/src/sys/ mps1@pci0:130:0:0: class=0x010700 card=0x30201000 chip=0x00721000 rev=0x03 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]' class = mass storage subclass = SAS mps0: mpssas_scsiio_timeout checking sc 0xff8002145000 cm 0xff80021a6b78 (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983 command timeout cm 0xff80021a6b78 ccb 0xfe002bb5f800 mps0: mpssas_alloc_tm freezing simq mps0: timedout cm 0xff80021a6b78 allocated tm 0xff80021587b0 (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983 completed timedout cm 0xff80021a6b78 ccb 0xfe002bb5f800 during recovery ioc 8048 scsi 0 state c xfer 0 (noperiph:mps0:0:40:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0 count 1 (noperiph:mps0:0:40:0): SMID 6 finished recovery after aborting TaskMID 983 mps0: mpssas_free_tm releasing simq (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 (probe40:mps0:0:40:0): CAM status: Command timeout (probe40:mps0:0:40:0): Retrying command mps1: mpssas_scsiio_timeout checking sc 0xff8002384000 cm 0xff80023e5b78 (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983 command timeout cm 0xff80023e5b78 ccb 0xfe002be14800 mps1: mpssas_alloc_tm freezing simq mps1: timedout cm 0xff80023e5b78 allocated tm 0xff80023977b0 (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983 completed timedout cm 0xff80023e5b78 ccb 0xfe002be14800 during recovery ioc 8048 scsi 0 state c xfer 0 (noperiph:mps1:0:37:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0 count 1 (noperiph:mps1:0:37:0): SMID 6 finished recovery after aborting TaskMID 983 mps1: mpssas_free_tm releasing simq (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 (probe292:mps1:0:37:0): CAM status: Command timeout (probe292:mps1:0:37:0): Retrying command ___ 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-stable/release?
On Tue, May 21, 2013 at 2:18 PM, Pol Hallen wrote: > Hi all :-) > > quick question: for a production server, what it best way? I've done work with organizations that will not install anything that is considered a development branch, of which stable/ is. Therefore, for production environments, those organizations will only install -RELEASE or releng/ releases. It comes down to a decision you and/or your organization must make and that decision will be based on a risk/reward analysis. Hope that helps. -- Take care Rick Miller ___ 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-stable/release?
Hi all :-) quick question: for a production server, what it best way? now I using the release: 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:11:52 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 thanks! Pol ___ 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-STABLE with xterm-292 oddity
Recently (last week) I upgraded two systems to 9.1-STABLE. One system is i386 and the other is amd64. The upgrades were done about one day apart. While I have not checked every single commit, for the purposes of this problem, I am assuming these two systems have the same ports, src, and docs changes applied. This is how I began these upgrades: % cd /usr % rm -rf src ports doc % svn co svn://svn.freebsd.org/base/stable/9 src % svn co svn://svn.freebsd.org/doc/head doc % svn co svn://svn.freebsd.org/ports/head ports Note: these systems are desktop systems, not headless servers. The hardware of both systems is nearly identical, in particular, the graphics card (ATI) is identical on each system. After each upgrade, I wiped all my ports and rebuilt all the ports on the list of ports I use on these systems. While these two lists are slightly different, the "basics" are the same in both cases. I run Xorg on both systems along with open-motif and xterms: xorg-7.5.2 open-motif-2.3.4 xterm-292 The /var/db/ports/xterm/options files on both systems are identical. # This file is auto-generated by 'make config'. # Options for xterm-292 _OPTIONS_READ=xterm-292 _FILE_COMPLETE_OPTIONS_LIST=256COLOR DABBREV DECTERM GNOME LUIT PCRE WCHAR OPTIONS_FILE_UNSET+=256COLOR OPTIONS_FILE_UNSET+=DABBREV OPTIONS_FILE_UNSET+=DECTERM OPTIONS_FILE_UNSET+=GNOME OPTIONS_FILE_SET+=LUIT OPTIONS_FILE_UNSET+=PCRE OPTIONS_FILE_SET+=WCHAR Also the /usr/ports/x11/xterm/work/xterm-292/xtermcfg.h files are the same on both systems. The oddity is this: on one system, when I iconify/minimize/close an open xterm window, the resulting small icon window holds a pixmap (48x48) that is monochrome. It resembles an outline drawing of an old style dumb terminal. On the other system, when I perform the same operation (close/iconify an xterm window), the resulting small icon window contains a color pixmap (48x48) of our Beastie! While I have an .Xdefaults file in my home directory on both systems, and there are XTerm resources configured therein, I do not configure any resources that control xterm icons. In fact, those .Xdefaults files are identical in the XTerm resource lines. I have rebuilt the x11/xterm port on the system with the color Beastie pixmap for closed/iconic xterm windows using the following steps: # cd /usr/ports/x11/xterm # make deinstall # /bin/rm -rf work # make install The results are the same as before, unfortunately. Interesting enough, one can see the color Beastie pixmap _inside_ the unstripped xterm executable on each system using this command: % strings /usr/local/bin/xterm | less The Beastie embedded pixmap appears after scrolling to about the 83% point (and runs up to about the 93% point) of the strings output. I am at a loss as to how one system is displaying the unwanted color pixmap while the other is showing the desired monochrome pixmap. Any ideas, or suggested avenues for further detective work, on this issue would be greatly appreciated. Thanks in advance. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template ->| ___ 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-STABLE doesn't boot: can't load 'kernel'
On 4/16/2013 1:36 AM, J David wrote: loader.conf was empty and there's no 4k gnops, geli, anything like that. This is a 100% normal install. Although, since you mentioned 4k blocks, I did leave a gap between ada0p1 and ada0p2 to start the root partition on a 4k boundary. (It's an SSD that will almost never be written to once installed, so that might be a bit silly, but it's a habit already.) I decided to try this again without the gap, and that seems to have worked. I made it through install and partitioning and OS updating to 9-STABLE and installing new boot blocks and it seems to have worked. I even got it to work with a ZFS root. Here's the partition table I ended up with: => 34 234441581 ada0 GPT (111G) 34990 1 freebsd-boot (495k) 1024 226051072 2 freebsd-zfs (107G) 2260520968389519 3 freebsd-swap (4.0G) I'm not sure why this would make a difference, but either it does or doing it cleared out whatever else was wrong. This box will be stress tested and rebooted quite a bit in the next few days, so I will report back if it comes unglued. :) Thanks for the suggestion! I'd say file a bug report, since subtly hidden parts of the disk can be beneficial in the right circumstances. That, and it should just work. Does your drive report the blocks as 512 bytes or 4k? If you're using zfs now, run `zdb | grep ashift` and it should list 12 if it's 4k. Otherwise, you can get a performance hit if the drive's 4k native. Two of my drives are 4k native but report as 512b, so I had to trick zfs with gnop. ___ 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-STABLE doesn't boot: can't load 'kernel'
loader.conf was empty and there's no 4k gnops, geli, anything like that. This is a 100% normal install. Although, since you mentioned 4k blocks, I did leave a gap between ada0p1 and ada0p2 to start the root partition on a 4k boundary. (It's an SSD that will almost never be written to once installed, so that might be a bit silly, but it's a habit already.) I decided to try this again without the gap, and that seems to have worked. I made it through install and partitioning and OS updating to 9-STABLE and installing new boot blocks and it seems to have worked. I even got it to work with a ZFS root. Here's the partition table I ended up with: => 34 234441581 ada0 GPT (111G) 34990 1 freebsd-boot (495k) 1024 226051072 2 freebsd-zfs (107G) 2260520968389519 3 freebsd-swap (4.0G) I'm not sure why this would make a difference, but either it does or doing it cleared out whatever else was wrong. This box will be stress tested and rebooted quite a bit in the next few days, so I will report back if it comes unglued. :) Thanks for the suggestion! ___ 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-STABLE doesn't boot: can't load 'kernel'
I can't recall, does the cd come with the btx loader? Is it able to see the hard drive partitions and boot that way? Did you put anything in loader.conf? I'm guessing that if you're getting to /boot/loader but not any further, it's something wrong with the conf file. If you're booting UFS, you might be safe just deleting/renaming the file. And just for sanity's sake, you didn't try anything special with geom did you, such as 4k blocks, geli, etc? On 4/15/2013 1:03 PM, J David wrote: After installing 9.1-RELEASE amd64 on a system, it boots up fine. If I then build and install a new 9-STABLE kernel & world, reboots die in the loader with: can't load 'kernel' This is a pretty straightforward system, one drive, not large (128GB SSD). GPT partitioned, gptboot boot code. One UFS root partition to boot from, a swap partition and, the rest for ZFS. (At first I tried to do this system with root-on-ZFS but that also failed, adding "unable to load zpool by guid" or similar before the "can't load 'kernel'" message.) Once this happens, the disk is unbootable. I can start from the install CD and access the disk just fine, but even if I move kernel.old back to kernel, it doesn't boot anymore. Likewise, it doesn't matter if I overwrite the boot code with gptboot & pmbr from the install CD or the new ones from /boot after installworld. The disk looks like: # gpart show => 34 234441581 ada0 GPT (111G) 34 222 1 freebsd-boot (111k) 256 1792 - free - (896k) 2048 8388608 2 freebsd-ufs (4.0G) 8390656 8388608 3 freebsd-swap (4.0G) 16779264 217662351 4 freebsd-zfs (103G) In the loader: BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 621kB/2067924kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (root@builder, Mon Apr 15 09:14:38 UTC 2013) can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK show […] currdev=disk0p2: […] loaddev=disk0p2: […] OK lsdev cd devices: disk devices: disk0: BIOS drive C: pxe devices: OK ls open '/' failed: no such file or directory OK help Verbose help not available, use '?' to list commands So it's getting the boot device right (disk0p2 / ada0p2), but can't see it at all. Does anyone know what might be wrong? Thanks for any advice! ___ 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"
9-STABLE doesn't boot: can't load 'kernel'
After installing 9.1-RELEASE amd64 on a system, it boots up fine. If I then build and install a new 9-STABLE kernel & world, reboots die in the loader with: can't load 'kernel' This is a pretty straightforward system, one drive, not large (128GB SSD). GPT partitioned, gptboot boot code. One UFS root partition to boot from, a swap partition and, the rest for ZFS. (At first I tried to do this system with root-on-ZFS but that also failed, adding "unable to load zpool by guid" or similar before the "can't load 'kernel'" message.) Once this happens, the disk is unbootable. I can start from the install CD and access the disk just fine, but even if I move kernel.old back to kernel, it doesn't boot anymore. Likewise, it doesn't matter if I overwrite the boot code with gptboot & pmbr from the install CD or the new ones from /boot after installworld. The disk looks like: # gpart show => 34 234441581 ada0 GPT (111G) 34 222 1 freebsd-boot (111k) 256 1792 - free - (896k) 2048 8388608 2 freebsd-ufs (4.0G) 8390656 8388608 3 freebsd-swap (4.0G) 16779264 217662351 4 freebsd-zfs (103G) In the loader: BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 621kB/2067924kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (root@builder, Mon Apr 15 09:14:38 UTC 2013) can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK show […] currdev=disk0p2: […] loaddev=disk0p2: […] OK lsdev cd devices: disk devices: disk0: BIOS drive C: pxe devices: OK ls open '/' failed: no such file or directory OK help Verbose help not available, use '?' to list commands So it's getting the boot device right (disk0p2 / ada0p2), but can't see it at all. Does anyone know what might be wrong? Thanks for any advice! ___ 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"
fresh binary packages for 9.1 / 9 stable
Hey hey :-) Are there any news on fresh binary packages for 9.1-RELEASE / 9-STABLE? :-) 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"
Does your 9.1-STABLE still hang on reboot?
Hi. I am talking about this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=172952&cat=%20jb It should be fixed in STABLE, but I want to make sure it's safe to upgrade my 9.0 systems to 9.1-STABLE now. ___ 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: Ports & Packages [Stable] in sync
On Feb 17, 2013, at 3:44 PM, Jeff Tipton wrote: > On 02/17/2013 13:13, Damien Fleuriot wrote: >> On 16 Feb 2013, at 16:56, Jeff Tipton wrote: >> >>> Hi, >>> >>> I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are >>> no packages for 9.1-RELEASE. On my desktops, I keep ports and packages at >>> the RELEASE versions, so I only have to compile when I need non-default >>> options or when there are no packages. Would it be possible to get the >>> ports snapshot that was used to compile the 9-STABLE packages? I think I >>> could use subversion but then I need to know the revision number of that >>> snapshot. What do you suggest? >>> >>> Thanks, >>> Jeff >>> >> Hi Jeff, >> >> I think you might be confused here. >> >> It is my understanding that there are ports for: >> - HEAD >> - x.y-RELEASE >> >> I don't think you're going to be able to get a snapshot from 9-STABLE, >> because -STABLE is a continuing work. >> >> What version do you consider to be 9-STABLE ? >> Every time there's a new commit you get a "new" 9-STABLE. >> ___ >> 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" > Thank you, Damien, for the reply. AFAIK, STABLE gets updated every 2 weeks > but not every day, and it seems to be that because of the intrusion, it has > not been updated for long. The versions of the ports that come with the > 9.1-RELEASE are even slightly newer than those of 9-STABLE packages. I think > if I don't get the revision number from which the 9-STABLE was updated last > time I'll use the ports tree that comes with 9.1-RELEASE. I hope it won't > cause much version incompatibilities. I'm not sure where you're getting your 9-STABLE ports from, Jeff. In the SVN repository I only see release tags and HEAD: http://svn.freebsd.org/ports/ I also second Gilbert's advice about using HEAD for your ports tree, we do this here in production with over 50 boxes and have had no problems so far. If you still want to use the branch from 9.1-RELEASE, it's here: svn://svn.freebsd.org/ports/tags/RELEASE_9_1_0/ Note that, unless I'm wrong, you will not be getting *ANY* update to the ports tree then, it's frozen. This means no security updates and all, AFAICT. ___ 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: Ports & Packages [Stable] in sync
Jeff Tipton writes: > Thank you, Damien, for the reply. AFAIK, STABLE gets updated every 2 > weeks but not every day, and it seems to be that because of the > intrusion, it has not been updated for long. The versions of the ports > that come with the 9.1-RELEASE are even slightly newer than those of > 9-STABLE packages. I think if I don't get the revision number from > which the 9-STABLE was updated last time I'll use the ports tree that > comes with 9.1-RELEASE. I hope it won't cause much version > incompatibilities. Um, not really. Or at least, not specific enough to be sure whether it is correct or not. The ports tree is not branched, and is intended to work with all supported branches and releases. In other words, regardless of whether you're running 9.1-RELEASE, 9-STABLE (in svn/cvs terms, RELENG_9), or 10.x (HEAD), you can (and, unless you have specific reasons otherwise, usually corporate security dictates) should use a ports tree checked out from HEAD. This is unrelated to whether packages are available for the ports on a particular branch or tag. Package availability is unusually limited at the moment, but that's because the build cluster has very limited capacity right now for a variety of reasons. That situation will improve over time, but until computers are infinitely fast, the package collection will lag somewhat behind the ports tree. Packages need to be built for a particular base system (or "close enough": generally all base-system versions in the same major-number release can run the packages for any other within that same series, most notably the -STABLE version). Additionally, -STABLE base system is "updated" by definition every time a developer checks into the relevant branch (currently RELENG_9). For ports, as I said earlier, there is no equivalent; updates go to HEAD, period. When packages get built for a particular base system is a matter of policy on the build cluster. I don't use downloaded packages for ports updates, but I would expect that to evolve as the new build cluster does. ___ 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: Ports & Packages [Stable] in sync
On 02/17/2013 13:13, Damien Fleuriot wrote: On 16 Feb 2013, at 16:56, Jeff Tipton wrote: Hi, I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are no packages for 9.1-RELEASE. On my desktops, I keep ports and packages at the RELEASE versions, so I only have to compile when I need non-default options or when there are no packages. Would it be possible to get the ports snapshot that was used to compile the 9-STABLE packages? I think I could use subversion but then I need to know the revision number of that snapshot. What do you suggest? Thanks, Jeff Hi Jeff, I think you might be confused here. It is my understanding that there are ports for: - HEAD - x.y-RELEASE I don't think you're going to be able to get a snapshot from 9-STABLE, because -STABLE is a continuing work. What version do you consider to be 9-STABLE ? Every time there's a new commit you get a "new" 9-STABLE. ___ 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" Thank you, Damien, for the reply. AFAIK, STABLE gets updated every 2 weeks but not every day, and it seems to be that because of the intrusion, it has not been updated for long. The versions of the ports that come with the 9.1-RELEASE are even slightly newer than those of 9-STABLE packages. I think if I don't get the revision number from which the 9-STABLE was updated last time I'll use the ports tree that comes with 9.1-RELEASE. I hope it won't cause much version incompatibilities. ___ 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: Ports & Packages [Stable] in sync
On 16 Feb 2013, at 16:56, Jeff Tipton wrote: > Hi, > > I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are no > packages for 9.1-RELEASE. On my desktops, I keep ports and packages at the > RELEASE versions, so I only have to compile when I need non-default options > or when there are no packages. Would it be possible to get the ports snapshot > that was used to compile the 9-STABLE packages? I think I could use > subversion but then I need to know the revision number of that snapshot. What > do you suggest? > > Thanks, > Jeff > Hi Jeff, I think you might be confused here. It is my understanding that there are ports for: - HEAD - x.y-RELEASE I don't think you're going to be able to get a snapshot from 9-STABLE, because -STABLE is a continuing work. What version do you consider to be 9-STABLE ? Every time there's a new commit you get a "new" 9-STABLE. ___ 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"
Ports & Packages [Stable] in sync
Hi, I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are no packages for 9.1-RELEASE. On my desktops, I keep ports and packages at the RELEASE versions, so I only have to compile when I need non-default options or when there are no packages. Would it be possible to get the ports snapshot that was used to compile the 9-STABLE packages? I think I could use subversion but then I need to know the revision number of that snapshot. What do you suggest? Thanks, Jeff ___ 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: why is bacula-client looking for libz.so.5 on 9-STABLE
Den 06.02.2013 00:03, skrev Per olof Ljungmark: Hi, Upgraded a system from 8.3 to 9-STABLE and did make delete-old-libs afterwards. System has around thirty ports installed and all except bacula-client upgraded gracefully. Why does it want libz.so.5 when libz.so.6 is present? I'm pretty sure I'm missing the obvious here... Linking bacula-fd ... /usr/ports/sysutils/bacula-client/work/bacula-5.2.12/libtool --silent --tag=CXX --mode=link /usr/bin/c++ -L/usr/local/lib -L../lib -L../findlib -o bacula-fd filed.o authenticate.o acl.o backup.o estimate.o fd_plugins.o accurate.o filed_conf.o heartbeat.o job.o pythonfd.o restore.o status.o verify.o verify_vol.o xattr.o-lz -lbacfind -lbacpy -lbaccfg -lbac -lm -lpthread -lintl -lwrap /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -Wl,-rpath -Wl,/usr/local/lib /usr/bin/ld: warning: libz.so.5, needed by /usr/local/lib/libbac.so, not found (try using -rpath or -rpath-link) 'libbac.so' is installed by bacula-server; try to rebuild this port first! Use 'sysutils/libchk' or pkg_libchk (from bsdadminscripts) to find other broken ports. -- Herbert ___ 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"
why is bacula-client looking for libz.so.5 on 9-STABLE
Hi, Upgraded a system from 8.3 to 9-STABLE and did make delete-old-libs afterwards. System has around thirty ports installed and all except bacula-client upgraded gracefully. Why does it want libz.so.5 when libz.so.6 is present? I'm pretty sure I'm missing the obvious here... Linking bacula-fd ... /usr/ports/sysutils/bacula-client/work/bacula-5.2.12/libtool --silent --tag=CXX --mode=link /usr/bin/c++ -L/usr/local/lib -L../lib -L../findlib -o bacula-fd filed.o authenticate.o acl.o backup.o estimate.o fd_plugins.o accurate.o filed_conf.o heartbeat.o job.o pythonfd.o restore.o status.o verify.o verify_vol.o xattr.o-lz -lbacfind -lbacpy -lbaccfg -lbac -lm -lpthread -lintl -lwrap /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -Wl,-rpath -Wl,/usr/local/lib /usr/bin/ld: warning: libz.so.5, needed by /usr/local/lib/libbac.so, not found (try using -rpath or -rpath-link) -- Intersonic AB Registered in Solna, Sweden SE556539368201 ___ 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"
Anyone else seeing problems with dtrace and cyclic in 9.1-stable???
Greetings all, Has anyone else seen these errors during 9.1-stable boot... Jan 16 08:12:05 sleipnir kernel: link_elf_obj: symbol cyclic_clock_func undefined Jan 16 08:12:05 sleipnir kernel: KLD file cyclic.ko - could not finalize loading Jan 16 08:12:05 sleipnir kernel: KLD file dtrace.ko - cannot find dependency "cyclic" This began around 14th - 15th Jan 2013. I have no recollection of seeing these symptoms before. Cheers, // jau .--- ..- -.- -.- .-.- .-.-.-..- -.- -.- --- -. . -. /Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng & cs)(Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi /Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + ___ 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: how to change from STABLE to RELEASE?
>> === >> >> When I reboot I get: >> >> Enter full pathname of shell or RETURN for /bin/sh: >> I press enter and try: >> >> # mount -a >> mount: not found >> # mount -urw / >> mount: not found >> # >> >> I try >> # /rescue/vi /etc/defaults/rc.conf >> which is the one that is borked, to fix it and remove the "" that >> present in there, I get >> >> ex/vi: Error: /var/tmp/vi.recover: Read-only file sytem >> ex/vi: Modifications not recoverable if the session fails >> ex/vi: Error: /etc/defaults/rc.conf: Read-only file sytem >> ex/vi: Error: Unable to create temporary file: Read-only file system >> >> I can boot the livedvd for FreeBSD 9.1 or 8.2/8.3 series as I have >> them available. There used to be the fixit command and I could use >> it. I try the advice in System Administration chapter of handbook, >> but it does not work here :( >> >> boot -s >> mount -a >> mount -urw / >> >> as found in: >> >> http://www.freebsd.org/doc/faq/admin.html#rcconf-readonly >> >> >> Words of advice and suggestions are greatly appreciated and would get >> me to fix the mess that I started by myself :( >> >> Regards, > > > > > mount -o rw / > > > Alternatively boot a livefs CD (or martin matuska's mfsbsd) and mount your / > partition from there, read-write. > > Thank you for the suggestion. I am now back in the saddle and running 9.1-RELEASE on this machine. Thanks for all the help provided. $ uname -r 9.1-RELEASE $ uname -a FreeBSD e213-amd64-1.grullahighschool.org 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 Regards, Antonio ___ 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: how to change from STABLE to RELEASE?
On Wed, 9 Jan 2013, Fleuriot Damien wrote: On Jan 9, 2013, at 3:56 PM, Warren Block wrote: On Tue, 8 Jan 2013, Antonio Olivares wrote: Dear folks, I am happily running FreeBSD 9.0-STABLE on one of my machines, but I want to move to FreeBSD-RELEASE and use # freebsd-update upgrade -r 9.1-RELEASE but it does not find a valid repository. How can I solve this issue to move to newer RELEASE and avoid staying on STABLE because I will have to compile/build world and it takes a good while to build and then may have to rebuild all the ports. As long as you stay on 9-STABLE, it is not necessary to rebuild all ports. Actually, that is what the "stable" part means, a stable ABI: http://www.wonkity.com/~wblock/docs/html/stable.html Interesting article, Warren. If I may say, you may want, on occasion, to update the section about csup. Doh! Done now, please refresh your browser. I'm going to take the opportunity to favorite your post, which I had read previously, regarding the simplification of kernel config files. http://www.wonkity.com/~wblock/docs/html/kernelconfig.html Thanks! ___ 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: how to change from STABLE to RELEASE?
On Jan 9, 2013, at 3:56 PM, Warren Block wrote: > On Tue, 8 Jan 2013, Antonio Olivares wrote: > >> Dear folks, >> >> I am happily running FreeBSD 9.0-STABLE on one of my machines, but I >> want to move to FreeBSD-RELEASE and use >> # freebsd-update upgrade -r 9.1-RELEASE >> but it does not find a valid repository. How can I solve this issue >> to move to newer RELEASE and avoid staying on STABLE because I will >> have to compile/build world and it takes a good while to build and >> then may have to rebuild all the ports. > > As long as you stay on 9-STABLE, it is not necessary to rebuild all ports. > Actually, that is what the "stable" part means, a stable ABI: > > http://www.wonkity.com/~wblock/docs/html/stable.html Interesting article, Warren. If I may say, you may want, on occasion, to update the section about csup. I'm going to take the opportunity to favorite your post, which I had read previously, regarding the simplification of kernel config files. http://www.wonkity.com/~wblock/docs/html/kernelconfig.html ___ 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: how to change from STABLE to RELEASE?
On Tue, 8 Jan 2013, Antonio Olivares wrote: Dear folks, I am happily running FreeBSD 9.0-STABLE on one of my machines, but I want to move to FreeBSD-RELEASE and use # freebsd-update upgrade -r 9.1-RELEASE but it does not find a valid repository. How can I solve this issue to move to newer RELEASE and avoid staying on STABLE because I will have to compile/build world and it takes a good while to build and then may have to rebuild all the ports. As long as you stay on 9-STABLE, it is not necessary to rebuild all ports. Actually, that is what the "stable" part means, a stable ABI: http://www.wonkity.com/~wblock/docs/html/stable.html ___ 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: how to change from STABLE to RELEASE?
On Jan 9, 2013, at 2:26 PM, Antonio Olivares wrote: >>> Give this a try >>> >>> setenv UNAME_r "9.0-RELEASE" >>> freebsd-update fetch update >>> freebsd-update upgrade -r 9.1-RELEASE >> >> Thank you very much! It seems to be working: >> >> $ su - >> Password: >> %seten UNAME_r "9.0-RELEASE" >> seten: Command not found. >> %setenv UNAME_r "9.0-RELEASE" >> %freebsd-update fetch update >> usage: freebsd-update [options] command ... [path] >> >> Options: >> -b basedir -- Operate on a system mounted at basedir >> (default: /) >> -d workdir -- Store working files in workdir >> (default: /var/db/freebsd-update/) >> -f conffile -- Read configuration options from conffile >> (default: /etc/freebsd-update.conf) >> -k KEY -- Trust an RSA key with SHA256 hash of KEY >> -r release -- Target for upgrade (e.g., 6.2-RELEASE) >> -s server-- Server from which to fetch updates >> (default: update.FreeBSD.org) >> -t address -- Mail output of cron command, if any, to address >> (default: root) >> Commands: >> fetch-- Fetch updates from server >> cron -- Sleep rand(3600) seconds, fetch updates, and send an >> email if updates were found >> upgrade -- Fetch upgrades to FreeBSD version specified via -r option >> install -- Install downloaded updates or upgrades >> rollback -- Uninstall most recently installed updates >> IDS -- Compare the system against an index of "known good" files. >> %freebsd-update fetch >> Looking up update.FreeBSD.org mirrors... 3 mirrors found. >> Fetching public key from update5.freebsd.org... done. >> Fetching metadata signature for 9.0-RELEASE from update5.freebsd.org... done. >> Fetching metadata index... done. >> Fetching 2 metadata files... done. >> Inspecting system... done. >> Preparing to download files... >> >> Will get back to see if it went through all the way! >> >> Best Regards, >> >> >> Antonio > > Dear folks, > > Everything almost worked. Now I get some errors. > /etc/defaults/rc.conf: 18: Syntax error: redirection unexpected > Enter full pathname of shell or RETURN for /bin/sh: > > I try to edit the file, but I cannot see it I get a readonly file > system. There were some mistakes that I could not correct some lines > like << and then === were present in the file, but vi could > not allow me to remove them I got error and I wanted to :wq! quickly > and now I cannot boot. How can I get into the computer with > read/write permission to fix this one and a /boot/device.hints error > that is present here? > > Thanks for any pointers and help/advice. > > Regards, > > > Antonio > > === > > When I reboot I get: > > Enter full pathname of shell or RETURN for /bin/sh: > I press enter and try: > > # mount -a > mount: not found > # mount -urw / > mount: not found > # > > I try > # /rescue/vi /etc/defaults/rc.conf > which is the one that is borked, to fix it and remove the "" that > present in there, I get > > ex/vi: Error: /var/tmp/vi.recover: Read-only file sytem > ex/vi: Modifications not recoverable if the session fails > ex/vi: Error: /etc/defaults/rc.conf: Read-only file sytem > ex/vi: Error: Unable to create temporary file: Read-only file system > > I can boot the livedvd for FreeBSD 9.1 or 8.2/8.3 series as I have > them available. There used to be the fixit command and I could use > it. I try the advice in System Administration chapter of handbook, > but it does not work here :( > > boot -s > mount -a > mount -urw / > > as found in: > > http://www.freebsd.org/doc/faq/admin.html#rcconf-readonly > > > Words of advice and suggestions are greatly appreciated and would get > me to fix the mess that I started by myself :( > > Regards, mount -o rw / Alternatively boot a livefs CD (or martin matuska's mfsbsd) and mount your / partition from there, read-write. ___ 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"
Fwd: how to change from STABLE to RELEASE?
>> Give this a try >> >> setenv UNAME_r "9.0-RELEASE" >> freebsd-update fetch update >> freebsd-update upgrade -r 9.1-RELEASE > > Thank you very much! It seems to be working: > > $ su - > Password: > %seten UNAME_r "9.0-RELEASE" > seten: Command not found. > %setenv UNAME_r "9.0-RELEASE" > %freebsd-update fetch update > usage: freebsd-update [options] command ... [path] > > Options: > -b basedir -- Operate on a system mounted at basedir > (default: /) > -d workdir -- Store working files in workdir > (default: /var/db/freebsd-update/) > -f conffile -- Read configuration options from conffile > (default: /etc/freebsd-update.conf) > -k KEY -- Trust an RSA key with SHA256 hash of KEY > -r release -- Target for upgrade (e.g., 6.2-RELEASE) > -s server-- Server from which to fetch updates > (default: update.FreeBSD.org) > -t address -- Mail output of cron command, if any, to address > (default: root) > Commands: > fetch-- Fetch updates from server > cron -- Sleep rand(3600) seconds, fetch updates, and send an > email if updates were found > upgrade -- Fetch upgrades to FreeBSD version specified via -r option > install -- Install downloaded updates or upgrades > rollback -- Uninstall most recently installed updates > IDS -- Compare the system against an index of "known good" files. > %freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching public key from update5.freebsd.org... done. > Fetching metadata signature for 9.0-RELEASE from update5.freebsd.org... done. > Fetching metadata index... done. > Fetching 2 metadata files... done. > Inspecting system... done. > Preparing to download files... > > Will get back to see if it went through all the way! > > Best Regards, > > > Antonio Dear folks, Everything almost worked. Now I get some errors. /etc/defaults/rc.conf: 18: Syntax error: redirection unexpected Enter full pathname of shell or RETURN for /bin/sh: I try to edit the file, but I cannot see it I get a readonly file system. There were some mistakes that I could not correct some lines like << and then === were present in the file, but vi could not allow me to remove them I got error and I wanted to :wq! quickly and now I cannot boot. How can I get into the computer with read/write permission to fix this one and a /boot/device.hints error that is present here? Thanks for any pointers and help/advice. Regards, Antonio === When I reboot I get: Enter full pathname of shell or RETURN for /bin/sh: I press enter and try: # mount -a mount: not found # mount -urw / mount: not found # I try # /rescue/vi /etc/defaults/rc.conf which is the one that is borked, to fix it and remove the "" that present in there, I get ex/vi: Error: /var/tmp/vi.recover: Read-only file sytem ex/vi: Modifications not recoverable if the session fails ex/vi: Error: /etc/defaults/rc.conf: Read-only file sytem ex/vi: Error: Unable to create temporary file: Read-only file system I can boot the livedvd for FreeBSD 9.1 or 8.2/8.3 series as I have them available. There used to be the fixit command and I could use it. I try the advice in System Administration chapter of handbook, but it does not work here :( boot -s mount -a mount -urw / as found in: http://www.freebsd.org/doc/faq/admin.html#rcconf-readonly Words of advice and suggestions are greatly appreciated and would get me to fix the mess that I started by myself :( Regards, Antonio ___ 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: how to change from STABLE to RELEASE?
Antonio Olivares wrote: Dear folks, I am happily running FreeBSD 9.0-STABLE on one of my machines, but I want to move to FreeBSD-RELEASE and use # freebsd-update upgrade -r 9.1-RELEASE but it does not find a valid repository. How can I solve this issue to move to newer RELEASE and avoid staying on STABLE because I will have to compile/build world and it takes a good while to build and then may have to rebuild all the ports. Thanks in advance for suggestions/advice and words of caution. Best Regards, Antonio Give this a try setenv UNAME_r "9.0-RELEASE" freebsd-update fetch update freebsd-update upgrade -r 9.1-RELEASE ___ 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"
how to change from STABLE to RELEASE?
Dear folks, I am happily running FreeBSD 9.0-STABLE on one of my machines, but I want to move to FreeBSD-RELEASE and use # freebsd-update upgrade -r 9.1-RELEASE but it does not find a valid repository. How can I solve this issue to move to newer RELEASE and avoid staying on STABLE because I will have to compile/build world and it takes a good while to build and then may have to rebuild all the ports. Thanks in advance for suggestions/advice and words of caution. Best Regards, Antonio ___ 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"
poudriere jail stable/0 create via svn: auditdistd user is missing
Hello, # poudriere jail -c -j 9amd64 -v stable/9 -m svn ... -- >>> World build completed on Wed Jan 9 01:32:43 CET 2013 -- >> Starting make installworld ERROR: Required auditdistd user is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /poudriere/jails/9amd64/usr/src. *** Error code 1 Stop in /poudriere/jails/9amd64/usr/src. >> Error: Fail to install world >> Error while creating jail, cleaning up. >> Removing 9amd64 jail...done Any idea to work-around this (in a normal buildworld I would use mergesmaster -p) ? I'm using an old 9-stable from april. Thanks, 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"
last(1) does not work after upgrade to 9.1-STABLE
Colleagues, I have upgraded from 9.0-STABLE to 9.1-STABLE (via make world) and have found out that last(1) does not work any more. From the output of "strings /var/log/utx.log" I guess that the information about recent logins, users, hosts etc is there, but somehow "last" does not show it. The last entries it shows are from the moment before installworld. [sudakov@vas ~] last | head -n3 sudakovpts/4:0 ср 2 янв 13:32 still logged in sudakovpts/5:0 ср 2 янв 13:01 - 13:01 (00:00) sudakovpts/4:0 ср 2 янв 13:01 - 13:19 (00:18) [sudakov@vas ~] What can it mean? -- 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"
Upgrading from 9.0-STABLE to 9.1-RELEASE with freebsd-update?
I've used STABLE for years, but with csup going away, I don't want to deal with adding extra packages, and keeping them unbroken, just to stay up date. Running freebsd-update doesn't work for people running STABLE, and I'm not sure freebsd-update will work properly anyway if I compile world for myself. What's the best way to switch from running STABLE to running the RELEASE channel? ___ 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: following 9-STABLE but getting 9.1-PRERELEASE
> From owner-freebsd-questi...@freebsd.org Mon Dec 31 02:45:09 2012 > Date: Mon, 31 Dec 2012 09:42:03 +0100 (CET) > From: Marco Beishuizen > To: freebsd-questions@freebsd.org > Subject: following 9-STABLE but getting 9.1-PRERELEASE > > Hi, > > I'm following the 9-STABLE branch with svn and just updated my system. But > after booting I noticed that my system is still at 9.1-PRERELEASE, and not > 9.1-STABLE or 9-STABLE. > Surely you're not suggesting someone forgot to lock the horse after the stable escaped? *groan* ___ 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: following 9-STABLE but getting 9.1-PRERELEASE
On Mon, 31 Dec 2012 09:42:03 +0100 (CET) Marco Beishuizen wrote: > Hi, > > I'm following the 9-STABLE branch with svn and just updated my > system. But after booting I noticed that my system is still at > 9.1-PRERELEASE, and not 9.1-STABLE or 9-STABLE. > > Does someone know what happened? Yeah, sys/conf/newvers.sh in stable/9 has not been updated yet. It will happen... -- Herbert ___ 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"
following 9-STABLE but getting 9.1-PRERELEASE
Hi, I'm following the 9-STABLE branch with svn and just updated my system. But after booting I noticed that my system is still at 9.1-PRERELEASE, and not 9.1-STABLE or 9-STABLE. Does someone know what happened? Thanks in advance. Regards, Marco -- To get something done, a committee should consist of no more than three persons, two of them absent. ___ 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-update - To 'Stable'?
On Sun, 25 Nov 2012 12:06:06 +, Karl Pielorz wrote: > > > --On 22 November 2012 17:41 +0100 Polytropon wrote: > > >> I'm looking at switching to 'freebsd-update' - is there an equivalent > >> way to get it to update me to '-STABLE'? > > > > No. The freebsd-update program can only be used to follow > > the RELEASE branch, plus the security updates (RELEASE-pN). > > Following STABLE branch still requires you to update by > > source. > > Ok, as csup is 'deprecated' - I guess what I need to do is move over to > Subversion instead? Sadly, yes. There still is no csup-equivalent (efficient and fast implementation distributed with the base OS) provided yet. And it's not just about "being provided with the OS", but also about nice integration (like /etc/sup/* config files or the option to simply "make update"). > - As 'freebsd-update' is only going to get me release + > security (-pX), not 'stable'. Correct. You _can_ use this to compile your own non-GENERIC kernel, but it will always have the "pre-STABLE" content, just as the rest of /usr/src. > At the moment we have a local host that has the entire FreeBSD source tree > on it - so we can just 'cherry pick' versions we need to update - I'd guess > / hope a similar setup is possible, but with Subversion... It should be possible, as the functionality of CVS and SVN can be seen as quite comparable. -- 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-update - To 'Stable'?
--On 22 November 2012 17:41 +0100 Polytropon wrote: I'm looking at switching to 'freebsd-update' - is there an equivalent way to get it to update me to '-STABLE'? No. The freebsd-update program can only be used to follow the RELEASE branch, plus the security updates (RELEASE-pN). Following STABLE branch still requires you to update by source. Ok, as csup is 'deprecated' - I guess what I need to do is move over to Subversion instead? - As 'freebsd-update' is only going to get me release + security (-pX), not 'stable'. At the moment we have a local host that has the entire FreeBSD source tree on it - so we can just 'cherry pick' versions we need to update - I'd guess / hope a similar setup is possible, but with Subversion... -Karl [Off to look for a setup guide ;)] ___ 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-update - To 'Stable'?
On 11/22/12 17:32, Karl Pielorz wrote: > > Hi, > > I have a number of 9.0-R boxes, some of which I've updated in the past > to 9.0-STABLE (as of the date they were done). > > I'm looking at switching to 'freebsd-update' - is there an equivalent > way to get it to update me to '-STABLE'? freebsd-update works for RELEASE, BETA and RELEASE CANDIDATES, the latter two when announced so. This means you can use freebsd-update to go from 9.0-RELEASE to 9.1-RC3. You wil have to be on RELEASE or RC to be able to do so. > > i.e. If I run this on a 9.0-RELEASE box, I end up with 9.0-RELEASE-p4 > (even though uname says '-p3' - it's apparently -p4. This is because form p3 to p4 the kernel has not been modified and the last p# from newvers.sh is not shown unless you rebuild your kernel. > > I'm guessing that's not the same as if I'd csup'd to 9.0-STABLE on > that day, and rebuilt the world? Right, it is not the same. 9.0-STABLE is at 9.1-PRERELEASE. > > I'd also guess freebsd-update will bring up some more queries / info > if it has to merge any config files (I seem to have been lucky going > from 9.0-R to 9.0-R-p4 nothings been displayed other than 'completed' > - unless I'm doing something wrong :). When going to a new RELEASE you will be prompted. Within the same release I have not seen yet that configuration files get changed. > > Also, does freebsd-update warn you if you need to reboot/rebuild > anything (e.g. the kernel / userland or anything?) Yes it warns you when you have a cutom kernel. There is no need to rebuild world or the GENERIC kernel (unless you want the p# to reflect the actual patchlevel), because freebsd-update takes care of the binaries and the sources also when installed. The whole process is very well documented in the handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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-update - To 'Stable'?
On Thu, 22 Nov 2012 16:32:21 +, Karl Pielorz wrote: > I'm looking at switching to 'freebsd-update' - is there an equivalent way > to get it to update me to '-STABLE'? No. The freebsd-update program can only be used to follow the RELEASE branch, plus the security updates (RELEASE-pN). Following STABLE branch still requires you to update by source. > i.e. If I run this on a 9.0-RELEASE box, I end up with 9.0-RELEASE-p4 (even > though uname says '-p3' - it's apparently -p4. The -pN number will only be changed if the kernel has gotten a change in this security patch run. > I'm guessing that's not the same as if I'd csup'd to 9.0-STABLE on that > day, and rebuilt the world? Correct. STABLE is a development branch (even though as the name suggests, it's stable, not experimental, which would apply to HEAD or CURRENT). > Also, does freebsd-update warn you if you need to reboot/rebuild anything > (e.g. the kernel / userland or anything?) You usually _have_ to reboot the system, as you've just upgraded to a new operating system version. So at least that would be the safest way. :-) Rebuilding is only needed if you run a custom kernel. The userland will be upgraded in a binary way (just as the GENERIC kernel in case you're using it). -- 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-update - To 'Stable'?
Hi, I have a number of 9.0-R boxes, some of which I've updated in the past to 9.0-STABLE (as of the date they were done). I'm looking at switching to 'freebsd-update' - is there an equivalent way to get it to update me to '-STABLE'? i.e. If I run this on a 9.0-RELEASE box, I end up with 9.0-RELEASE-p4 (even though uname says '-p3' - it's apparently -p4. I'm guessing that's not the same as if I'd csup'd to 9.0-STABLE on that day, and rebuilt the world? I'd also guess freebsd-update will bring up some more queries / info if it has to merge any config files (I seem to have been lucky going from 9.0-R to 9.0-R-p4 nothings been displayed other than 'completed' - unless I'm doing something wrong :). Also, does freebsd-update warn you if you need to reboot/rebuild anything (e.g. the kernel / userland or anything?) Thanks, -Karl ___ 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: svn checkout "head" or "stable"
On Fri, 28 Sep 2012, David Noel wrote: Apologies for the spam and the hastily written closing paragraph. I was hoping to end with a heartwarming anecdote that would leave the reader with no choice but to agree that anonymous ssh+svn access would benefit us all. AnonCVS is still of course an option, but with its eventual retirement the addition of an anonymous svn+ssh account would seem fitting, or at least consistent. http://www.freebsd.org/doc/handbook/mirrors-svn.html shows https mirrors. Check out from the https site instead of svn, and you'll be asked to verify the certificate fingerprint the first time: svn co https://svn0.us-west.freebsd.org/ports/head /usr/ports ___ 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: svn checkout "head" or "stable"
On 9/28/12, David Noel wrote: > On 9/28/12, Matthew Seaman wrote: >> On 28/09/2012 20:41, Ed Flecko wrote: >>> David - I'd like to, but every time I try that it prompts me for a >>> password...and I don't know what password it wants??? >> >> That would be the password to a freebsd.org account, which isn't going >> to work for most people on two counts: >> >>* freebsd.org uses SSH keys for authentication, not passwords. >> >>* even if you've got a SSH key, not being a FreeBSD committer you >> probably don't have a freebsd.org account. >> >> For anonymous access, you can use http or svn. Given that anonymous >> access is read-only, there's really not much to be gained from SSH or >> other means of encrypting the connection, either for you, or for the >> FreeBSD servers. It's anonymous, so you don't care about >> authentication. FreeBSD sources are publicly available, so you don't >> care about anyone eavesdropping on the traffic. About the only thing >> you're still exposed to is a man-in-the-middle attack, where someone >> could pose as a FreeBSD server and feed you a trojanned set of sources >> -- but then, you'ld still be exposed in exactly the same way even using >> svn+ssh. In practice, attacks of this type are very (pretty much >> vanishingly) rare. If they do concern you, then use portsnap(8) / >> freebsd-update(8) which has specific cryptographic protection against >> such things. The portsnap and freebsd-update build systems also have >> special access to the master FreeBSD repositories to minimize the >> chances that they themselves could be fed trojanned sources. >> >> Cheers, >> >> Matthew >> >> -- >> Dr Matthew J Seaman MA, D.Phil. >> PGP: http://www.infracaninophile.co.uk/pgpkey > > > MITM-based attacks--and subsequent corrupted sources--are my concern. > It was my understanding that anonymous svn+ssh would prevent this > assuming the host key was properly verified against > http://www.freebsd.org/internal/ssh-keys.asc. > > Recently I've installed from an iso and then manually updated with > pgp-signed security patches. It would certainly be nice to have some > secure source update mechanism though. > Apologies for the spam and the hastily written closing paragraph. I was hoping to end with a heartwarming anecdote that would leave the reader with no choice but to agree that anonymous ssh+svn access would benefit us all. AnonCVS is still of course an option, but with its eventual retirement the addition of an anonymous svn+ssh account would seem fitting, or at least consistent. -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"
Re: svn checkout "head" or "stable"
On 9/28/12, Matthew Seaman wrote: > On 28/09/2012 20:41, Ed Flecko wrote: >> David - I'd like to, but every time I try that it prompts me for a >> password...and I don't know what password it wants??? > > That would be the password to a freebsd.org account, which isn't going > to work for most people on two counts: > >* freebsd.org uses SSH keys for authentication, not passwords. > >* even if you've got a SSH key, not being a FreeBSD committer you > probably don't have a freebsd.org account. > > For anonymous access, you can use http or svn. Given that anonymous > access is read-only, there's really not much to be gained from SSH or > other means of encrypting the connection, either for you, or for the > FreeBSD servers. It's anonymous, so you don't care about > authentication. FreeBSD sources are publicly available, so you don't > care about anyone eavesdropping on the traffic. About the only thing > you're still exposed to is a man-in-the-middle attack, where someone > could pose as a FreeBSD server and feed you a trojanned set of sources > -- but then, you'ld still be exposed in exactly the same way even using > svn+ssh. In practice, attacks of this type are very (pretty much > vanishingly) rare. If they do concern you, then use portsnap(8) / > freebsd-update(8) which has specific cryptographic protection against > such things. The portsnap and freebsd-update build systems also have > special access to the master FreeBSD repositories to minimize the > chances that they themselves could be fed trojanned sources. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey MITM-based attacks--and subsequent corrupted sources--are my concern. It was my understanding that anonymous svn+ssh would prevent this assuming the host key was properly verified against http://www.freebsd.org/internal/ssh-keys.asc. Recently I've installed from an iso and then manually updated with pgp-signed security patches. It would certainly be nice to have some secure source update mechanism though. ___ 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: svn checkout "head" or "stable"
On 28/09/2012 20:41, Ed Flecko wrote: > David - I'd like to, but every time I try that it prompts me for a > password...and I don't know what password it wants??? That would be the password to a freebsd.org account, which isn't going to work for most people on two counts: * freebsd.org uses SSH keys for authentication, not passwords. * even if you've got a SSH key, not being a FreeBSD committer you probably don't have a freebsd.org account. For anonymous access, you can use http or svn. Given that anonymous access is read-only, there's really not much to be gained from SSH or other means of encrypting the connection, either for you, or for the FreeBSD servers. It's anonymous, so you don't care about authentication. FreeBSD sources are publicly available, so you don't care about anyone eavesdropping on the traffic. About the only thing you're still exposed to is a man-in-the-middle attack, where someone could pose as a FreeBSD server and feed you a trojanned set of sources -- but then, you'ld still be exposed in exactly the same way even using svn+ssh. In practice, attacks of this type are very (pretty much vanishingly) rare. If they do concern you, then use portsnap(8) / freebsd-update(8) which has specific cryptographic protection against such things. The portsnap and freebsd-update build systems also have special access to the master FreeBSD repositories to minimize the chances that they themselves could be fed trojanned sources. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: svn checkout "head" or "stable"
On 9/28/12, Ed Flecko wrote: > David - I'd like to, but every time I try that it prompts me for a > password...and I don't know what password it wants??? > > Ed Great question. I'm running into the same issue. I guessed around a bit with no luck: svn/anonsvn... Would anyone on the list be able to set up anonymous svn+ssh access for us? ___ 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: svn checkout "head" or "stable"
David - I'd like to, but every time I try that it prompts me for a password...and I don't know what password it wants??? Ed ___ 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: svn checkout "head" or "stable"
On 9/28/12, Ed Flecko wrote: > Excellent! Thank you all. > > :-) > > So, for ME...does this look right? This will track the latest release > that has the patches applied? > > > svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src > > svn co svn://svn.freebsd.org/ports/releng/9.1 /usr/ports > > svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 /usr/doc > > (I too, only need English docs) > > > > Ed > ___ > 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" > For something as fundamental as source and ports tree updates I'd suggest taking advantage of the available SSH2-wrapper for subversion and securing your line of communication with the repository: svn co svn+ssh://svn.freebsd.org/base/releng/9.1 /usr/src etc.. -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"
Re: svn checkout "head" or "stable"
On Fri, 28 Sep 2012, Alexandre wrote: On Fri, Sep 28, 2012 at 5:51 PM, Ed Flecko wrote: Excellent! Thank you all. :-) So, for ME...does this look right? This will track the latest release that has the patches applied? svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src svn co svn://svn.freebsd.org/ports/releng/9.1 /usr/ports svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 /usr/doc (I too, only need English docs) For ports you are wrong. Use this one : svn co svn://svn.freebsd.org/ports/head /usr/ports You can check here http://svnweb.freebsd.org/ports/ Another way to put this is: "ports are not branched". There is no separate ports tree to go with a release, there is just the same one everybody uses. For doc, I'm not sure I'd go with the branched version. Many of our docs apply to multiple releases, so going with the trunk seems better. Might not make a lot of difference, depending. svn co http://svn.freebsd.org/doc/head/en_US.ISO8859-1 /usr/doc/en_US.ISO8859-1 I think that directory will put them in their normal locations. ___ 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: svn checkout "head" or "stable"
On Fri, Sep 28, 2012 at 5:51 PM, Ed Flecko wrote: > Excellent! Thank you all. > > :-) > > So, for ME...does this look right? This will track the latest release > that has the patches applied? > > > svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src > > svn co svn://svn.freebsd.org/ports/releng/9.1 /usr/ports > > svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 /usr/doc > > (I too, only need English docs) > > > > Ed Hi Ed, For ports you are wrong. Use this one : svn co svn://svn.freebsd.org/ports/head /usr/ports You can check here http://svnweb.freebsd.org/ports/ Regards, Alexandre ___ 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: svn checkout "head" or "stable"
Excellent! Thank you all. :-) So, for ME...does this look right? This will track the latest release that has the patches applied? svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src svn co svn://svn.freebsd.org/ports/releng/9.1 /usr/ports svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 /usr/doc (I too, only need English docs) Ed ___ 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: svn checkout "head" or "stable"
[ Trond Endrestøl wrote on Fri 28.Sep'12 at 12:44:10 +0200 ] > On Fri, 28 Sep 2012 11:28+0100, Jamie Paul Griffin wrote: > > > My question is, does it pull in docs for all languages or can I > > exclude docs in languages that I don't need - I only need en docs. > > Yes, you can check out a subset/subdirectory, e.g.: > > svn co svn://svn.freebsd.org/doc/head/en_US.ISO8859-1 > /path/to/local/working/copy > > svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 > /path/to/local/working/copy Great, thanks for that Trond. Very helpful. Cheers mate. ___ 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: svn checkout "head" or "stable"
On Fri, 28 Sep 2012 11:28+0100, Jamie Paul Griffin wrote: > My question is, does it pull in docs for all languages or can I > exclude docs in languages that I don't need - I only need en docs. Yes, you can check out a subset/subdirectory, e.g.: svn co svn://svn.freebsd.org/doc/head/en_US.ISO8859-1 /path/to/local/working/copy svn co svn://svn.freebsd.org/doc/release/9.1.0/en_US.ISO8859-1 /path/to/local/working/copy -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ freebsd-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: svn checkout "head" or "stable"
[ Trond Endrestøl wrote on Fri 28.Sep'12 at 1:07:57 +0200 ] > On Thu, 27 Sep 2012 15:39-0700, Ed Flecko wrote: > > > Cool...thank you Trond. > > NP. > > > Is that true of the "docs" branch as well, in other words... > > > > svn co svn://svn.freebsd.org/doc/head /usr/doc > > > > works just fine? > > Browsing through http://svnweb.freebsd.org/doc/, indicates > http://svnweb.freebsd.org/doc/head/ being the current branch of the > documentation, with release branches located at > http://svnweb.freebsd.org/doc/release/ and below. > > E.g. http://svnweb.freebsd.org/doc/release/9.1.0/, or > svn://svn.freebsd.org/doc/release/9.1.0, for the upcoming 9.1-RELEASE. > > I've never CVSup'ed nor done any svn co/up ops on doc/head, but you > seem to have got it right. Sorry to jump in on the thread, but I wondered about pulling in the docs using svn. I use svn for base updates and ports, but haven't yet don so the docs. My question is, does it pull in docs for all languages or can I exclude docs in languages that I don't need - I only need en docs. Cheers, Jamie ___ 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: svn checkout "head" or "stable"
Ed Flecko schreef: My goal is to simply have a production server that's fully patched, but I will be running custom kernels (which is why I'm not using freebsd-update). I've seen a lot of subversion references to checking out the "head" branch and the "stable" branch. I understand the "head" branch is the most current, so that's the same as the "current" branch, right? If I understand correctly, "most" people will not follow the "current" branch for production servers. My goal is to have all of the files I need to rebuild my kernel and my system after security updates have been released, therefore I should do something like: svn co svn://svn.freebsd.org/base/stable/9 /usr/src svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports svn co svn://svn.freebsd.org/doc/stable/9 /usr/doc This will give me everything I need to recompile and have a fully patched system, right? I do not make changes to the src, ports, or doc directories. From that point forward, as new security patches are released, I can simply: svn up /usr/src svn up /usr/ports svn up /usr/doc and once again rebuild my kernel and system. Does this sound correct? Ed ___ 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" It sounds correct but is not :D If you use svn co svn://svn.freebsd.org/base/stable/9 /usr/src then you are tracking stable. Stable is a not a release that receives patches. Stable receives code from head(current) that has been tested in Current(head), but did not get real exposure in the stable branch which is now 9. Stable is the code that is altered between releases. So Stable might contain some bugs from head that are only exposed in the current code base. So if you want a production system which only receive patches you need to track release. svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src To sum it up: (please correct me if i am wrong) So for the latest and greatest use head which is FreeBSD 10 Current svn co svn://svn.freebsd.org/base/head /usr/src If you want the stable branch use svn co svn://svn.freebsd.org/base/stable/9 /usr/src This will give you FreeBSD 9 Stable If you want to track release with patches use svn co svn://svn.freebsd.org/base/releng/9.1 /usr/src This will give you FreeBSD 9.1-px where px is the patch level if any. I hope this clearify things a little bit regards Johan ___ 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: svn checkout "head" or "stable"
On Thu, 27 Sep 2012 15:39-0700, Ed Flecko wrote: > Cool...thank you Trond. NP. > Is that true of the "docs" branch as well, in other words... > > svn co svn://svn.freebsd.org/doc/head /usr/doc > > works just fine? Browsing through http://svnweb.freebsd.org/doc/, indicates http://svnweb.freebsd.org/doc/head/ being the current branch of the documentation, with release branches located at http://svnweb.freebsd.org/doc/release/ and below. E.g. http://svnweb.freebsd.org/doc/release/9.1.0/, or svn://svn.freebsd.org/doc/release/9.1.0, for the upcoming 9.1-RELEASE. I've never CVSup'ed nor done any svn co/up ops on doc/head, but you seem to have got it right. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ freebsd-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: svn checkout "head" or "stable"
Cool...thank you Trond. Is that true of the "docs" branch as well, in other words... svn co svn://svn.freebsd.org/doc/head /usr/doc works just fine? Ed ___ 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: svn checkout "head" or "stable"
On Thu, 27 Sep 2012 15:03-0700, Ed Flecko wrote: > My goal is to simply have a production server that's fully patched, > but I will be running custom kernels (which is why I'm not using > freebsd-update). I've seen a lot of subversion references to checking > out the "head" branch and the "stable" branch. > > I understand the "head" branch is the most current, so that's the same > as the "current" branch, right? > > If I understand correctly, "most" people will not follow the "current" > branch for production servers. > > My goal is to have all of the files I need to rebuild my kernel and my > system after security updates have been released, therefore I should > do something like: > > svn co svn://svn.freebsd.org/base/stable/9 /usr/src > > svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports The ports tree resides in ports/head no matter what branch from the main source tree you check out, i.e.: svn co svn://svn.freebsd.org/ports/head /usr/ports > svn co svn://svn.freebsd.org/doc/stable/9 /usr/doc > > This will give me everything I need to recompile and have a fully > patched system, right? > > I do not make changes to the src, ports, or doc directories. From that > point forward, as new security patches are released, I can simply: > > svn up /usr/src > > svn up /usr/ports > > svn up /usr/doc > > and once again rebuild my kernel and system. > > Does this sound correct? Yes. -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
svn checkout "head" or "stable"
My goal is to simply have a production server that's fully patched, but I will be running custom kernels (which is why I'm not using freebsd-update). I've seen a lot of subversion references to checking out the "head" branch and the "stable" branch. I understand the "head" branch is the most current, so that's the same as the "current" branch, right? If I understand correctly, "most" people will not follow the "current" branch for production servers. My goal is to have all of the files I need to rebuild my kernel and my system after security updates have been released, therefore I should do something like: svn co svn://svn.freebsd.org/base/stable/9 /usr/src svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports svn co svn://svn.freebsd.org/doc/stable/9 /usr/doc This will give me everything I need to recompile and have a fully patched system, right? I do not make changes to the src, ports, or doc directories. From that point forward, as new security patches are released, I can simply: svn up /usr/src svn up /usr/ports svn up /usr/doc and once again rebuild my kernel and system. Does this sound correct? Ed ___ 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"
svn commit: r240807 - in stable/9/contrib/bind9: . lib/dns lib/dns/include/dns
Hi This morning at about 7 am, I noticed to commits to stable/9 that I wanted to pull in and so did and then rebuilt from source. Just now, I noticed this: svn commit: r240807 - in stable/9/contrib/bind9: . lib/dns lib/dns/include/dns I really can't be bother to requildworld again, can I just go into /usr/src/contrib/bind9 and make, build, install that bit? It does affect me do I should really update to this commit, up to now i've only rebuilt the entire system from source rather than individual code commits. Cheers, Jamie ___ 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: 8.3 stable or 9.0 stable amd64 iso with mfi driver changes of May 18, 2012
Kevin, Thank you for your response. It is great to get confirmation and I will try with 9.1-RC1 I DO have on board Broadcom 5720 NIC. Nice to know what my next problem is likely to be. Hopefully that will be easy to solve if I install another NIC card. Thanks! Jean Jean Christofferson je...@relevantpower.com Relevant Power, Inc. www.relevanttools.com On Sep 14, 2012, at 6:14 PM, kpn...@pobox.com wrote: On Fri, Sep 14, 2012 at 04:45:49PM -0700, Jean Christofferson wrote: I am trying to install FreeBSD stable - either 8.3 or 9.0 - on a Dell 420 with Perc H310 LSI PCI Express SAS Raid controllers. Although the physical disks are present and recognized by the BIOS the sysinstall does not see the disks. I think the issue is mfi driver and was added to the stable release May 18, 2012. Yup, the 12G machines came out when the paint was drying on 8.3. So there isn't a -stable release with the updated driver. The new mfi driver is in 9.1-RC1 if you are OK with a pre-release. I hope you don't have the Broadcom 5720 NIC like the R620. The FreeBSD driver (bge) isn't finished yet. At least, I don't remember seeing it go into the tree. It's known to _not_ work on the R620 and I believe R720. -- Kevin P. Nealhttp://www.pobox.com/ ~kpn/ "Nonbelievers found it difficult to defend their position in \ the presense of a working computer." -- a DEC Jensen paper ___ 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"
8.3 stable or 9.0 stable amd64 iso with mfi driver changes of May 18, 2012
I am trying to install FreeBSD stable - either 8.3 or 9.0 - on a Dell 420 with Perc H310 LSI PCI Express SAS Rain controllers. Although the physical disks are present and recognized by the BIOS the sysinstall does not see the disks. I think the issue is mfi driver and was added to the stable release May 18, 2012. http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+8.3-RELEASE I do not have an environment to download the source and make my own installation disk. The 8.3 image on the ftp site is dated April 9, 2012 and the 9.0 is Jan 2012. Is there some place I can download an amd63 iso that was includes the mfi driver update done on May 18, 2012? Or perhaps that is not really the issue at all - any help that anyone can provide will be welcome! Thanks, Jean Jean Christofferson je...@relevantpower.com Relevant Power, Inc. www.relevanttools.com 415-472-8400 ___ 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: 8-STABLE base BIND version number typo ?
I seem to have seen no replies. Would anyone kindly confirm they've got the same problem so we can get a PR filled ? # named -V BIND 9.6.-ESV-R5-P1 built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' # uname -a FreeBSD xxx.xx 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Mon Jun 11 23:52:38 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 ___ 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: 8-STABLE base BIND version number typo ?
On 27 August 2012 10:11, Damien Fleuriot wrote: > Hello list, > > > > We're currently running Nessus PCI DSS scans on our infrastructure to > eliminate known vulnerabilities and problems. > > The scan reports that my version of BIND is vulnerable to exploits I > *know* it isn't. > > The problem, to me, seems to be with the version number as reported by > named -V : > BIND 9.6.-ESV-R7-P2 built with '--prefix=/usr' > '--infodir=/usr/share/info' '--mandir=/usr/share/man' > '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' > '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' > '--without-libxml2' > > (notice the .- notation) > > > This is the base's BIND running on 8.3-STABLE 64 bits compiled and > built on 22/08/12 : > FreeBSD pf1-dmz-gs.[snip] 8.3-STABLE FreeBSD 8.3-STABLE #2: Wed Aug 22 > 10:41:47 CEST 2012 > > > I have verified that building the exact same version from the ports, > at /usr/ports/dns/bind96 yields the correct version number and the > vulnerabilities are no longer reported by the scan, which uses BIND's > version number as a reference. > > > > Has anyone else noticed the same oddity, that I might fill a PR ? Hello list, I seem to have seen no replies. Would anyone kindly confirm they've got the same problem so we can get a PR filled ? ___ 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"
8-STABLE base BIND version number typo ?
Hello list, We're currently running Nessus PCI DSS scans on our infrastructure to eliminate known vulnerabilities and problems. The scan reports that my version of BIND is vulnerable to exploits I *know* it isn't. The problem, to me, seems to be with the version number as reported by named -V : BIND 9.6.-ESV-R7-P2 built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' (notice the .- notation) This is the base's BIND running on 8.3-STABLE 64 bits compiled and built on 22/08/12 : FreeBSD pf1-dmz-gs.[snip] 8.3-STABLE FreeBSD 8.3-STABLE #2: Wed Aug 22 10:41:47 CEST 2012 I have verified that building the exact same version from the ports, at /usr/ports/dns/bind96 yields the correct version number and the vulnerabilities are no longer reported by the scan, which uses BIND's version number as a reference. Has anyone else noticed the same oddity, that I might fill a PR ? ___ 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"
Problem with cvsup since 9.0-STABLE FreeBSD 9.0-STABLE #225 r229960M
TreeList failed: Error in "/usr/local/etc/cvsup/sup/cvsroot-all/checkouts.cvs:RELENG_9": Bad header line. Delete it and try again. I deleted that above mentioned file before running cvsup. I've been using the configuration file for many years with no changes and don't normally check because it has never failed me. Any suggestions appreciated. ed My cvs-supfile contains: *default tag=RELENG_9 *default host=cvsup15.freebsd.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs *default delete use-rel-suffix src-all cvsroot-all ___ 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 Stable production version.
On 25/07/2012 13:13, Jerry wrote: On Wed, 25 Jul 2012 13:19:53 +0200 Damien Fleuriot articulated: I'd say it's a matter of personal preference. We're mostly running 8.3 in production here. I've recently installed 9-STABLE servers to try them out and fill PRs if I get problems. I would encourage you to use 9-STABLE so that you may do the same and ensure the stability of future releases. I would agree with that philosophy up to a point. It is definitely a matter of personal preference; however, for myself, I NEVER install version X.0 of any software if said software is to be used in a mission critical situation. I always wait until X.1 is released. If possible in your case, would it be feasible to wait until 9.1 is released? You can gather some info on it here: <http://www.freebsd.org/releases/9.1R/schedule.html>. As usual, any correlation between the expected release date and the actual date is purely coincidental. Just my 2¢ on the matter. not disagreeing per se..but just a reminder that with the excellent freebsd-update you get updates to 9.0 quickly ( i hadn't realised there was 61 already) from a new install earlier tonight Inspecting system... done. Preparing to download files... done. Fetching 61 patches.102030405060 done. Paul. ___ 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 Stable production version.
I finally decided to take off my FreeBSD 7.2 server which is onlin esince 2009. I will go for a new FreeBSD version and will move out all data. you mean just new freebsd or new server? if first there is no need to move data at all Which version do you recommend? Shall I go for 9 ? or 8.3 is still more fit for a production and bsns server ? i use 8.3 ___ 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 Stable production version.
8.3 or 9.1. Using 9.0 when 9.1 is behind the corner is going backwards IMHO. or 9-STABLE if you want your system evolving up to release, which is nice because you can catch and solve all possible problems one at the time, and not be overwhelmed upgrading only to RELEASE. -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-Stable-production-version-tp5729696p5729739.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: FreeBSD Stable production version.
Hi, On Wed, 25 Jul 2012 13:19:53 +0200 Damien Fleuriot wrote: > On 7/25/12 1:13 PM, Marwan Sultan wrote: > > > > Hello all and Good Morning, Afternoon or evening :) > > > > I finally decided to take off my FreeBSD 7.2 server which is onlin > > esince 2009. > > I will go for a new FreeBSD version and will move out all data. > > > > My Server is mainly is a MAIL server, sendmail. > > and ofcourse few websites, data.etc.. > > > > Which version do you recommend? > > Shall I go for 9 ? > > or 8.3 is still more fit for a production and bsns server ? > > > > > I'd say it's a matter of personal preference. > > We're mostly running 8.3 in production here. > I do not wonder. This is the best choice. But I must say that I moved my machines now all to 10 and I am surprised how robust it already is. If robustness is the main concern, I would still recommend 8.x. Erich ___ 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 Stable production version.
On Wed, Jul 25, 2012 at 3:24 PM, Marwan Sultan wrote: > > Well, I also like your philosophy of waiting x.1 ! > its a very good point. > > Maybe 8.3-R would be the best. > > I will wait to hear more comments. > > For cowards, yes! Whoever said that -RELEASE is bad is a joker, too. Now, what the hell do you think can go so wrong on a Mail server running Sendmail and Apache? Network stack?? -- 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: FreeBSD Stable production version.
While I participate in this philosophy, a very good point was made on this list that if everyone waits for x.1 , then x.1 will just be riddled with all the bugs that nobody (or only a select few) found in x.0 That is the point that decided me to get 9-STABLE for 2 of our new firewall boxes. On 7/25/12 2:24 PM, Marwan Sultan wrote: > > Well, I also like your philosophy of waiting x.1 ! > its a very good point. > > Maybe 8.3-R would be the best. > > I will wait to hear more comments. > > >> Date: Wed, 25 Jul 2012 08:13:28 -0400 >> From: je...@seibercom.net >> To: freebsd-questions@freebsd.org >> Subject: Re: FreeBSD Stable production version. >> >> On Wed, 25 Jul 2012 13:19:53 +0200 >> Damien Fleuriot articulated: >> >>> I'd say it's a matter of personal preference. >>> >>> We're mostly running 8.3 in production here. >>> >>> I've recently installed 9-STABLE servers to try them out and fill PRs >>> if I get problems. >>> >>> I would encourage you to use 9-STABLE so that you may do the same and >>> ensure the stability of future releases. >> >> I would agree with that philosophy up to a point. It is definitely a >> matter of personal preference; however, for myself, I NEVER install >> version X.0 of any software if said software is to be used in a mission >> critical situation. I always wait until X.1 is released. If possible in >> your case, would it be feasible to wait until 9.1 is released? You >> can gather some info on it here: >> <http://www.freebsd.org/releases/9.1R/schedule.html>. As usual, any >> correlation between the expected release date and the actual date is >> purely coincidental. Just my 2¢ on the matter. >> >> -- >> Jerry ♔ >> >> Disclaimer: off-list followups get on-list replies or get ignored. >> Please do not ignore the Reply-To header. >> __ >> If you steal from one author it's plagiarism; if you steal from >> many it's research. >> >> Wilson Mizner > > > > > ___ > 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: FreeBSD Stable production version.
Well, I also like your philosophy of waiting x.1 ! its a very good point. Maybe 8.3-R would be the best. I will wait to hear more comments. > Date: Wed, 25 Jul 2012 08:13:28 -0400 > From: je...@seibercom.net > To: freebsd-questions@freebsd.org > Subject: Re: FreeBSD Stable production version. > > On Wed, 25 Jul 2012 13:19:53 +0200 > Damien Fleuriot articulated: > > > I'd say it's a matter of personal preference. > > > > We're mostly running 8.3 in production here. > > > > I've recently installed 9-STABLE servers to try them out and fill PRs > > if I get problems. > > > > I would encourage you to use 9-STABLE so that you may do the same and > > ensure the stability of future releases. > > I would agree with that philosophy up to a point. It is definitely a > matter of personal preference; however, for myself, I NEVER install > version X.0 of any software if said software is to be used in a mission > critical situation. I always wait until X.1 is released. If possible in > your case, would it be feasible to wait until 9.1 is released? You > can gather some info on it here: > <http://www.freebsd.org/releases/9.1R/schedule.html>. As usual, any > correlation between the expected release date and the actual date is > purely coincidental. Just my 2¢ on the matter. > > -- > Jerry ♔ > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __ > If you steal from one author it's plagiarism; if you steal from > many it's research. > > Wilson Mizner ___ 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 Stable production version.
On Wed, 25 Jul 2012 13:19:53 +0200 Damien Fleuriot articulated: > I'd say it's a matter of personal preference. > > We're mostly running 8.3 in production here. > > I've recently installed 9-STABLE servers to try them out and fill PRs > if I get problems. > > I would encourage you to use 9-STABLE so that you may do the same and > ensure the stability of future releases. I would agree with that philosophy up to a point. It is definitely a matter of personal preference; however, for myself, I NEVER install version X.0 of any software if said software is to be used in a mission critical situation. I always wait until X.1 is released. If possible in your case, would it be feasible to wait until 9.1 is released? You can gather some info on it here: <http://www.freebsd.org/releases/9.1R/schedule.html>. As usual, any correlation between the expected release date and the actual date is purely coincidental. Just my 2¢ on the matter. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ If you steal from one author it's plagiarism; if you steal from many it's research. Wilson Mizner signature.asc Description: PGP signature
Re: FreeBSD Stable production version.
On 7/25/12 1:13 PM, Marwan Sultan wrote: > > Hello all and Good Morning, Afternoon or evening :) > > I finally decided to take off my FreeBSD 7.2 server which is onlin esince > 2009. > > I will go for a new FreeBSD version and will move out all data. > > My Server is mainly is a MAIL server, sendmail. > and ofcourse few websites, data.etc.. > > Which version do you recommend? > Shall I go for 9 ? > or 8.3 is still more fit for a production and bsns server ? > I'd say it's a matter of personal preference. We're mostly running 8.3 in production here. I've recently installed 9-STABLE servers to try them out and fill PRs if I get problems. I would encourage you to use 9-STABLE so that you may do the same and ensure the stability of future releases. ___ 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 Stable production version.
Hello all and Good Morning, Afternoon or evening :) I finally decided to take off my FreeBSD 7.2 server which is onlin esince 2009. I will go for a new FreeBSD version and will move out all data. My Server is mainly is a MAIL server, sendmail. and ofcourse few websites, data.etc.. Which version do you recommend? Shall I go for 9 ? or 8.3 is still more fit for a production and bsns server ? Thank you. -marwan Sultan ___ 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 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer wrote: > On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: >> Hi All, >> >> I have 2 hosts, HP DL360 G8 and Dell R620. Both have the >> X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD >> 8-STABLE image. The Dell displays the following in dmesg and we are >> unable to configure the ix0 or ix1 interfaces where the HP works just >> fine. Wondering if anyone else has experienced this? >> >> pci4: at device 0.0 (no driver attached) >> pci4: at device 0.1 (no driver attached) > > Please see > > http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html > > it may be of some assistance. It looks like adding the Dell specific > PCI IDs may be all thats required. We removed an Intel branded equivalent from the DL360 and tried it in the R620. It detected it no problem. Only problem was we could not see it in the BIOS, not a huge deal to us. -- Rick Miller ___ 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 8-STABLE on R620 w/ X520-DA2/Intel 82599
Be patient, a new version will hit HEAD soon with the ID added. Jack On Fri, Jun 29, 2012 at 9:35 AM, Rick Miller wrote: > On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer wrote: > > On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: > >> Hi All, > >> > >> I have 2 hosts, HP DL360 G8 and Dell R620. Both have the > >> X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD > >> 8-STABLE image. The Dell displays the following in dmesg and we are > >> unable to configure the ix0 or ix1 interfaces where the HP works just > >> fine. Wondering if anyone else has experienced this? > >> > >> pci4: at device 0.0 (no driver attached) > >> pci4: at device 0.1 (no driver attached) > > > > Please see > > > > http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html > > > > it may be of some assistance. It looks like adding the Dell specific > > PCI IDs may be all thats required. > > Hrmm, very interesting indeed. > > How do I identify if/when/where the source has been updated? > > -- > Take care > Rick Miller > ___ > freebsd-sta...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-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: FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer wrote: > On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: >> Hi All, >> >> I have 2 hosts, HP DL360 G8 and Dell R620. Both have the >> X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD >> 8-STABLE image. The Dell displays the following in dmesg and we are >> unable to configure the ix0 or ix1 interfaces where the HP works just >> fine. Wondering if anyone else has experienced this? >> >> pci4: at device 0.0 (no driver attached) >> pci4: at device 0.1 (no driver attached) > > Please see > > http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html > > it may be of some assistance. It looks like adding the Dell specific > PCI IDs may be all thats required. Hrmm, very interesting indeed. How do I identify if/when/where the source has been updated? -- Take care Rick Miller ___ 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 8-STABLE on R620 w/ X520-DA2/Intel 82599
On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote: > Hi All, > > I have 2 hosts, HP DL360 G8 and Dell R620. Both have the > X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD > 8-STABLE image. The Dell displays the following in dmesg and we are > unable to configure the ix0 or ix1 interfaces where the HP works just > fine. Wondering if anyone else has experienced this? > > pci4: at device 0.0 (no driver attached) > pci4: at device 0.1 (no driver attached) Please see http://lists.freebsd.org/pipermail/freebsd-net/2012-June/032579.html it may be of some assistance. It looks like adding the Dell specific PCI IDs may be all thats required. Gary ___ 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 8-STABLE on R620 w/ X520-DA2/Intel 82599
Please post the output of pciconf -lvc for these devices. -Andrew On Jun 29, 2012, at 10:50 AM, Rick Miller wrote: > Hi All, > > I have 2 hosts, HP DL360 G8 and Dell R620. Both have the > X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD > 8-STABLE image. The Dell displays the following in dmesg and we are > unable to configure the ix0 or ix1 interfaces where the HP works just > fine. Wondering if anyone else has experienced this? > > pci4: at device 0.0 (no driver attached) > pci4: at device 0.1 (no driver attached) > > > -- > Take care > Rick Miller > ___ > freebsd-sta...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Andrew Boyerabo...@averesystems.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"
FreeBSD 8-STABLE on R620 w/ X520-DA2/Intel 82599
Hi All, I have 2 hosts, HP DL360 G8 and Dell R620. Both have the X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD 8-STABLE image. The Dell displays the following in dmesg and we are unable to configure the ix0 or ix1 interfaces where the HP works just fine. Wondering if anyone else has experienced this? pci4: at device 0.0 (no driver attached) pci4: at device 0.1 (no driver attached) -- Take care Rick Miller ___ 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: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
Thanks You, now I understand how badly it was broken (the config of course), I confirm that using the config You send everything works like a charm now, for the record, here is mine complete config: | default: | set log Phase Chat LCP IPCP CCP tun command | | 3g: | set device /dev/cuaU0 | set speed 921600 | | set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ | \"\" AT OK-AT-OK \ | AT+CFUN=1 OK \ | AT+COPS=0 OK \ | AT+CGDCONT=1,\\\"IP\\\",\\\"www.plusgsm.pl\\\" OK \ | \dATDT\\T TIMEOUT 40 CONNECT" | | set logout "ABORT BUSY ABORT ERROR TIMEOUT 30 \"\" +++ATH O ATH OK" | | set phone *99\# | set timeout 300 | set ifaddr 10.64.64.64/0 10.64.64.64/0 255.255.255.255 0.0.0.0 | add default HISADDR | enable dns | disable ipv6cp I am going to send update to the PR to close it ;) Thanks again, vermaden "Matthias Apitz" pisze: > El día Friday, June 29, 2012 a las 08:02:17AM +0200, vermaden escribió: > > > > I said this already: the /etc/ppp/ppp.conf file you are > > > using is completely broken and the log matches this; > > > > > > what should these AT cmds do in the section of 3g: > > > > > > 3g: > > > set device /dev/cuaU0 > > > set speed 38400 > > > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > > > add default HISADDR > > > term > > > AT+CFUN=1 > > > AT+CGDCONT=1,"IP","www.plusgsm.pl" > > > ATD*99# > > > > > > matthias > > > > I did not knew that its broken, I used the '3g' > > profile to connect, like that: # ppp -ddial 3g > > > > It worked very well without errors on 9.0-RELEASE > > and it stopped working after the update to the > > 9-STABLE, what is broken there? > > I can't imagine that 9-STABLE delivers such a broken file (already > because the "www.plusgsm.pl" entry in your file); I do not know how you > did the update and if maybe this is the result of some kind of broken > merging; I'm attaching the original file out of SVM (CURRENT) and mine > which have a working entry 'umts'; try to rebuild from both a workin one > by hand; > > matthias > > -- > Matthias Apitz > e - w http://www.unixarea.de/ > UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 > -- ... ___ 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: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
El día Friday, June 29, 2012 a las 08:02:17AM +0200, vermaden escribió: > > I said this already: the /etc/ppp/ppp.conf file you are > > using is completely broken and the log matches this; > > > > what should these AT cmds do in the section of 3g: > > > > 3g: > > set device /dev/cuaU0 > > set speed 38400 > > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > > add default HISADDR > > term > > AT+CFUN=1 > > AT+CGDCONT=1,"IP","www.plusgsm.pl" > > ATD*99# > > > > matthias > > I did not knew that its broken, I used the '3g' > profile to connect, like that: # ppp -ddial 3g > > It worked very well without errors on 9.0-RELEASE > and it stopped working after the update to the > 9-STABLE, what is broken there? I can't imagine that 9-STABLE delivers such a broken file (already because the "www.plusgsm.pl" entry in your file); I do not know how you did the update and if maybe this is the result of some kind of broken merging; I'm attaching the original file out of SVM (CURRENT) and mine which have a working entry 'umts'; try to rebuild from both a workin one by hand; matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 # # PPP Sample Configuration File # Originally written by Toshiharu OHNO # Simplified 5/14/1999 by ws...@cdrom.com # # See /usr/share/examples/ppp/ for some examples # # $FreeBSD: head/etc/ppp/ppp.conf 203943 2010-02-16 01:07:06Z jkim $ # default: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION # Ensure that "device" references the correct serial port # for your modem. (cuau0 = COM1, cuau1 = COM2) # set device /dev/cuau1 set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT" set timeout 180# 3 minute idle timer (the default) enable dns # request DNS info (for resolv.conf) papchap: # # edit the next three lines and replace the items in caps with # the values which have been assigned by your ISP. # set phone PHONE_NUM set authname USERNAME set authkey PASSWORD set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR# Add a (sticky) default route # # $Id: ppp.conf,v 1.1 2011/11/20 06:07:03 guru Exp $ # # APN (AT+CGDCONT value): pinternet.interkom.de # # # default: set log Phase Chat LCP IPCP CCP tun command umts: set device /dev/cuaU0.0 # device name in CURRENT set speed 921600 # set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATZ OK \ AT+CFUN=1 OK \ AT+COPS=0 OK \ AT+CGDCONT=1,\\\"IP\\\",\\\"pinternet.interkom.de\\\" OK \ \\dATDT\\T TIMEOUT 40 CONNECT" set logout "ABORT BUSY ABORT ERROR TIMEOUT 30 \"\" +++ATH O ATH OK" # NAT (not used by me) # nat enable yes # alias enable yes # nat port tcp 192.168.0.0:ftp ftp # nat port tcp 192.168.0.0:http http nat enable yes nat port udp 127.0.0.1:1024-1030 1024-1030 nat port tcp 127.0.0.1:22 22 set phone *99*1\# set authname "x" set authkey "x" set timeout 300 set ifaddr 10.64.64.64/0 10.64.64.64/0 255.255.255.255 0.0.0.0 # add default HISADDR# Add a (sticky) default route enable dns disable ipv6cp # disable deflate # disable pred1 ___ 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: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
Hi, > Did it perhaps create more serial ports for you that were > not there before ? What is the output of ls -l /dev/cuaU* > > ---Mike # ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 155 2012.06.29 06:42 /dev/cuaU0 crw-rw 1 uucp dialer0, 156 2012.06.29 06:42 /dev/cuaU0.init crw-rw 1 uucp dialer0, 157 2012.06.29 06:42 /dev/cuaU0.lock crw-rw 1 uucp dialer0, 161 2012.06.29 07:55 /dev/cuaU1 crw-rw 1 uucp dialer0, 162 2012.06.29 06:42 /dev/cuaU1.init crw-rw 1 uucp dialer0, 163 2012.06.29 06:42 /dev/cuaU1.lock I have tried both cuaU0 and cuaU1 but same result. > I said this already: the /etc/ppp/ppp.conf file you are > using is completely broken and the log matches this; > > what should these AT cmds do in the section of 3g: > > 3g: > set device /dev/cuaU0 > set speed 38400 > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > add default HISADDR > term > AT+CFUN=1 > AT+CGDCONT=1,"IP","www.plusgsm.pl" > ATD*99# > > matthias I did not knew that its broken, I used the '3g' profile to connect, like that: # ppp -ddial 3g It worked very well without errors on 9.0-RELEASE and it stopped working after the update to the 9-STABLE, what is broken there? Regards, vermaden -- ... ___ 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: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
El día Thursday, June 28, 2012 a las 07:54:48AM +0200, vermaden escribió: > Hi, > > at the 9.0-RELEASE I have had fully working ppp/3g connection via the > Dell 5530 modem in my Dell Latitude E6400 laptop. After I upgraded > to 9-STABLE r237458 it does not work any more. > > Were there any significant changes in 9-STABLE that broke it? > > Here is more detailed info: > http://freebsd.org/cgi/query-pr.cgi?pr=169459 I said this already: the /etc/ppp/ppp.conf file you are using is completely broken and the log matches this; what should these AT cmds do in the section of 3g: 3g: set device /dev/cuaU0 set speed 38400 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 add default HISADDR term AT+CFUN=1 AT+CGDCONT=1,"IP","www.plusgsm.pl" ATD*99# matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
On 6/28/2012 1:54 AM, vermaden wrote: > Hi, > > at the 9.0-RELEASE I have had fully working ppp/3g connection via the > Dell 5530 modem in my Dell Latitude E6400 laptop. After I upgraded > to 9-STABLE r237458 it does not work any more. > > Were there any significant changes in 9-STABLE that broke it? Did it perhaps create more serial ports for you that were not there before ? What is the output of ls -l /dev/cuaU* ---Mike > > Here is more detailed info: > http://freebsd.org/cgi/query-pr.cgi?pr=169459 > > Regards, > vermaden -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.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"
umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
Hi, at the 9.0-RELEASE I have had fully working ppp/3g connection via the Dell 5530 modem in my Dell Latitude E6400 laptop. After I upgraded to 9-STABLE r237458 it does not work any more. Were there any significant changes in 9-STABLE that broke it? Here is more detailed info: http://freebsd.org/cgi/query-pr.cgi?pr=169459 Regards, vermaden -- ... ___ 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: Intel X520-DA2 Supported in stable/8?
Glad you figured it out. Cheers, Jack On Mon, Jun 25, 2012 at 3:52 PM, Rick Miller wrote: > Turns out the gbic in the switch was bad...I didn't think there was a > problem on the host, but you all still gave me some good info. I > appreciate it! > > > > On 6/25/12, Rick Miller wrote: > > On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel wrote: > >> Would probably be good to take care of the storm threshold if you > >> haven't, > >> set it to 0 > >> and you disable the check, that's what we do internally. As for the > >> queues > >> and number > >> of descriptors, that's kind of up to you, different work loads and > >> environments work best > >> with different setups. > >> > >> Hopefully, when you get rid of the rx ring setup failure you will get > >> things > >> working. > > > > Thanks, Jack. I did get rid of the rx ring failure. Link status > > still shows no carrier. I think everything looks right from the > > host's perspective. > > > > -- > > Take care > > Rick Miller > > > > -- > Sent from my mobile device > > Take care > Rick Miller > ___ 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: Intel X520-DA2 Supported in stable/8?
Turns out the gbic in the switch was bad...I didn't think there was a problem on the host, but you all still gave me some good info. I appreciate it! On 6/25/12, Rick Miller wrote: > On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel wrote: >> Would probably be good to take care of the storm threshold if you >> haven't, >> set it to 0 >> and you disable the check, that's what we do internally. As for the >> queues >> and number >> of descriptors, that's kind of up to you, different work loads and >> environments work best >> with different setups. >> >> Hopefully, when you get rid of the rx ring setup failure you will get >> things >> working. > > Thanks, Jack. I did get rid of the rx ring failure. Link status > still shows no carrier. I think everything looks right from the > host's perspective. > > -- > Take care > Rick Miller > -- Sent from my mobile device Take care Rick Miller ___ 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: Intel X520-DA2 Supported in stable/8?
On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel wrote: > Would probably be good to take care of the storm threshold if you haven't, > set it to 0 > and you disable the check, that's what we do internally. As for the queues > and number > of descriptors, that's kind of up to you, different work loads and > environments work best > with different setups. > > Hopefully, when you get rid of the rx ring setup failure you will get things > working. Thanks, Jack. I did get rid of the rx ring failure. Link status still shows no carrier. I think everything looks right from the host's perspective. -- Take care Rick Miller ___ 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"
