Re: x.0 RELASE isn't for production.
On Fri, Oct 14, 2011 at 10:55 AM, Pavel Timofeev wrote: > That's what most people think. > I think we hurry. Imo, BETA/RC period for !NEW! STABLE branch should be > longer. Six months, for example. > New STABLE branch is very important! IMHO different OS releases (Unix or not) are usually at the state of FreeBSD current regarding stability. FreeBSD late BETA and early RC are usually very stable. Therefore the approximate one month period between the first beta and the release is adequate time. Many users are reluctant to follow stable because they have to go through the wolrd && kernel procedure. Since freebsd-update exists as a means of binary upgrading a system through releases, I don't think that it would be a bad idea to be able to use is for stable as well. Let's assume that we would have monthly minor releases something like 9.0.1, 9.0.2 etc. That could ease the fear of .0 release. This is coming from someone who is using current all the time for workstations and stable for production servers and never uses freebsd-update! Best Regards -- George Kontostanos aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Use of newest version number such as 10.0 instead of current
On Fri, Nov 11, 2011 at 4:39 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > Chuck Burns wrote: >> >> On Friday, November 11, 2011 08:17:52 AM you wrote: >> -snip- >>> >>> My sentence is NOT about "Current" , but 9.0 RC1 . >>> Perhaps , you will NOT say , if a person is NOT knowledgeable , he should >>> NOT use 9.0 RC1 . >>> >> >> If you use a proper RC, then pkg_add will work until a new RC, and since >> there >> is no binary upgrade path for anything other than releases, you will need >> to >> reinstall, with the newly released RC. > > You can use freebsd-update for RC upgrades too! > >> -snip- >>> >>> Up to now , my most disappointed situation is that , there is NO any >>> tendency to >>> lower required expertise level to use FreeBSD . >>> Such an approach is confining FreeBSD to a small number of elite users >>> when compared to millions of Linux users let alone hundred millions of >>> some other operating systems which they are approaching to billions when >>> version users are summed in spite of paying money also . >> >> GhostBSD, PCBSD are two options for "lower expertise" and, as such, are >> billed >> as desktop versions of FreeBSD. >> >> FreeBSD itself (as well as the other BSDs) is a minimalistic OS, where you >> can >> build your own system, making it either into a server, workstation, or >> even >> into a desktop system if you so desire. >> >> If you want something with point-n-click ease of use, go use one of the >> two >> desktop-oriented versions. >> >> Both GhostBSD, and PCBSD are just a desktop environment built on top of >> FreeBSD. PCBSD even has a 9.0 RC out now as well, if you're into testing. >> >> PCBSD uses the kde environment, and GhostBSD uses the gnome 2.32 >> environment. >> If you want something else, feel free to create your own. There is nothing >> in >> the BSD license that prevents you from doing that. >> >> Instead of complaining that SOMEONE ELSE should do something that YOU want >> done, why not just do it yourself. >> >> In other words, put up, or shut up. :) > > Really, this is not a proper worded answer to someone who just tried to > request some more friendliness to new users and increase our user base. > > It doesn't metter if there are some other "freebsd based" projects. FreeBSD > it-self has a problem - fewer users = fewer manufacturers will support > FreeBSD (drivers). > > Miroslav Lachman > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > I agree 100%. The more people follow current the better releases we will have in the future. Sure current in not for the beginner, you will need to be able to compile world and kernel and produce debug symbols. That is expected. But maybe we should keep an open mind into ideas and not condemn them immediately. -- George Kontostanos aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Use of newest version number such as 10.0 instead of current
On Fri, Nov 11, 2011 at 7:29 PM, Benjamin Kaduk wrote: > On Fri, 11 Nov 2011, Mehmet Erol Sanliturk wrote: > >> Dear all , >> >> Instead of using Current and then renaming everything for a new version >> number , >> is it not possible to use the newest version number in place of Current >> when it is branched . >> >> Such a change will prevent unnecessary renaming problems . >> >> >> For everyone , it i very easy to understand that 10.0 is the latest , >> therefore the current one . >> >> The current may be used as a symbolic link to the newest version number , >> such as used by Debian . >> >> >> For example , for FreeBSD 9.0 RC1 , the ports directory name was >> >> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-current/Latest/ >> >> >> which is NOT available now , and >> >> >> pkg_add -r * >> >> is giving error about directory not found . >> >> >> This is preventing testing and / or using efforts . >> >> >> I know , it is possible to rename local link names , but >> everyone is not so much knowledgeable . > > I'm not sure I understand your proposal. > In a month (er, two. well, maybe three) when 9.0 is released, do you > propose that the svn HEAD be called: > (a) 10.0 > (b) 9-CURRENT > (c) CURRENT > (d) something else > > I do not realy care for either (a) or (b), since (a) would imply that the > version is not changing, even as incompatible KBI/ABI changes are made. > Likewise for (b), once the KBI/ABI changes, HEAD is decidedly no longer a > form of '9'. > > -Ben Kaduk > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > I think he suggests a) 10 BTW I follow both stable and current lists. I have noticed that people still ask questions in current regarding 9-RC(*) problems. Maybe if it was clear that current is now 10 this would not happen. Cheers, -- George Kontostanos Aicom telecoms ltd http://www.barebsd.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 9.0-RC2 Available...
On Fri, Nov 18, 2011 at 1:35 PM, Luchesar V. ILIEV wrote: > On 18/11/2011 12:53, Thomas Mueller wrote: >>> If you would like to use csup/cvsup mechanisms to access the source >>> tree the branch tag to use is now "RELENG_9_0", if you use "." (head) >>> you will get 10-CURRENT. If you would like to access the source tree >>> via SVN it is "svn://svn.freebsd.org/base/releng/9.0/". We still have >>> the nit that the creation of a new SVN branch winds up causing what >>> looks like a check-in of the entire tree in CVS (a side-effect of the >>> svn2cvs exporter) so "mergemaster -F" is your friend if you are using >>> csup/cvsup. >> >> About a couple days before seeing this message, or the message on the >> FreeBSD web site, but after seeing RC2 on the ftp.freebsd.org server, >> I already ran csup with >> >> *default release=cvs tag=RELENG_9 >> >> Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0 >> instead of RELENG_9 ? > > RELENG_9 (cvs) = stable/9 (svn) = 9.N-STABLE (newvers.sh, `uname -r`) > RELENG_9_0 (cvs) = releng/9.0 (svn) = 9.0-RELEASE (newvers.sh, uname) > > In short, if you want to use the 9.0-RELEASE (when it finally gets > ready), then you need to switch to RELENG_9_0. If you prefer using > -STABLE for your systems, then you're OK with RELENG_9. > > In case you don't know or are not quite sure about the differences > between -RELEASE and -STABLE, I'd recommend switching to RELENG_9_0. > >> Again, I can't find that file (needle in the haystack) in /usr/src tree that >> shows version number such as RC2. > > This has already been answered, but just a quick note. If you've > recently updated your sources using the RELENG_9 tag, you'll most likely > see the version in newvers.sh as: > > REVISION="9.0" > BRANCH="PRERELEASE" > > If you switch to RELENG_9_0 and update your sources again, you should > see the familiar: > > REVISION="9.0" > BRANCH="RC2" > > HTH, > Luchesar > > -- > i.dea.is/luchesar > _______ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > Correct me if I am wrong but up until 9.0 is released there isn't any practical difference between RELENG_9 & RELENG_9_0 -- George Kontostanos Aicom telecoms ltd http://www.barebsd.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ahci in FreeBSD 9
Hi everyone, >From my understanding as of 20110424 revision device ahci has been integrated into kernel: It is possible to load devices ahci, ata, siis and mvs as modules, but option ATA_CAM should remain in kernel configuration to make ata module work as CAM driver supporting legacy ATA controllers. Device ata still can be used in modular fashion ... No kernel config options or code have been removed, so if a problem arises, please report it and optionally revert to the old ATA stack. In order to do it you can remove from the kernel config: optionsATA_CAM device ahci Does this mean that loading ahci in loader.conf is useless ? Thanks -- George Kontostanos Aicom telecoms ltd http://www.barebsd.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
9-RC3 & Super Micro IPMI disconnects
Hi everyone, I started running FreeBSD9-RC1 on this server. Yesterday, RC3, I noticed that I could not get IPMI console to apply the necessary security patches. A reset in IPMI fixed the problem temporarily. I keep getting those messages: Dec 24 15:35:12 mail kernel: ums0: at uhub2, port 2, addr 3 (disconnected) Dec 24 15:35:12 mail kernel: ukbd0: at uhub2, port 2, addr 3 (disconnected) Dec 24 15:35:14 mail kernel: usb_alloc_device: set address 3 failed (USB_ERR_TIMEOUT, ignored) Dec 24 15:35:14 mail kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED Dec 24 15:35:15 mail kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) Dec 24 15:35:15 mail kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED Dec 24 15:35:15 mail kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) Dec 24 15:35:15 mail kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED Dec 24 15:35:15 mail kernel: ugen0.3: at usbus0 (disconnected) Dec 24 15:35:15 mail kernel: uhub_reattach_port: could not allocate new device Dec 24 15:35:16 mail kernel: ugen0.3: at usbus0 Dec 24 15:35:16 mail kernel: ums0: on usbus0 Dec 24 15:35:16 mail kernel: ums0: 3 buttons and [XYZ] coordinates ID=0 Dec 24 15:35:16 mail kernel: ukbd0: on usbus0 Dec 24 15:35:16 mail kernel: kbd2 at ukbd0 Dec 24 15:35:17 mail kernel: ugen0.3: at usbus0 (disconnected) Dec 24 15:35:17 mail kernel: ums0: at uhub2, port 2, addr 3 (disconnected) Dec 24 15:35:17 mail kernel: ukbd0: at uhub2, port 2, addr 3 (disconnected) Dec 24 15:35:18 mail kernel: ugen0.3: at usbus0 Dec 24 15:35:18 mail kernel: ums0: on usbus0 Dec 24 15:35:18 mail kernel: ums0: 3 buttons and [Z] coordinates ID=0 Dec 24 15:35:18 mail kernel: ukbd0: on usbus0 Dec 24 15:35:18 mail kernel: kbd2 at ukbd0 Dec 24 15:36:40 mail login: ROOT LOGIN (root) ON ttyv0 Dec 24 15:54:05 mail kernel: ugen0.3: at usbus0 (disconnected) Dec 24 15:54:05 mail kernel: ums0: at uhub2, port 2, addr 3 (disconnected) Dec 24 15:54:05 mail kernel: ukbd0: at uhub2, port 2, addr 3 (disconnected) Dec 24 15:54:06 mail kernel: ugen0.3: at usbus0 Dec 24 15:54:06 mail kernel: ums0: on usbus0 Dec 24 15:54:06 mail kernel: ums0: 3 buttons and [Z] coordinates ID=0 Dec 24 15:54:06 mail kernel: ukbd0: on usbus0 Dec 24 15:54:06 mail kernel: kbd2 at ukbd0 Full dmesg from the server: Dec 23 21:37:57 mail kernel: Copyright (c) 1992-2011 The FreeBSD Project. Dec 23 21:37:57 mail kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Dec 23 21:37:57 mail kernel: The Regents of the University of California. All rights reserved. Dec 23 21:37:57 mail kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Dec 23 21:37:57 mail kernel: FreeBSD 9.0-RC3 #0: Fri Dec 23 21:23:00 EET 2011 Dec 23 21:37:57 mail kernel: r...@my.domain.tld:/usr/obj/usr/src/sys/GENERIC amd64 Dec 23 21:37:57 mail kernel: CPU: Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz (3093.04-MHz K8-class CPU) Dec 23 21:37:57 mail kernel: Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Dec 23 21:37:57 mail kernel: Features=0xbfebfbff Dec 23 21:37:57 mail kernel: Features2=0x159ae3bf Dec 23 21:37:57 mail kernel: AMD Features=0x28100800 Dec 23 21:37:57 mail kernel: AMD Features2=0x1 Dec 23 21:37:57 mail kernel: TSC: P-state invariant, performance statistics Dec 23 21:37:57 mail kernel: real memory = 8589934592 (8192 MB) Dec 23 21:37:57 mail kernel: avail memory = 8206499840 (7826 MB) Dec 23 21:37:57 mail kernel: Event timer "LAPIC" quality 600 Dec 23 21:37:57 mail kernel: ACPI APIC Table: Dec 23 21:37:57 mail kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs Dec 23 21:37:57 mail kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads Dec 23 21:37:57 mail kernel: cpu0 (BSP): APIC ID: 0 Dec 23 21:37:57 mail kernel: cpu1 (AP): APIC ID: 1 Dec 23 21:37:57 mail kernel: cpu2 (AP): APIC ID: 2 Dec 23 21:37:57 mail kernel: cpu3 (AP): APIC ID: 3 Dec 23 21:37:57 mail kernel: ioapic0 irqs 0-23 on motherboard Dec 23 21:37:57 mail kernel: kbd1 at kbdmux0 Dec 23 21:37:57 mail kernel: acpi0: on motherboard Dec 23 21:37:57 mail kernel: acpi0: Power Button (fixed) Dec 23 21:37:57 mail kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 Dec 23 21:37:57 mail kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 Dec 23 21:37:57 mail kernel: cpu0: on acpi0 Dec 23 21:37:57 mail kernel: cpu1: on acpi0 Dec 23 21:37:57 mail kernel: cpu2: on acpi0 Dec 23 21:37:57 mail kernel: cpu3: on acpi0 Dec 23 21:37:57 mail kernel: pcib0: port 0xcf8-0xcff on acpi0 Dec 23 21:37:57 mail kernel: pci0: on pcib0 Dec 23 21:37:57 mail kernel: em0: port 0xf020-0xf03f mem 0xfba0-0xfba1,0xfba24000-0xfba24fff irq 20 at device 25.0 on pci0 Dec 23 21:37:57 mail kernel: em0: Using an MSI interrupt Dec 23 21:37:57 mail kernel: em0: Ethernet
Re: 9-RC3 & Super Micro IPMI disconnects
On Sat, Dec 24, 2011 at 8:55 PM, Garrett Cooper wrote: > On Sat, Dec 24, 2011 at 6:08 AM, George Kontostanos > wrote: >> Hi everyone, >> >> I started running FreeBSD9-RC1 on this server. Yesterday, RC3, I >> noticed that I could not get IPMI console to apply the necessary >> security patches. A reset in IPMI fixed the problem temporarily. I >> keep getting those messages: > > Have you updated your firmware to the latest version? What motherboard is > this? > -Garrett I apologize for the delayed response. I had no knowledge of the exact board. The board is Supermicro X9SCL-F running the latest Firmware Revision: 01.27. -- George Kontostanos ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD 9 & recompile ports
Greetings all and my apologies for cross posting! There seems to be a confusion regarding the ABI change in FreeBSD 9 and if this affects the usual upgrade path which includes a full port rebuild. The relevant post is here: http://forums.freebsd.org/showthread.php?t=28831 Frankly, I am also confused because I remember a relevant discussion a few months ago in the lists. Traditionally a major RELEASE upgrade requires a full ports rebuild, however this time there is no COMPAT_FREEBSD8 in GENERIC and most upgraded systems seem to be working fine. On the other hand this is stated in UPDATING: 20110828: Bump the shared library version numbers for libraries that do not use symbol versioning, have changed the ABI compared to stable/8 and which shared library version was not bumped. Done as part of 9.0-RELEASE cycle. Your input would be appreciated! Regards, -- George Kontostanos Aicom telecoms ltd ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 9 & recompile ports
On Fri, Jan 13, 2012 at 2:34 PM, Johan Hendriks wrote: > George Kontostanos schreef: > >> On Fri, Jan 13, 2012 at 12:55 PM, Andriy Gapon wrote: >>> >>> on 13/01/2012 11:59 Doug Barton said the following: >>>> >>>> On 01/13/2012 01:52, George Kontostanos wrote: >>>>> >>>>> On Thu, Jan 12, 2012 at 8:42 PM, George Kontostanos >>>>> wrote: >>>>>> >>>>>> Greetings all and my apologies for cross posting! >>>>>> >>>>>> There seems to be a confusion regarding the ABI change in FreeBSD 9 >>>>>> and if this affects the usual upgrade path which includes a full port >>>>>> rebuild. >>>>>> >>>>>> The relevant post is here: >>>>>> http://forums.freebsd.org/showthread.php?t=28831 >>>>>> >>>>>> Frankly, I am also confused because I remember a relevant discussion a >>>>>> few months ago in the lists. Traditionally a major RELEASE upgrade >>>>>> requires a full ports rebuild, however this time there is no >>>>>> COMPAT_FREEBSD8 in GENERIC and most upgraded systems seem to be >>>>>> working fine. On the other hand this is stated in UPDATING: >>>>>> >>>>>> 20110828: >>>>>> Bump the shared library version numbers for libraries that >>>>>> do not use symbol versioning, have changed the ABI compared >>>>>> to stable/8 and which shared library version was not bumped. >>>>>> Done as part of 9.0-RELEASE cycle. >>>>>> >>>>>> Your input would be appreciated! >>>>> >>>>> Hmm, anyone :) ? >>>> >>>> If your question is, "Do I need to rebuild my ports when doing a major >>>> OS version upgrade?" the answer is always "Yes." >>>> >>>> The method described at the end of the portmaster man page is preferred, >>>> whether you actually use portmaster to do the upgrade or not. (I.e., >>>> good backups, delete everything, start over from scratch.) >>> >>> I think that another part of the question was "why there is no >>> COMPAT_FREEBSD8 >>> kernel option in 9?" and I think that Volodymyr has tried to answer this >>> part >>> with another question. >>> >>> -- >>> Andriy Gapon >> >> Hi guys, >> >> I am aware of the proper procedure which requires a full rebuild after >> a major upgrade. >> >> Doug, the question had to to with COMPAT_FREEBSD8 missing from GENERIC. >> >> It seems this and the fact that some upgrades from 8.2-STABLE worked >> fine without a recompile, has created the confusion. >> >> > Did he do make delete-old-libs, if you leave them, then no recompile is > needed, and the ports still have there old libs laying around.! > If you do the make delete-old-libs command, your ports do not work anymore. > > regards > Johan Hendriks > > Very good point! Still the question remains regarding COMPAT_FREEBSD8 and how does this affects ports/misc/compat8x/ Cheers -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 9 & recompile ports
On Fri, Jan 13, 2012 at 4:18 PM, Kostik Belousov wrote: > On Fri, Jan 13, 2012 at 04:11:22PM +0200, Andriy Gapon wrote: >> on 13/01/2012 14:57 George Kontostanos said the following: >> > Still the question remains regarding COMPAT_FREEBSD8 and how does this >> > affects ports/misc/compat8x/ >> >> Looks like all the previous hints have not been clear enough. >> There is no direct relation between COMPAT_FREEBSD8 and misc/compat8x. >> COMPAT_FREEBSD options are only needed when going from release X to >> release X+1 >> there was a change to an existing system call at the kernel-userland >> boundary. >> A side note: kernel options affect only what's in the kernel, quite >> obviously. >> misc/compatx contains versions of shared libraries from release X that >> are no >> longer present in X+1. > > Additional twist is that not every change at the kernel/usermode boundary > is covered with backward-compatibility shims. Recent example is the CAM > ABI change, which makes libcam.so.5 from the compat8x useless. Thanks to all for your input. It looks quite obvious to me know and I think this clears any further confusion. Best Regards, George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS TRIM support committed to HEAD.
On Mon, Sep 24, 2012 at 1:25 AM, Pawel Jakub Dawidek wrote: > On Sun, Sep 23, 2012 at 10:24:53PM +0100, Bob Bishop wrote: >> Hi, >> >> On 23 Sep 2012, at 20:53, Pawel Jakub Dawidek wrote: >> >> > FYI, I just committed TRIM support to ZFS, especially useful for >> > SSD-only pools. [etc] >> >> Is any of this applicable to -STABLE or 8.x? > > I have a patch against stable/8, but not stable/9: > > http://people.freebsd.org/~pjd/patches/zfstrim8.patch > > -- > Pawel Jakub Dawidek http://www.wheelsystems.com > FreeBSD committer http://www.FreeBSD.org > Am I Evil? Yes, I Am! http://tupytaj.pl This sounds great. I guess we will have to wait for MFC, probably after 9.1-RELEASE, right? -- George Kontostanos --- http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 10 Beta2 /etc/rc.d/named script and /etc/defaults/rc.conf
On Mon, Nov 4, 2013 at 12:54 AM, Stefan Bethke wrote: > > Am 03.11.2013 um 23:06 schrieb Gleb Smirnoff : > > > On Sun, Nov 03, 2013 at 10:05:02PM +0200, Özkan KIRIK wrote: > > Ö> Altough bind removed from FreeBSD 10 distribution, "/etc/rc.d/named" > script > > Ö> still exists. > > Ö> and this script depends on "/etc/mtree/BIND.chroot.dist" file but > there is > > Ö> no such file in source tree. > > Ö> I think this file was forgotten to be removed. > > Ö> > > Ö> And also, named_* definitions still exists in /etc/defaults/rc.conf > file. > > > > Please review attached file that removes named from /etc. > > It would be great if the port would learn to install its own script etc. > in time for that change. (Unless it’s already there, and I’m just too blind > to see it.) > > > Stean > > -- > Stefan BethkeFon +49 151 14070811 > > > > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > No you are not blind. Installing bind from ports still relies on the /etc/rc.d/named script. Best -- George Kontostanos --- http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 10 Beta2 /etc/rc.d/named script and /etc/defaults/rc.conf
On Mon, Nov 4, 2013 at 6:34 PM, Gleb Smirnoff wrote: > On Mon, Nov 04, 2013 at 12:11:02PM +0100, Erwin Lansing wrote: > E> > On Mon, Nov 04, 2013 at 01:41:01AM +0200, George Kontostanos wrote: > E> > G> > Am 03.11.2013 um 23:06 schrieb Gleb Smirnoff >: > E> > G> > > E> > G> > > On Sun, Nov 03, 2013 at 10:05:02PM +0200, Özkan KIRIK wrote: > E> > G> > > Ö> Altough bind removed from FreeBSD 10 distribution, > "/etc/rc.d/named" > E> > G> > script > E> > G> > > Ö> still exists. > E> > G> > > Ö> and this script depends on "/etc/mtree/BIND.chroot.dist" > file but > E> > G> > there is > E> > G> > > Ö> no such file in source tree. > E> > G> > > Ö> I think this file was forgotten to be removed. > E> > G> > > Ö> > E> > G> > > Ö> And also, named_* definitions still exists in > /etc/defaults/rc.conf > E> > G> > file. > E> > G> > > > E> > G> > > Please review attached file that removes named from /etc. > E> > G> > > E> > G> > It would be great if the port would learn to install its own > script etc. > E> > G> > in time for that change. (Unless it’s already there, and I’m > just too blind > E> > G> > to see it.) > E> > G> > E> > G> No you are not blind. Installing bind from ports still relies on > the > E> > G> /etc/rc.d/named script. > E> > > E> > Erwin, can you please handle that? > E> > E> Things are much worse that this, the ports are completely written under > the assumption that there is a Bind in base, which of course would already > break with WITHOUT_BIND before Bind was completely removed. It will be > hard to fix without breaking the installed base of 8 and 9. Sigh. > E> > E> I'll try to work on it this week, but unfortunately have a full > schedule of meetings and travel as well. > Suggestion. An option to install the rc script would solve that problem. > > What should we do with src? > > IMO, we should proceed with removal of remnants of bind in src. In the > worst case, > if you can't handle it this week, the situation will be the following: > > 1) 8.x, 9.x users are okay > 2) 10+.x users w/o bind are okay > 3) 10+.x users with bind have problems > > If we skip updating src, then situation would be: > > 1) 8.x, 9.x users are okay > 2) 10+.x users w/o bind have problems > 3) 10+.x users with bind are okay > > I think, there are less 10.x users with bind, than 10.x without it. > > Please warn about this in UPDATING. I am personally use 12 FreeBSD servers as dedicated DNS servers only. > -- > Totus tuus, Glebius. > -- George Kontostanos --- http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 10 Beta2 /etc/rc.d/named script and /etc/defaults/rc.conf
On Wed, Nov 6, 2013 at 3:59 PM, Erwin Lansing wrote: > > > On 06/11/2013, at 14.22, George Kontostanos > wrote: > > On Mon, Nov 4, 2013 at 6:34 PM, Gleb Smirnoff wrote: > >> On Mon, Nov 04, 2013 at 12:11:02PM +0100, Erwin Lansing wrote: >> E> > On Mon, Nov 04, 2013 at 01:41:01AM +0200, George Kontostanos wrote: >> E> > G> > Am 03.11.2013 um 23:06 schrieb Gleb Smirnoff < >> gleb...@freebsd.org>: >> E> > G> > >> E> > G> > > On Sun, Nov 03, 2013 at 10:05:02PM +0200, Özkan KIRIK wrote: >> E> > G> > > Ö> Altough bind removed from FreeBSD 10 distribution, >> "/etc/rc.d/named" >> E> > G> > script >> E> > G> > > Ö> still exists. >> E> > G> > > Ö> and this script depends on "/etc/mtree/BIND.chroot.dist" >> file but >> E> > G> > there is >> E> > G> > > Ö> no such file in source tree. >> E> > G> > > Ö> I think this file was forgotten to be removed. >> E> > G> > > Ö> >> E> > G> > > Ö> And also, named_* definitions still exists in >> /etc/defaults/rc.conf >> E> > G> > file. >> E> > G> > > >> E> > G> > > Please review attached file that removes named from /etc. >> E> > G> > >> E> > G> > It would be great if the port would learn to install its own >> script etc. >> E> > G> > in time for that change. (Unless it’s already there, and I’m >> just too blind >> E> > G> > to see it.) >> E> > G> >> E> > G> No you are not blind. Installing bind from ports still relies on >> the >> E> > G> /etc/rc.d/named script. >> E> > >> E> > Erwin, can you please handle that? >> E> >> E> Things are much worse that this, the ports are completely written >> under the assumption that there is a Bind in base, which of course would >> already break with WITHOUT_BIND before Bind was completely removed. It >> will be hard to fix without breaking the installed base of 8 and 9. Sigh. >> E> >> E> I'll try to work on it this week, but unfortunately have a full >> schedule of meetings and travel as well. >> > > Suggestion. An option to install the rc script would solve that problem. > > > > If only it was that simple, it would have been done a long time ago. As > Gleb points out, the ports are broken by design. The rc script needs a > complete rewrite, and that's only after fixing all configuration files, > setting up chroot, etc etc and all that while not breaking the installed > base on 8 and 9. I spent most of yesterday on this and if I'm lucky, I'm > halfway through. > > Erwin, sent from a phone at the train station > > Thank you all for your effort! -- George Kontostanos --- http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 10 Beta2 /etc/rc.d/named script and /etc/defaults/rc.conf
On Tue, Nov 12, 2013 at 1:13 PM, Erwin Lansing wrote: > On Wed, Nov 06, 2013 at 02:59:15PM +0100, Erwin Lansing wrote: > > >> E> > > > >> E> > Erwin, can you please handle that? > > >> E> > > >> E> Things are much worse that this, the ports are completely written > under the assumption that there is a Bind in base, which of course would > already break with WITHOUT_BIND before Bind was completely removed. It > will be hard to fix without breaking the installed base of 8 and 9. Sigh. > > >> E> > > >> E> I'll try to work on it this week, but unfortunately have a full > schedule of meetings and travel as well. > > > > > > Suggestion. An option to install the rc script would solve that > problem. > > > > > > > If only it was that simple, it would have been done a long time ago. As > Gleb points out, the ports are broken by design. The rc script needs a > complete rewrite, and that's only after fixing all configuration files, > setting up chroot, etc etc and all that while not breaking the installed > base on 8 and 9. I spent most of yesterday on this and if I'm lucky, I'm > halfway through. > > > > > Sorry about the delay, but I did finally update all three dns/bind9* > ports today. I have dropped the complicated chroot, and related > symlinking, logic from the default rc script as I don't think that > is the right place to implement things. I would recommend users > who want the extra security to use jail(8) instead of a mere chroot. > > This change should not affect the installed base of FreeBSD 9.x and > earlier systems, but new installations there should note that the > symlink option is no longer turned on by default, but still supported. > > I tested some default cases, but by no means can test every corner case, > so please let me know how this works out. > > Best, > Erwin > > Excellent thanks so much! If you had named running using the old rc scripts and config in 10 you will need to: 1) Backup your zones & stop named 2) Delete /var/named/* 3) Create a new symlink in etc to /usr/local/etc/namedb 4) Restore your zones 5) Start named from the new rc script -- George Kontostanos --- http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 10 Beta2 /etc/rc.d/named script and /etc/defaults/rc.conf
On Wed, Nov 13, 2013 at 7:59 PM, George Kontostanos wrote: > On Tue, Nov 12, 2013 at 1:13 PM, Erwin Lansing wrote: > >> On Wed, Nov 06, 2013 at 02:59:15PM +0100, Erwin Lansing wrote: >> > >> E> > >> > >> E> > Erwin, can you please handle that? >> > >> E> >> > >> E> Things are much worse that this, the ports are completely written >> under the assumption that there is a Bind in base, which of course would >> already break with WITHOUT_BIND before Bind was completely removed. It >> will be hard to fix without breaking the installed base of 8 and 9. Sigh. >> > >> E> >> > >> E> I'll try to work on it this week, but unfortunately have a full >> schedule of meetings and travel as well. >> > > >> > > Suggestion. An option to install the rc script would solve that >> problem. >> > > >> > >> > If only it was that simple, it would have been done a long time ago. >> As Gleb points out, the ports are broken by design. The rc script needs a >> complete rewrite, and that's only after fixing all configuration files, >> setting up chroot, etc etc and all that while not breaking the installed >> base on 8 and 9. I spent most of yesterday on this and if I'm lucky, I'm >> halfway through. >> > >> >> >> Sorry about the delay, but I did finally update all three dns/bind9* >> ports today. I have dropped the complicated chroot, and related >> symlinking, logic from the default rc script as I don't think that >> is the right place to implement things. I would recommend users >> who want the extra security to use jail(8) instead of a mere chroot. >> >> This change should not affect the installed base of FreeBSD 9.x and >> earlier systems, but new installations there should note that the >> symlink option is no longer turned on by default, but still supported. >> >> I tested some default cases, but by no means can test every corner case, >> so please let me know how this works out. >> >> Best, >> Erwin >> >> > Excellent thanks so much! > > If you had named running using the old rc scripts and config in 10 you > will need to: > > 1) Backup your zones & stop named > 2) Delete /var/named/* > 3) Create a new symlink in etc to /usr/local/etc/namedb > 4) Restore your zones > 5) Start named from the new rc script > > Sorry I forgot also that if if you don't specify the location of named in the rc.conf: named_program="/usr/local/sbin/named" You will get an error message: root@hp:/etc # /usr/local/etc/rc.d/named start /usr/local/etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named Those are observations from a test machine that I use which was running bind with the old rc style. Thanks -- George Kontostanos --- http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ZFS dedup and temporary freeze
Hi List, I am using dedup=on for my ezjail /jails directory. I noticed a strange behavior during the installation of the ports tree in the basejail. The system appears to freeze for a while and the cpu appears to be idle during that time. The same behavior is shown when building ports inside the jail. Here is some information about the pool: capacity operationsbandwidth poolalloc free read write read write -- - - - - - - zhome 15.0G 59.5G 4 14 61.2K 468K zhome 15.0G 59.5G 38 66 107K 68.9K zhome 15.0G 59.5G 43 71 119K 45.0K zhome 15.0G 59.5G 37 67 103K 45.0K zhome 15.0G 59.5G 39103 102K 4.71M zhome 15.0G 59.5G 42 72 114K 45.0K zhome 15.0G 59.5G 36 59 97.9K 37.0K zhome 15.0G 59.5G 42 69 114K 48.0K zhome 15.0G 59.5G 39 72 105K 43.5K zhome 15.0G 59.5G 33 58 93.4K 42.0K zhome 15.0G 59.5G 44 77 117K 53.4K NAMESIZE ALLOC FREECAP DEDUP HEALTH ALTROOT zhome 74.5G 15.8G 58.7G21% 1.06x ONLINE - I thought that jails would be a good candidate for dedup. So far I am using it without any issues in my /usr/src and /virtualBox directories. Best Regards -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS dedup and temporary freeze
The system has 4Gs of RAM. I don''t use any devices for L2ARC and my tuning is like this: vm.kmem_size="3072M" vfs.zfs.arc_max="2048M" I had my eyes on the memory during the whole procedure and things looked "normal". Thanks On Tue, Mar 29, 2011 at 10:53 PM, Sean M. Collins wrote: > How much memory do you have in the system? Any L2ARC devices? Depending > on the amount of memory in your box, it could be that ddt is spilling > over ARC? > > > -- > Sean Collins > Core IT Pro, LLC > www.coreitpro.com > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS dedup and temporary freeze
As far as I am aware ezjail has the option to use compression and disable access time updates. ezjail_zfs_properties="-o compression=lzjb -o atime=off" In my case the dedup option was turned on only in the basejail causing the system to temporarily freeze. Once the dedup option was removed everything went back to normal. What I am trying to figure out here is why did this occur. Thanks On Wed, Mar 30, 2011 at 10:53 AM, Alexander Leidinger < alexan...@leidinger.net> wrote: > Quoting George Kontostanos (from Tue, 29 Mar 2011 > 17:57:49 +0300): > > I thought that jails would be a good candidate for dedup. So far I am >> using >> it without any issues in my /usr/src and /virtualBox directories. >> > > No idea about your problem, but ezjail is already doing some dedup. The > basejail is the dedup-place, and the jails do a null-mount of it. Inside the > jails are only some links to the basejail. So if you do not install the same > programs (the same packages, so make sure there is no different compile > timestamp (some programs have this) inside the newly generated binaries) or > data inside the jail-specific area, you will not have a benefit from this. > > Bye, > Alexander. > > -- > Real programmers never work 9 to 5. If any real > programmers are around at 9 a.m., it's because they > were up all night. > > http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS dedup and temporary freeze
Very useful thank you! DDT-sha256-zap-duplicate: 177 entries, size 9493 on disk, 12010 in core DDT-sha256-zap-unique: 20016 entries, size 1232 on disk, 1524 in core DDT histogram (aggregated over all DDTs): bucket allocated referenced __ __ __ refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE -- -- - - - -- - - - 119.5K 2.44G 2.44G 2.44G19.5K 2.44G 2.44G 2.44G 2 175 21.9M 21.9M 21.9M 407 50.9M 50.9M 50.9M 41128K128K128K6768K768K768K 2561128K128K128K 297 37.1M 37.1M 37.1M Total19.7K 2.46G 2.46G 2.46G20.2K 2.53G 2.53G 2.53G dedup = 1.03, compress = 1.00, copies = 1.00, dedup * compress / copies = 1.03 On Wed, Mar 30, 2011 at 7:11 PM, Sean M. Collins wrote: > Can you attach the output from zdb -DD zhome ? > > -- > Sean Collins > Core IT Pro, LLC > www.coreitpro.com > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
make release
I am trying to make a release with the following arguments: make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES however /usr/home/current is being ignored completely and everything ends up in /usr/obj/usr/src. Am I doing something wrong ? Thanks -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: make release
Sorry I didn't read the man pages lately!
releaseMeta-target to build all release media and distributions
applicable to this platform. All output goes to
${.OBJDIR}, which will likely be either src/release or
the
equivalent path in /usr/obj.
The following sequence of commands can be used to build a ``-CURRENT
snapshot'' in a clean environment, including ports and documentation:
cd /usr/src
make buildworld
cd release
export CVSUP_HOST=cvsupN.freebsd.org
sh generate-release.sh head /local3/release
On Tue, Apr 12, 2011 at 6:14 PM, Nathan Whitehorn wrote:
> On 04/12/11 10:02, George Kontostanos wrote:
>
>> I am trying to make a release with the following arguments:
>>
>> make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT
>> EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES
>>
>> however /usr/home/current is being ignored completely and everything ends
>> up
>> in /usr/obj/usr/src. Am I doing something wrong ?
>>
>
> Following switching the default installer away from sysinstall, make
> release works differently now (see release(7), which has been updated to
> reflect the new release-building process). The closest analog to the command
> above (though you may want to do something different) is:
> cd /usr/src/release
> ./generate-release.sh head /usr/home/current
> -Nathan
>
--
George Kontostanos
aisecure.net <http://www.aisecure.net>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ZFS V28
I was wondering if ZFS v28 is going to be MFC to 8-Stable or not. Regards, -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS V28
I think that at this point it takes more than a patch. That is way I am asking if there is a plan to MFC to 8-Stable. On Fri, Apr 15, 2011 at 9:48 PM, Leon Meßner wrote: > On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote: > > I was wondering if ZFS v28 is going to be MFC to 8-Stable or not. > > On Fri, Apr 15, 2011 at 06:28:07PM +0300, George Kontostanos wrote: > > I was wondering if ZFS v28 is going to be MFC to 8-Stable or not. > > Is there a recent patch against stable sources ? I tried the following: > > > http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110317.patch.xz > > This patch failes at sys/cddl/compat/opensolaris/sys/sysmacros.h which i > think should just be deleted. I tried deleting this file and then > building produces some errors then walls of text and then aborts. > The first errors look like this: > > Script started on Fri Apr 15 18:32:36 2011 > make -j 6 buildworld > "/usr/share/mk/bsd.prog.mk", line 128: warning: duplicate script for > target "_EXTRADEPEND" ignored > "Makefile", line 222: warning: duplicate script for target "clean" > ignored > "Makefile", line 222: warning: duplicate script for target "cleandepend" > ignored > "Makefile", line 222: warning: duplicate script for target "distribute" > ignored > "Makefile", line 222: warning: duplicate script for target "lint" > ignored > "Makefile", line 222: warning: duplicate script for target "obj" ignored > "Makefile", line 222: warning: duplicate script for target "objlink" > ignored > "Makefile", line 222: warning: duplicate script for target "tags" > ignored > "Makefile", line 222: warning: duplicate script for target "files" > ignored > "Makefile", line 222: warning: duplicate script for target "includes" > ignored > -- > >>> World build started on Fri Apr 15 18:32:36 UTC 2011 > -- > > cherio, > Leon > > > Regards, > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Switch from legacy ata(4) to CAM-based ATA
EAD code and contact me if problem is still there. > >>>> Next three weeks before BSDCan I am going to dedicate to fixing > >>>> possibly remaining issues. > >>> I've not checked recently with -current, but at least on the > >>> latest 8-stable there's a problem with using ATA_CAM on Xen: during > boot > >>> there's a pause for a minute after which "run_interrupt_driven_hooks: > >>> still waiting after 60 seconds for xpt_config" is displayed. > >> Verbose dmesg from the fresh system would be appreciated. > >> > > I have a similar problem, but it's under 8.2-stable: > > This should fix your problem: > http://svn.freebsd.org/changeset/base/220920 > > -- > Alexander Motin > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Switch from legacy ata(4) to CAM-based ATA
My mistake! Everything back to normal thanks and very nice work. On Thu, Apr 21, 2011 at 3:41 PM, Alexander Motin wrote: > George Kontostanos wrote: > > First patch seemed to work fine. > > > > Second however, > > It was unrelated breakage related to WiFi MIMO support. Already fixed. > > -- > Alexander Motin > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Switch from legacy ata(4) to CAM-based ATA
I also think that labeling disks & partitions should be the default approach on new installations. I wonder why the new bsdinstaller does not adopt this policy yet. It is practical, easy and saves a lot of hassles when it comes to disk replacements. On Thu, Apr 21, 2011 at 7:18 PM, Ted Faber wrote: > On Wed, Apr 20, 2011 at 03:35:38PM -0700, Doug Barton wrote: > > On 04/20/2011 15:18, Scott Long wrote: > > >I agree with what Alexander is saying, but I'd like to take it a step > further. We should all be using [...] mount-by-label > > > > +1 > > > > When I first saw this on linux my gut reaction was "e, > > different." But now that I've worked with it a bit, I really like > > it. Doing this by default in 9.0 would be a really useful step > > forward, and would allow greater innovation down the road. > > > > Is there a handy tutorial somewhere for making this change in > > FreeBSD? Or is it even possible to do in a rational way? > > Judging from the thread that followed this: no. > > I agree with you that there should be and that mount-by-label is the way > to go. > > I seem to recall some flakiness with mounting labelled gmirrors. Anyone > know if that's been resolved? > > -- > Ted Faber > http://www.isi.edu/~faber PGP: > http://www.isi.edu/~faber/pubkeys.asc > Unexpected attachment on this mail? See > http://www.isi.edu/~faber/FAQ.html#SIG > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.14 (GNU/Linux) > > iEYEARECAAYFAk2wWMYACgkQaUz3f+Zf+XtI2ACfUz7zukI/G/4d5jEmsOuR73v4 > YMgAoNsRHB255xZpx9IbEmoV+IxKWkTM > =HvFZ > -END PGP SIGNATURE- > > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
The new bsdinstall has a different layout so the previous guides don't work. I have prepared one that works for recent 9-Current at : "http://www.aisecure.net/?p=132"; Regards On Sun, May 29, 2011 at 9:55 AM, Andriy Gapon wrote: > on 29/05/2011 07:08 Scott Lambert said the following: > > If you want to end up with a mirrored ZFS only setup, have you seen ? > > > > > http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ > > > > That one was pretty straight-forward for me. You get to use > > sysinstall and don't have to manually install the OS. > > There is no sysinstall :-) [in the latest CURRENT] > > -- > Andriy Gapon > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
Last time I checked it was practically the same. On Sun, May 29, 2011 at 4:10 PM, Daniel Staal wrote: > --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to > have said: > > The new bsdinstall has a different layout so the previous guides don't >> work. I have prepared one that works for recent 9-Current at : >> >> "http://www.aisecure.net/?p=132"; >> > > --As for the rest, it is mine. > > Thanks, that's about what I expected the install procedure to be at this > point. Nice to have the reminder about the zpool.cache. (Do I have to use > the Live CD mode? Can I use shell mode instead?) > > > Daniel T. Staal > > --- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --- > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
Could you please explain where did you actually got stacked ?
Have you installed the OS by :
for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz;
do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done
Did you copy zpool.cache ?
On Mon, May 30, 2011 at 6:01 PM, Daniel Staal wrote:
> --As of May 29, 2011 9:10:57 AM -0400, George Kontostanos,
> freebsd-current@freebsd.org is alleged to have said:
>
> --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to
>> have said:
>>
>> The new bsdinstall has a different layout so the previous guides don't
>>> work. I have prepared one that works for recent 9-Current at :
>>>
>>> "http://www.aisecure.net/?p=132";
>>>
>>
>> --As for the rest, it is mine.
>>
>> Thanks, that's about what I expected the install procedure to be at this
>> point. Nice to have the reminder about the zpool.cache. (Do I have to
>> use the Live CD mode? Can I use shell mode instead?)
>>
>
> --As for the rest, it is mine.
>
> Ok, I've tried shell mode and live CD mode. I've re-partitioned my disks
> several different ways.
>
> Nothing gets me a system that will actually boot. Or even recognize that
> there is an OS loaded anywhere. Help?
>
> (My preferred partitioning:
>
> ada1:
> 1 freebsd-boot
> 2 freebsd-swap 8G
> 3 freebsd-zfs 4G (zil)
> 4 freebsd-zfs 17G (cache)
>
> ada0: Managed by ZFS, ~250G Main filesystem.
>
> This takes advantage of the mSATA SSD in ada1.)
>
>
> Daniel T. Staal
>
> ---
> This email copyright the author. Unless otherwise noted, you
> are expressly allowed to retransmit, quote, or otherwise use
> the contents for non-commercial purposes. This copyright will
> expire 5 years after the author's death, or in 30 years,
> whichever is longer, unless such a period is in excess of
> local copyright law.
> ---
>
--
George Kontostanos
aisecure.net <http://www.aisecure.net>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
I suppose that you didn't forget to add a boot code to your boot disk(s) ?
gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0
On Mon, May 30, 2011 at 6:25 PM, Daniel Staal wrote:
> --As of May 30, 2011 6:11:19 PM +0300, George Kontostanos is alleged to
> have said:
>
> Could you please explain where did you actually got stacked ?
>>
>> Have you installed the OS by :
>>
>> for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz;
>> do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done
>>
>> Did you copy zpool.cache ?
>>
>
> --As for the rest, it is mine.
>
> Did both of those. A half-dozen times. ;)
>
> The machine fails to find a bootable drive. It searches, tries PXE booting
> a couple of times, then dumps me into the BIOS's boot drive chooser. I can
> try selecting either of the internal drives at that point if I wish, and it
> will just loop back to there.
>
>
> Daniel T. Staal
>
> ---
> This email copyright the author. Unless otherwise noted, you
> are expressly allowed to retransmit, quote, or otherwise use
> the contents for non-commercial purposes. This copyright will
> expire 5 years after the author's death, or in 30 years,
> whichever is longer, unless such a period is in excess of
> local copyright law.
> ---
>
--
George Kontostanos
aisecure.net <http://www.aisecure.net>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
Sorry about the typos. The bootcode should be installed to the drive that you are booting from. I see that you have: ada1: 1 freebsd-boot 2 freebsd-swap 8G 3 freebsd-zfs 4G (zil) 4 freebsd-zfs 17G (cache) ada0: Managed by ZFS, ~250G Main filesystem. I don't think that ada1 holds any OS files therefore you will need to boot from ada0 gpart create -s gpt ada0 gpart add -b 34 -s 64k -t freebsd-boot ada0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 On Mon, May 30, 2011 at 6:33 PM, Daniel Staal wrote: > --As of May 30, 2011 6:29:06 PM +0300, George Kontostanos is alleged to > have said: > > I suppose that you didn't forget to add a boot code to your boot disk(s) ? >> >> gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0 >> > > --As for the rest, it is mine. > > Nope, I got that. Although that line as written threw errors. I used: > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 > > (Normally I was installing the boot code to the mSATA drive, as it was the > one I was partitioning.) > > > Daniel T. Staal > > --- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --- > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
Thanks, I will reproduce it and update the guide. On Mon, May 30, 2011 at 6:26 PM, Daniel Kalchev wrote: > > > On 29.05.11 16:10, Daniel Staal wrote: > >> --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to >> have said: >> >>> "http://www.aisecure.net/?p=132"; >>> >> >> Thanks, that's about what I expected the install procedure to be at this >> point. Nice to have the reminder about the zpool.cache. (Do I have to use >> the Live CD mode? Can I use shell mode instead?) >> >> Actually, you don't need to go via the trouble to make /boot writable. > You can obtain zpool.cache by using > > zpool import -c /tmp/zpool.cache zroot > > Then copy that file to the mounted root filesystem of the zpool. > > Daniel > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
Could you please post the output of: gpart show On Mon, May 30, 2011 at 8:04 PM, Daniel Staal wrote: > --As of May 30, 2011 6:47:32 PM +0300, George Kontostanos is alleged to > have said: > > The bootcode should be installed to the drive that you are booting from. >> >> I see that you have: >> >> ada1: >>> 1 freebsd-boot >>> 2 freebsd-swap 8G >>> 3 freebsd-zfs 4G (zil) >>> 4 freebsd-zfs 17G (cache) >>> >>> ada0: Managed by ZFS, ~250G Main filesystem. >>> >> >> I don't think that ada1 holds any OS files therefore you will need to boot >> from ada0 >> >> gpart create -s gpt ada0 >> gpart add -b 34 -s 64k -t freebsd-boot ada0 >> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 >> > > --As for the rest, it is mine. > > I said that was my preferred partitioning. I had tried others. ;) I just > double-checked putting the bootcode on ada0. It doesn't help. > > (Note that if it did that'd be an interesting regression from 8.2. My home > server is running with *only* the bootcode on one drive, and the OS loaded > from a ZFS RAIDZ array.) > > > Daniel T. Staal > > --- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --- > _______ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
*zpool import -c /tmp/zpool.cache zroot can not import /tmp/zpool.cache no such pool available * Well, it seems that -c switch is for specifying where to read from and not where to write. I haven't been able to import the pool and find a way to store zpool.cache in a diffrent place other than /boot/zfs On Mon, May 30, 2011 at 6:26 PM, Daniel Kalchev wrote: > > > On 29.05.11 16:10, Daniel Staal wrote: > >> --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to >> have said: >> >>> "http://www.aisecure.net/?p=132"; >>> >> >> Thanks, that's about what I expected the install procedure to be at this >> point. Nice to have the reminder about the zpool.cache. (Do I have to use >> the Live CD mode? Can I use shell mode instead?) >> >> Actually, you don't need to go via the trouble to make /boot writable. > You can obtain zpool.cache by using > > zpool import -c /tmp/zpool.cache zroot > > Then copy that file to the mounted root filesystem of the zpool. > > Daniel > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
Bingo! That did it. I will update the guide soon. @Daniel my apologies it seems that another typo is preventing you from booting. You have to set the bootfs in the pool. zpool set bootfs=zroot zroot On Tue, May 31, 2011 at 12:30 AM, Pan Tsu wrote: > George Kontostanos writes: > > > *zpool import -c /tmp/zpool.cache zroot > > can not import /tmp/zpool.cache no such pool available > > Try modifying pool's property: > > $ zpool import -o cachefile=/tmp/zpool.cache zroot > > > Well, it seems that -c switch is for specifying where to read from and > not > > where to write. I haven't been able to import the pool and find a way to > > store zpool.cache in a diffrent place other than /boot/zfs > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ZFS install from -CURRENT snapshot
oops typos, typos! That's one of the bad things that happens when you type without having the copy - paste functionality. On Tue, May 31, 2011 at 1:48 AM, Daniel Staal wrote: > --As of May 31, 2011 1:21:49 AM +0300, George Kontostanos is alleged to > have said: > > Bingo! That did it. I will update the guide soon. >> >> @Daniel my apologies it seems that another typo is preventing you from >> booting. You have to set the bootfs in the pool. >> >> zpool set bootfs=zroot zroot >> > > --As for the rest, it is mine. > > I'd actually caught that one... (Yesterday afternoon.) > > I was hoping this was something people had seen before. At this point, > I've been trying to get a FreeBSD+ZFS install on this box for about a month > - including spending much of my first vacation in two years on it - and I > know that even if I do manage to do so I'll still have a problem with the > screen resolution. (Sandy Bridge integrated graphics. It works in VERSA > mode, but doesn't detect the native mode.) > > I've decided to call it quits for now. A current Linux runs fine. The > power management isn't as good as FreeBSD, I'm loosing the ZFS coolness, and > the other advantages of a FreeBSD box over Linux, but it means I've got a > working laptop for the moment. I'll revisit putting FreeBSD on it sometime > in the future, once the hardware isn't quite so current-edge. For now, I've > invested too much time into just getting this running. > > George, a couple other notes on your walkthrough: (I'd decided to wait > until I was done to go over all of these.) > cd /tmp && copy -R * /boot# Needs to be cp. > zpool create -O mountpoint=/mnt zroot /dev/gpt/disk0 # Will avoid the > export/import later. > > And in theory it doesn't make *much* difference, but setting the checksum > before creating usr, var, and tmp is slightly better practice. (The > directory entries are checksummed as well, which would be the only > difference. If any files were created in between they'd get the fletcher2 > checksum.) > > > Daniel T. Staal > > --- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --- > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
xpt_action_default: CCB type 0xe not supported
Fresh installation and after world && kernel update I get these messages during boot: xpt_action_default: CCB type 0xe not supported xpt_action_default: CCB type 0xe not supported The system is running GENERIC with debugging for use in current off options. Full dmesg attached. Regards, -- George Kontostanos aisecure.net <http://www.aisecure.net> Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #0: Tue Jun 21 19:28:33 EEST 2011 r...@core2duo.aicom.loc:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2401.97-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Family = 6 Model = f Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 4057284608 (3869 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 ACPI Warning: Incorrect checksum in table [OEMB] - 0xE7, should be 0xDA (20110527/tbutils-282) cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x9c00-0x9c7f mem 0xfd00-0xfdff,0xc000-0xcfff,0xfc00-0xfcff irq 16 at device 0.0 on pci1 uhci0: port 0xdc00-0xdc1f irq 16 at device 26.0 on pci0 uhci0: LegSup = 0x2f00 usbus0: on uhci0 uhci1: port 0xe000-0xe01f irq 17 at device 26.1 on pci0 uhci1: LegSup = 0x2f00 usbus1: on uhci1 ehci0: mem 0xfebffc00-0xfebf irq 18 at device 26.7 on pci0 usbus2: EHCI version 1.0 usbus2: on ehci0 hdac0: mem 0xfebf8000-0xfebfbfff irq 22 at device 27.0 on pci0 pcib2: irq 16 at device 28.0 on pci0 pci4: on pcib2 pcib3: irq 19 at device 28.3 on pci0 pci3: on pcib3 re0: port 0xb800-0xb8ff mem 0xfeaff000-0xfeaf irq 19 at device 0.0 on pci3 re0: Using 1 MSI message re0: Chip rev. 0x3800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:18:f3:03:66:7e pcib4: irq 16 at device 28.4 on pci0 pci2: on pcib4 atapci0: port 0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0xa400-0xa40f mem 0xfe9fe000-0xfe9f irq 16 at device 0.0 on pci2 ahci0: on atapci0 ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ata2: on atapci0 uhci2: port 0xd480-0xd49f irq 23 at device 29.0 on pci0 uhci2: LegSup = 0x2f00 usbus3: on uhci2 uhci3: port 0xd800-0xd81f irq 19 at device 29.1 on pci0 uhci3: LegSup = 0x2f00 usbus4: on uhci3 uhci4: port 0xd880-0xd89f irq 18 at device 29.2 on pci0 uhci4: LegSup = 0x2f00 usbus5: on uhci4 ehci1: mem 0xfebff800-0xfebffbff irq 23 at device 29.7 on pci0 usbus6: EHCI version 1.0 usbus6: on ehci1 pcib5: at device 30.0 on pci0 pci5: on pcib5 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f,0xe080-0xe08f irq 19 at device 31.2 on pci0 ata3: on atapci1 ata4: on atapci1 pci0: at device 31.3 (no driver attached) atapci2: port 0xd400-0xd407,0xd080-0xd083,0xd000-0xd007,0xcc00-0xcc03,0xc880-0xc88f,0xc800-0xc80f irq 19 at device 31.5 on pci0 ata5: on atapci2 ata6: on atapci2 acpi_button0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 ppc0: port 0x378-0x37f,0x778
Re: Exactly that commit (was Re: Latest -current 100% hang at the late boot stage)
After applying the patch the system does not boot anymore! It hangs after probing for scsi devices. On Tue, Jun 21, 2011 at 8:58 PM, Will Andrews wrote: > Hi Andrey, > > On Mon, Jun 20, 2011 at 5:46 AM, Andrey Chernov wrote: > > As the second message in the thread states, I try first even 223296 with > > the same hang and the same > > xpt_action_default: CCB type 0xe not supported > > As I think, DDB's 'ps' indicates that kernel waits something from geom > and > > geom waits something from ccb_scan forever, just raw guess. I will be > glad to > > issue more specific DDB commands and upload corresponding photos. > > BTW, pluging and unplugging USB devides works in that stage. > > Please try this patch: > http://people.freebsd.org/~will/patches/ata_xpt_add_advinfo.0.diff > > Thanks. > --Will. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Intel snd
I was wondering if there are any issues lately with snd_hda since I am not able to load the module anymore. Jun 22 16:04:59 core2duo kernel: interface snd_hda.1 already present in the KLD 'kernel'! Jun 22 16:04:59 core2duo kernel: linker_load_file: Unsupported file type > sysctl hw.snd hw.snd.vpc_reset: 0 hw.snd.vpc_0db: 45 hw.snd.vpc_autoreset: 1 hw.snd.latency_profile: 1 hw.snd.latency: 5 hw.snd.report_soft_matrix: 1 hw.snd.report_soft_formats: 1 hw.snd.compat_linux_mmap: 0 hw.snd.feeder_eq_exact_rate: 0 hw.snd.feeder_eq_presets: PEQ:16000,0.2500,62,0.2500:-9,9,1.0:44100,48000,88200,96000,176400,192000 hw.snd.feeder_rate_quality: 1 hw.snd.feeder_rate_round: 25 hw.snd.feeder_rate_max: 2016000 hw.snd.feeder_rate_min: 1 hw.snd.feeder_rate_polyphase_max: 183040 hw.snd.feeder_rate_presets: 100:8:0.85 100:36:0.92 100:164:0.97 hw.snd.vpc_mixer_bypass: 1 hw.snd.verbose: 0 hw.snd.maxautovchans: 16 hw.snd.default_unit: 0 hw.snd.version: 2009061500/amd64 hw.snd.default_auto: 1 > dmesg | grep 'pcm[0-9]' pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 0 nid 1 on hdac0 pcm2: http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Intel snd
Thanks, so I don't need to load sound.ko anymore either ? On Wed, Jun 22, 2011 at 4:58 PM, Sergey Kandaurov wrote: > On 22 June 2011 17:54, George Kontostanos wrote: > > I was wondering if there are any issues lately with snd_hda since I am > not > > able to load the module anymore. > > > > Jun 22 16:04:59 core2duo kernel: interface snd_hda.1 already present in > the > > KLD 'kernel'! > > Jun 22 16:04:59 core2duo kernel: linker_load_file: Unsupported file type > > Hi. > It is in GENERIC since svn r222980 (Jun 11). > > > -- > wbr, > pluknet > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Intel snd
Cheers! On Wed, Jun 22, 2011 at 5:53 PM, Sergey Kandaurov wrote: > On 22 June 2011 18:30, George Kontostanos wrote: > > Thanks, so I don't need to load sound.ko anymore either ? > > Yes. > > > > > On Wed, Jun 22, 2011 at 4:58 PM, Sergey Kandaurov > wrote: > >> > >> On 22 June 2011 17:54, George Kontostanos > wrote: > >> > I was wondering if there are any issues lately with snd_hda since I am > >> > not > >> > able to load the module anymore. > >> > > >> > Jun 22 16:04:59 core2duo kernel: interface snd_hda.1 already present > in > >> > the > >> > KLD 'kernel'! > >> > Jun 22 16:04:59 core2duo kernel: linker_load_file: Unsupported file > type > >> > >> Hi. > >> It is in GENERIC since svn r222980 (Jun 11). > >> > >> > >> -- > >> wbr, > >> pluknet > > > > > > > > -- > > George Kontostanos > > aisecure.net > > > > > > > > -- > wbr, > pluknet > -- George Kontostanos aisecure.net <http://www.aisecure.net> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
virtualbox-ose 4.0.8 fails
Hi everyone, I am trying to compile virtualbox-ose 4.0.8 but it fails with /out/freebsd.amd64/debug -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\" -DRT_LOCK_STRICT -DRT_LOCK_STRICT_ORDER -DDEBUG -DDEBUG_gkontos -DDEBUG_USERNAME=gkontos -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -DIN_RING3 -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM -DVBOX_MAIN_SETTINGS_ADDONS -DIN_VMM_STATIC -DVBOX_WITH_SYS_V_IPC_SESSION_WATCHER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_NETFLT -DVBOX_WITH_CROGL -DVBOX_WITH_GUEST_PROPS -DVBOX_WITH_GUEST_CONTROL -DVBOX_WITH_HOSTNETIF_API -DVBOX_WITH_VDE -DVBOX_WITH_NEW_SYS_V_KEYGEN -DVBOX_WITH_VBOXSDL -DVBOX_WITH_HEADLESS -DVBOX_WITH_QTGUI -DVBOX_WITH_HGCM -DVBOX_WITH_ALSA -DVBOX_WITH_E1000 -DVBOX_WITH_VIRTIO -DVBOX_WITH_AHCI -DVBOX_WITH_LSILOGIC -DVBOX_WITH_RESOURCE_USAGE_API -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_EXTPACK -DVBOX_WITH_VUSB -DVBOX_WITH_S3 -DVBOX_WITH_USB -DVBOX_WITH_NEW_USB_CODE_ON_DARWIN -DVBOX_WITH_HOSTNETIF_API -DVBOX_USE_LIBHAL -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o.dep -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o -Wp,-MP -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/out/freebsd.amd64/debug/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.8_OSE/src/VBox/Main/src-server/freebsd/HostHardwareFreeBSD.cpp kmk: *** Waiting for unfinished jobs kmk: *** Exiting with status 2 *** Error code 2 Stop in /usr/ports/emulators/virtualbox-ose. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. I have even try to build with debug symbols but I don't see anything different. The system is running GENERIC kernel with debug options disabled. options COMPAT_FREEBSD32 Is included in the kernel as I saw that this has caused similar problems in the past. Any help would be appreciated -- George Kontostanos aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: virtualbox-ose 4.0.8 fails
> > You should be able to build the kmod with this patch. > > http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-mp-r0drv-freebsd.c > > Just drop this patch in ports/emulators/virtualbox-ose-kmod/files and > rebuild. > > Please note the revision wasn't set right for the obvious reason, > though. Do we really need revision bump, BTW? "Current" means "no > seat belt" anyway. ;-) > > Cheers, > > Jung-uk Kim > Yes the module build fine with this. Any ideas regarding the virtualbox itself ? Cheers -- George Kontostanos aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: virtualbox-ose 4.0.8 fails
On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim wrote: > >> Any ideas regarding the virtualbox itself ? > > I am rebuilding world/kernel now. After that, I'll rebuild > virtualbox-ose and try to fix it unless someone beat me to it. :-) > > Jung-uk Kim > Brilliant !!! -- George Kontostanos aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: virtualbox-ose 4.0.8 fails
On Fri, Jun 24, 2011 at 11:11 PM, Jung-uk Kim wrote: > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim > wrote: >> >> Any ideas regarding the virtualbox itself ? >> > >> > I am rebuilding world/kernel now. After that, I'll rebuild >> > virtualbox-ose and try to fix it unless someone beat me to it. >> > :-) >> > >> > Jung-uk Kim >> >> Brilliant !!! > > Please try this patch: > > http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-freebsd-HostHardwareFreeBSD.cpp > > Just drop this in ports/emulators/virtualbox-ose/files and rebuild. > > Cheers, > > Jung-uk Kim > Excellent work! Best Regards, -- George Kontostanos aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dbus broken?
unsubscribe On Mon, Apr 24, 2023 at 10:02 AM Lizbeth Mutterhunt, Ph.D wrote: > > > > Wenn einem gar niets meer einfällt, schreit man auch nix. Mijn mute reminder! > > Begin doorgestuurd bericht: > > Van: "Lizbeth Mutterhunt, Ph.D" > Datum: 24 april 2023 om 08:58:54 CEST > Aan: current-us...@freebsd.org > Onderwerp: dbus broken? > > As I tried the CURRENT Image from Aor., 4th, I recognised the dbus Package > is broken, Even in Building from Ports. > > The Image from 20th Apr. is ok again. Something went wrong on Apr. 4th > (missing dbus config). > > Just for information purpose, now everything is fine again on my Acer > Vhromebook 314! > > Thx for patience! > > Liz > > Wenn einem gar niets meer einfällt, schreit man auch nix. Mijn mute reminder! -- George Kontostanos ---
