public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] 2.5.18 IDE 73
Date: Thu, 30 May 2002 16:01:09 +0200	[thread overview]
Message-ID: <3CF630A5.40002@evision-ventures.com> (raw)
In-Reply-To: <UTC200205301443.g4UEhvn20167.aeb@smtp.cwi.nl>

Andries.Brouwer@cwi.nl wrote:
>     > Of course - improvements are always welcome.
>     > (But I try to be slightly more careful than you are.
>     > Util-linux runs on all libc's and all kernels, from libc4 to glibc2
>     > and from 0.99 to 2.5. So, changes must be compatible.)
> 
>     Having them compatible acroess an insane range of kernels
>     is a nice but futile exercise.
>     Perhaps this partly explains why:
> 
>     1. util-linux doesn't cover half of the system utilities needed on
>         a sanely actual Linux system.
> 
>     2. The Linux vendors have to apply insane number of patches to it
>         util it's moderately usable.
> 
> If you do the kernel ATA stuff, I'll take care of util-linux.

Well that's actually a deal :-).

> (Does it need more utilities? Probably those are in some other package.
> Sometimes stuff is added, but not very often. However, your suggestions
> are welcome.
> Do the vendors add patches? Half of that is vendor extensions, that is
> their business. Half of that is their stupidity. They blindly copy the
> patches other vendors apply "it is a patch - must be an improvement";
> sometimes I have to reject the same buggy patch more than a dozen times.
> When I ask for the reason of a patch, they don't know themselves.)

Well somehow I have partly to agree. But however having a way to
exclude network devices from mounting during mount -a is *very* usefull,
becouse failing NFS servers will sometines prohibit your watchdog
triggered reboot to happen for example!

Or not doing swapon twice and beeing silent about it - just good
UNIX habit the user requested it to go on - well it's on, so all
is fine, no error in this.

I can stuff together what I think is usefull however...

> 
>     >     No need to invent here. No need to do the book keeping in kernel.
>     > 
>     > Some need. Things like mount-by-label want to know what partitions
>     > exist in order to look at the labels on each.
>     > Yes, we really need a list of disk-like devices.
>     > The gendisk chain.
> 
>     No I don't see that point. Data which has to be persistant across
>     reboots is simple data which has to reside on disk. That's the
>     way it is in UNIX (PalmOS to name an example).
> 
> Maybe you never heard of mount-by-label?
> 
> Andries


Urhg? I did of course hear about them!


~# ssh kozaczek
root@kozaczek's password:
Last login: Thu May 30 14:37:32 2002 from 10.0.0.1
cd [root@kozaczek root]# cd /etc
[root@kozaczek etc]# cat fstab
LABEL=/                 /                       ext3    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
[root@kozaczek etc]#


Hmm I didn't check whatever they can be used on swap partitions too.
If not I will fix it right away.


  reply	other threads:[~2002-05-30 14:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30 14:43 [PATCH] 2.5.18 IDE 73 Andries.Brouwer
2002-05-30 14:01 ` Martin Dalecki [this message]
2002-05-30 15:09   ` Rene Rebe
2002-05-31 13:25     ` Denis Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2002-05-30 15:56 Andries.Brouwer
2002-05-30 12:35 Bartlomiej Zolnierkiewicz
2002-05-30  0:19 Andries.Brouwer
2002-05-30 13:02 ` Martin Dalecki
2002-05-30 15:32   ` Alan Cox
2002-05-30 13:54     ` Martin Dalecki
2002-05-30 15:05       ` Tomas Szepe
2002-05-30 15:13       ` Rene Rebe
2002-05-30 15:39       ` Wichert Akkerman
2002-05-30 16:13       ` Alan Cox
2002-05-30 14:20         ` Martin Dalecki
2002-05-30 15:31           ` Linus Torvalds
2002-05-30 18:55             ` Martin Dalecki
2002-05-30 15:25         ` Linus Torvalds
2002-05-29 23:40 Andries.Brouwer
2002-05-29 22:53 ` Martin Dalecki
2002-05-29 18:16 Andries.Brouwer
2002-05-29 18:07 Andries.Brouwer
2002-05-29 21:57 ` Martin Dalecki
2002-05-29 13:59 Gerald Champagne
2002-05-29 13:03 ` Martin Dalecki
2002-05-29 14:26   ` Gerald Champagne
2002-05-29 14:35   ` Russell King
2002-05-29 13:40     ` Martin Dalecki
2002-05-29 16:33   ` Vojtech Pavlik
2002-05-29 15:46     ` Martin Dalecki
2002-05-29 18:47       ` Alan Cox
2002-05-30  8:48         ` David Woodhouse
2002-05-30 12:22           ` Martin Dalecki
2002-05-29 17:55     ` Alan Cox
2002-05-29 17:01       ` Vojtech Pavlik
2002-05-29 16:05         ` Martin Dalecki
2002-05-29 17:05           ` Vojtech Pavlik
2002-05-29 18:43         ` Alan Cox
2002-05-25  2:02 Linux-2.5.18 Linus Torvalds
2002-05-29 12:11 ` [PATCH] 2.5.18 IDE 73 Martin Dalecki
2002-05-29 12:58   ` Zwane Mwaikambo
2002-05-29 12:52     ` Martin Dalecki

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=3CF630A5.40002@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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