From: Keith Owens <kaos@ocs.com.au>
To: Rusty Russell <rusty@linuxcare.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Persistent module storage - modutils design
Date: Thu, 09 Nov 2000 16:21:17 +1100 [thread overview]
Message-ID: <4925.973747277@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 09 Nov 2000 15:52:47 +1100." <20001109045247.BE39A8120@halfway.linuxcare.com.au>
On Thu, 09 Nov 2000 15:52:47 +1100,
Rusty Russell <rusty@linuxcare.com.au> wrote:
>In message <14032.973605093@ocs3.ocs-net> you write:
>> Looks like persistent data has to be stored in /lib/modules/persist (no
>> <version>, see earlier mail).
>
>You need versions: binary data is too prone to change (proven kernel
>history). It's the kernel installer's duty to know which ones can be
>safely linked/copied to the new version.
Not saving persistent data in binary format, so no problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-09 5:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 4:00 Persistent module storage - modutils design Keith Owens
2000-11-07 4:45 ` Keith Owens
2000-11-07 12:45 ` Horst von Brand
2000-11-07 13:30 ` Horst von Brand
2000-11-07 13:51 ` Keith Owens
2000-11-09 4:52 ` Rusty Russell
2000-11-09 5:09 ` H. Peter Anvin
2000-11-09 5:25 ` Keith Owens
2000-11-09 5:21 ` Keith Owens [this message]
2000-11-07 13:55 ` Alan Cox
2000-11-09 12:22 ` Ralf Baechle
2000-11-07 13:33 ` Keith Owens
2000-11-07 14:47 ` Horst von Brand
2000-11-07 15:19 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2000-11-07 16:01 Jesse Pollard
2000-11-07 21:51 ` Keith Owens
2000-11-07 22:30 Jesse Pollard
2000-11-07 22:52 ` Keith Owens
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=4925.973747277@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linuxcare.com.au \
/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.