mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
	Vojtech Pavlik <vojtech@suse.cz>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	Andries.Brouwer@cwi.nl
Subject: Re: [PATCH] Artop update
Date: Fri, 31 May 2002 20:53:34 +0200	[thread overview]
Message-ID: <20020531205334.C24455@ucw.cz> (raw)
In-Reply-To: <200205311951.35809@enzo.bigblue.local> <3CF7B339.3000406@evision-ventures.com>

On Fri, May 31, 2002 at 07:30:33PM +0200, Martin Dalecki wrote:
> Franz Sirl wrote:
> > Hi,
> > 
> > finally I was able to test the new driver and except for the "return 0 instead 
> > of dev-irq" typo all was fine. I added a few minor changes based on the 
> > discussion with Vojtech though.
> 
> Hey cool!
> 
> > The hunk to main.c is needed to be able to boot with DEVFS enabled.
> 
> Better just don't do devfs :-). But anyway...
> 
> Well I'm planing to add kernel version tagging of fstab line enties
> to util-linux. This seems to be the only way to make major/minor
> transitions (and the more I think about it the more I'm convinced
> that they will be unevitable at some not so distant point in time!)
> 
> Something along the lines of:
> 
> cat /etc/fstab:
> 
> /dev/hdc                /                       ext3    v2.4,defaults    1 1
> /dev/sda1 
>          /                       ext3    v2.5,defaults    1 1
> LABEL=/boot             /boot                   ext3    defaults        1 2
> /dev/fd0                /mnt/floppy             auto    noauto,owner    0 0
> # /dev/loop1            /mnt/1                  auto    noauto,owner    0 0
> # /dev/loop2            /mnt/2                  auto    noauto,owner    0 0
> none                    /proc                   proc    defaults        0 0
> none                    /tmp                    tmpfs   defaults        0 0
> none                    /dev/pts                devpts  gid=5,mode=620  0 0
> /dev/hda6               swap                    swap    defaults        0 0
> 
> 
> Would be *very* convenient for this purpose and solve 99.9999% percent
> of portability problems. Well the above syntax may be the esiest to
> imeplement however the below syntax would be perhaps more palatable:
> 
> 2.5:/dev/sda1 
> 		/		ext3 ....
> 
> Opinnions?

I don't like this much - while it solves a setup where you use both
kernels, it isn't solving a 2.4->2.5 transition for not-really-skilled
users. I think Linus's way is the best here - provide both /dev/sda, ...
and provide also major/minor aliases (which will go away later) as
/dev/hd*

> perhaps a similar adjustments would be required for the kernel root parameter of 
> course.
> 
> With something along
> root=2.5:/dev/sda1,2.4:/dev/hdc
> one could be living with... The respecive kernel would just pick the entry
> which is matching it's version and be fine.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-05-31 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200205311951.35809@enzo.bigblue.local>
2002-05-31 17:30 ` Martin Dalecki
2002-05-31 18:53   ` Vojtech Pavlik [this message]
2002-05-31 18:55   ` Franz Sirl

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=20020531205334.C24455@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®