9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Ori Bernstein <ori@eigenstate.org>
To: 9front@9front.org
Subject: Re: [9front] Staying up-to-date
Date: Wed, 12 Jun 2024 15:35:21 -0400	[thread overview]
Message-ID: <7F181CD8-1AB1-46D0-8D35-2053C7AF0E5F@eigenstate.org> (raw)
In-Reply-To: <8418174.T7Z3S40VBb@cixi>

That looks like a corrupted file system.

On June 12, 2024 2:11:48 PM EDT, Thomas Nemeth <tnemeth@free.fr> wrote:
>Le mercredi 12 juin 2024 19:56:15 CEST, vous avez écrit :
>> sure, but my point is that automations like this are not supported by
>> 9front developers, and *will* sooner or later lead to unexpected
>> non-diagnosable errors.
>> as long as you're prepared for this risk i don't see anything that
>> would hinder automation.
>> the fqa script is an example, which does not contain a single bit of
>> error handling ;)
>
>    Indeed :)
>
>    I stumble upon them a lot of time. Eg, since a few days, while
>    doing a "mk install" in /sys/src:
>
>ar vu /arm64/lib/ape/libap.a _assert.7 abort.7 abs.7 atof.7 atoi.7 atol.7 
>atoll.7 bsearch.7 calloc.7 clock.7 ctype.7 difftime.7 div.7 getenv.7 
>putenv.7 isalnum.7 itoa.7 itol.7 ldiv.7 mbwc.7 memccpy.7 memchr.7 memcmp.7 
>mktime.7 mkstemp.7 qsort.7 raise.7 rand.7 strcat.7 strchr.7 strcmp.7 
>strcoll.7 strcpy.7 strcspn.7 strftime.7 strlen.7 strncat.7 strncmp.7 
>strncpy.7 strnlen.7 strpbrk.7 strrchr.7 strspn.7 strstr.7 strtod.7 strtok.
>7 strtol.7 strtoll.7 strtoul.7 strtoull.7 strxfrm.7 toupper.7 strdup.7
>ar: /arm64/lib/ape/libap.a not in archive format
>mk: ar vu /arm64/lib/ape/libap.a ...  : exit status=ar 24249: error
>mk: for(i in gen ...  : exit status=rc 24234: mk 24235: error
>mk: for (i in ...  : exit status=rc 24227: mk 24232: error
>mk: cd lib mk install  : exit status=mk 24224: error
>mk: mk lib.install mk ...  : exit status=rc 24222: mk 24223: error
>mk: date for (i ...  : exit status=rc 23407: mk 24220: error
>/sys/src% 
>
>
>    To the point of wondering if my filesystem is corrupted. Only
>    trying to compile the kernel:
>
>file system made
>mkpaqfs: read failed: bootfs/arm64/bin/9660srv: phase error -- type 
>mismatch
>mkpaqfs: could not read directory: bootfs/arm64/bin/auth: phase error -- 
>type mismatch
>mkpaqfs: could not read directory: bootfs/arm64/bin/aux: phase error -- 
>type mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/cfs: phase error -- type mismatch
>mkpaqfs: could not read directory: bootfs/arm64/bin/disk: phase error -- 
>type mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/dossrv: phase error -- type 
>mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/cwfs64x: phase error -- type 
>mismatch
>mkpaqfs: could not read directory: bootfs/arm64/bin/ip: phase error -- 
>type mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/ls: phase error -- type mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/mntgen: phase error -- type 
>mismatch
>mkpaqfs: could not read directory: bootfs/arm64/bin/ndb: phase error -- 
>type mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/hjfs: phase error -- type mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/tlsclient: phase error -- type 
>mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/nusb/usbd: phase error -- type 
>mismatch
>mkpaqfs: read failed: bootfs/arm64/bin/nusb/ether: phase error -- type 
>mismatch
>../port/mkrootall \
>	paqfs __objtype_bin_paqfs /arm64/bin/paqfs\
>	factotum __objtype_bin_auth_factotum /arm64/bin/auth/factotum\
>	bootfs.paq bootfs_paq bootfs.paq\
>	boot boot boot\
>>pi3.root.s
>../port/mkrootc \
>	paqfs __objtype_bin_paqfs /arm64/bin/paqfs\
>	factotum __objtype_bin_auth_factotum /arm64/bin/auth/factotum\
>	bootfs.paq bootfs_paq bootfs.paq\
>	boot boot boot\
>>pi3.rootc.c
>7c -FTVw pi3.rootc.c
>cp: can't stat boot: file does not exist: 'boot'
>cannot open: file does not exist: 'mkroot.30532.out'
>../port/mkrootall:29: < can't open: mkroot.30532.out: file does not exist: 
>'mkroot.30532.out'
>mk: ../port/mkrootall \  ...  : exit status=mkrootall 30532: file does not 
>exist: 'mkroot.30532.out', deleting 'pi3.root.s'pi3.root.s: file does not 
>exist: 'pi3.root.s'
>
>/sys/src/9/bcm64% 
>
>
>
>

  reply	other threads:[~2024-06-12 19:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 14:57 Thomas Nemeth
2024-06-11 15:08 ` phil9
2024-06-11 15:15   ` Thomas Nemeth
2024-06-12 11:57     ` cosarara
2024-06-12 16:57       ` Thomas Nemeth
2024-06-13  0:46         ` sl
2024-06-13  1:05           ` sl
2024-06-13  6:31           ` Thomas Nemeth
2024-06-13 17:16             ` hiro
2024-06-12 12:21     ` ori
2024-06-12  2:30 ` Thaddeus Woskowiak
2024-06-12 17:10   ` Thomas Nemeth
2024-06-12 12:51 ` hiro
2024-06-12 13:04   ` ori
2024-06-12 17:10     ` Thomas Nemeth
2024-06-12 19:34       ` Ori Bernstein
2024-06-12 21:55         ` Stanley Lieber
2024-06-12 17:03   ` Thomas Nemeth
2024-06-12 17:56     ` hiro
2024-06-12 18:11       ` Thomas Nemeth
2024-06-12 19:35         ` Ori Bernstein [this message]
2024-06-13  6:38           ` Thomas Nemeth
2024-06-14 20:11             ` hiro
2024-06-16 10:01               ` Thomas Nemeth
2024-06-16 13:03                 ` Thaddeus Woskowiak
2024-06-16 14:27                   ` Thomas Nemeth
2024-06-16 18:02                     ` ori
2024-06-17 11:04                     ` hiro
2024-06-16 18:00                 ` ori
2024-06-16 20:20                   ` [9front] Out-of-date and obsolete documentation Lyndon Nerenberg (VE7TFX/VE6BBM)

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=7F181CD8-1AB1-46D0-8D35-2053C7AF0E5F@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.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 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 NNTP newsgroup(s).