Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bad filesystem/partition layout #8

Open
mirabilos opened this issue Jan 6, 2024 · 4 comments
Open

bad filesystem/partition layout #8

mirabilos opened this issue Jan 6, 2024 · 4 comments

Comments

@mirabilos
Copy link

After installing, I tried to mount the filesystems from the host in order to copy files over.

I could mount /boot but only after fixing tons of e2fsck errors, I could not mount / at all, and the disc now does not boot any more either (enters GRUB rescue mode).

I suspect that something does not honour the partition layout (and, arrrgh why do you use GPT?) correctly.

kpartx also says that one of the two GPT copies is corrupt.

I think this will lead to data loss.

(I just wanted to look whether my shell works. It’s more liberally licenced than GNU bash, leaner and faster. If you want, get the Debian package, extract usr/lib/i386-linux-musl/bin/mksh from the inside (it’s statically linked) and copy it over. Also put usr/share/doc/mksh/examples/dot.mkshrc as ~/.mkshrc.)

@llenotre
Copy link
Member

llenotre commented Jan 6, 2024

Thank you for the bug report!
Before trying to make fixes, I urgently need to refactor the codebase, this is absolutely necessary. So I will need some time.

I will take a look at your shell. For the support of Perl (referring to this), it will be coming at the same time as I start testing compilers, right after adding network support.

For the license, I have to admit I am not sure what to use. There is an ongoing war around the project about this very subject.

and, arrrgh why do you use GPT?

What is wrong exactly with GPT? What would you recommend using instead?

@mirabilos
Copy link
Author

mirabilos commented Jan 6, 2024 via email

@workingjubilee
Copy link

People who write OS kernels are rarely non-ambitious people, however, and are unlikely to settle for 32-bit x86 support.

@llenotre
Copy link
Member

llenotre commented Jan 7, 2024

People who write OS kernels are rarely non-ambitious people, however, and are unlikely to settle for 32-bit x86 support.

Indeed, 64 bits support is absolutely on my roadmap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants