Microsoft .NET now Open Source?

This is a turn up for the books. Who would have thought this would even have been a option a few years back. Microsoft is open sourcing .NET, making the source available on GitHub, and even plans to make the framework cross platform to run on Linux and Mac – more here.

One can only speculate that they feel pressured to do this for .NET to stay relevant, and/or to expand it’s usage to other platforms outside of Windows? Given the accelerating trend to deploy to the cloud on virtualized platforms (in most cases on OSes almost certainly not to be Microsoft Windows), maybe Microsoft sees this as a strategic move for them to keep their development framework an option in this changing landscape?

(Page views: 35)

Mac OS X Yosemite

Ars Technica has a fantastically detailed review (25 pages) of the latest OS X release, Yosemite. I’m browsing though the article as my 5.1GB download is slowly coming across the tubes. Maybe sometime tonight it will have completed and I’ll be ready to install :-)

In the meantime, I’m wondering whether I like the ‘flat’ UI look, and prefer the 3d style icons and shadows in my dock, but I’m sure I’ll get used to it.

(Page views: 121)

Kantronics All Mode TNC – useful commands and tips

I’m still learning what the different commands are, but here’s what I’ve worked out so far (some of this might be wrong, if so leave me a comment!)

  • c callsign : connect to callsign
  • c callsign1 via callsign2 : connect via some other station you can hear
  • unproto name via call1, call2, etc : sets the routing list of stations where your want your packets to be sent when in conv mode (?)
  • when you connect (c) direct to another station, you enter conv mode with that station
  • conv: enter conv mode when not directly connected to another station (packets are broadcast to the stations in your unproto string)
  • Ctrl-C : to exit conv mode, and get back to cmd: mode
  • perm : write settings to eprom

Useful commands when connected to someone’s bbs:

  • l : list all messages
  • lm : list messages to me
  • b : list broadcast messages
  • s callsign : send message to callsign
  • r # : read msg #
  • b (bye) : exit

(Page views: 122)

Mounting Atari ST floppies on Ubuntu

I’m transferring some apps downloaded for my Atari ST (don’t ask) to floppies that are formatted with 80 tracks and 8 or 9 sectors, on double density disks (formatted on the ST). From what I understand these are MS-DOS readable but not exactly FAT format. Anyway, they don’t seem to mount by default on Ubuntu as it doesn’t know what format they are, but forcing a mount with this seems to work:

sudo udisks --mount /dev/fd0

seems to do the job (tip from here)

(Page views: 107)

2014 vs 2013 California QSO Party (CQP) scores for Yolo County

Since having my Amateur Radio license just over a year, I’ve yet to go all out on a contest and work every hour permitted, but I have enjoyed the opportunity to work some contacts for my log. Last year’s California QSO Party I only worked a few QSOs. If I remember back to last year, I did call CQ for 20 mins or so and didn’t get any takers, so did some search and pounce and picked up a handful of contacts:2013 CQP Yolo resultsThis year I worked a couple of hours over Sat and Sun, and got significantly more that my 8 QSOs last year, but nowhere close to K6Y’s score. I’ve submitted my log and will wait for the final scores to be published :-) All in all, had a good result this year!

 

(Page views: 134)

Updating log4j 1.x to 2.x

I’ve used Log4J 1.x for ages, and not even realized that the 1.x code line is not maintained any more, it seems all the activity is on 2.x as the latest maintained version of the framework.

To move from 1.x to 2.x, there’s a few changes:

If you’re using Maven for your dependencies, replace

<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.15</version>
</dependency>

with

<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.0.2</version>
</dependency>

<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>2.0.2</version>
</dependency>

The API has changed from:

org.apache.log4j.Logger

and

Logger.getLogger()

 

to

org.apache.logging.log4j.Logger

and

org.apache.logging.log4j.LogManager.getLogger()

 

Sample xml config – use filename log4j2.xml instead of log4j.xml (or log4j.properties):

<?xml version=”1.0″ encoding=”UTF-8″?>
<Configuration>
<Appenders>
<Console name=”STDOUT” target=”SYSTEM_OUT”>
<PatternLayout pattern=”%C – %m%n”/>
</Console>
</Appenders>
<Loggers>
<Logger name=”example.logger.name” level=”debug”/>
<Root level=”debug”>
<AppenderRef ref=”STDOUT”/>
</Root>
</Loggers>
</Configuration>

Additional useful info here.

(Page views: 158)

Adding a JMS Queue to Wildfly 8.x

The messaging subsystem in Wildfly is enabled in the standalone-full.xml config (not standalone.xml).

To add a new queue, search for <subsystem xmlns=”urn:jboss:domain:messaging:2.0″>, and then within the <hornetq-server> section, add a new <jms-destinations> if it doesn’t exist already, and define your queue name and JNDI lookup:

<jms-destinations>
    <jms-queue name="exampleQueue">
        <entry name="jms/queue/example"/>
        <entry name="java:jboss/exported/jms/queue/example"/>
    </jms-queue>
</jms-destinations>

 

(Page views: 192)