Re: error building stable/9 on FreeBSD 10
I had same issues, since 10 is have some CLANG changes it is not ready to cross-build 9. I think this deserve PR as major problem. 2013/10/31 Luigi Rizzo > I am having trouble building stable/9 on FreeBSD 10: > > luigi@bsd10:~ # uname -a > FreeBSD bsd10 10.0-BETA1 FreeBSD 10.0-BETA1 #0 r256420: Sun Oct 13 > 01:43:07 UTC > 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > # ./do TREE TARGET > # is a script that invokes a make in the source tree (first > argument), > # for a speciic target (second argument) and with a few options to > # do the build in a local subtree. > # Works fine building head on FreeBSD 10 and > # building 9 and head on FreeBSD 9 > > luigi@bsd10:~ ./do RELENG_9 toolchain > > > ... > ===> gnu/usr.bin/cc/cc_tools (depend) > --- genattrtab --- > --- genautomata --- > --- genconditions --- > --- genconfig --- > --- genconstants --- > --- genemit --- > --- genopinit --- > --- genoutput --- > --- genconstants --- > cc -O2 -pipe -I. -DGCCVER=\"4.2\" -DIN_GCC -DHAVE_CONFIG_H > -DPREFIX=\"/usr/home/luigi/FreeBSD/RELENG_9/../usr/obj-pico-amd64/usr/home/luigi/FreeBSD/RELENG_9/tmp/usr\" > -I/usr/home/luigi/FreeBSD/RELENG_9/../usr/obj-pico-amd64/usr/home/luigi/FreeBSD/RELENG_9/tmp/usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc > -I/usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config > -I/usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include > -I/usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include > -I/usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber > -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 > -I/usr/home/luigi/FreeBSD/RELENG_9/../usr/obj-pico-amd64/usr/home/luigi/ > FreeBSD/RELENG_9/tmp/legacy/usr/include -static > -L/usr/home/luigi/FreeBSD/RELENG_9/../usr/obj-pico-amd64/usr/home/luigi/FreeBSD/RELENG_9/tmp/legacy/usr/lib > -o genconstants genconstants.o rtl.o read-rtl.o ggc-none.o vec.o > min-insn-modes.o gensupport.o print-rtl.o errors.o libiberty.a -lm > print-rtl.o: In function `print_rtx': > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0x631): > undefined reference to `dump_addr' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0x6d1): > undefined reference to `insn_file' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0x6e9): > undefined reference to `insn_file' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0x6f4): > undefined reference to `insn_line' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0x772): > undefined reference to `reg_names' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0xc04): > undefined reference to `dump_addr' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0xc61): > undefined reference to `print_node_brief' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0xd39): > undefined reference to `bitmap_print' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0xe62): > undefined reference to `real_to_decimal' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0xe90): > undefined reference to `real_to_hexadecimal' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0xfac): > undefined reference to `mode_size' > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/print-rtl.c:(.text+0x1027): > undefined reference to `mode_size' > cc: error: linker command failed with exit code 1 (use -v to see > invocation) > *** [genconstants] Error code 1 > > make[4]: stopped in > /usr/home/luigi/FreeBSD/RELENG_9/gnu/usr.bin/cc/cc_tools > > > > any idea on what is going wrong ? > > cheers > luigi > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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: Problem building stable-9 in current host
Thanks for hint, I've rebuilt my host machine with given parameters, command was: make -DWITH_GCC=yes -DWITH_GNUCXX=yes buildworld buildkernel and make -DWITH_GCC=yes -DWITH_GNUCXX=yes -DNO_GAMES=YES -DNO_MAN=YES -DNO_INFO=YES -DNO_BLUETOOTH=YES -DNO_HTML=YES -DNO_SHAREDOCS=YES -DNO_EXAMPLES=YES installworld distribution installkernel DESTDIR=$mnt But I got same error while trying to build 9-Stable from sources. c++ -O2 -pipe -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/include -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/tool s/clang/include -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGen -I. -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../cont rib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd9 .2\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd9.2\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/zbuilder/vm4all/src-stable-9-clone/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /zbuilder/vm4 all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGen/X86RecognizableInstr.cpp make: don't know how to make /usr/lib/libstdc++.a. Stop *** [bootstrap-tools] Error code 2 Stop in /zbuilder/vm4all/src-stable-9-clone. *** [_bootstrap-tools] Error code 1 And my current host Pc: 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1 r256052: Sat Oct 5 03:20:01 EEST 2013 yama@r247396:/usr/obj/zbuilder/vm4all/src-head-clone/sys/GENERIC amd64 Do I really need other 9 to build 9-stable ? 2013/10/4 Davide Italiano > On Tue, Oct 1, 2013 at 9:05 AM, Alexander Yerenkow > wrote: > > Hello all. > > Can someone help me? :) > > [trim] > > > > > ===> usr.bin/clang/tblgen (obj,depend,all,install) > > ... > > c++ -O2 -pipe > > > -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/include > > -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/ > > clang/tblgen/../../../contrib/llvm/tools/clang/include > > > -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGe > > n -I. > > > -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/../../lib/clang/include > > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__S > > TDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing > > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd9.2\" > > -DLLVM_HOST_TRIPLE=\"x86_64 > > -unknown-freebsd9.2\" -DDEFAULT_SYSROOT=\"\" > > -I/usr/obj/zbuilder/vm4all/src-stable-9-clone/tmp/legacy/usr/include > > -fno-exceptions -fno-rtti -c /zbuil > > > der/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGen/X86RecognizableInstr.cpp > > make: don't know how to make /usr/lib/libstdc++.a. Stop > > *** [bootstrap-tools] Error code 2 > > > > It's one of the gifts of the recent "no gcc and libstdc++ built by > default". > I think the easiest way to fix that would be rebuilding world on your > 10 machine with WITH_GCC=yes and WITH_GNUCXX=yes in src.conf(5) > The long term solution, as proposed by dim@ is that of fixing > bsd.prog.mk in 9 and 8. > One of the major drawbacks of this, is that, even though it will be > done immediately, won't hit 9.2. > > Thanks, > > -- > Davide > > "There are no solved problems; there are only problems that are more > or less solved" -- Henri Poincare > -- Regards, Alexander Yerenkow ___ 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"
Problem building stable-9 in current host
Hello all. Can someone help me? :) # uname -a FreeBSD 10.0-ALPHA3 FreeBSD 10.0-ALPHA3 #5 r255924: Sat Sep 28 15:22:40 EEST 2013 yama@host:/zbuilder/local/obj/zbuilder/vm4all/src-head-clone/sys/GENERIC amd64 # svn info Path: . Working Copy Root Path: /zbuilder/vm4all/src-stable-9-clone URL: http://svn.freebsd.org/base/stable/9 Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 255962 make buildworld buildkernel produced: ===> usr.bin/clang/tblgen (obj,depend,all,install) ... c++ -O2 -pipe -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/include -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/ clang/tblgen/../../../contrib/llvm/tools/clang/include -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGe n -I. -I/zbuilder/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__S TDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd9.2\" -DLLVM_HOST_TRIPLE=\"x86_64 -unknown-freebsd9.2\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/zbuilder/vm4all/src-stable-9-clone/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /zbuil der/vm4all/src-stable-9-clone/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGen/X86RecognizableInstr.cpp make: don't know how to make /usr/lib/libstdc++.a. Stop *** [bootstrap-tools] Error code 2 Stop in /zbuilder/vm4all/src-stable-9-clone. *** [_bootstrap-tools] Error code 1 Stop in /zbuilder/vm4all/src-stable-9-clone. *** Error code 1 Stop. make: stopped in /zbuilder/vm4all/src-stable-9-clone Is it known issue, or I'm doing something wrong? This builder was working just fine by this scheme for a year, but to build more recent current I updated it self OS. -- Regards, Alexander Yerenkow ___ 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: Fwd: Problem with curret in vmware
2013/8/2 Attilio Rao > On Fri, Aug 2, 2013 at 8:27 PM, Alexander Yerenkow > wrote: > > > > That was their official tools, which are came from ISO which mounted with > > command "install/upgrade client tools". > > There is not much I can do then, unless they update their source-code. > Or do you have any pointer? > No, I just poked here, maybe there is someone who connected with them somehow. Currently I'm switched to open-vm tools and wrote in wiki about this caveat. Probably this is the only way for some time for me :) > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein > -- Regards, Alexander Yerenkow ___ 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: Fwd: Problem with curret in vmware
That was their official tools, which are came from ISO which mounted with command "install/upgrade client tools". 2013/8/2 Attilio Rao > On Tue, Jul 30, 2013 at 5:55 PM, John Baldwin wrote: > > On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote: > >> Hello all. > >> I have panics in vmware with installed vmwaretools (they are guessed > >> culprit). > >> Seems that memory balooning (or using more memory in all vms than there > is > >> in host) > >> produces some kind of weird behavior in FreeBSD. > >> This vm aren't shutted down now, is there somethin I can do to help > >> investigate this? > >> > >> Panic screens: > >> http://gits.kiev.ua/FreeBSD/panic1.png > >> http://gits.kiev.ua/FreeBSD/panic2.png > > > > Looks like their code needs to be updated to work with locking changes in > > HEAD. Attilio is probably the best person to ask. > > Exactly which is the ports you installed? > > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein > -- Regards, Alexander Yerenkow ___ 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: Problem with curret in vmware
Can I suggest? We desperately need for "vmware" page at wiki. I created stub, will fill it with known info to me, help and experience appreciated! https://wiki.freebsd.org/VmWare P.S. Some time ago there was message in lists, about improved speed of intel-emulated network card under vmware, this could go there too. 2013/7/31 Bryan Venteicher > > On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote: > > > Hello all. > > > I have panics in vmware with installed vmwaretools (they are guessed > > > culprit). > > > Seems that memory balooning (or using more memory in all vms than > there is > > > in host) > > > produces some kind of weird behavior in FreeBSD. > > > This vm aren't shutted down now, is there somethin I can do to help > > > investigate this? > > > > > > Panic screens: > > > http://gits.kiev.ua/FreeBSD/panic1.png > > > http://gits.kiev.ua/FreeBSD/panic2.png > > > > Looks like their code needs to be updated to work with locking changes in > > HEAD. Attilio is probably the best person to ask. > > > > This highlights why we should move away from the poorly supported, out of > tree, unfriendly licensed VMware tools. I have a port of the vmxnet3 from > OpenBSD [1] that I intend to commit in time for 10. Next, I hope to look > at the OpenBSD vmt [2] VMware tools driver. > > The balloon is a bit trickier. AFAIK, OpenBSD doesn't have a driver for > easy porting. The VMware tools driver for FreeBSD is GPL licensed, and > VMware has shown no interest/ability to relicense their tools. Likely, > the best way forward is to port their CDDL licensed Solaris driver. > > [1] - > http://svnweb.freebsd.org/base/projects/vmxnet/sys/dev/vmware/vmxnet3/ > [2] - > http://www.openbsd.org/cgi-bin/man.cgi?query=vmt&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html > > > -- > > John Baldwin > > ___ > > 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" > > > -- Regards, Alexander Yerenkow ___ 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"
Fwd: Problem with curret in vmware
Hello all. I have panics in vmware with installed vmwaretools (they are guessed culprit). Seems that memory balooning (or using more memory in all vms than there is in host) produces some kind of weird behavior in FreeBSD. This vm aren't shutted down now, is there somethin I can do to help investigate this? Panic screens: http://gits.kiev.ua/FreeBSD/panic1.png http://gits.kiev.ua/FreeBSD/panic2.png -- Regards, Alexander Yerenkow ___ 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: BSD sleep
I'm just saying that there's pretty space for discussion. If someone raised this now, why not discuss it now. > If you sleep one hour, do you sleep one hour from now or one hour from the system clock which may change in the next hour? If it's the system clock, you may sleep for ten minutes or ten hours. If you need to sleep for 3600 seconds, that's simple and understandable. How about rephrase it: > If you sleep 3600 seconds, do you sleep 3600 seconds from now or 3600 seconds from the system clock which may change in the next hour? If it's the system clock, you may sleep for ten minutes or ten hours. How "way of specifying period" changing the fact that "internal minimal unit of sleep" is not clearly specified in manpage? Also, there no info on how DST/ ntp time changes affects of running sleeps. I don't see right now how new flag (which currently if specified makes `sleep` exit with help), could break something, but I see that this is could be useful in some cases. This also raise question what sleep should do if something specified incorrectly, like sleep 2h30m30m , or 1h1h or else. And also if any changes would be accepted, this should be specified in manpage (that one about `m` as month). About non-portable feature with non-integers, it was just side observation. -- Regards, Alexander Yerenkow ___ 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: BSD sleep
>what is stopping from interpreting 1h in similar manner to 3600? i.e. from now No, this is user-friendly, and thus can't be done :) But if think a second, sleep is used rarely by average users, mostly by programmers and other scripts, and they should know better what they are doing. Seriously, that explanation about different hours is not enough to prevent at least useful option. like sleep -f 1h (-f means force convert, without it you can see good explanation why sleep for 1 hour will be not sleep for 1 hour, and etc, and not get sleep at all.). Exact units in which sleeps happens (seconds, ticks, minutes, years) can be described in manual page, even without accepting m,h - that info would be useful for one. P.S. There is already non-portable feature in sleep - non-integer, and I'm sure that no one thought about some financists from various countries, who used to specify long numbers with separator, e.g. 3.600, and this means for them one hour and not 3 point 6 seconds. -- Regards, Alexander Yerenkow ___ 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: head && auditdistd
That's a pretty anti-user design, when such information is pretty obscure and spread in Updating and wiki. You can have buildbox, which just builds worlds and install it not to self-host system, but instead to some image / or to other disk. And in one day all just stops working, and ask you to run mergemaster or manually add new user (Exactly was my case when this fresh user appeared) . Hm, even actually not asking, but simply failing with some message. If this is pretty obvious, why not insert adding this user into Makefile, with prompting if user actually wants to add it. That was my point, not the way of adding user itself. 2013/5/14 Justin Hibbits > You should run 'mergemaster -p' before installworld, as that would add any > necessary new users to the file. > > - Justin > On May 13, 2013 11:48 PM, "Matthias Apitz" wrote: > > > > > Hello, > > > > Today morning I wanted to make and install a fresh /head to an USB key > > for further distribution the usual way: > > > > ... > > # make installworld DESTDIR=/mnt > > # make installkernel DESTDIR=/mnt KERNCONF=GENERIC INSTALL_NODEBUG=t > > # make distrib-dirs DESTDIR=/mnt > > # make distribution DESTDIR=/mnt > > > > 'installworld' instructed me about the missing user 'auditdistd'; I have > > read what src/UPDATING says, but can't find any pointer to the man page > > of auditdistd(8) or in our handbook; with Don Google I got to know that I > > have to add this with something like > > > > # pw useradd -n auditdistd -g audit -c "Auditdistd unprivileged user" -d > > /var/empty -s /usr/sbin/nologin > > > > Can someone bring a bit light into this? Thanks in advance > > > > matthias > > > > -- > > Sent from my FreeBSD netbook > > > > Matthias Apitz | - No system with backdoors like > > Apple/Android > > E-mail: g...@unixarea.de | - Never being an iSlave > > WWW: http://www.unixarea.de/ | - No proprietary attachments, no > HTML/RTF > > in E-mail > > phone: +49-170-4527211 | - Respect for open standards > > ___ > > 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-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Regards, Alexander Yerenkow ___ 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: head && auditdistd
This is new (relatively) user which required in host machine when you make installworld. Months ago I proposed to add check for existence of this user at begin of any actions with sources (for example for interactive mode only, and optional for build-, but mandatory for install- ). But as it seems that just not happened, and more and more peoples are stumbling at same missed user-thing. Second thing, yes, would be good to have more information either in man or in handbook about this user and else. 2013/5/14 Matthias Apitz > > Hello, > > Today morning I wanted to make and install a fresh /head to an USB key > for further distribution the usual way: > > ... > # make installworld DESTDIR=/mnt > # make installkernel DESTDIR=/mnt KERNCONF=GENERIC INSTALL_NODEBUG=t > # make distrib-dirs DESTDIR=/mnt > # make distribution DESTDIR=/mnt > > 'installworld' instructed me about the missing user 'auditdistd'; I have > read what src/UPDATING says, but can't find any pointer to the man page > of auditdistd(8) or in our handbook; with Don Google I got to know that I > have to add this with something like > > # pw useradd -n auditdistd -g audit -c "Auditdistd unprivileged user" -d > /var/empty -s /usr/sbin/nologin > > Can someone bring a bit light into this? Thanks in advance > > matthias > > -- > Sent from my FreeBSD netbook > > Matthias Apitz | - No system with backdoors like > Apple/Android > E-mail: g...@unixarea.de | - Never being an iSlave > WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF > in E-mail > phone: +49-170-4527211 | - Respect for open standards > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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: Tell me how to increase the virtual disk with ZFS?
2013/5/11 Paul Kraus
> On May 11, 2013, at 10:03 AM, Alexander Yerenkow
> wrote:
>
> > There's no mature (or flexible, or "can do what I want" ) way to
> > increase/decrease disk sizes in FreeBSD for now {ZFS,UFS}.
> > Best and quickest way - to have twice spare space, copy data, create new
> > sufficient disk and copy back.
>
> Is this a statement or a question ? If a statement, then it is factually
> FALSE. If it is supposed to be a question, it does not ask anything.
>
It was a statement, and luckily I was partially wrong, as Vladislav did
made what he wanted to.
However, last time I checked there were no such easy ways to decrease
zpools or increase/decrease UFS partitions.
Or grow mirrored ZFS as easily as single zpool. Or (killer one) remove
added by mistake vdev from zpool ;)
Of course I'm not talking about real hw, rather virtual one.
If you happen to point me somewhere to have such task solved I'd be much
appreciated.
> --
> Paul Kraus
> Deputy Technical Director, LoneStarCon 3
> Sound Coordinator, Schenectady Light Opera Company
>
>
--
Regards,
Alexander Yerenkow
___
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: Tell me how to increase the virtual disk with ZFS?
There's no mature (or flexible, or "can do what I want" ) way to
increase/decrease disk sizes in FreeBSD for now {ZFS,UFS}.
Best and quickest way - to have twice spare space, copy data, create new
sufficient disk and copy back.
2013/5/11 Vladislav Prodan
>
> I have a Debian server virtual ok with Proxmox.
> In one of the virtual machines is FreeBSD 9.1 ZFS with one disk to 100G.
> Free space is not enough, how to extend the virtual disk without losing
> data?
>
> Add another virtual disk and do a RAID0 - not an option. It is not clear
> how to distribute the data from the old virtual disk to the new virtual
> disk.
>
> The manual of the Proxmox http://pve.proxmox.com/wiki/Resizing_disksFreeBSD
> is not mentioned :(
>
> You may have to do a Native ZFS for Linux on Proxmox and it will be easier
> to resize the virtual disk for the virtual machines?
>
> --
> Vladislav V. Prodan
> System & Network Administrator
> http://support.od.ua
> +380 67 4584408, +380 99 4060508
> VVP88-RIPE
> ___
> 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"
>
--
Regards,
Alexander Yerenkow
___
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: Light humour
Not criticizing, just commenting. I heard such utter nonsense sometimes, in which people do believe despite all common sense, that I'm not amused, but scared :) This blog is humor to very small, limited group of people, and at same time it's anti-bsd blog to bigger audience, who will not bother read some lines, instead peek in title, get few words here, few there, and close it. In they memory will be essence - that *BSD is suck, probably not allover, but they will remember that there are exist areas in which BSD have big problems. Mix this with lacking `nextgen techs` like KMS, decent virtualization level, no utf-8 in console and other myths, partial myths, or obsolete problems of old releases, and you'll receive bad opinion on BSD. But, there's not much to be done actually :) -- Regards, Alexander Yerenkow ___ 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: Cannot unmount nullfs in current
Can we pretend an user-friendly-os and spam to syslog corresponding blocking file and process whenever umount going to fail ? :) Like, make this to be default ( or with some key at least ) behavior of umount. Regards, Alexander Yerenkow ___ 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: Unexpected SU+J inconsistency AGAIN -- please, don't shift topic to ZFS!
2013/2/28 Lev Serebryakov > Hello, Lev. > You wrote 28 февраля 2013 г., 12:33:25: > > LS>> My server runs 9.1-STABLE and have 8Tb UFS2 SU+J FS. > LS>> It crashed a several minutes ago (I don't know reason yet) and fsck > LS>> says "Unexpected SU+J inconsistency" (Inode mode/directory tyme > LS>> mismatch) and requested full check (which will take more than hour on > LS>> such FS). > LS> Full fsck found "INTERNAL ERROR: DUPS WITH SOFTUPDATES" and keeps > running... > full fsck reconnected about 1000 files, which was written in time of > crash. > Really, sever crashed when SVN mirror seed was been unpacking on > this FS, so there was massive file creation at this time. > > Could you afford reproducing this? :) Also, would be nice to know how look your setup (CPUs, how much disks, how they connected, is it hw raid, etc). > -- > // Black Lion AKA Lev Serebryakov > > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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: Unexpected SU+J inconsistency AGAIN -- please, don't shift topic to ZFS!
How about tell us 9.1-STABLE from which date you run? Do you use any dumps/snapshots in this FS? In past, that could broke things. -- Regards, Alexander Yerenkow ___ 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 Testing Facility
How about create -testing mail list, and start searching for any kind of volunteers? I could lend a hand in creating auto-testing some aspects of FreeBSD (at leas successful booting/working net/route etc), someone else probably could have to say something too. I think resources are there, they just need to be gathered :) -- Regards, Alexander Yerenkow ___ 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 Testing Facility
Decent testing system is a pretty complex system to be. I spent some time in this area, and gave it up, at least till better times :) But anyway, at least booting/working network stack/firewall could be easily tested with VMs. There just need to be a person dedicated to this, which is lacking now. -- Regards, Alexander Yerenkow ___ 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: Auditdistd user question
2013/1/2 Chris Rees > On 2 January 2013 14:04, Alexander Yerenkow wrote: > > Hello there and please excuse my harshness. > > > > I just installed 9.1, and I tried to set up poudriere with 9/stable. > > It took a lot of time compiling kernel and world, and after this it all > > failed with message about missing auditdistd user. > > I just can't find words. > > Why this user presence not checked during buildworld at least? Or by just > > invoking updated Makefile? If there any need to build world without > install > > it, wouldn't be better make some conditional flag, > > like BUILD_WITHOUT_AUDITDISTD, instead of silent building and failing > after > > that at install stage. > > Of course, in current way just "buildworld" not broken, but "buildworld > > installworld" is. > > This looks like like carefully hidden trap, from someone with specific > > sense of humor. > > Or am I missing something, and this is not terribly wrong? > > While I agree with you in principle, I must point out that you mustn't > try to run package builds on a newer jail than your host. This causes > weird kernel/world synchronisation issues. > I'm just provided info about my setup as background. My main builder is on some current revision, and it can't build 9.1 due to some compiler bug. To not mess with upgrading it, I tried to setup additional 9.1 builder (With having in plans probably upgrade host to stable, maybe not). I just think that such improvements could be improved, and in future better think of all possible cases, not about one. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169659 [for an example] > > As far as I know there are no problems with running older jails on > newer hosts (thankfully). > > Chris > -- Regards, Alexander Yerenkow ___ 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: Reproduceable hang
I'm using official tools, not open ones. Will try to repeat this at saturday with openvm tools. I could place somewhere their archive. Btw, they require compat6x. Regards, Alexander Yerenkow 14.12.2012 16:39 пользователь "Andriy Gapon" написал: > on 14/12/2012 14:46 Alexander Yerenkow said the following: > > Setup: ESXi 5.1.0 > > Seems this happens when vmmemctl.ko loaded (from their latest vmtools), > and when > > you give a bit more memory than there is free. > > This is weird... As I can see in os_kmem_alloc function (in > modules/freebsd/vmmemctl/os.c of /usr/ports/emulators/open-vm-tools port), > the > object lock is correctly acquired there. I suspect some binary > incompatibility > between the module and your kernel. Try to recompile the module again > using the > same source tree tree and the option. > > > 2012/12/13 Andriy Gapon mailto:a...@freebsd.org>> > > > > on 13/12/2012 12:46 Alexander Yerenkow said the following: > > > 2012/12/13 Alexander Yerenkow yeren...@gmail.com>> > > > > > >> Hello there. > > >> I have here 100% reproduceable hangs when run one custom java > program. > > >> Can someone look into? > > >> > > >> I can give some more info (some other trace) if required. > > >> > > >> > > > > > > > > > If someone didn't get attachment - here's link to screenshot > > > > > > https://www.box.com/s/fir8ntjc4rjq5xv0vbyl > > > > Looks like either a bug or an "out-of-sync" issue in whatever > (virtualization?) > > driver that has function OS_ReservedPageAlloc. > > -- > 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"
Re: Reproduceable hang
Setup: ESXi 5.1.0 Seems this happens when vmmemctl.ko loaded (from their latest vmtools), and when you give a bit more memory than there is free. 2012/12/13 Andriy Gapon > on 13/12/2012 12:46 Alexander Yerenkow said the following: > > 2012/12/13 Alexander Yerenkow > > > >> Hello there. > >> I have here 100% reproduceable hangs when run one custom java program. > >> Can someone look into? > >> > >> I can give some more info (some other trace) if required. > >> > >> > > > > > > If someone didn't get attachment - here's link to screenshot > > > > https://www.box.com/s/fir8ntjc4rjq5xv0vbyl > > Looks like either a bug or an "out-of-sync" issue in whatever > (virtualization?) > driver that has function OS_ReservedPageAlloc. > > -- > Andriy Gapon > -- Regards, Alexander Yerenkow ___ 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: Reproduceable hang
2012/12/13 Alexander Yerenkow > Hello there. > I have here 100% reproduceable hangs when run one custom java program. > Can someone look into? > > I can give some more info (some other trace) if required. > > If someone didn't get attachment - here's link to screenshot https://www.box.com/s/fir8ntjc4rjq5xv0vbyl -- Regards, Alexander Yerenkow ___ 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 as read-only firmware
2012/12/4 Warner Losh
> [ replying to an old thread, sorry ]
>
> On Nov 3, 2012, at 4:56 PM, Lev Serebryakov wrote:
>
> > Hello, Alexander.
> > You wrote 4 ноября 2012 г., 2:12:03:
> >
> > AY> Quick glance to nanobsd give me impression that:
> > AY> 1) nanobsd is MBR based, so :
> > AY> 2) nanobsd is disk-name-change sensitive.
> > Here are patches to support GPT
>
> I'd love to see those... The mailing list must have eaten the original
> ones.
>
> > AY> GPT way is better - I'm using r${REV} as label, and root can be
> mounted no
> > AY> matter how many other "firmware's" present, or how disks are ordered.
> >
> > AY> BTW, due to bug 173309 I had to rebuild and update my server, which
> took
> > AY> only few minutes for reboot.
> >
> > AY> Well, nanobsd is great thing, I'll look into it a bit more, but it's
> goal
> > AY> to have minified FreeBSD, while I need read-only one.
> > No. Its goal is to have RO and ACID-upgradable system (with two code
> > slices for this).
>
> Yes. NanoBSD's way isn't the best, and if there's better ways for it to do
> its thing, then I'm all for updating it to cope better. I have a bit of a
> backlog of NanoBSD patches to get to, which is why this caught my eye, and
> since 9.1 will soon be a totally done deal, what better time to hack on
> NanoBSD and merge...
>
I'm using these simple scripts
https://github.com/yerenkow/freebsd-vm-image/tree/master/freebsd-firmware
to build RO-images both for VMs and for SD cards (GPT or MBR for buggy
BIOSes). I don't like idea of upgrading something (via some doubling
partitions, or else), at this stage; it's still potential room for problems.
Have one release image fully replaced by other release image - is what
seems fit for my goals and requirements; possibility of adding some
checksums would be nice too.
Probably this could be implemented in nanoBSD too.
>
> Warner
>
> ___
> 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"
--
Regards,
Alexander Yerenkow
___
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: weird network problems on current since 10/28/2012
Could this be same problem - PR/173309 ? -- Regards, Alexander Yerenkow ___ 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 as read-only firmware
Quick glance to nanobsd give me impression that:
1) nanobsd is MBR based, so :
2) nanobsd is disk-name-change sensitive.
GPT way is better - I'm using r${REV} as label, and root can be mounted no
matter how many other "firmware's" present, or how disks are ordered.
BTW, due to bug 173309 I had to rebuild and update my server, which took
only few minutes for reboot.
Well, nanobsd is great thing, I'll look into it a bit more, but it's goal
to have minified FreeBSD, while I need read-only one.
--
Regards,
Alexander Yerenkow
___
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 as read-only firmware
2012/11/3 Mehmet Erol Sanliturk > > > On Sat, Nov 3, 2012 at 9:08 AM, Alexander Yerenkow wrote: > >> Actually in my case, base system image r24243.vmdk, have exactly two >> partitions (gpt's freebsd-boot, and roots = freebsd-ufs), and second one is >> used only in read-only :) >> >> For virtual machines approach, base image can be even ISO, which will be >> implied RO for system, and upgrade is just switch ISO. >> >> For real hardware, it can be done with such approach - make two >> partitions with fixed size, and when you need upgrade - just `dd` new image >> to other partition, mark it as [bootonce] (And if all is ok, as [bootme]), >> reboot = and you have new OS very quick, with same configs (except for some >> LARGE changes which could happen in /etc and touch your configs), and with >> same packages. >> >> BTW, when you mount /etc-rw union over /etc, when you'll need upgrade, >> mergemaster could take less time, less places for errors - since you had to >> merge only changed files(which present on /etc-rw). >> I think these days with current hw, no one will complain against lost 1Gb >> to achieve clean and simple OS upgrade. >> >> I'm not saying about possible way to shrink it further (no debug, gzip, >> etc) - get lesser partition, but still RO, and get ability to make >> something dd if=/dev/gpt/rootfs bs=1M | sha256 >> >> >> -- >> Regards, >> Alexander Yerenkow >> > > > > I am assuming that ANY SOFTWARE read-only protection , whatever it is , > has security vulnerability . > Therefore , the first approach should be to provide HARDWARE read only . > If this is supplied , the next necessity is that , programs in > write-protected part should not attempt to write anything onto > write-protected part . > If you consider writing as a security issue, you better should look at cd-r, and also for hash checking with public-private keys pair (you prepare image, put there public key, calc hash, sign hash with your private key, and make some script to check hash during boot, and probably over time). And don't be over-concerned about security, it's danger one-way road. > > > > Thank you very much . > > Mehmet Erol Sanliturk > > > > > > -- Regards, Alexander Yerenkow ___ 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 as read-only firmware
Actually in my case, base system image r24243.vmdk, have exactly two partitions (gpt's freebsd-boot, and roots = freebsd-ufs), and second one is used only in read-only :) For virtual machines approach, base image can be even ISO, which will be implied RO for system, and upgrade is just switch ISO. For real hardware, it can be done with such approach - make two partitions with fixed size, and when you need upgrade - just `dd` new image to other partition, mark it as [bootonce] (And if all is ok, as [bootme]), reboot = and you have new OS very quick, with same configs (except for some LARGE changes which could happen in /etc and touch your configs), and with same packages. BTW, when you mount /etc-rw union over /etc, when you'll need upgrade, mergemaster could take less time, less places for errors - since you had to merge only changed files(which present on /etc-rw). I think these days with current hw, no one will complain against lost 1Gb to achieve clean and simple OS upgrade. I'm not saying about possible way to shrink it further (no debug, gzip, etc) - get lesser partition, but still RO, and get ability to make something dd if=/dev/gpt/rootfs bs=1M | sha256 -- Regards, Alexander Yerenkow ___ 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 as read-only firmware
2012/11/3 Lev Serebryakov > Hello, Alexander. > You wrote 3 ноября 2012 г., 16:14:21: > > AY> Hello all! > AY> Some time ago I got somewhere idea, that base OS should be RO - > readonly. > AY> And should be updated easily (ACID) and with possibility of fast > rollback. > Why it is better than nanobsd? > Of course, that's all IMHO and fit for my usage: 1) Same FreeBSD, as in laptop/desktop, (e.g. really same - GENERIC kernel is used, without dropping any kerberos or else), and yes, I know that nanobsd can that; 2) .vmdk simply deployed into Esxi/virtualbox (not sure nanobsd can produce that) 3) Transparent /etc/ modifiying VS nanobsd approach (edit, don't forget mount /cfg, copy there;) 4) Only OS, no packages included - e.g. I can upgrade/downgrade packages without touching any byte of OS. Except for symlinks :) nanobsd specified that if you want packages - you need built them in. Of course differences not so big, and I'm not saying that my way is more better. It just raised question deep in me - why OS still aren't modularized, and most of it not in RO (while it should). Something like this > -- > // Black Lion AKA Lev Serebryakov > > -- Regards, Alexander Yerenkow ___ 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 as read-only firmware
Hello all! Some time ago I got somewhere idea, that base OS should be RO - readonly. And should be updated easily (ACID) and with possibility of fast rollback. So, basically ideas was to have some RO root, with unionfs with other dirs. But then all machines was real (not virtualised), and predict some best layout of partitioning was hard. ZFS was nice, but it is not supported by unionfs (not fully IIRC). When I'm started working with virtual machines this idea is came back, and with help from Andriy Gapon, I made some progress. So, here I got some proof-of-concept, with FreeBSD in RO mode, and I want to share. Comments and thoughts appreciated! So, how to achieve RO FreeBSD? Firstly, you need create media with OS itself, and have it in .vmdk format (you can import it into any VM machine, and boot from it). My scripts doing install in memory-based md disk, dump it to flat file, creating from flat file .vmdk (ATA) by VBoxManage, and convert descriptor file, so VMware Esxi can import disk as SCSI (much faster than ATA). Here disks I have in VM: r24243.vmdk 750Mb #OS -- I did not tried to shrink it as possible, it could be much less if you want to. disk1.vmdk 2Gb # 128M = etcfs, 1.8Gb = localfs disk2.vmdk XXXGb # data here disk3.vmdk 8Gb #swap here's how look mount: /dev/gpt/r242434 on / (ufs, local, read-only) # r24243.vmdk devfs on /dev (devfs, local, multilabel) /dev/gpt/etcfs on /etc-rw (ufs, local, noatime) # disk1.vmdk :/etc-rw on /etc (unionfs, local) /dev/gpt/localfs on /usr/local (ufs, local, noatime) # disk1.vmdk /dev/md0 on /tmp (ufs, local) :/usr/local/usr-bin-rw on /usr/bin (unionfs, local) :/usr/local/root-rw on /root (unionfs, local) devfs on /usr/local/var-root/named/dev (devfs, local, multilabel) /dev/gpt/data on /usr/local/data (ufs, local) # disk2.vmdk Also, /var is symlinked to /usr/local/var-root. So, this setup shows how to upgrade OS = just replace r24243.vmdk with some REL10.vmdk or else rev. Also, /usr/local update possible - just setup all in some other machine, and bring new disk1.vmdk with fresh programs (Assuming all data is moved or symlinked to partition with data). The only caveat I got - is Perl (and probably some other programs) required to place some symlinks to /usr/bin <- so I had to create usr-bin-rw. Maybe there will be some other problems, but now I have production server set up in such way, working and not complainig :) So, this all raised such questions in my head - is it OK to have configs, scripts, data dirs, and default configs all messed in /etc ? :) I understand that this is how it historically happen, but have all partition in RW mode just to be able edit few files... Not want produce flamewar here, but this dir I think should be revised in some future. You can view my scripts here: https://github.com/yerenkow/freebsd-vm-image/tree/master/freebsd-firmware Thanks! -- Regards, Alexander Yerenkow ___ 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: Cross Architecture Compiling
Not sure if it helps, but maybe related: http://lists.freebsd.org/pipermail/freebsd-hackers/2012-September/040428.html -- Regards, Alexander Yerenkow ___ 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: pkgng and vmware-tools
Actually, I was mentioning their oficial tools, which provided as a cd with esxi. I thought maybe.situatiin like these will require some fake, but working pkg_info (and maybe other tools too, this could.be made as a different wrapper-port) when pkg are used and pkg_legacy not present (they should go away to ports anyway). But open tools of course will reqiure a bit more love too. Regards, Alexander Yerenkow ___ 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"
pkgng and vmware-tools
JFYI: When installing vmware tools from ESXI 5.x, their script trying to discover X, and some packages by invoking pkg_info (as it seems): pkg_info: Don't use the pkg_ tools if you are using pkgng pkg_info: no packages installed pkg_info: Don't use the pkg_ tools if you are using pkgng pkg_info: no packages installed Not sure if this could be fixed by upstream, but some workarounds like patch for "vmware-install.pl" would be appreciated by those who use X :) -- Regards, Alexander Yerenkow ___ 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: Raspberry PI gets USB support [FreeBSD 10 current]
http://www.raspberrypi.org/archives/2221 Is this will help somehow? :) 2012/9/14 Alexander Yerenkow > Well, I have 3 sd cards, and only one of them could boot prev kernel; > Currently, new mine built kernel can't mount working card too, only > difference that I got error 6 (IIRC) instead of 19. > I can check this if it's matters tomorrow. > > -- > Regards, > Alexander Yerenkow > -- Regards, Alexander Yerenkow ___ 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: A little question about safe mode
That's not what I want; If you press question mark at root prompt - to view choices, all devices are seen without /dev/, which leads further to single user mode fall-in. You can see screens with this situation. I think patch should be limited to ufs, then all should be ok - we could specify disk with, or without leading "/dev/" and all will "just work". At least this is how I see solution for this bug. Or, if this way is somehow bad - just extend help, so there will be less bruises at this point. Thanks. Regards, Alexander Yerenkow ___ 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: A little question about safe mode
2012/10/18 Andriy Gapon :
> on 18/10/2012 18:33 Andriy Gapon said the following:
>> on 18/10/2012 18:20 Andriy Gapon said the following:
>>> My guess is that the easiest way to avoid this ambiguity and the confusion
>>> that it
>>> causes (like the problem you described above) is to prepend "/dev/", if it's
>>> missing, right in vfs_mountroot.c before calling kernel_mount().
>>
>> A patch (not tested):
>>
>> --- a/sys/kern/vfs_mountroot.c
>> +++ b/sys/kern/vfs_mountroot.c
>> @@ -676,6 +676,7 @@ static int
>> parse_mount(char **conf)
>> {
>> char errmsg[255];
>> + char devbuf[MNAMELEN];
>> struct mntarg *ma;
>> char *dev, *fs, *opts, *tok;
>> int delay, error, timeout;
>> @@ -693,6 +694,11 @@ parse_mount(char **conf)
>> parse_advance(&tok);
>> dev = tok;
>>
>> + if (dev[0] != '\0' && strncmp(dev, "/dev/", 5) != 0) {
>> + snprintf(devbuf, sizeof(devbuf), "/dev/%s", dev);
>> + dev = devbuf;
>> + }
>> +
>> if (root_mount_mddev != -1) {
>> /* Handle substitution for the md unit number. */
>> tok = strstr(dev, "md#");
>>
>>
>
> Oops, the patch incorrectly assumes that all "device names" are device names,
> which is incorrect e.g. for ZFS. Maybe some other filesystems too.
> So don't try it :-)
I think correct patch should fix path and prepend "/dev/" only for
ufs:, for now.
Or at least help should mention this moment.
>
> --
> Andriy Gapon
--
Regards,
Alexander Yerenkow
___
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: A little question about safe mode
2012/10/18 Andriy Gapon > on 18/10/2012 12:11 Alexander Yerenkow said the following: > > 2012/10/18 Andriy Gapon mailto:a...@freebsd.org>> > > > > > > First, I see "safe mode" mentioned in the subject, but nowhere in > the body of > > the message? So, what's up with the safe mode? :-) > > > > > > The single mode of course, which is forced :) Mistype, sorry. > > I missed this part - what do you mean by "forced"? > You can send the screenshots (as links). > Here are screenshots, step-by step. http://imageshack.us/photo/my-images/407/sc1y.png/ http://imageshack.us/photo/my-images/90/sc2xs.png/ http://imageshack.us/photo/my-images/713/sc3y.png/ http://imageshack.us/photo/my-images/213/sc4h.png/ > > -- > Andriy Gapon > -- Regards, Alexander Yerenkow ___ 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: A little question about safe mode
Okay, anyway there's something wrong here, so I created misc/172849 -- Regards, Alexander Yerenkow ___ 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: A little question about safe mode
2012/10/18 Andriy Gapon > > First, I see "safe mode" mentioned in the subject, but nowhere in the body > of > the message? So, what's up with the safe mode? :-) > The single mode of course, which is forced :) Mistype, sorry. > on 18/10/2012 10:35 Alexander Yerenkow said the following: > > Hello there. > > I have problem here, and don't know if it's bug or "feature" :) > > If I prerare boot media (hdd, sd card,usb, etc) with FreeBSD, and NOT > > create there fstab, I see such behavior: > > > > 1. I need enter manually where from mount root (e.g. ufs:ada0s1a or > > ufs:ada0s1a rw) > > This is a feature. > You might want consider using options ROOTDEVNAME in your kernel. > Okay, then why little help there mentioning "rw" as an option? It's of bug in help there, or in parsing mount options (rw is ignored). If I'm not fully clear - I can provide some screenshots. > > > 2. If I enter ufs:ada0s1a rw - I have / mounted in read-only anyway. <== > Is > > this bug?... > > It looks like a feature. The low-level mountroot code always mounts / as > r/o. It's supposed to be later remounted as r/w by rc.d/root script. > Yes, it's feature when it mounting with default parameters (e.g. with none). But what about rw? > > > 3. If I try to make it rw, with commands > > mount -o rw -u /dev/ada0s1a / > > there is no errors, but root is still RO. > > This sounds like a bug. > Is there anything on the system console? > Nope, I'm already on console in single mode. > > 4. I can't umount / remount some elsewhere this disk, just to create > fstab > > (it's already mounted and can't be updated). > > > > So, is this as-by-design, that you need "any other" media to boot, just > to > > create fstab, or there is "rw" mode broken, or I just missed something? > > > > It's very disappointing to be able boot interactively into system, but > have > > no way to "fix" fstab to make it non-interactively bootable :) > > You can try to create an md-based filesystem, mount it under /mnt and then > unionfs-mount it over /etc. > That's not solve problem that on my rootfs no fstab exists, so next boot will bring me to same situation. If someone willing to help/debug with this thing - get any bootable media (like live FreeBSD), and just rename/move/delete fstab file, and simply boot. > > -- > Andriy Gapon > -- Regards, Alexander Yerenkow ___ 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"
A little question about safe mode
Hello there. I have problem here, and don't know if it's bug or "feature" :) If I prerare boot media (hdd, sd card,usb, etc) with FreeBSD, and NOT create there fstab, I see such behavior: 1. I need enter manually where from mount root (e.g. ufs:ada0s1a or ufs:ada0s1a rw) 2. If I enter ufs:ada0s1a rw - I have / mounted in read-only anyway. <== Is this bug?... 3. If I try to make it rw, with commands mount -o rw -u /dev/ada0s1a / there is no errors, but root is still RO. 4. I can't umount / remount some elsewhere this disk, just to create fstab (it's already mounted and can't be updated). So, is this as-by-design, that you need "any other" media to boot, just to create fstab, or there is "rw" mode broken, or I just missed something? It's very disappointing to be able boot interactively into system, but have no way to "fix" fstab to make it non-interactively bootable :) Thanks. -- Regards, Alexander Yerenkow ___ 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: GPIO on Raspberry Pi
2012/9/16 Sevan / Venture37 > Hi, I managed to get FreeBSD/arm on a Raspberry Pi this weekend, kernel is > booted from an SD card & root fs is mounted via a USB flash drive (by > hardcoding the path in the kernel config 'options > ROOTDEVNAME=\"ufs:/dev/da0s1a\"' > I was unable to mount / from the sd card otherwise as it appears the > SD is not detected by the kernel, also if there's no cable plugged > into the ethernet port the kernel doesn't detect the interface. > > Hi. We really need get gonzo@ back from vacation, or where he is now :) Internal SD is working via device sdhci (patch available for head at people.freebsd.org/~gozno/patches/ , but seems incomplete, kernel not building ok for me) > dmesg up at http://www.nycbug.org/?action=dmesgd&dmesgid=2417 > 10.0-CURRENT FreeBSD 10.0-CURRENT #4 r240529: Sun Sep 16 11:56:48 BST 2012 > > I was wondering what status of GPIO support for the pi is, kernel > manages to build happily with device gpio & gpioled specified but I > don't see anything related to gpio when I boot the kernel. > > Regards > > Sevan / Venture37 > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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: Raspberry PI gets USB support [FreeBSD 10 current]
Well, I have 3 sd cards, and only one of them could boot prev kernel; Currently, new mine built kernel can't mount working card too, only difference that I got error 6 (IIRC) instead of 19. I can check this if it's matters tomorrow. -- Regards, Alexander Yerenkow ___ 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: Raspberry PI gets USB support [FreeBSD 10 current]
We tested kernel built by gonzo@, there working framebuffer, ue0, and USB2.0 devices (in theory, I didn't have those). But after some activity (like download few megabytes file) all is stuck with message usb device stalled This is getting 100% repeatedly, no matter if download goes to sd card, or to malloc-md-device. If (When) this will be fixed, then Rpi would be a candy, prepared to testing and more or less usable. I have in plans try it with xorg-framebuffer, and with directfb, while there's no video support. -- Regards, Alexander Yerenkow ___ 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: pkg (aka pkgng) 1.0 released
I just found out, that first call of pkg (which also known as bootstrap) became interactive, and without options. This kinda brokes a bit my automated image creation scripts (which builds images from svn). Would it be nice to have non-interactive bootstrap, maybe pkg --bootstrap or something similar. About interactivity - yes, currently it's one question, yes/no, but I think it's better to make both way now, from beginning rather than later. Thanks. -- Regards, Alexander Yerenkow ___ 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: Where to ask questions about poudriere?
I don't see where you specify your zfs tank, is it missed in mail, or in conf? 2012/9/6 Rainer Duffner > Hi, > > I'm trying to get poudriere working with the following settings: > > f2d169d8-20d2-41d4-8e43-8a9fc5a2b509# cat /usr/local/etc/poudriere.conf > |grep -v ^# |grep -v ^$ ZPOOL=datapool > FTPHOST=ftp.ch.freebsd.org > FREEBSD_HOST=http://ftp.ch.freebsd.org/ > RESOLV_CONF=/etc/resolv.conf > BASEFS=/usr/local/poudriere > USE_PORTLINT=no > USE_TMPFS=yes > DISTFILES_CACHE=/usr/ports/distfiles > CSUP_HOST=localhost > CHECK_CHANGED_OPTIONS=yes > PKG_REPO_SIGNING_KEY=/etc/ssl/keys/repo.bla.ch.key > CCACHE_DIR=/data/cache/ccache > > > f2d169d8-20d2-41d4-8e43-8a9fc5a2b509# > cat /usr/local/etc/poudriere.d/make.conf WITH_CCACHE_BUILD=yes > USE_LOCAL_MK=yes > > f2d169d8-20d2-41d4-8e43-8a9fc5a2b509# poudriere bulk -f > ~/portlist-current-php53-mysql55 -j 90amd64 >> Mounting system > devices for 90amd64 /etc/resolv.conf > -> /usr/local/poudriere/jails/90amd64/etc/resolv.conf >> Starting > jail 90amd64 >> Mounting ports filesystems for 90amd64 > >> Mounting ccache from /data/cache/ccache > mount: /usr/local/poudriere/jails/90amd64/usr/ports/distfiles: No such > file or directory >> Umounting file systems > Failed to mount the distfile directory > You have new mail. > > > f2d169d8-20d2-41d4-8e43-8a9fc5a2b509# zfs list > NAME USED AVAIL REFER MOUNTPOINT > datapool 1.51G 47.5G32K /datapool > datapool/poudriere1.51G 47.5G > 33K /datapool/poudriere datapool/poudriere/data 36K > 47.5G36K /usr/local/poudriere/data > datapool/poudriere/jails 1017M 47.5G > 31K /datapool/poudriere/jails datapool/poudriere/jails/90amd64 1017M > 47.5G 1017M /usr/local/poudriere/jails/90amd64 > datapool/poudriere/ports 534M 47.5G > 31K /datapool/poudriere/ports datapool/poudriere/ports/current 534M > 47.5G 534M /usr/local/poudriere/ports/current > > > What is the problem? > > > > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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"
Fstab file path
Hello all. I'm trying to get single-world in read-only and multi-userland media and I get difficulties with path "/etc/fstab" been hardcoded and there is no way for override it. I'm talking about getrootmount in sys/boot/common/boot.c:315 Could we elaborate a bit this moment? What I'm trying to do is to get one single partition, with installed world+kernel; let's call it rootPT and also I have few partitions for mount to /usr/local and to /var, like localA, varA, localB, varB, etc. Main difficulty is that "fstab" path is hardcoded, and it searched in subdir of root partition, and I can't specify it in any way in stock FreeBSD. How about have one more env with path to fstab (like vfs.root.mountfrom, but with vfs.fstab.filepath, which checks, and if it's null falling back to default hard-coded one)? Note, that this will not change some default standards or behaviors, it will just add some flexibility. Currently, to make media as I need, I would need several absolutely same filesystems on different partitions, just to separate fstabs (As a result - duplication of world/kernel, or I end up with complex root system with many links). With ability to set path to fstab, I would need only edit loader.conf and restart system into new setup. Also, I noticed that fstab.c is implemented way for specifying different fstab (maybe just for editing?...). But there's also relatively lot of other scripts which used hardcoded fstab path too. Now I'm thinking that I'll end up with writing handy script which will override /etc/fstab just before reboot :) I just thought that lack of flexibility in this point could be interesting for someone. -- Regards, Alexander Yerenkow ___ 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: [CFT] Xorg 7.7 ready for testing!
Hello All! I'm created unofficial pkg repo for patched xorg tree. I'm still experimenting with it, but I already have built all required packages for CURRENT i386. You can find it here: http://pkgng.gits.kiev.ua/packages/test10-32-kmsxorg/ If anyone want to test new xorg, you can install all required packages using ports/pkg. pkg install -x xorg\* pkg install -x xf86\* pkg install xterm Also, you can try kde4 in this repo, pkg install kde I'll provide xorg testing enthusiasts with prebuilt images for "simply boot it and report any feedback" in near future. -- Regards, Alexander Yerenkow ___ 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"
Can't build amd64 version from 9.0-p3 host
Hello all, I have some problem with building amd64 version of current, while having 9 host. # svn status ? kernel.log ? world.log ? kernel2.log # svn info Path: . Working Copy Root Path: /zstorage/testenv/sources/10-kms URL: http://svn.freebsd.org/base/head Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 237169 Node Kind: directory Schedule: normal Last Changed Author: alc Last Changed Rev: 237168 Last Changed Date: 2012-06-16 21:56:19 +0300 (sat, 16 jun 2012) end of world.log: -- >>> World build completed on Sat Jun 16 21:50:03 EEST 2012 -- end of kernel.log: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions cc1: warnings being treated as errors /zstorage/testenv/sources/10-kms/sys/modules/ath/../../dev/ath/if_ath.c: In function 'ath_attach': /zstorage/testenv/sources/10-kms/sys/modules/ath/../../dev/ath/if_ath.c:666: warning: format '%d' expects type 'int', but argument 4 has type 'long unsigned int' [-Wformat] *** Error code 1 Any help? -- Regards, Alexander Yerenkow ___ 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"
Stucking processes
Hello all. Since I'm using stable as host, and current in chroot, I'll write to both mail list, sorry for any inconvenience. My host is binary freebsd-updated 9; FreeBSD 9.0-RELEASE-p3 (GENERIC) #0: Tue Jun 12 02:52:29 UTC 2012 I have chroot with latest current there installed r237089 (make buildworld && buildkernel, no specific flags) When I built from ports some programs in chroot all went fine, until I got stucked process automoc (when building kdelibs4); After few restarts I got build, and forget about it. I'm toying now with portupgrade, and see similar stucks in ruby18 and ruby19 (Even got few times in miniruby while building 1.8); Here's example of stucked processes (they aren't in top, and seems totally inactive. I haven't kill them yet, so can try to dig, but to where?): 2677 5 Is0:00,00 | `-- /bin/sh 2678 5 I 0:00,00 | `-- sudo su 2679 5 I 0:00,00 | `-- su 2680 5 I 0:00,01 | `-- _su (csh) 2687 5 I 0:00,03 | `-- /bin/csh -i 2690 5 I+0:04,34 | `-- ruby19: portupgrade: [1/237] audio/libsamplerate (ruby19) # procstat -k 2690 PIDTID COMM TDNAME KSTACK 2690 100477 ruby19 -mi_switch sleepq_catch_signals sleepq_timedwait_sig _sleep do_wait __umtx_op_wait_uint_private_compat32 ia32_syscall Xint0x80_syscall 2690 101110 ruby19 -mi_switch sleepq_catch_signals sleepq_wait_sig _cv_wait_sig seltdwait kern_select freebsd32_select ia32_syscall Xint0x80_syscall #top (with inactive filtered out;) last pid: 11049; load averages: 0.09, 0.16, 0.19 up 0+00:14:48 12:27:20 63 processes: 1 running, 62 sleeping CPU: 1.0% user, 0.0% nice, 0.8% system, 1.2% interrupt, 97.0% idle Mem: 184M Active, 96M Inact, 1104M Wired, 2412K Cache, 171M Buf, 454M Free Swap: 4096M Total, 4096M Free PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 2610 root 2 200 261M 82548K kqread 1 0:12 1.27% rtorrent Is this my side's problem, or there's something wrong with current? :) Any help appreciated. -- Regards, Alexander Yerenkow ___ 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: [CFT] Xorg 7.7 ready for testing!
Okay everyone interested - listen up :) http://gits.kiev.ua/FreeBSD/FreeBSD-10-i386-2012-06-08.img.xz Here is the image, which can be dd'ed to 4g+ flash drive. It should be bootable, and contains new xorg, and some soft from ports; - seamonkey (if you want go to internet) - stellarium (it's full of stars) - blender (but it depends on devel/icu which probably built with error, or by some other reason blender produces coredump) - xterm and openbox; How to use: boot, login as root; after passwordless login you can view simple x run script with: cat ./runx.sh or you just launch it ./runx.sh If you have non-intel card, you need edit xorg.conf, and runx.sh (remove load i915kms). Load process and X launching can be a while if you have not very fast flash. I'll continue improving of infrastructure for building such testing images, helps and advises appreciated. -- Regards, Alexander Yerenkow ___ 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: [CFT] Xorg 7.7 ready for testing!
Is this fresh installation or you were upgrading? I'm preparing now live image with new xorg, and don't saw such errors. But I had yesterday's src/ports tree. -- Regards, Alexander Yerenkow ___ 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: Weird wifi behavior
2012/6/1 Adrian Chadd : > Hi, > > Please file a bug. :) > Here it goes: http://www.freebsd.org/cgi/query-pr.cgi?pr=168530 > WEP shouldn't be broken in 9.x, that was before all of my TX > aggregation changes for 802.11n support. > Don't know if it is... since my other stuff working in same network. > WEP worked fine for me when I was using it a couple weeks ago. Would > you please provide further information in the bug, such as what the > key length is, which key slots are configured, your > ifconfig/wpa_supplicant.conf entry, etc. Yes, I will prepare this info now. > > Thanks, > > > > Adrian > > On 1 June 2012 06:13, Alexander Yerenkow wrote: >> Hello all. >> First of all, I'm not on current, but on stable: >> >> FreeBSD pcbsd-6648 9.0-STABLE FreeBSD 9.0-STABLE #8: Fri May 18 >> 16:12:29 UTC 2012 >> r...@build9x64.pcbsd.org:/usr/obj/builds/i386/pcbsd-build90/fbsd-source/9.0/sys/GENERIC >> i386 >> >> I have lenovo s10-2 (which is have some unsupported broadcom wifi). >> I did replace wifi with >> ath0: mem 0x5610-0x5610 irq 17 at device 0.0 on >> pci2 >> ath0: AR2425 mac 14.2 RF5424 phy 7.0 >> >> >> And weirdness begin. >> At my home I have wifi router in WEP mode. All devices/laptops are >> working just fine. But s10-2 is somehow get broken packets; >> fetch - got broken downloads (incorrect MD5, and sometimes say to me >> that length of file is invalid); >> wget - stops, saying something about MAC error. >> ssh - works fine while I simply use console (cd, ls) - can lasts >> hours.but! If I run mc, and starts something like copy/delete files >> (which heavily updates screen) - ssh drops connections with message >> packet error. >> browsing - pretty working (but not file downloads of course). >> >> At my workplace we using WPA with password. At work I can download >> packages,files,etc - all is OK with fine checksums. >> I happen to note this while testing PC-BSD 9.0, currently I'm on >> latest PC-BSD beta. >> >> Any thoughts/advices on how to test it/fix it? >> I'd gladly use broadcom (bcm94312MCG) if it works. BTW, maybe someone >> could mentor me on developing/porting driver? :) >> >> -- >> Regards, >> Alexander Yerenkow >> ___ >> 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" -- Regards, Alexander Yerenkow ___ 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"
Weird wifi behavior
Hello all. First of all, I'm not on current, but on stable: FreeBSD pcbsd-6648 9.0-STABLE FreeBSD 9.0-STABLE #8: Fri May 18 16:12:29 UTC 2012 r...@build9x64.pcbsd.org:/usr/obj/builds/i386/pcbsd-build90/fbsd-source/9.0/sys/GENERIC i386 I have lenovo s10-2 (which is have some unsupported broadcom wifi). I did replace wifi with ath0: mem 0x5610-0x5610 irq 17 at device 0.0 on pci2 ath0: AR2425 mac 14.2 RF5424 phy 7.0 And weirdness begin. At my home I have wifi router in WEP mode. All devices/laptops are working just fine. But s10-2 is somehow get broken packets; fetch - got broken downloads (incorrect MD5, and sometimes say to me that length of file is invalid); wget - stops, saying something about MAC error. ssh - works fine while I simply use console (cd, ls) - can lasts hours.but! If I run mc, and starts something like copy/delete files (which heavily updates screen) - ssh drops connections with message packet error. browsing - pretty working (but not file downloads of course). At my workplace we using WPA with password. At work I can download packages,files,etc - all is OK with fine checksums. I happen to note this while testing PC-BSD 9.0, currently I'm on latest PC-BSD beta. Any thoughts/advices on how to test it/fix it? I'd gladly use broadcom (bcm94312MCG) if it works. BTW, maybe someone could mentor me on developing/porting driver? :) -- Regards, Alexander Yerenkow ___ 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: ABI/architecture identification for packages
IMHO, 32 / 64 = easily parsable and represent integer. i386/amd64 - wellknown names, but this info about processor bits not lies in math. My point is i386 is arch, so can be kept, while 32 is processor bit count. If you'll keep 32/64 various checks in side software will be simple (if you have 32 bit processor, then this info is bundled in "32"), while if you consider using "i386" string as storage of information about "32" bit, it not so elegant. Also, linuxes has come to i386- i586- i686- mess, and many their scripts looks overbloated when they checks if system really 32 bit. Just my point of view :) ___ 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: No working IDE in FreeBSD!
2012/3/1 Eygene Ryabinkin > Thu, Mar 01, 2012 at 02:31:06PM +0200, Alexander Yerenkow wrote: > > I tried to take some time of Philip Paeps, but he is always busy with > > something. Maybe someone of you guys could be interested in filling > request > > for open source license. > > Are you requesting someone to create FreeBSD port for this IDE > or you meant something else? > I'm sorry to be not clear in hasteness of day! I think port is not required, they have good enough run.sh which gracefully understand what is FreeBSD and could start IDE just fine. What I meant, was that FreeBSD as a project could benefit from applying for their OpenSource Licensing program, so any commiter/developer could try and probably work efficiently in this IDE. Because I'm not committer nor some kind of mentor of project, I can only point someone to there. If you go on their site (google intellij), part of "IntelliJ IDEA" > "Buy & Upgrade" > "Open Source Project License" > Apply Now, you could learn more on conditions for applying. So, to summarize this all again: If there are some commiter/responsible person who can apply - then FreeBSD devs could gain one more IDE to develop some parts of FreeBSD. > -- > Eygene Ryabinkin,,,^..^,,, > [ Life's unfair - but root password helps! | codelabs.ru ] > [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] > -- Regards, Alexander Yerenkow ___ 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: No working IDE in FreeBSD!
I think this is just right post to intrude :) I'm developing software, and making it in pretty good IDE - Intellij Idea. There's community and pro version. What good in this company - it gives access to Pro version for not-small open source projects. I tried to take some time of Philip Paeps, but he is always busy with something. Maybe someone of you guys could be interested in filling request for open source license. IDE is very strong and smart, support java/c++/php and a lot of languages via plugins. Thanks. -- Regards, Alexander Yerenkow ___ 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: FEATURE: Implement 'make config' in /usr/src
15 января 2012 г. 21:24 пользователь Коньков Евгений написал: > It will be nice to create nice menu that will allow user > disable/enable modules to build kernel > > cd /usr/src > make config > FYI, I've tried to create POC of such thing, based on port.mk files; Kernel options almost similar to port's options, so I just converted LINT to file with options, and "make config" show me them. No saving, and no options comments were there :) ANyway, it's not big task should , to make it works, based on ports-options work. It would be nice, if options could declare hteir dependencies too. > > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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: Kernel does not build on 10.0-CURRENT (amd64)
2012/1/6 Adrian Chadd > On 6 January 2012 10:19, Rainer Hurling wrote: > > > I commented all wireless network drivers and their options out. But the > > error remains. Is it necessary to have this option uncommented even when > the > > driver ath is commented out? > > Yes, because of how the wlan/ath modules are built. You need to have > AH_SUPPORT_AR5416 in the kernel config file, as the driver/module > currently doesn't build without it. > I'm sorry for intruding in this topic, but it seems to me similar subject; Did FreeBSD ever tried to make config variables structured and with specified dependencies? To make clear what I mean - is anyone tried to implement some deps spec file (Or some special Makefile's sections, whatever), so if you specified feature A in kernel, it can check if you also specified B (which is required by A)? In this way config could provide feedback when you trying to build kernel without needed dependencies, and many peoples could save their time not compiling non-buildable kernel. > I'll eventually fix that, but right now I just want to leave that > option in and not hack up the Makefile to define said option. > Otherwise other options (eg enabling 11n, enabling hal debugging, etc) > are completely ignored when building modules. > > Same with IEEE80211_SUPPORT_MESH i believe. I should really re-verify that. > > > Adrian > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server
My thoughts about benchmarking - don't forget, it's the way to get at least estimate on how your system will behave in given circumstances. When testers measured new videocard, they tested few factors, like FPS in modern games, pixel/texture fillrate, and whatever they do there else. That's because videocard have few simple and plain applications. And different vendor/generation cards are compared without problems. Different version of compiler, OS, etc - is very irrelevant. It's like say we can't compare these shovels, because they made from different sort of wood. OS is created to serve (produce some useful actions), and not to be measured and turned off forever:) So, in ideal world, there will be benchmarks on some real-world situations (like FPS for videocards, there got to be something also if not common, but at least wide-spread amongst users). Like - benchmarking fully tuned FreeBSD vs fully tuned Linux in high net-load (for example http + php + mysql). It's hard to disagree that this is very common spread use case for server OS. Also good tests would be productivity of FTP/File/Samba/Nfs/rsync servers. For desktop aspects, there's not much space for tuning (for linuxes), mostly linuxes tested out-of-box, or tuned via some gui-settings applet;, while FreeBSD-OOB needs some additional care (like get latest ports, install latest video drivers, xorg, etc., sysctl tuning probably). I'm glad there's PC-BSD, and PC-BSD can be used for desktop testing. And what to test in desktop? IMHO - WM responsiveness; - Program multi-tasking, and how productivity decreases when many background program working; (It's like, which user experience we'll get when our system is pretty heavy loaded) - Probably would be fair to compare same software in same circumstances (like same version of FF, Chromium, maybe something else). There's such extension for FF imacros - which can be used to simulate user actions, any actions in many tabs; - Overall usage experience, like measure time between program launching and window appearing (file managers, browsers, settings applet, calculator, etc.) - Sleep/Wake times with empty system(and with many programs launched ); If at all supported sleep/wake (as for me - my laptop can be slept, but deny to wake properly) - Time between you press "KDE start menu icon" and menu appeared; - Your variant?... This would be more careful benchmarking, not only number-crunching and heavy-archiving is used by all peoples. And this benchmarking can be at least be applied for users; They can imagine how it is - to have dolphin (KDE file manager) launched in 1.03 seconds, and alt-tabbing gives new window in 0.2 seconds, when video is playing. But what about time of calculating of Super-PI? Or archiving 4Gb file? It's mostly abstract measurement, and almost useless; I repeat - for average desktop users. I've at work PC-BSD installed on 24Gb SSD, with default ZFS setup slightly tuned (disabled prefetch), and I can say that system is great, and not sluggish. I sometimes happen to fill FS to 100%, then delete logs and continue working, without any signs of ZFS problems (I read somewhere that ZFS don't like to work when not much of free space available). KDE is old, but pretty fast. How can I measure this all with some few numbers :) ? My point is, that if not now, then in some near future benchmarking need to be more practical and applicable for users. Desktop measurements and server measurements. I hope Phoronix test suite will support desktop-experience benchmarking soon :) Thanks. -- Regards, Alexander Yerenkow ___ 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: VM images for FreeBSD
2011/12/21 Baptiste Daroussin > On Mon, Dec 19, 2011 at 10:31:51PM +0200, Alexander Yerenkow wrote: > > 2011/12/19 Adrian Chadd > > > > > Hi, > > > > > > Hm, so this lets us create a virtualbox image from what, a set of > > > install tarballs? Or /usr/src build? > > > > > > I'm using cross-build and installation from sources dir (which is after > > that got svn-up'ed and all goes again). > > It shouldn't be complex to install to image from installation media > and/or > > tarballs, but mine main idea is to have rolling image for making some > > automated tests. > > Currently I'm establishing building and providing images scheme, will do > > images with KMS+small graphical programs, with qt+unstable KDE, and > > probably with BHyVe. I think that's most useful setups currently. And > maybe > > some image for benchmarking :) > > > > > > FYI I have been working on a ova file generator for the release, I manage > to > create ova images that do work on VirtualBox without problems, there are > still > some problems with vmware for now, the goal is to have a standard vm ready > image > (ova is standard) that would work on every system that do support it. > This is good :) Do you have some scripts left? > the image can be easily created from the release. > Well, I'm trying to build custom images, like rolling from svn [+ patches] [+ packages] [+ some initial config]. A way for building images from release I think can be taken from PC-BSD, they distribute upcoming 9 in VM formats too. > > regards, > Bapt > -- Regards, Alexander Yerenkow ___ 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: regression: Xorg get 100% cpu and freeze
20 декабря 2011 г. 15:37 пользователь Alex Keda написал: > I use CURRENT from 2011-11-18 - all OK > After update to today - I have problem - on start, Xorg get 100% CPU and > freeze (monitor go to turn off) > I recompile Xorg, all modules - no happy. > I try update x11-drivers/xf86-video-ati to 6.14.3 - no happy > > If I delete /boot/kernel/drm.ko - all work OK, but very slow... > BTW, mine test images built from sources with KMS do the same thing - start xorg, and it just totally hangs pc. I think it's about a month I have such situation. > > = > FreeBSD lissyara.moskb.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r228726: > Tue Dec 20 08:24:56 MSK 2011 > root@lissyara.moskb.local:/usr/obj/usr/src/sys/GENERIC > amd64 > = > pciconf, Xorg.log with and without drm.ko - in attached files > > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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: VM images for FreeBSD
2011/12/19 Adrian Chadd > Hi, > > Hm, so this lets us create a virtualbox image from what, a set of > install tarballs? Or /usr/src build? > > I'm using cross-build and installation from sources dir (which is after that got svn-up'ed and all goes again). It shouldn't be complex to install to image from installation media and/or tarballs, but mine main idea is to have rolling image for making some automated tests. Currently I'm establishing building and providing images scheme, will do images with KMS+small graphical programs, with qt+unstable KDE, and probably with BHyVe. I think that's most useful setups currently. And maybe some image for benchmarking :) > > Adrian > -- Regards, Alexander Yerenkow ___ 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: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server
IMHO, no offence, as always. As were told, Phoronix used "default" setup, not tuned. So? Is average user will tune it after setup? No, he'll get same defaults, and would expect same performance as in tests, and he probably get it. The problem of FreeBSD is not it's default settings, some kind of very-safe defaults really should be there. But problem really is lacking of choosing them (defaults) during install, for average users. For example, few checkboxes with common sysctl tuning would be perfect, even if they would be marked as "Experimental", or not recommended. I'm thinking it's better way to make something in one place (like in installer) rather than require make almost same actions in many (hundreds of thousands?... more?...) places (end-users forced to read mail-lists/handbooks/forums over and over for same solutions). Simple example - many connections for PostgreSQL is not available on FreeBSD out-of-box. Just google "postgresql freebsd max connection" and you'll see how many there bikesheds requested and same solutions posted again and again :) FreeBSD currently have very obscure, closed community. To get in touch, you need to subscribe to several mail lists, constantly read them, I've just found recently (my shame of course) in mail list that there is service ( pub.allbsd.org) which constantly building current versions. This is great, but at homepage of freebsd.org there is no word about it :) I hope we all do something good about this, and things will going to change. -- Regards, Alexander Yerenkow ___ 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: VM images for FreeBSD
If anyone interested, I got here [1] VirtualBox Image: FreeBSD-10-amd64-r228694-2011-12-19.vdi.xz Anyone who's looking to test 10 can get to test it :) It contains package-installed partial system with openbox; Image configured to run DHCP on em0, you can change this in /etc/rc.conf, as usually. When you'll get internet working, you can add packages (9 ones), running /root/addpackage.sh $1 To get X, login as root, start /root/runx.sh In a few seconds (there's delays for safety) you should get X with openbox. BTW, it contains also qt 4.8.0 and qtcreator 2.4.0, you can test something and help a bit for KDE/QT team with any feedbacks. It's installed with default settings in their default prefixes (qt in /usr/local/Trolltech, and qtcreator in / ), so, to run something you probably must set correct LD_PATH. As for qtcreator, I created script for launch it, placed in root, which is also launched when you start X. 1. http://gits.kiev.ua/FreeBSD/ P.S. As always, I'm looking for anyone who will lend me a hand in enhancing build scripts. -- Regards, Alexander Yerenkow ___ 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: grabbing console (syscons) in kernel
2011/12/11 Andriy Gapon > > There are a few cases when the kernel needs to interact with a user via > syscons. > This is the cases where the kernel not only spews some output but also > expects > some input. Some examples are: > - asking for a root filesystem specification > - entering ddb > - asking to press a key for reboot > > In this cases the kernel implicitly grabs the console for its own use. > I'd like to make action more explicit. > > What do you think about the approach and implementation in the following > patches? > Thank you! > > > https://gitorious.org/~avg/freebsd/avgbsd/commit/5248b49ebf84d98a0597fa5aa4d813a38f581acc > > https://gitorious.org/~avg/freebsd/avgbsd/commit/a0849c52242378474bb2eaa41726376fbc4c5bf6 > > https://gitorious.org/~avg/freebsd/avgbsd/commit/a67515cbd720b16f03ba435ed182966a8a338b15 > > https://gitorious.org/~avg/freebsd/avgbsd/commit/b8864b68b4c0e26ece065a38301c305833be32eb > > https://gitorious.org/~avg/freebsd/avgbsd/commit/1017ae425d8abecd7482bd6c6deaaf9f25f5c6cd > > P.S. one of the benefits is that a keyboard is put into and out of the > polling > mode before getting all the required input and after that; not around each > character as it is done now in rather twisted way. > Does asking for geli password is such case too? For example, I have mouse, which can disappear/reappear while laying still; and when geli asks password, ums0 connect message can appear, which moves line "Please enter geli password..." to top, and it can be missed; This behavior somehow change? > > -- > 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" > -- Regards, Alexander Yerenkow ___ 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"
Problem building current
Hello. I think I have some problem building current on my system (which is not current). # uname -a FreeBSD 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 18 18:51:43 UTC 2011 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # pwd /zpool0/testenv/sources/10-kms/lib/libc # svn info Path: . Working Copy Root Path: /zpool0/testenv/sources/10-kms URL: http://svn.freebsd.org/base/head/lib/libc Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 228276 Node Kind: directory Schedule: normal Last Changed Author: jilles Last Changed Rev: 228269 Last Changed Date: 2011-12-05 02:00:47 +0200 (пн, 05 дек 2011) # make -DNO_CCACHE cc -O2 -pipe -I/zpool0/testenv/sources/10-kms/lib/libc/include -I/zpool0/testenv/sources/10-kms/lib/libc/../../include -I/zpool0/testenv/sources/10-kms/lib/libc/amd64 -DNLS -D__DBINTERFACE_PRIVATE -I/zpool0/testenv/sources/10-kms/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/zpool0/testenv/sources/10-kms/lib/libc -I/zpool0/testenv/sources/10-kms/lib/libc/resolv -D_ACL_PRIVATE -DPOSIX_MISTAKE -I/zpool0/testenv/sources/10-kms/lib/libc/../../contrib/tzcode/stdtime -I/zpool0/testenv/sources/10-kms/lib/libc/stdtime -I/zpool0/testenv/sources/10-kms/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/zpool0/testenv/sources/10-kms/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c /zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c: In function 'sctp_opt_info': /zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:416: error: 'SCTP_REMOTE_UDP_ENCAPS_PORT' undeclared (first use in this function) /zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:416: error: (Each undeclared identifier is reported only once /zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:416: error: for each function it appears in.) /zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:417: error: dereferencing pointer to incomplete type *** Error code 1 I'm getting this error when I'm trying to buildworld from svn checkouted sources (e.g. I'm using plain "make buildworld", without NO_CLEAN or some else). Any ideas why it is happening? -- Regards, Alexander Yerenkow ___ 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: CVS removal from the base
I understand that this is not my business at all :) But anyway, IMHO, you should take GPL-free effort as an example. When you visit http://wiki.freebsd.org/GPLinBase you easily can see what going to be dumped, why, and with what it's going to be replaced. What I mean exactly - throw emails to mail list like this, telling that we need to specify software list for removal, provide page in wiki, with each software listed, propose something in exchange, collect not opinions, but real usage examples, and some stats, like "feature A is used by approx 100 peoples". Or "Feature B is used by 3 peoples, but there's no replace ATM". If you think it's time to move from CVS, create page in wiki, find most frequent use cases, think about replacing them with other tools, collaborate with peoples, create simple pro/con table with free editing. I'm sure that very few peoples, or even no one know _every_ usage of FreeBSD base, so deep investigating on each item is would be necessary. That's only my 2c. -- Regards, Alexander Yerenkow ___ 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: 9RC2 amd64 "Can't work out which disk we are booting from"
Actually when I was trying to build amd64 image from sources from about PRE-RC1 I have exactly same error. But I have not found what it was, and switched to build i386 images only yet. 2011/11/19 Jakub Lach > Hello. > > I'm almost positive it's probably my fault, > but anyway, I have installed FreeBSD on > laptop from source (9-STABLE), on the same > machine I can't boot RC2 usb.img due to "Can't > work out which disk we are booting.." and after > installing RC2 on usbstick and trying to boot > it, same problem occurs. > (well, surprise). > > I have used default layout on usbdrive. > > Any ideas? > > ls show files structure, but boot /boot/kernel > doesn't work. > > On the side note, Verbatim STORE N GO 2.66 > 8GB gave me nothing but problems, not > recommended. (it's actually "Blaze Drive" > but it's recognised as store 'n go) > > best regards, > - Jakub Lach > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/9RC2-amd64-Can-t-work-out-which-disk-we-are-booting-from-tp5006547p5006547.html > Sent from the freebsd-current mailing list archive at Nabble.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" > -- Regards, Alexander Yerenkow ___ 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: KMS testing, intel only
>Thanks. Do you think you'll provide amd64 version of that img as well? I'm working currently on fully automatizing this process, and it mostly done. But, I got now FreeBSD-9-kms-i386-r227450-2011-11-12.img and... it seems not seeing none of my two intel cards. :( Well, or I did broke something, or some commit did broke everything, can't say yet. I'm going build now amd64 version as well, will see if it will work. -- Regards, Alexander Yerenkow ___ 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
> If FreeBSD starts using numbers for HEAD/CURRENT, i think a lot of users > would find them selves in a situation > that they download version 10 in this case and that they are using a > develepment version instead of a real release version. > Assuming there will be link from main page - probably yes. But if from official site they can get only RELEASE, and in some deep dark page link to current - they will not run into this. > > So FreeBSD will get more frustrated users, who need to download the latest > release again and so on. > Keeping the name more seperated from the normal numbering prevents this > more or less. > Hm, what's the problem to name development ISO's differently? Like, 10-CURRENT-UNSTABLE-*.iso VS 9-RELEASE.ISO So even very novice user will think twice before downloading. Is there any reason why ISOs can't be named differently from svn tag/branch? I don't see this. IMHO, this must have been done a lot of time ago. But, I may not know some constraints/restrictions/rules of development process, maybe HEAD is really necessary. I think this is more question to release engineering team than to current. > > Gr > Johan Hendriks > > > > > ___ > 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" > -- Regards, Alexander Yerenkow ___ 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"
KMS testing, intel only
neramaproto-1.2.1 xkbcomp-1.2.3 xkeyboard-config-2.4.1 xorg-fonts-truetype-7.5.1 xorg-macros-1.15.0 xorg-server-1.10.4_1,1 xproto-7.0.22 xterm-276 xtrans-1.2.6 xvid-1.3.2,1 zip-3.0 -- Regards, Alexander Yerenkow ___ 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: Problem compiling kernel
2011/11/7 Garrett Cooper > On Nov 6, 2011, at 11:57 PM, Peter Jeremy wrote: > > > On 2011-Nov-06 17:41:49 +0200, Alexander Yerenkow > wrote: > >> And problem compiling kernel for amd64 arch. > >> > >> I attached full log: > >> > >> http://www.box.net/shared/juajg1o2lg1mxbht5x9b > > > > It looks like you did a parallel - in which case the actual error is > > buried somewhere in that output. Please repeat without any '-j' > > and post the last 50-100 lines of output. > > ip_fw_nat.o: In function > `del_redir_spool_cfg':/zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:123: > undefined reference to `LibAliasRedirectDelete' > ip_fw_nat.o: In function `ipfw_nat_destroy': > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:615: undefined > reference to `LibAliasUninit' > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:615: undefined > reference to `LibAliasUninit' > ip_fw_nat.o: In function `ifaddr_change': > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:80: undefined > reference to `LibAliasSetAddress' > ip_fw_nat.o: In function `ipfw_nat_del': > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:482: undefined > reference to `LibAliasUninit'ip_fw_nat.o: In function > `ipfw_nat_cfg':/zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:437: > undefined reference to > `LibAliasSetMode'/zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:438: > undefined reference to `LibAliasSetAddress' > ip_fw_nat.o: In function > `add_redir_spool_cfg':/zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:193: > undefined reference to > `LibAliasAddServer'/zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:158: > undefined reference to > `LibAliasRedirectAddr'/zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:167: > undefined reference to `LibAliasRedirectPort' > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:178: undefined > reference to `LibAliasRedirectProto'ip_fw_nat.o: In function > `ipfw_nat_cfg':/zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:416: > undefined reference to `LibAliasInit'ip_fw_nat.o: In function `ipfw_nat': > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:216: undefined > reference to `m_megapullup' > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:295: undefined > reference to `LibAliasOut' > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:276: undefined > reference to `LibAliasOutTry' > /zpool0/testenv/sources/9/sys/netinet/ipfw/ip_fw_nat.c:292: undefined > reference to `LibAliasIn' > > You need to compile with libalias support. > Thanks, that does fix the problem. Is there somewhere request for feature that config must check kernel config for dependencies specified? Or maybe even auto-dependency :) What I mean, someone working at kernel configuration/sanity check util at all? Or mabye it's not requested feature? -Garrett -- Regards, Alexander Yerenkow ___ 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"
Problem compiling kernel
Hello all! I have sources: Path: . URL: http://svn.freebsd.org/base/stable/9 Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 227206 Node Kind: directory Schedule: normal Last Changed Author: dougb Last Changed Rev: 227146 Last Changed Date: 2011-11-06 09:50:25 +0200 (вс, 06 ноя 2011) And problem compiling kernel for amd64 arch. I attached full log: http://www.box.net/shared/juajg1o2lg1mxbht5x9b I find somewhere that to build kernel I need to have world build; So, world built just fine before I tried to build kernel. Also, just in case I've updated (binary way) host to: FreeBSD testpc 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 18 18:51:43 UTC 2011 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 The problem persist, can't compile kernel. My config is: include GENERIC ident MYK machine amd64 # Bus support. device isa # Pseudo devices. device mem # Memory and kernel memory devices device io # I/O device # UART chips on this platform device uart_ns8250 # Default partitioning schemes options GEOM_PART_BSD options GEOM_PART_EBR options GEOM_PART_EBR_COMPAT options GEOM_PART_MBR options NEW_PCIB device pf device pflog device pfsync options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD options IPFIREWALL_NAT options IPDIVERT While I'm waiting for any help, I'll try to compile GENERIC. Thanks! -- Regards, Alexander Yerenkow ___ 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: VM images for FreeBSD
2011/11/4 Daniel O'Connor > > On 19/10/2011, at 21:19, Alexander Yerenkow wrote: > > I can't specify to pkg_add that it should treat /zpool0/testroot as > root, as > > I need (so record really should be @cwd /usr/local) > > Instead, pkg_add allows me to make chroot, which as you understand is not > > good (In specified chroot all required by pkg* binaries/libraries must > > exists, unfortunately I can't specify some empty dir and install there). > > Hmmm, why is it empty? > When I have made something analogous I did an installkernel/world into a > directory and then chroot'd in there and built ports. There is no reason > you couldn't pkg_add from a local mirror (or nullfs mount a local package > mirror directory into the chroot). > >From beginning I thought about having a lot of directories, which contains one installed package; I assume using plain copy all requried data, to have requried packages installed in new chroot env. Not via install, but simply by copy. Reason was - to make composing of images with pre-installed software faster (avoiding pkg_add/unpack/mtree/etc. steps). I could easily use unionfs, if only it could work under zfs :) In any way, all package installation process, all running scripts ends and leaving a bunch of new files (links too), and some changed files (like added groups/users etc), that's all. I just wanted have unpacked and initialized packages in directories, which I could use as puzzle parts, to build image with pre-installed packages. Of course, I understand that there required some tricks to make it all works (like adding users/groups/ X config etc.), but many straightforward software will just work, which is in mostly cases enough to test another release. Currently I'm using pretty slow way to make pre-installed images, new fresh copy of base world for each package-set, after that created install script, and runned in chroot. for i in `cat test-package-list` ; do echo "env PACKAGESITE=$packagesite pkg_add -rifF $i" >> $blank/root/install.sh done parameters used: -r, --remote Use the remote fetching feature. -i, --no-deps Install the package without fetching and installing dependencies. -I, --no-script If any installation scripts (pre-install or post-install) exist for a given package, do not execute them. -f, --force Force installation to proceed even if prerequisite packages are not installed or the requirements script fails. -F Already installed packages are not an error So, package not getting dependencies (they all must be specified too), but all went installed and even working somehow. But all this is pretty rough :) About long way to standardize installation process - I think even if it's so complex, it should just start somewhere. Best candidate - all pear install scripts; they can easily be moved to *.mk. A bit more complex is standardizing user/groups. > > > Why is that? Because there is +INSTALL script in packages, in which > > package/port system allows execute any code/script written by porter. > > This is a feature ;) > > > To summarize my efforts: > > I checked 21195 packages; > > I found 880 install scripts; > > > > 3 scripts contains plain "exit 0" > > 8 install scripts contains some perl code; > > 17 scripts contains some additional "install" commands; > > 70 scripts contains some chgroup/chown actions (which probably could be > done > > by specifying mtree file?...) > > 75 contains uncategorized actions (print of license, some interactive > > questions, ghostscript actions, tex, fonts etc.) > > 161 scripts contains some file commands, like (ld / cp / mv, creating > > backups, creating configs if they aren't exists etc. ) > > 166 scripts contains useradd/groupadd commands (many similar > constructions, > > not too hard to move this to .mk, in pkgng group/users can be specified > in > > yaml config) > > 380 contains pear component registration (md5 -q * | uniq - produces > > exactly one result, so these all scripts are really one, could be moved > to > > some pear.mk) > > Interesting stats, thanks for taking the time to do the analysis. > > I think one of the reasons pkg_add is so slow is that it copies everything > to a staging directory, then copies the files.. This is very tedious > (obviously). I wonder if it could be modified to have a "stream" mode where > it unpacks directly into the target FS. > > Alternatively you could cut it in 2 conceptually and modify pkg_add so it > can run it a mode where it just unpacks to a staging area, and another mode > where it copies from the staging area to the destination. > > -- > Daniel O'Connor software and network engineer > for Genesis So
Re: VM images for FreeBSD
2011/10/17 Warren Block > On Mon, 17 Oct 2011, Alexander Yerenkow wrote: > > Hello all. >> I'm currently made set of scripts, which builds FreeBSD from svn sources, >> and packing it in VirtualBox (*.vdi) compatible images. >> It's working now, and producing something like >> >> FreeBSD-9-i386-r226409-2011-10-16.vdi.xz (also .vdi, .vdi.zip and plain >> .img >> which can be dd to USB flash). >> >> I'm developing this here: >> https://github.com/yerenkow/freebsd-vm-image >> >> I have more goals to do (like producing more images, with a installed sets >> of packages, like KDE-from-ports, KDE-from-area51, with experimental GEM >> drivers etc.) >> > > Excellent! If live CD/memdisk features are added, this could also be > useful for testing large xorg port updates before commit. > > PS: why bash for cron-auto-action.sh? > Hello all! I'm working currently on creating images with a set pre-installed packages. I looked at project pkgng (candidate for replacing current pkg_* subsystem), and also I have some thought about current packages/ports system. 1. pkg_add can be launched with parameter -p $PREFIX. So, my first thought was: I create empty directory structure with mtree, and I'll install there all required packages; after that I need only update this installation tree (manually by pkg_delete $old pkg_add $new, or with some tool). But I cannot specify to pkg_add relative root, instead of real one. Let me show example: PKG_DBDIR=/zpool0/testroot/var/db/pkg pkg_add -p /zpool0/testroot/usr/local ubench-0.32.tbz installs package, and in /zpool0/testroot/var/db/pkg/ubench-0.32/+CONTENTS there will be such record: @cwd /zpool0/testroot/usr/local I can't specify to pkg_add that it should treat /zpool0/testroot as root, as I need (so record really should be @cwd /usr/local) Instead, pkg_add allows me to make chroot, which as you understand is not good (In specified chroot all required by pkg* binaries/libraries must exists, unfortunately I can't specify some empty dir and install there). Why is that? Because there is +INSTALL script in packages, in which package/port system allows execute any code/script written by porter. 2. In ports enhancements task list (somewhere i read it) there was one item: Make packages non-executable (or something similar). To do this properly, we must get rid of of free-form post-install post-deinstall scripts. To do this, we need some deep analysis of what types of actions there happening, formalize them and provide some way to porters specify all needed actions in Makefile. I downloaded all packages for 9-current i386, found all +INSTALL scripts, and kinda categorized them, you can get all of them here: http://www.box.net/shared/ieovjj7l8omkrm3l21xb To summarize my efforts: I checked 21195 packages; I found 880 install scripts; 3 scripts contains plain "exit 0" 8 install scripts contains some perl code; 17 scripts contains some additional "install" commands; 70 scripts contains some chgroup/chown actions (which probably could be done by specifying mtree file?...) 75 contains uncategorized actions (print of license, some interactive questions, ghostscript actions, tex, fonts etc.) 161 scripts contains some file commands, like (ld / cp / mv, creating backups, creating configs if they aren't exists etc. ) 166 scripts contains useradd/groupadd commands (many similar constructions, not too hard to move this to .mk, in pkgng group/users can be specified in yaml config) 380 contains pear component registration (md5 -q * | uniq - produces exactly one result, so these all scripts are really one, could be moved to some pear.mk) Why I'm interested in non-executable install of package (e.g. simple unpack + execute some typical actions based on package description): - Unpacking of hundreds Mb packages takes several minutes (to mdconfig-ed filesystem) - Installation of these packages via pkg_add (they downloads from local ftp) took hours in my case (to mdconfig-ed filesystem) As you understand, to make efficient image building system, I need to deal with package installation without spending too many cpu/disk resources. Ideally I consider all required packages are extracted to some their own directory, like for ubench: $X/packages/ubench/ (and here goes all directory structure which should be copied to new root) plus separated info of new users/groups (maybe there need some additional data to make package installed in such way fully working). So, maybe someone working in this direction, or have any comments? 3. Other "ports" ideas/thoughts. I proposed small enahcement to pkgng, but instead in pkgng this should be implemented in ports subsystem, it's about specifying abstract dependencies, and correct resolving of them: https://github.com/pkgng/pkgng/issues/100 Who can comment/elaborate a
VM images for FreeBSD
Hello all. I'm currently made set of scripts, which builds FreeBSD from svn sources, and packing it in VirtualBox (*.vdi) compatible images. It's working now, and producing something like FreeBSD-9-i386-r226409-2011-10-16.vdi.xz (also .vdi, .vdi.zip and plain .img which can be dd to USB flash). I'm developing this here: https://github.com/yerenkow/freebsd-vm-image I have more goals to do (like producing more images, with a installed sets of packages, like KDE-from-ports, KDE-from-area51, with experimental GEM drivers etc.) Why I'm writing this letter: 1. Get some help from peoples who interesting in this; 2. Introduce myself in -current (I wasn't active here before) 3. Discuss current bug behavior (or bug in my scripts/mind) of boot loader PR/161677 4. Also, I'd like to see producing these images semi- or fully- official :) (Lacking of virtual images to test even of major releases is not good for project like FreeBSD.) -- Regards, Alexander Yerenkow ___ 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"
