change a file in perforce to be executable on checkout.
p4 edit -t <type>+x <file name> p4 submit <file name>
change a file in perforce to be executable on checkout.
p4 edit -t <type>+x <file name> p4 submit <file name>
In years gone by, and I am thinking of FreeBSD 7.0 specifically, portmgr@
gave some latitude to *ALL* committers to “just fix things” to get a port
into shape. In the case of 7.0, it was making ports build for gcc4.
What we have laying ahead of us is a ports tree in various states of modern
preparedness (new style USES=, stagefication, etc) and the old way of doing
We would like committers, and contributors to generate a PR and/or “just
fix” the old ports to update them to the new way of doing things regardless
of maintainership. We are looking for fixes in the following areas
- Convert to LIB_DEPENDS
- stagify ports
- convert things like USE_GMAKE -> USES=gmake USE_DOS2unix -> USES=dos2unix
This can be done with implicit portmgr@ blanket approval, and without
Please, however, respect some boundaries, do not change ports belonging to
kde@, gnome@ or x11@. These teams work in private repos that may have
Also, cross reference GNATS, to see if a port has an open PR that you can
factor into the fix. It is important to stress here that we *DO NOT* want
to invalidate existing patches that a maintainer has offered up or already
If the change is very trivial AND has been tested, “just fix it”. One of
the strengths of the Ports Collection is it’s volunteer maintainers, if you
make a change, regardless of how trivial, just send a courtesy email to the
2013 is gone, and a new PC-BSD image is here. Â We are now in 10.0 Release Candidate 3 (p2) and are moving very quickly towards final release. Â There is still some fine tuning that we are working on, so keep those bug reports coming. Â There are some awesome new key features / support features that have been added so letâ€™s have a look at whatâ€™s new in PC-BSD land.
The guys and gals at the PC-BSD project continue to push the envelope on cutting edge features. Â This week a new detection routine was finished that will offer simple detection on ATI Hybrid Graphics enabled laptop computers. Â The new detection system was tested on a Samsung NP350 that would stall during installation because X was not able to detect either graphics card properly during the installation and first start-up respectively. Â Now if the first video card fails X detection, a message will be displayed that it could not be started. Â It will then try the next one. Â More research and development is needed to see if we can apply this same fix to laptops using Nvidia as well.
For any of our testers out there that want to stay as cutting edge as possible and also assist in the current development in PC-BSD 10 Release, please go ahead and upgrade to the newest image by clicking here. Â We are in a time crunch now, but we want to make sure we find any major / critical bugs and get them squashed ASAP. Â Also I am still looking for testers to help us isolate any issues with the HPLIP package when installed while other printers (i.e brother, epson, etc) are installed as well. Â The goal is too possibly add more printer support to PC-BSD, however please understand this is something for down the road and will not be a quick fix. Â If you need more specific information about our goals with this side project please send me an e-mail at [email protected]
New logic has been added to handling disk detection during PC-BSD installation. Â There was an issue in the gui install as well as text install where the 4k sector size option was causing an installation failure. Â If you were experiencing this issue and would like to test out PC-BSD 10.0 please go ahead and download the latest image and give it a go.
Special shout out to our Indonesian translation team for translating PC-BSD entirely into Indonesian Bahasa. Â Thanks for the hard work, andâ€¦record time for a translation to be completed. Â When I said â€œrun with itâ€� I didnâ€™t actually know you were going to be able to finish it in 5 days. Â We went from having around 20% translated a few days ago to completely localized now, and we couldnâ€™t be happier at the potential for reaching an entirely new market for us.
Due to the state of upstream support for Linux jails in FreeBSD we are re-classifying Linux jails as unsupported / experimental. Â The decision comes after frequent breaks in the way jails are handling the linux scripts and also the inability to handle advanced linux programs. Â We are hoping this is something that we can again start supporting in 10.1, but currently it is just too darned clunky to be called a supported feature. Â One thing Kris also mentioned to me in passing was that Linux jails were never meant to be pushed as far as they are sometimes pushed. Â We will continue to monitor the state of progress on this upstream and keep you informed on any information that comes our way.
Thatâ€™s it for this week. Â You crazy kids stay out of trouble.
Just a short update today to let you all know what the low down is!
PC-BSD version 10.0 Release Candidate 2 is now live! Â Please note this is a beta-test release and NOT an official release. Â For more information on RC2 please visit the following blog page:Â http://blog.pcbsd.org/2013/12/pc-bsd-10â€“0-rc2-available/Â . Â PC-BSD 10.0 Release RC2 can be downloaded fromÂ http://iso.cdn.pcbsd.org/.
Quick Note: Â Please report any bugs found @ trac.pcbsd.org. Â The window is closing to get bug reports in before official release and we need to try to get any â€œmajorâ€� or higher priority bugs knocked out before then.
Kris has reported today that he is in the final stages of getting virtualbox working on PC-BSD 10.0. Â He has fixed many of the seg fault issues that we were seeing from previous versions and will be looking to have these packages ready in the next week or so hopefully by RC3.
AMD KMS support appears to be improving based on my first interactions with the new 10.0 release RC2 image. Â Iâ€™ve noticed much less graphical distortion, and better stability all around.
Tons of bugfixes and stability improvements went in today so big thanks to everyone involved for knocking those out. Â We are still aware of the issue with the FreeBSD bootloader not functioning, but rest assured Kris is putting in every effort to get this resolved for you quickly.
Thatâ€™s it for this week folks!
The first PC-BSD 10.0-RELEASE image, based upon FreeBSD 10.0-RC2, is now available for download!
This image is still a pre-release version of the upcoming 10.0-RELEASE. There is a known issue with VirtualBox not yet working, so if you rely upon this functionality you should wait to update until it is fixed in RC3, or the official RELEASE.
Online updating to 10.0-RELEASE is not yet enabled, but will be for the next test revision based upon FreeBSD 10.0-RC3.
10.0-RELEASE notable features
Found a bug? Please report it, in as much detail as possible, to our Trac database.
In this interview, we talk to the newest member of the team, Bryan Drewery. Â Bryan first came to the attention of many by adopting portupgrade and friends, and then jumping into pkgng and poudriere.
TLD of origin
<Editor’s note: while Bryan claims to be a netizen, it is believed he is originally from .us :)>
When did you join portmgr@
March 2013. Joined FreeBSD as a committer in August 2012. As a contributor
in March 2012.
http://blog.shatow.net is my blog. I have not made much effort on it yet but
have a lot of ideas and content to add eventually.
Inspiration for using FreeBSD
It took a long time for me to discover FreeBSD. I wish I had 10 years
sooner. My first experience with a computer was with MS-DOS 5. Then I worked
up through Windows 3.1, 95, 98, XP. Somewhere around here I discovered Redhat
5 and shortly after Debian and Gentoo. In high school I took an AP CS class
that used FreeBSD 4, which was my first introduction to it. My first
introduction to ports was in the same class where not having root and wanting
to install an application I went into /usr/ports/irc/BitchX and tried to ‘make
install’ and failed of course. I still wish this worked. Shortly after that I
started doing work for a Shell Hosting company that used FreeBSD 4.10. At this
time I was still much more fond of Linux though. When I met my Wife, she was
also doing Shell Hosting with FreeBSD. That’s when I started doing actual
development on it and customizing the system. I found that with FreeBSD I
could customize the system far more than I could with any Linux distribution.
This is what sold me the most and led me away from Linux. Though I do still
use Linux for Xen dom0 and some development.
Who was your first contact in FreeBSD
Probably garga@ qmail patches I sent in years ago. Once I discovered pkgng
though it was bapt@. That’s what led me to becoming a committer. I actually
knew zi@ outside of FreeBSD too from when I was an EFNet oper.
Who was your mentor(s)
Baptiste Daroussin (bapt@) and Eitan Adler (eitan@)
What was your most embarrassing moment in FreeBSD
Wiping systems of course. One of which was someone else’s system who ran my
vi(m) / emacs / other
I was a longtime (6 years) pico/nano poweruser (haha) until I discovered vim
in my first real job.
What keeps you motivated in FreeBSD
I just like to write code. It’s hard for me to let go of things I put a lot
of effort into! I got into this with the intent to help get packaging working
for my own servers and to takeover ports that were abandoned that I felt were
critical for my servers.
There’s so many. Lately I’ve been listening to metalcore and post-hardcore
bands. http://www.last.fm/user/bdrewery has all of the music I listen to.
What book do you have on your bedside table
Design and Implementation of FreeBSD, Kindle, C++ Standard Template Library
coffee / tea / other
I used to drink insane amounts of diet Mt. Dew. Not anymore though, no
caffeine for me.
Do you have a guilty pleasure
I get into games every now and then. Xbox 360, PS3, PC, Wii. I love Windows
7. I’ve been a Mac user for a few months now as well.
sendmail / postfix / other
qmail. My mail server is something that I setup years ago, hacked at quite a
bit with custom patches and never want to redo again.
What is your favorite TV show
Breaking Bad, Lost, The Wire, Dr. Who, Sons of Anarchy, Dexter.
What sports team do you support
I’m not really into rooting on sports teams. I enjoy playing much more than
What else do you do in the world of FreeBSD
I maintain upstream for portupgrade and poudriere, help with pkgng, qmail,
openssh-portable. I also am starting to work more in the src world. I maintain
portmaster but have not put much real effort into it. For portmgr I help test
Mk/ patches, I do exp-runs, help manage the package building systems, and fix
Mk/ bugs as I run across them.
What can you tell us about yourself that most people don’t know
I was involved with the eggdrop IRC bot project and have been maintaining a
pretty popular fork of my own for the past 10 years.
Any parting words you want to share
Getting involved with Open Source is really easy. We’re all volunteers like
you. Just start helping. Send patches, bug reports, code, documentation,
translations, typo fixes. Everything helps.
What is your .sig at the moment
In the words of Dr. Sheldon Cooper (The Big Bang Theory TV Show), â€œiâ€™m not insaneâ€¦my mother had me testedâ€�. Â Thatâ€™s the way iâ€™m sure many of the devs felt at the end of this week. Â While fending off the impending insanity caused by lack-of-flash-itis, the reason for our package issues with version 10.0 finally have started to come into focus. Â For more information on the package / pkgng debacle please see this blog post:Â http://blog.pcbsd.org/2013/12/end-of-the-pkg-woes/. Â Though we typically just recommend users just upgrade to new package sets, I personally opted to do a complete reinstall of 10.0 Beta P6. Â The primary issue myself and many other developers kept running into was issues with the centOS linux compatibility layer that was just too buggy to make good use of at this time.
In other similar news PC-BSD is likely to begin starting a new version naming system to help differentiate the different types of releases and hopefully offer a little more clarity to users that may be less than familiar with the conventional FreeBSD naming system. Â Along with the new naming system a new package release schedule will also be added to help users maintain more stability by not having to update their packages every couple of weeks. Â Stay tuned for more information on this as it develops.
Flash is now working in both firefox and chromium as well as many other internet browsers. Â The new PBIâ€™s have been approved and include the fixes to make sure flash works with all the recent changes in version PC-BSD 10.0. Â For Chromium look for the version of 31 ending in .63. Â For Firefox look for version 25_01. Â Iâ€™m not sure if the issue is widespread but there was an additional step needed to make flash work in firefox on one of my primary test systems. Â If flash is working in other browsers, but not firefox run the commandÂ nspluginwrapper â€“v â€“a â€“i. Â For some reason flashpluginctl on / off was not running the script as it was supposed to. Â From most mainstream testing this looks to be a fairly minor and isolated issue.
PBIâ€™s continue to be added to the PC-BSD AppCafe as well as tons of new compatibility updates for current 10.0 PBIâ€™s. Â Total PBIâ€™s ready for PC-BSDâ€™s 10.0 release are now in excess of 720. Â PC-BSD version 9.2 has also been receiving tons of PBI updates so make sure to check those out as well!
Special thanks to Ken and Kris both as well for all the bug fixes you guys have committed this week (and for listening to my non-stop rants on why flash is so important). Â The schedule has been insane, but the light at the end of the tunnel is near.
As we go into the new year soon weâ€™d like to tell everyone thank you and wish you the best during the holidays. Â I will now leave you with a bit of holiday cheer for all of who have or will experience that inevitable holiday computer failure.
Best Regards and Happy Holidays,
On the twelfth day I left it, my PC gave to me:
Twelve programs stalling;
Eleven chips a-smoking;
Ten ports a-jamming;
Nine jails a-frying;
Eight times iâ€™m crying;
Seven blown partitions;
Six bad controllers;
Five seeeeeeg faults; (singer should hold out seg just FYI)
Four bad blocks;
Three bad controllers;
Two faulty pools;
And a burnt-out CPU fan.