Hi!
> Script started on Wed Mar 7 12:22:20 2001
> # mke2fs -Fq /dev/ram0 1440
> mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> # mount /dev/ram0 /mnt
> # ls -la /mnt
> total 0
> # umount /mnt
> # exit
> exit
No "." and ".."? something is definitely wrong here!
--
Philips Velo 1: 1"x4"x8
On Fri, Mar 09, 2001 at 08:23:43PM +0100, [EMAIL PROTECTED] wrote:
> > Andries, comments?
>
> > remount
> >Attempt to change the mount flags of
> >already-mounted file system. This is commonly
> >used to make a readonly file system writeable.
>
> Yes. But maybe "mount flags" is to
> Andries, comments?
> remount
>Attempt to change the mount flags of
>already-mounted file system. This is commonly
>used to make a readonly file system writeable.
Yes. But maybe "mount flags" is too narrow?
It is up to the filesystem what precisely it does.
What about
remount
On Fri, 9 Mar 2001, Alexander Viro wrote:
> On Fri, 9 Mar 2001, Mike Galbraith wrote:
>
> > I think I've figured it out.. at least I've found a way to reproduce
> > the exact errors to the last detail and some pretty nasty corruption
> > to go with it. The operator must help though.. a lot ;-)
>
On Fri, 9 Mar 2001, Mike Galbraith wrote:
> I was generally exercising with 'what can I do wrong' scenarios when I
> noticed some strangness. If you boot a ramdisk root with init=/bin/sh,
> mount a drive, cd to it and exec chroot . /bin/sh and then mount proc,
> proc/mounts shows /dev/root and
On Fri, 9 Mar 2001, Alexander Viro wrote:
> On Fri, 9 Mar 2001, Mike Galbraith wrote:
>
> > I was generally exercising with 'what can I do wrong' scenarios when I
> > noticed some strangness. If you boot a ramdisk root with init=/bin/sh,
> > mount a drive, cd to it and exec chroot . /bin/sh and
On Fri, 9 Mar 2001, Alexander Viro wrote:
>
>
> On Fri, 9 Mar 2001, Mike Galbraith wrote:
>
> > I think I've figured it out.. at least I've found a way to reproduce
> > the exact errors to the last detail and some pretty nasty corruption
> > to go with it. The operator must help though.. a lo
On Fri, 9 Mar 2001, Richard B. Johnson wrote:
> On Fri, 9 Mar 2001, Mike Galbraith wrote:
>
> > On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> >
> > > On Wed, 7 Mar 2001, Mike Galbraith wrote:
> > >
> > > > On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> > > >
> > > > > After attempting to run 2
On Fri, 9 Mar 2001, Mike Galbraith wrote:
> I think I've figured it out.. at least I've found a way to reproduce
> the exact errors to the last detail and some pretty nasty corruption
> to go with it. The operator must help though.. a lot ;-)
>
> If you do mount -o remount /dev/somedisk / thi
On Fri, 9 Mar 2001, Mike Galbraith wrote:
> On Wed, 7 Mar 2001, Richard B. Johnson wrote:
>
> > On Wed, 7 Mar 2001, Mike Galbraith wrote:
> >
> > > On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> > >
> > > > After attempting to run 2.4.2, and killing all my hard disks, I
> > > > have finally got
On Fri, 9 Mar 2001, Mike Galbraith wrote:
> You must exec a shell (or something) chrooted to your mounted harddisk
> to un-busy the old root and then pivot_root/unmount that old root. I
> tested this, and all is well.
This came out a little backassward.. pivot_root then chroot/unmount.
-
To un
On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> On Wed, 7 Mar 2001, Mike Galbraith wrote:
>
> > On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> >
> > > After attempting to run 2.4.2, and killing all my hard disks, I
> > > have finally gotten 2.4.1 back up. There is a continual problem
> > > that
On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> Would you please check your /dev/ram0 and verify that it is:
>
> block special (1/0)
Why zzzt zzt are we now zzt troubleshooting _my_ t system :-)
tilt
-Mike
-
To unsubscribe from this list: send the line "unsubscribe l
On Wed, 7 Mar 2001 [EMAIL PROTECTED] wrote:
>
> > Question. How come you show a lost+found directory in the ramdisk??
> > mke2fs version 1.19 doesn't create one on a ram disk.
> >
> > Script started on Wed Mar 7 12:22:20 2001
> > # mke2fs -Fq /dev/ram0 1440
> > mke2fs 1.19, 13-Jul-2000 for EXT
On Wed, 7 Mar 2001, Mike Galbraith wrote:
> On Wed, 7 Mar 2001, Richard B. Johnson wrote:
>
> > On Wed, 7 Mar 2001, Mike Galbraith wrote:
> >
> > > I'd sweat bullets over system integrity if _I_ got this reply ;-)
> > > Something is seriously amiss.
> >
> > Well now the denial phase sets in. Thi
> Question. How come you show a lost+found directory in the ramdisk??
> mke2fs version 1.19 doesn't create one on a ram disk.
>
> Script started on Wed Mar 7 12:22:20 2001
> # mke2fs -Fq /dev/ram0 1440
> mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> # mount /dev/ram0 /mnt
> # ls -la /mn
On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> On Wed, 7 Mar 2001, Mike Galbraith wrote:
>
> > I'd sweat bullets over system integrity if _I_ got this reply ;-)
> > Something is seriously amiss.
>
> Well now the denial phase sets in. This system has run fine for
> two years. It ran until I tried
On Wed, 7 Mar 2001, Mike Galbraith wrote:
> On Wed, 7 Mar 2001, Richard B. Johnson wrote:
>
> > After attempting to run 2.4.2, and killing all my hard disks, I
> > have finally gotten 2.4.1 back up. There is a continual problem
> > that even exists on 2.4.1, that will show if you execute this.
>
On Wed, 7 Mar 2001, Richard B. Johnson wrote:
> After attempting to run 2.4.2, and killing all my hard disks, I
> have finally gotten 2.4.1 back up. There is a continual problem
> that even exists on 2.4.1, that will show if you execute this.
> However, unmount your hard disks before you execute
After attempting to run 2.4.2, and killing all my hard disks, I
have finally gotten 2.4.1 back up. There is a continual problem
that even exists on 2.4.1, that will show if you execute this.
However, unmount your hard disks before you execute this simple
harmless script.
dd if=/dev/zero of=/de
20 matches
Mail list logo
