All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: 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 19:30:33 +0200	[thread overview]
Message-ID: <3CF7B339.3000406@evision-ventures.com> (raw)
In-Reply-To: <200205311951.35809@enzo.bigblue.local>

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?

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.


       reply	other threads:[~2002-05-31 18:29 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 [this message]
2002-05-31 18:53   ` [PATCH] Artop update Vojtech Pavlik
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=3CF7B339.3000406@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=vojtech@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.