From: Frank Kotler <fbkotler@verizon.net>
To: Bodo Giannone <Bodo@Giannone.de>
Cc: linux-assembly@vger.kernel.org
Subject: Re: init.asm - 0.03 (19-Jun-2002) - asmutils 0.18
Date: Thu, 01 May 2008 05:32:09 -0400 [thread overview]
Message-ID: <48198E19.7090605@verizon.net> (raw)
In-Reply-To: <4817406D.5000605@Giannone.de>
Bodo Giannone wrote:
> Hello,
>
> I am the maintainer of BG-Tiny Linux Bootdisk.
Thank you. I downloaded it and tried it. Sure is tiny! Seemed to work
fine. (unlike "a-linux" which hung on me the last time I tried it, IIRC)
> The tiny init version included in asmutils-0.18 (init.asm 0.03,
> 19-Jun-2002) is exactly what I was looking for to integrate into BG-Tiny
> Linux Bootdisk. Unfortunately I am havging some problems I cannot
> resolve myself due to lacking assembler skills.
>
> I want to start /bin/sh on tty1-4 without using getty or login.
> Unfortunately directly after booting I get the following error message:
> "can't access tty, job control turned off". This could mean that init
> does not activate the ttys completely. Is there a possibility to change
> that?
Always a "possibility"! I'm gradually acquiring a few assembly skills...
but I'm not sure what "init" is supposed to do. Quite a difference
between the asmutils "init" and /sbin/init on my system!!! The "init"
you're using comes from Busybox, right?
> The sh I am using is ash from BusyBox 1.3.2. If I try to use sh.asm from
> asmutils-0.18 I only get a segfault.
Hmmm. It seems to work okay for me - that's launching it from my "usual"
shell or from the shell from Busybox (I guess) that I get after booting
your disk... and mounting the partition with asmutils on it - not "from
scratch". How would I see this segfault?
> I am using linux kernel 2.4.36.2 and uClibc 0.9.27 (linked statically).
>
> It would be great if someone had a suggestion.
I'd be willing to attempt to modify the asmutils "init", if I knew what
it needed to do differently. Anyone know where I can find a "newbie's
quickstart guide to init"? Maybe I should look at the Busybox code...
That's not much of a "suggestion". I just wanted to give ya some
encouragement. It "should" be a "possibility" to fix any problems you're
having with asmutils.
Best,
Frank
next prev parent reply other threads:[~2008-05-01 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 15:36 init.asm - 0.03 (19-Jun-2002) - asmutils 0.18 Bodo Giannone
2008-05-01 9:32 ` Frank Kotler [this message]
2008-05-02 12:12 ` Faré
2008-05-02 15:46 ` Bodo Giannone
2008-05-02 20:19 ` Frank Kotler
2008-05-30 20:34 ` Karsten Scheibler
-- strict thread matches above, loose matches on Subject: below --
2008-04-29 16:08 Bodo Giannone
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=48198E19.7090605@verizon.net \
--to=fbkotler@verizon.net \
--cc=Bodo@Giannone.de \
--cc=linux-assembly@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 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).