From: "Marc-François LUCCA-DANIAU" <mfld.fr@gmail.com>
To: Jody Lee Bruchon <jody@jodybruchon.com>
Cc: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: ls not working
Date: Wed, 25 May 2016 22:42:59 +0200 [thread overview]
Message-ID: <CACpuWUm=20RTh=9UBp3-bTvGBSv0kqygsce3J3WJnHGNApuF9g@mail.gmail.com> (raw)
In-Reply-To: <CACpuWUmcNDbdE+Pu1_812W0hJgHzFnKeJ25ztSdqJW4XKx1qAA@mail.gmail.com>
Git bisect tells me that the problem occurs starting from commit
4286d710caee2e25a0446932104d99b6cec2fe39
file_utils: add usage to some programs, clean up futils.h, ls fix
MFLD
2016-05-25 22:24 GMT+02:00 Marc-François LUCCA-DANIAU <mfld.fr@gmail.com>:
> OK, the problem does not occur with the latest release 0.2.0 (commit
> 3c302cad12d34de58aba1b166da06c9173a43364).
>
> Now starting to bisect...
>
> MFLD
>
>
> 2016-05-25 21:47 GMT+02:00 Jody Lee Bruchon <jody@jodybruchon.com>:
>> If you look for the last commits where I made changes instead of just pulling other people's contributions, those definitely should work. You have to be sure to do a "make distclean" in dev86 and a clean in elks.
>>
>> On May 25, 2016 3:16:31 PM EDT, "Marc-F. LUCCA-DANIAU" <mfld.fr@gmail.com> wrote:
>>>Same failure on my side with latest /dev86 and /elks, with QEMU 2.5.1.
>>>
>>>Do you remember the last known good version of the three (dev86, elks,
>>>qemu) ?
>>>
>>>MFLD
>>>
>>>
>>>
>>>Le 25/05/2016 18:08, - - a écrit :
>>>>> On May 25, 2016 at 10:38 AM Marc-François LUCCA-DANIAU
>>><mfld.fr@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Yes, please, try again to run ELKS under VB, but before testing,
>>>>> please update both DEV86 and ELKS from Jody's repositories and
>>>rebuild
>>>>> all.
>>>> Unfortunately, I have tried numerous combinations of git checkouts of
>>>dev86 and
>>>> elks including reverting both to the last pair I knew was working in
>>>QEMU, but
>>>> even those are not working for me at this point. I don't currently
>>>have time to
>>>> look into it in more depth. Can someone try it in an old version of
>>>QEMU to see
>>>> if that works?
>>>>
>>>> -Jody
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-8086"
>>>in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>>--
>>>To unsubscribe from this list: send the line "unsubscribe linux-8086"
>>>in
>>>the body of a message to majordomo@vger.kernel.org
>>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>> --
>> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-05-25 20:42 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
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 [this message]
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='CACpuWUm=20RTh=9UBp3-bTvGBSv0kqygsce3J3WJnHGNApuF9g@mail.gmail.com' \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@vger.kernel.org \
--cc=jody@jodybruchon.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).