singularity Forum Rss Feed

New Post: singularity build fail

MpDzik — Tue, 11 Jun 2013 08:53:32 GMT

Hi danholmes,

Could you create a pull request and upload this change to the Singularity RDK on BitBucket (https://bitbucket.org/MpDzik/singularity-rdk)? The Singularity source code on codeplex is no longer maintained by Microsoft and only Microsoft employees have permissions to check in new code. In effect this makes the repository read-only... On the other hand on BitBucket anyone can create a new fork to share their work with the Singularity community.

Cheers,
Marek

New Post: singularity build fail

danholmes — Thu, 02 May 2013 08:12:18 GMT

I downloaded the latest version of this source code yesterday and had the same issue. I fixed it by modifying the build\msb.cmd script so that it used the correct characters from the date string appropriate to my locale.

Figure out the starting character number for each piece of the date:
>echo 0123456789
0123456789
>echo %DATE%
dd/mm/yyyy

Then change:
set _timestamp=%_date:~10,4%%_date:~4,2%%_date:~7,2%-%_time:~0,2%%_time:~3,2%%_time:~6,2%%_time:~9,2%

to:
set _timestamp=%_date:~6,4%%_date:~3,2%%_date:~0,2%-%_time:~0,2%%_time:~3,2%%_time:~6,2%%_time:~9,2%

New Post: singularity build fail

danholmes — Thu, 02 May 2013 08:12:18 GMT

New Post: Microsoft stop faffing about!

CosmosKey — Sun, 14 Apr 2013 15:32:06 GMT

Microsoft,

Stop faffing about. Just start deving and supporting Singularity properly and port it to ARM. You know that it is way more cool than any Windows or any UN*X like thing out there. I wanna run Singularity on my Raspberry Pi so go on, get going. :)

New Post: Getting Singularity running on VMware

arfonzo — Fri, 26 Oct 2012 10:16:05 GMT

Kipter,

This is extremely late, but may help someone else:

You need to create the directory: D:\singularity-45126\base.obj\MSBuildLogs\5

Then try the MS Build line again.

Hope that helps,

Arfonzo

New Post: Singularity RDK on BitBucket

MpDzik — Thu, 23 Aug 2012 19:53:11 GMT

Hi everyone!

I've been interested in the Singularity project for some time now (about 3 years), and sadly, I see that not much is going on in the project. I have written my Master thesis about Singularity more than one year ago and my source code patch is still being evaluated! It seems that Microsoft is no longer taking care of this project.

I see that from time to time there are people who want to do something with Singularity. However, it is hard to collaborate on a project with a closed, read-only source code repository which no one takes care of. That's why I decided to upload Singularity RDK to a decentralized Mercurial repository on BitBucket. This way people who want to contribute to the project and share their work can do so easily! Using a decentralized source code repository, it is easy to create forks and share your source code or even work together. I hope that this will resurrect the Singularity project at least a little bit! :)

You can find the Singularity RDK here:
https://bitbucket.org/MpDzik/singularity-rdk

I also created a fork with my implementation of SIP-based bus drivers for Singularity (that was the subject of my Master thesis). You can also find my thesis paper in this fork:
https://bitbucket.org/MpDzik/singularity-bus-drivers

If anyone is doing anything with Singularity, then I strongly recommend creating a fork of the RDK on BitBucket and using it as your source control. This way we can share source code and do something interesting with Singularity. For those of you who are not familiar with Mercurial, you can find more information on the project's home page (http://mercurial.selenic.com). It is a great, modern, decentralized source control system and it's free!

By the way, I have spent a lot of time analyzing and extending Singularity source code when I was working on my Master thesis, so if anyone has questions, feel free to contact me - I'll try to help if I can! :)

-- Marek

New Post: .NET and Singularity?

andrew2325 — Tue, 07 Aug 2012 03:19:09 GMT

Will you be developing .NET to be used with Singularity? If you are doing so, I would definitely be interested in helping a little bit. I took a year of C#, and I am a bit rusty. I have a little bit of a nack for some things technical... Configuration files on Linux, remembering commands and basic switches, and I've worked with some basic, c#, and perl. Newb by some standards, but newbs can actually lay groundwork for apps on projects like this. Like cli apps that move files around and some much more advanced ideas. Let me know.

