From: Sean Hinchee <henesy.dev@gmail.com>
To: 9front@9front.org
Subject: Fwd: Linuxemu
Date: Mon, 24 Nov 2014 09:37:50 -0600 [thread overview]
Message-ID: <547350CE.8060708@gmail.com> (raw)
In-Reply-To: <546D448A.70903@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
I have no idea how useful this is for anyone, but I was told by some
folks on #cat-v that this should be e-mailed out. Linuxemu3 breaks on
new kernels/linux trees. Here's the fix for that error and some other
little tidbits left over from experimentation.
-------- Forwarded Message --------
Subject: Linuxemu, FATAL: kernel too old
Date: Wed, 19 Nov 2014 19:31:54 -0600
From: Sean Hinchee <henesy.dev@gmail.com>
To: cinap_lenrek@gmx.de
Error: FATAL: kernel too old
Debug: http://okturing.com/src/2478/body
Debug Command: 'linux -dd -r mroot/ /bin/bash -i'
FS Tree:
http://download.proxmox.com/appliances/system/debian-7.0-standard_7.0-2_i386.tar.gz
Notes: Does not crash, exits with an error.
Fix: Debian 7.0 uses kernel 3.2.x, changed
Kernel Reference:
https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html
<cinap_lenrek> open linuxemu3/proc.c
<cinap_lenrek> strncpy(p->release, "2.6.11", 65);
<cinap_lenrek> and change this arround to something more *modern*
<cinap_lenrek> in sys_uname()
Changed using the above to "3.2.1" then 'mk; mk install'
Characters double themselves, use 'vt'.
Aptitude can update itself, but not install anything:
https://wiki.debian.org/SourcesList#Example_sources.list_for_Debian_7_.22Wheezy.22
apt-get update succeeds after sources.list is changed from default to ^ and you run:
apt-get autoclean; apt-get clean; apt-get update
apt-get install fails on:
E: Couldn't determine free space in/var/cache/apt/archives/ - statvfs
(38: Function not implemented)
The above error was found in some Linux From Scratch threads relating to
a problem in glibc, no definitive answer has yet been found.
If apt-get update is run and there are no changes from the current
state, an error returns:
GPG Error: The following signatures were invalid: NODATA 1 NODATA 2
Ping fails on: icmp open socket: Invalid argument
[-- Attachment #2: Type: text/html, Size: 3717 bytes --]
parent reply other threads:[~2014-11-24 15:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <546D448A.70903@gmail.com>]
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=547350CE.8060708@gmail.com \
--to=henesy.dev@gmail.com \
--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).