adding VAMI port (5480) to /etc/services
Eitan, colleagues, any objection to adding this (now almost standard, while not registered), port 5480 to /etc/services? simple patch (I'm not sure about SCTP): marck@castor:/FreeBSD/pristine/src.current/etc svn diff Index: services === --- services(revision 275952) +++ services(working copy) @@ -2345,6 +2345,8 @@ mdns 5353/udp #Multicast DNS postgresql 5432/tcp #PostgreSQL Database postgresql 5432/udp #PostgreSQL Database +vami 5480/tcp #VMware Appliance Management Interface, HTTPS-like +vami 5480/udp #VMware Appliance Management Interface, HTTPS-like rplay /udp amqp 5672/sctp #AMQP amqp 5672/tcp #AMQP -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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
Get started with FreeBSD: A brief intro for Linux users by Paul Venezia
There is the following page : http://www.infoworld.com/article/2858288/unix/intro-to-freebsd-for-linux-users.html Get started with FreeBSD: A brief intro for Linux users by Paul Venezia Thank you very much . Mehmet Erol Sanliturk ___ 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: Build failed in Jenkins: Build-UFS-image #599
On Dec 5, 2014, at 19:59, Garrett Cooper yaneurab...@gmail.com wrote: On Dec 5, 2014, at 16:52, jenkins-ad...@freebsd.org wrote: See https://jenkins.freebsd.org/job/Build-UFS-image/599/ I’m not entirely sure why the could not determine COMPILER_TYPE error popped up, but I have a couple of questions/concerns related to the makefile snippet. I looked at the error and the jenkins jobs a bit more and I think the real problem is that the FreeBSD_Head job is being run in parallel with the Build-UFS-image job, because the FreeBSD_Head job completes without issue and the Build-UFS-image job is not being run with -j anything. I know based on past experience if the tree is updated but not rebuilt with -DNO_CLEAN and installkernel/installworld is being run, sporadic build failures like this will occur, depending on whether or not something needs to be [re]built. One way to deal with this issue is to svn up a source tree, then rsync the checked out copy of the source tree to a unique memory disk, build from there, and install to a unique location as well. Using the jenkins job identifier should be enough… but I’m not sure what the best way with Jenkins is to do this, partly because I don’t know what plugins are installed on the Jenkins server. Thanks! signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Build failed in Jenkins: Build-UFS-image #599
On Sat, Dec 20, 2014 at 01:43:50PM -0800, Garrett Cooper wrote: One way to deal with this issue is to svn up a source tree, then rsync rsync? ITYM zfs clone :-) mcl ___ 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: Build failed in Jenkins: Build-UFS-image #599
On Dec 20, 2014, at 14:27, Mark Linimon lini...@lonesome.com wrote: On Sat, Dec 20, 2014 at 01:43:50PM -0800, Garrett Cooper wrote: One way to deal with this issue is to svn up a source tree, then rsync rsync? ITYM zfs clone :-) That’d work too. Sadly, zfs was a bit undesirable on older versions of FreeBSD, so rsync was the chosen solution... signature.asc Description: Message signed with OpenPGP using GPGMail