New Post: Scheduling Algorithm

mohammadmoein — Tue, 10 Jul 2012 11:59:15 GMT

is there any chance to change scheduling algorithm and use for experimental purpose?

New Post: Hardware requirements for booting Singularity

Eric6eyser — Wed, 26 Oct 2011 17:35:50 GMT

our snapshot of Singularity is from 2008. no work has been published since then to bring it up-to-date with newer hardware profiles.
use this OS to leverage your older 32-bit hardware, or add some compatible drivers and get props for bringing it current.

New Post: Hardware requirements for booting Singularity

sharadb — Mon, 24 Oct 2011 14:10:49 GMT

Hi Marek,

I am using Singularity for my project which will include sending Signals and getting feedback from the hardware. So I need a physical computer and a VM is not enough for me.

Thanks,

Sharad

New Post: Hardware requirements for booting Singularity

MpDzik — Mon, 24 Oct 2011 13:31:43 GMT

I'm not sure if this is related to 32/64-bit hardware. It seems that Singularity does not support new hardware to well. I had the same issue on an Alienware M17xR2. However, I was able to boot the system on some older Dell.

Why do you want to boot Singularity on a physical computer?

Marek

New Post: Hardware requirements for booting Singularity

sharadb — Sun, 23 Oct 2011 21:59:54 GMT

What is the hardware configuration required to run Singularity on a physical computer (and not a virtual machine)? I was using a 64 bit , 4 GB RAM brand new intel machine and the boot just hangs after showing:

"Looking for Debugger.

Boot time...

Booting from CD in drive 0xEF.."

Is it necessary that I have a 32 bit hardware to boot Singularity ?

New Post: Burned Disc Image Won't Boot

Eric6eyser — Thu, 29 Sep 2011 16:04:44 GMT

you probably tried a USB keyboard. make sure you have a ps2 keyboard.

plenty of older hardware, especially Dells will boot this. somewhere in 99 there's a PC in clear plastic that booted singularity. it was a demo for power management code that i added. you could watch the disc and fans spin down.

New Post: Burned Disc Image Won't Boot

AnaxEnder — Wed, 28 Sep 2011 18:33:27 GMT

Hi Michael, the disc should boot up Singularity OS (it's not an installer). However, only some specific hardware is supported because Singularity is just a research OS (there are only a few drivers implemented).

From my experience, on an Alienware M17x R2 I wasn't able to boot the system at all. On another, older, Dell the system booted up, but the keyboard did not work (probably the keyboard driver didn't support my device).

The best way to work with Singularity is using a virtual machine (preferably Microsoft Virtual PC). Is there a specific reason why you want to run it on a real machine?

Marek

New Post: Burned Disc Image Won't Boot

MichaelCroghan — Sun, 25 Sep 2011 21:54:35 GMT

Perhaps I am missing some piece of information. I thought the disc would boot on a "real" x86 machine from disc.

Does this boot disc function as an "installer?"

New Post: Singularity I/O Subsystem

br_chiang — Thu, 18 Aug 2011 04:30:38 GMT

Thanks for sharing! I'll read it later this day... :)

New Post: Singularity I/O Subsystem

MpDzik — Wed, 17 Aug 2011 18:19:07 GMT

Hi,

I recently finished writing my Master thesis about Singularity's I/O Subsystem and I wanted to share it with the Singularity community. The thesis is available at http://students.mimuw.edu.pl/~md234040/master.pdf.

Regards,
Marek

New Post: Getting Singularity running on VMware

Kipter — Thu, 19 May 2011 12:42:02 GMT

i'm having some troubles building the whole whing... i get this error:

D:\singularity-45126\base>msb Distro\World.projUsing 64-bit MSBuild from .NET Framework 3.5MSBUILD : Logger error MSB4104: Failed to write to log file "D:\singularity-45126\base.obj\MSBuildLogs\5/01-14393719.log". Could not find a part of the path 'D:\singularity-45126\base.obj\MSBuildLogs\5\01-14393719.log'.Wall time elapsed: 00:00:00 (User: 00:00:00, Kernel: 00:00:00)Total processes: 1Page faults: 4520The system cannot find the path specified. D:\singularity-45126\base.obj\MSBuildLogs\5/01-14393719.log

