I’ve recently run into a problem with 7-STABLE on VMware ESXi 3.5u4. With a recent change my VM shuts off shortly after probing the LSI (mpt) disk controller. The same behavior started occurring over the summer in HEAD and the quick workaround is to change the VM’s disk controller type from LSI to BusLogic. Lately I have some time to poke people about this issue so I figured I would. The problem is getting as much as I can while booting and having some usable boot messages for someone to look at. This would usually be accomplished by redirecting console output to a serial port on the problem machine and hooking up a cross over cable between it and another box. I haven’t done this on VMware before though so I had to do a little googling and it’s pretty simple.
On the FreeBSD side the following needs to be added to /boot/loader.conf:
This will redirect the console to both the video display and a serial port. Once that is done shutdown the VM so the serial port can be added and configured.
With the crashing VM turned off go to “Edit Settings”:
Click the “Add” button to add a serial port to the VM:
For the serial port output select “Connect to named pipe”:
Finally configure the pipe:
The name of the pipe should be a file location on the VM host machine, not the guest. The near end is “Server” since I want to see the output from this VM and the far end will be another virtual machine. For the VM I’ll be connecting from to view the console output I would do the same but near end would be “Client”.
Once all this is done, from the second working VM launch cu(1).
# cu -l cuad0
After that boot the crashing VM and kernel messages should appear on the second VM. That’s all it takes to setup a serial connection between two FreeBSD VMs on VMware.
Update: Images fixed.
The following is from a report on 60 Minutes II back in October of 2002. NITV is a California based Iranian-American TV station carried internationally via satellite with viewership in Iran.
And the mullahs really couldn’t take what NITV did on Sept. 11. Hours after the attacks, Zia [Ataby] took to the air with a message for Iranian youth: “To show your feeling and share your feelings with American people, come to the Mossani square in Tehran and bring your candle.”
They brought their candles and their voices, shouting, ”Death to terrorists.” Six thousand demonstrators were called to the streets of Tehran by Zia Atabay in North Hollywood, the only show of support for America in the Islamic world.
Note: I’ve tried searching for video of the orignal report but cannot find it. If anyone can help me out with that it would be pretty sweet. Thanks.
Update: Only article I was able to find on the event filed when it occured.
“It was on June 16th, 1987 that the SDF-1 received its first caller at 300bps. This little Apple ][e BBS of the late 80s turned into a Public access UNIX System with the demise of “killer.dallas.tx.us” during the Operation Sundevil” raids. Since then it has grown to become the oldest and largest continually operating PUBNIX on the planet.
Over the years SDF has been a home to 2+ million people from all over the world and has been supported by donations and membership dues. SDFers pride themselves on the fact that theirs is one of the last bastions of “the real INTERNET”, out of the reach and scope of the commercialism and advertising of the DOT COM entities…”
About five years ago I was out of college, my school email address was going to expire, and I didn’t have an ISP. I hate webmail and just wanted simple pop3 email access. I remembered back in high school having a free shell account from some system I couldn’t remember and went searching. Most of the google hits I found were service providers with monthly fees (I wasn’t paying $5 a month just for email) or had no email access. Eventually I stumbled on SDF. It was a $2 donation for a permanent account. A full unix shell account for $2! Just couldn’t beat that and it hasn’t been a bad decision. I’ve always liked the fact that SDF is a non-profit and is paid for by donations and while run by volunteers. It’s nice to know there still exists a place which just provides internet services for the sake of just providing those services to anybody that could use them.Â By the way, they’re also active NetBSD supporters.
It’s ports tree freeze time and Novel has yet to announce it but Mono 1.2.4 is in the BSD# CVS repo ready and waiting.Â If you’re interested in Mono on FreeBSD please use and test it to make sure the update goes smoothly and there are no surprises.Â You can see the BSD# homepage and instructions for using mono-merge to use the ports in the BSD# repo.
If anyone has had problems building or updating Mono because it crashes please update to 184.108.40.206_3 as this should solve the problem.Â Thanks to Phillip Neumann for suggesting the patch based on some LC environment issues he had sometime ago.Â Also thanks to kib@ and mux@ for testing changes for me repeatedly to narrow down the problem.
(I’m reposting my recent email to ports@ here for a wider audience.)
For the last 2 years I’ve been maintaining Mono and it’s consumers on FreeBSD and running the BSD# project. Mono has come a long way in the past two years with the help of a few people but it still has further to go to work as well as it does on Novell’s targeted platforms. With that said, I’ve realized that it is time for me to step aside from maintaining Mono and running BSD#. A few months ago I realized I was not enjoying my FreeBSD work at all. That made me come to the conclusion that it’s time for me to pursue other FreeBSD work. My life has changed in the past two years. The biggest change is a new job. I have less free time and I like spending the free time I have working on projects related to what I find interesting at work. I’ve also accumulated a number of ideas over the past few years for FreeBSD which I want to pursue. Maintaining Mono and trying to run BSD# just doesn’t fit into my life very well anymore.
Many people familiar with Mono know how I got this job. As a completely novice programmer I just wanted to learn C#. Soon after I did a port or two the last Mono maintainer left. At that point I decided to keep Mono up to date in the interim until someone else wanted the job. (Can 2 years be called interim?) This is why I started BSD# instead of maintaining the ports on my own. Mono’s issues on FreeBSD have long been over my head. It needs someone who will actually port it not just keep it up to date. I used to keep a list of known issues that could be easily reproduced with certain applications. Not having someone to look at the cause of and fix these issues I eventually gave up. This has stalled a few applications from making their way into the FreeBSD tree.
I’m not dropping Mono, all the C# ports, and BSD# right now. In fact, I was at Novell’s Mono conference this week. I want to ensure a smooth transition and avoid dropping all the ports maintained by [email protected] to ports@. I don’t think it’s fair to users for me to drop all this without sufficient warning. 1.2 comes out in the next few weeks and 2.0 is expected by the end of 2007. I plan on seeing 1.2 and a few of the maintenance releases make their way into FreeBSD tree. With 1.2 will come enabled amd64 support and better stability. (amd64 support has actually worked for a while but there hasn’t been an amd64 tinderbox available until recently.) But as 2.0 ramps up I’d like to hand the reigns over to someone else moreinterested and more capable of maintaining it.
For anyone interested in Mono on FreeBSD, please, join the BSD# mailing list. You can find more information about it on the BSD# homepage. I’m also on Freenode’s #BSD-Sharp from 20:00 EDT to 23:00 EDT most evenings after work. Occasionally I’m available on there during the day while at work too. There’s always something for an interested and motivated party to do. We could use more C# application ports. There’s also a lingering crash that happens on occasion when people attempt to build Mono which typically goes away on the next try.
Realistically, I plan on stepping down in the next three months or so but I will hang around longer if it looks like someone wants the responsibility for everything. I’ll always be around to wrangle update PRs as well.
Mono was fun for some time but it’s just come time for me to move on.
Mono 1.1.18 was committed by Phillip Neumann to the BSD# CVS repo recently. In addition, last night gtk# (gtk-sharp20) was updated to 2.10. With this update the Gnome specific bindings were split out into a seperate Gnome# package (gnome-sharp20). I’ve also patched bsd.gnome.mk to add gtksharp10, gtksharp20, and gnomesharp20 to USE_GNOME. It’s tough to quickly figuring out which ports need gnome-sharp20 instead of just gtk-sharp20 so for now I’ve just switched all ports in the repo with a gtk-sharp20 dependency to USE_GNOME=gtksharp20 and I’m in the midst of tinderboxing the entire tree. That should catch all the ports which really need the Gnome# bindings. I’ll be fixing those issues as the tinderbox mails them to me.
Mono 1.2 will be announced in the comming weeks. With the current ports freeze in place I’m figuring I’ll wait until 1.2 is ready and commit all the changes in the BSD# tree to the FreeBSD tree in one large commit. amd64 support will also be left enabled at that time and all ports will be moved to LOCALBASE. If you’re interested in Mono on FreeBSD please see the BSD# homepage and instructions for using mono-merge to use the ports in the BSD# repo.