Ilya Martynov wrote:
> It is called read-only because user programs that work at level of
> files and directories can't write on mounted filesystem. Tools that
> mount filesystem work on lower level.
I have visited the web page you pointed out the other day; I have no
conclusion (neither did they,
Ilya Martynov wrote:
> It is called read-only because user programs that work at level of
> files and directories can't write on mounted filesystem. Tools that
> mount filesystem work on lower level.
I guess the guys at www.reiserfs.org should create a better startup
message; currently, it says (a
>> I'm not sure about reiserfs but at least ext3 does replays logs on
>> read only filesystem. I'm going to check if it so with reiserfs.
>>
>> Here http://kt.zork.net/kernel-traffic/kt20010119_103.html#1 you can
>> find some discussion why on jornaling filesystems log can be replayed
>> even if
Ilya Martynov wrote:
> I'm not sure about reiserfs but at least ext3 does replays logs on
> read only filesystem. I'm going to check if it so with reiserfs.
>
> Here http://kt.zork.net/kernel-traffic/kt20010119_103.html#1 you can
> find some discussion why on jornaling filesystems log can be repla
Here is what I did step by step on 2 separate computers to change over to
reiserfs.
First of all you must have a partition large enough to hold everything. Lets
say you have 4 partitions and part4 is big enough to hold everything.
Lets say the 4 partitions are mounted as /boot, swap, /, /var. Y
>> I'm sorry but what is the problem with replaying log on read only
>> filesystem? It should be readonly only for user's programs that use
>> mounted filesystem.
OD> Well, my understanding is that if you have a read-only filesytem, then
OD> you wouldn't be able to write anyting to it. Having a t
Andrew Pollock wrote:
> Using LILO?
I use Grub.
Thanks for the info, I'm going to lookup the man page for the identical
feature.
Oki
Ilya Martynov wrote:
> I'm sorry but what is the problem with replaying log on read only
> filesystem? It should be readonly only for user's programs that use
> mounted filesystem.
Well, my understanding is that if you have a read-only filesytem, then
you wouldn't be able to write anyting to it. H
On Wed, 2 May 2001, Oki DZ wrote:
> William Leese wrote:
> > oh, i didn't backup /proc and /tmp because tar spewed out a few error
> > messages. but from what i can recall /proc is created by the kernel(?) and
> > for /tmp the directory just needs to be recreated, correct?
>
> You'd need to recre
OD> BTW, I have all my partitions running on reiserfs; problem is, when the
OD> system booted up, / partition is always mounted read-only, so that the
OD> transaction log is always replayed on, well, read-only filesystem. I
OD> have done update-rc.d -f checkfs.sh remove, so that fsck wouldn't be
O
William Leese wrote:
> oh, i didn't backup /proc and /tmp because tar spewed out a few error
> messages. but from what i can recall /proc is created by the kernel(?) and
> for /tmp the directory just needs to be recreated, correct?
You'd need to recreate the /proc directory; the system uses it as
On Wed, May 02, 2001 at 09:06:04AM +1000, Brian May wrote:
> > "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
>
> Ethan> cp -R is a horribly wrong thing to use for this task, it
> Ethan> will destroy symlinks and hardlinks. turning them into
> Ethan> duplicate files. use cpi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> hdparms and reiser, havent done this yet myself. I would think it would
> work fine though. I dont think hdparms cares whats actually on the disk.
I've been doing hdoarm -d 1 on my disk holding a couple of heavily-used
ReiserFS partitions. No troub
> $ which tar
> /bin/tar
> $ ldd /bin/tar
> /lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0x40015000)
> libc.so.6 => /lib/libc.so.6 (0x4001f000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
>
> Debian is probably similar, so most likely /lib and its contents w
William Leese wrote:
>
> > > 3) rm -rf /usr, /lib.. etc after mounting the vfat partition which also
> > > contains a copy of /sbin and /bin untarred.
> >
> > Hmmm... aren't there important things in /lib, namely libc?
>
> would that be needed for running mkreiserfs, tar and perhaps a few other g
> > 3) rm -rf /usr, /lib.. etc after mounting the vfat partition which also
> > contains a copy of /sbin and /bin untarred.
>
> Hmmm... aren't there important things in /lib, namely libc?
would that be needed for running mkreiserfs, tar and perhaps a few other gnu
tools? because thats all that is
William Leese wrote:
> also, is it 'safe' to use hdparm when having reiserfs partitions?
If you used it with ext2 partitions, I don't see why using it with
reiserfs would be a problem. It's all disk access.
> I'll be doing the following:
>
> 1) backup each dir and its subdirs with tar (tar cf /
> "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
Ethan> cp -R is a horribly wrong thing to use for this task, it
Ethan> will destroy symlinks and hardlinks. turning them into
Ethan> duplicate files. use cpio or tar.
or
cp -a
will preserve everything, too, I think. I often
On Tue, May 01, 2001 at 01:54:58PM -0400, Ron Bettle wrote:
> You will need the reiserFS utils, get these rom reisers site.
>
> Its not difficult more time consuming than anything. What needs to happen is
> this. Say your /usr is it own partition. You need a 'spare' partition that is
> as big as
On Tue, May 01, 2001 at 03:38:54PM -0400, Ron Bettle wrote:
> Sounds fool proof(your plan that is).
This depends on how much disk spaces you have.
If you do not install X programs, 500MB is sufficient for Linux.
I would rather make 500MB worth extra space by reorganizing current
system and do no
On Tuesday 01 May 2001 21:38, Ron Bettle wrote:
> Sounds fool proof(your plan that is).
>
> hdparms and reiser, havent done this yet myself. I would think it would
> work fine though. I dont think hdparms cares whats actually on the disk.
i think the same, but better safe than sorry :)
> heh rm -
Sounds fool proof(your plan that is).
hdparms and reiser, havent done this yet myself. I would think it would work
fine though. I dont think hdparms cares whats actually on the disk.
heh rm -fr the directories before copyin, even with a tar backup would scare me
=). Hope it works for you let us
http://www.reiserfs.com/install.html
William Leese <[EMAIL PROTECTED]> wrote:
I'm considering moving my partitions to ReiserFS. I'll not be using lilo,
instead I'm using boot floppies. So, I can safely move all my partitions over
to ReiserFS.
I'm aware that I have to compile a kernel
> not exactly efficient, but simple enough to not make any large mistakes..
> (i hope, but if something goes seriously wrong i still have everything in
> tarballs on the vfat partition)
oh, i didn't backup /proc and /tmp because tar spewed out a few error
messages. but from what i can recall /pro
On Tuesday 01 May 2001 19:54, Ron Bettle wrote:
> You will need the reiserFS utils, get these rom reisers site.
is there any reason why i should not use the packaged reiserFS utils in Sid?
also, is it 'safe' to use hdparm when having reiserfs partitions?
I'll be doing the following:
1) backup e
You will need the reiserFS utils, get these rom reisers site.
Its not difficult more time consuming than anything. What needs to happen is
this. Say your /usr is it own partition. You need a 'spare' partition that is
as big as /usr. Then you unmount the 'spare' format it as reiser (mkreiserfs
/
I'm considering moving my partitions to ReiserFS. I'll not be using lilo,
instead I'm using boot floppies. So, I can safely move all my partitions over
to ReiserFS.
I'm aware that I have to compile a kernel with ReiserFS support but apart
from that I have no clue how to create the ReiserFS par
27 matches
Mail list logo
