All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc-F. LUCCA-DANIAU" <mfld.fr@gmail.com>
To: Derek Johansen <djohanse678@gmail.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: ls not working
Date: Wed, 25 May 2016 08:58:10 +0200	[thread overview]
Message-ID: <57454D02.2010600@gmail.com> (raw)
In-Reply-To: <122e35c2-b670-9d54-8bcb-9581baca8bf5@jodybruchon.com>


As told by the README, you should not use the /dev86 master branch from 
lkundrak, but the latest from Jody:

To build ELKS, you
will need to obtain a copy of Dev86, currently available at:

https://github.com/jbruchon/dev86 <https://github.com/jbruchon/dev86>

When you build dev86, you need to move, copy, or symlink to it in the
ELKS source code root. For a Dev86 source at /usr/src/dev86 do this:

user:/usr/src/elks$ ln -s /usr/src/dev86 dev86

MFLD

  parent reply	other threads:[~2016-05-25  6:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25  4:52 ls not working Derek Johansen
2016-05-25  4:55 ` Jody Bruchon
2016-05-25  5:53   ` Derek Johansen
2016-05-25  5:55     ` Derek Johansen
2016-05-25  6:58   ` Marc-F. LUCCA-DANIAU [this message]
2016-05-25 13:55     ` Derek Johansen
2016-05-25 14:35       ` Marc-François LUCCA-DANIAU
     [not found] ` <57454B74.7010101@gmail.com>
2016-05-25  6:56   ` Marc-F. LUCCA-DANIAU
     [not found]     ` <CAMKR1ysV2G+omnqFEOe2PDiP_14qfvnT3JmPNTqLRTD-6N5jjg@mail.gmail.com>
2016-05-25  8:44       ` Marc-François LUCCA-DANIAU
2016-05-25 13:59   ` Derek Johansen
2016-05-25 14:38     ` Marc-François LUCCA-DANIAU
     [not found]       ` <1603480025.4412.85bac19a-2c59-4bca-930c-210d80a97978.open-xchange@email.1and1.com>
2016-05-25 15:41         ` Fwd: Re: ls not working [confirmed] - -
2016-05-25 16:08       ` ls not working - -
2016-05-25 19:16         ` Marc-F. LUCCA-DANIAU
     [not found]           ` <B5F3BEBA-6AA5-41D4-8D82-4927B089E3C3@jodybruchon.com>
     [not found]             ` <CACpuWUmcNDbdE+Pu1_812W0hJgHzFnKeJ25ztSdqJW4XKx1qAA@mail.gmail.com>
2016-05-25 20:42               ` Marc-François LUCCA-DANIAU

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57454D02.2010600@gmail.com \
    --to=mfld.fr@gmail.com \
    --cc=djohanse678@gmail.com \
    --cc=linux-8086@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.