New Post: singularity 2.0 build fail

Domi — Mon, 09 May 2011 11:57:24 GMT

I had the same problem.

For some reason some of the developers inserted hard spaces (Ascii code 160) which are not recognized in many charsets.

But since its still a kind of whitespace, deleting it, would not affect anything.

New Post: Unable to build a service with a contract

Domi — Sun, 08 May 2011 19:00:03 GMT

The problem is caused by the compiler: The AddPeekMethod() method is called twice, once for each ep.

The first time it is called for Imp which is fine and it's BaseType is "Microsoft.Singularity.Channels.Endpoint".

The second time it is called for Exp whose BaseType is "System.ValueType" for mysterious reasons.

Now there are two questions:

1. Why does it only happen to my custom contracts? I am assuming all default contracts are pre-compiled? How did you compile them if the compiler is flawed?

2. When looking at all members of the Exp ep, I see the following, however, "PeerClosed" is not among them:

       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.#ctor(System.Int32)
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.InState(System.Int32)
RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.CurrentState        RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.RecvBind(System.optional(NonNullType) optional(CustomVector) optional(ExHeap) Char*@,System.optional(NonNullType) optional(CustomVector) optional(ExHeap) Char*@
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.SendAckBind
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.SendNakBind
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.SendReady
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.TransferContentsOwnership(Microsoft.Singularity.Channels.Endpoint@)
         RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.TransferOwnership(Microsoft.Singularity.Channels.Endpoint@,optional(Microsoft.Singularity.Channels.ExHeap) RemoteDirectory.Contracts.RemoteDirectoryContract+Exp*)
         RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.TransferVectorOwnership(Microsoft.Singularity.Channels.Endpoint@,optional(Microsoft.SingSharp.CustomVector) optional(Microsoft.Singularity.Channels.ExHeap) RemoteDirectory.Contracts.RemoteDirectoryContract+Exp*)
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.MarshallAll(System.Byte*,Microsoft.Singularity.Channels.Endpoint@)
         RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.MarshallVector(System.Byte*,Microsoft.Singularity.Channels.Endpoint@,System.Byte*,optional(Microsoft.SingSharp.CustomVector) optional(Microsoft.Singularity.Channels.ExHeap) RemoteDirectory.Contracts.RemoteDirectoryContract+Exp*)
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.MarshallContent(System.Byte*,Microsoft.Singularity.Channels.Endpoint@,System.Byte*)
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.Dispose
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.Expose
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.UnExpose
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.Acquire
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.Release
       RemoteDirectory.Contracts.RemoteDirectoryContract+Exp.TagPod0

Still - Any help would be greatly appreciated!

-Domi

This is how my contract looks like:

using Microsoft.SingSharp;
using Microsoft.Singularity.Channels;
using Microsoft.Singularity.Directory;
using System;

namespace RemoteDirectory.Contracts
{
    public contract RemoteDirectoryContract : ServiceContract
    {
        // This is the name under which the Remote Directory Service registers itself with the name server
        public const string ModuleName = "/service/remotedir";

		// ######################################################
        // Request messages by the DirectoryService:
		
		// Bind the given ep to the given path.
		// The nodeName is the name of the node that is sending the request.
        in	message Bind(char[]! in ExHeap nodeName, char[]! in ExHeap path, ServiceContract.Exp:Start! exp);
		
		
		// ######################################################
        // Response messages:
		
		// bind succeeded, exp now belongs to the RDC
		out	message AckBind();
		
		// attempt to return unused endpoint if possible
		out	message NakBind(ServiceContract.Exp:Start! exp, ErrorCode code);
		
		// Send upon successful connection
        out message Ready();
		
		// ######################################################
        // State diagram
        override state Start : Ready! -> ReadyState;

        state ReadyState : one
        {
            Bind? -> (AckBind! or NakBind!) -> ReadyState;
        }
    }
}