LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Lars Callenbach" <lars.callenbach@gmx.de>
To: Hans-Peter Jansen <hpj@urpla.net>, alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux device ordering at boot time
Date: Sun, 20 Jan 2008 14:22:50 +0100	[thread overview]
Message-ID: <20080120132250.34100@gmx.net> (raw)
In-Reply-To: <200801201143.23612.hpj@urpla.net>

Hello,

I followed your discussion. I still have a problem. The workaround of Alan works fine from a technical point of view using mkinitramfs. Now the hardware is assigned to the right devices. But I have some commercial software that (somehow) determines the "setup" of the computer. After the mkinitramfs change this setup has changed and the software does not work any more. Unfortunately my previous running image does not work at the moment (same problem, maybe related to "grub"). 

Are there other "simple" workarounds? Are there some simple steps that can be used to change the setup?

>From my point of view the following might be a solution. A policy should define how  information related to kernel functionality and hardware can be determined over a long time period. This can be defined by kernel (and kernel related) developers, software vendors and linux distributors. It can be something similar to "udev should be part of any linux installation and use UUID as id".


Thank you very much for your hints,
   Lars


-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

      reply	other threads:[~2008-01-20 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 18:55 Lars Callenbach
2008-01-19 19:14 ` Oliver Pinter (Pintér Olivér)
2008-01-19 19:41   ` Jan Engelhardt
2008-01-19 23:06 ` Hans-Peter Jansen
2008-01-19 23:48   ` Alan Cox
2008-01-20 10:43     ` Hans-Peter Jansen
2008-01-20 13:22       ` Lars Callenbach [this message]

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=20080120132250.34100@gmx.net \
    --to=lars.callenbach@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: linux device ordering at boot time' \
    /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

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).