public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: mike <localgost@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: linux-m68k@vger.kernel.org, debian-68k@lists.debian.org
Subject: Re: debian installation
Date: Tue, 29 Sep 2009 11:45:27 +0200	[thread overview]
Message-ID: <8259f0250909290245n7328cae1nfe88cf6a2582ebf3@mail.gmail.com> (raw)
In-Reply-To: <8259f0250909280744t69991f25pb6a498775c57482d@mail.gmail.com>

Hm,

Is there a problem with slip?
When i do ifup sl0 i get siocsifflags no such file or directory

-Mike

2009/9/28 mike <localgost@gmail.com>:
> Thanks Finn
>
> depmod -ae did it.
>
> With a bit of luck i can get a dist-upgrade if i can get slip working
> and sharing between my box here.. Think i'll upload this install to
> aminet so i dont loose it when im done with a detailed guide on how to
> configure etc...... This is the most complicated install i've ever
> done
>
> -Mike
>
> 2009/9/28 Finn Thain <fthain@telegraphics.com.au>:
>>
>>
>> On Mon, 28 Sep 2009, mike wrote:
>>
>>> Ok, i've nearly finished my manual install of 3.1r8...
>>> I've got two problems, im missing
>>> /lib/modules/2.4.27-amiga/modules.dep ( does anyone have it handy? )
>>
>> It is generated using the "depmod -ae" command (I think those are the
>> correct arguments...) Normally it is generated at boot time, but I guess
>> it is not run if you stop at the single user run level.
>>
>>>
>>> And a "passwd: Authentication token manipulation error"
>>
>> Sounds familiar but I don't recall what the cause was. Maybe google it.
>>
>> Finn
>>
>>> I've checked the perms of /etc/shadow they are shadow root and correct
>>> rw. so is passwd
>>>
>>> And i can so far only boot into single user mode. But that will work for now.
>>>
>>> -Mike
>>
>

  reply	other threads:[~2009-09-29  9:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  3:28 bogl: don't know screen type 1 mike
2009-08-31 12:06 ` Stephen R Marenka
2009-08-31 12:58   ` mike
2009-08-31 22:11     ` mike
2009-08-31 22:16       ` mike
2009-09-01 15:17         ` Stephen R Marenka
2009-09-03  1:16           ` mike
2009-09-03  1:22             ` mike
2009-09-03  9:50               ` Maxim Kuvyrkov
2009-09-03 16:41                 ` mike
2009-09-11 20:01               ` Kolbjørn Barmen
2009-09-11 20:25                 ` Geert Uytterhoeven
2009-09-12 10:24                 ` fthain
2009-09-04 15:43           ` toolchain, was " Finn Thain
2009-09-05  1:08             ` Stephen R Marenka
2009-09-05  1:57               ` mike
2009-09-05  2:17                 ` mike
2009-09-05  7:08               ` Petr Stehlik
2009-09-05  8:49               ` Ingo Jürgensmann
2009-09-06  5:07               ` Finn Thain
2009-09-05 13:31             ` Maxim Kuvyrkov
2009-09-05 16:00               ` mike
2009-09-06 10:00                 ` Finn Thain
2009-09-06  2:37               ` toolchain Finn Thain
2009-09-06 23:09                 ` toolchain Stephen R Marenka
2009-09-06  5:20               ` toolchain Finn Thain
2009-09-08 13:07                 ` toolchain Finn Thain
2009-09-13  3:38               ` toolchain, was Re: bogl: don't know screen type 1 fthain
2009-09-13  5:01                 ` Maxim Kuvyrkov
2009-09-14 10:37                   ` fthain
2009-09-22  5:11                     ` mike
2009-09-22 13:09                       ` benchmarks, was Re: toolchain Finn Thain
2009-09-22 14:51                         ` mike
2009-09-22 15:08                           ` Geert Uytterhoeven
2009-09-28 14:00                       ` toolchain, was Re: bogl: don't know screen type 1 mike
2009-09-28 14:26                         ` debian installation Finn Thain
2009-09-28 14:44                           ` mike
2009-09-29  9:45                             ` mike [this message]
2009-09-29 22:23                               ` Rolf Anders

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=8259f0250909290245n7328cae1nfe88cf6a2582ebf3@mail.gmail.com \
    --to=localgost@gmail.com \
    --cc=debian-68k@lists.debian.org \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-m68k@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