otaviosoares

Using Ubuntu 15.10, you can install vhdimount and tsk (The Sleuth Kit) via:

sudo apt-get install libvhdi-utils sleuthkit
Then you can proceed as follows:

sudo mkdir -v /mnt/vhd
sudo vhdimount -X allow_root /path/to/file.vhd /mnt/vhd/
sudo mmls -aB /mnt/vhd/vhdi1
Next, you'll have to calculate the offset from the output of mmls like this:

otaviosoares

2016-10-28T04:48:49.373+0000 I CONTROL  [initandlisten] MongoDB starting : pid=7 port=27017 dbpath=/data/db 64-bit host=auth-mongo-3362045018-yrlyk
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten] db version v3.2.10
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten] git version: 79d9b3ab5ce20f51c272b4411202710a082d0317
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten] OpenSSL version: LibreSSL 2.4.3
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten] allocator: system
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten] modules: none
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten] build environment:
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten]     distarch: x86_64
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2016-10-28T04:48:49.374+0000 I CONTROL  [initandlisten] options: {}

otaviosoares

'use strict'

var Seneca = require('seneca')
var Mesh = require('seneca-mesh')

var envs = process.env
var opts = {
  seneca: {
    tag: envs.BASE_TAG || 'base'
  },

otaviosoares

1 - Desenhe um EAP inicial para o projeto do estudo de caso (mínimo 3 níveis)
2 - Proponha um sistema de controle de mudanças para o projeto de estudo de caso.
3 - Proponha um documento de declaração de escopo para o caso.
4 - Quais as lições aprendidas do caso?
5 - O que deve conter o termo de abertura do projeto de caso?
6 - Quais possíveis problemas de integração no caso?
7 - O que você pensa dos riscos no projeto? Havia como prever todos?

otaviosoares

# Clears all the unused images
sudo docker images --format "{{.Repository}}:{{.Tag}}" | xargs sudo docker rmi


sudo docker rm $(sudo docker ps -a -q) && sudo docker rmi $(sudo docker images -q) && sudo docker ps -a | cut -c-12 | xargs sudo docker rm

otaviosoares

var entity = seneca.make('cliente')
entity.name = 'Otavio'
entity.save$(function(err) {
  console.log('saved')
})

// Collection cliente
//id name
//1  Otavio

otaviosoares

'use strict'

var seneca = require('seneca')

function eventStore () {

  // This is the acid part, if this stores correctly all events are
  // emitted, if not you die because you are in an invalid state. this
  // whole part is usually based on optimistic concurrency.
  seneca.add('role:eventStore,cmd:update', functiom (msg, done) {

otaviosoares

// USUARIO
// Obra
{
  "id": "object-id",
  "name": "minha obra",
  "artist": "Leandro",
  "owner": {"id": "user-id", "type": "USER"},
  "shares": [{"id": "company-id", "type": "COMPANY"},{"id": "another-user-id", "type": "USER"}]
}

otaviosoares

# WARNING - THIS IN NOT a SHELL SCRIPT - JUST a LIST of COMMANDS
# based on https://github.com/coreos/coreos-overlay/issues/595 with links updated

# Build cifs-utils in a container and copy it into /tmp on the host.
$docker run -t -i -v /tmp:/host_tmp fedora /bin/bash
# On the container bash prompt
yum groupinstall -y "Development Tools" "Development Libraries"
yum install -y tar
yum install -y bzip2
curl https://download.samba.org/pub/linux-cifs/cifs-utils/cifs-utils-6.3.tar.bz2 | bunzip2 -c - | tar -xvf -

otaviosoares

box: nodesource/trusty:4.3.0

build:
  steps:
    - script:
        name: set env vars
        code: export NODE_ENV=test

    - npm-install