Re: IDE backup on single host (was: Re: Software backup)
> > Ingenious. :b > > > > Does it work reliably with devfs? (So that devices don't magically > > reappear after deletion, for example)? > > I can hear sarcasm in your words, Not at all - except towards my own stupidity for not even thinking of such a simple solution. :) The follow-up question was just that does removing and recreating the device files work OK with devfs - do they stay deleted? I.e. when does devfs(d) create the devices? On startup only, "on demand" or does it poll through them periodically? - Jarno
Re: IDE backup on single host (was: Re: Software backup)
On Thu, Oct 24, 2002 at 11:15:05PM +0300, Jarno Elonen wrote: > > > Does anyone know any way to make this more difficult without introducing > > > a remote host? Are there, for example, any Linux kernel options for > > > "device access passwords" or such? > > > > Maybe removing the appropriate /dev/hd* entries after backup, and > > recreating them just before backup with mknod. > > Ingenious. :b > > Does it work reliably with devfs? (So that devices don't magically reappear > after deletion, for example)? I can hear sarcasm in your words, but what was the purpose of my answer is to make accidental removal of your backups on a spare hard drive less probable. It doesn't mean you can't delete them if you really want, and I doubt if there is an easy software method to do it. And yes, it doesn't apply to devfs, but using devfs is not obligatory :) What's your suggestion, anyway? Marcin
Re: IDE backup on single host (was: Re: Software backup)
> > Does anyone know any way to make this more difficult without introducing > > a remote host? Are there, for example, any Linux kernel options for > > "device access passwords" or such? > > Maybe removing the appropriate /dev/hd* entries after backup, and > recreating them just before backup with mknod. Ingenious. :b Does it work reliably with devfs? (So that devices don't magically reappear after deletion, for example)? - Jarno
Re: IDE backup on single host (was: Re: Software backup)
> > Ingenious. :b > > > > Does it work reliably with devfs? (So that devices don't magically > > reappear after deletion, for example)? > > I can hear sarcasm in your words, Not at all - except towards my own stupidity for not even thinking of such a simple solution. :) The follow-up question was just that does removing and recreating the device files work OK with devfs - do they stay deleted? I.e. when does devfs(d) create the devices? On startup only, "on demand" or does it poll through them periodically? - Jarno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE backup on single host (was: Re: Software backup)
> > Does anyone know any way to make this more difficult without introducing > > a remote host? Are there, for example, any Linux kernel options for > > "device access passwords" or such? > > Maybe removing the appropriate /dev/hd* entries after backup, and > recreating them just before backup with mknod. Ingenious. :b Does it work reliably with devfs? (So that devices don't magically reappear after deletion, for example)? - Jarno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE backup on single host (was: Re: Software backup)
On Thu, Oct 24, 2002 at 11:15:05PM +0300, Jarno Elonen wrote: > > > Does anyone know any way to make this more difficult without introducing > > > a remote host? Are there, for example, any Linux kernel options for > > > "device access passwords" or such? > > > > Maybe removing the appropriate /dev/hd* entries after backup, and > > recreating them just before backup with mknod. > > Ingenious. :b > > Does it work reliably with devfs? (So that devices don't magically reappear > after deletion, for example)? I can hear sarcasm in your words, but what was the purpose of my answer is to make accidental removal of your backups on a spare hard drive less probable. It doesn't mean you can't delete them if you really want, and I doubt if there is an easy software method to do it. And yes, it doesn't apply to devfs, but using devfs is not obligatory :) What's your suggestion, anyway? Marcin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE backup on single host (was: Re: Software backup)
On Thu, Oct 24, 2002 at 11:30:19AM +0300, Jarno Elonen wrote: > Does anyone know any way to make this more difficult without introducing a > remote host? Are there, for example, any Linux kernel options for "device > access passwords" or such? Maybe removing the appropriate /dev/hd* entries after backup, and recreating them just before backup with mknod. Marcin
Re: IDE backup on single host (was: Re: Software backup)
On Thu, Oct 24, 2002 at 11:30:19AM +0300, Jarno Elonen wrote: > Does anyone know any way to make this more difficult without introducing a > remote host? Are there, for example, any Linux kernel options for "device > access passwords" or such? Maybe removing the appropriate /dev/hd* entries after backup, and recreating them just before backup with mknod. Marcin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
IDE backup on single host (was: Re: Software backup)
> We're using rsync to mirror a hot drive in our main server to a cold drive > (one that is only mounted when backing up, and is briefly mounted read only > for per file restoration). ...which reminds me of a related problem of mine. On my own system, I'm using a fixed spare IDE hard drive for backups. Every night, Backup2l automatically mounts it, makes an incremental backup and then unmount it again. While not a remote backup scheme, this protects the system from most common destructive mistakes and malfunctions like "sudo rm -rf * - whoops, What whas I thinking?!!" or software that goes wild and does similar things. But: all the backups can be erased with one simple line: "dd if=/dev/zero of=/dev/". :( Does anyone know any way to make this more difficult without introducing a remote host? Are there, for example, any Linux kernel options for "device access passwords" or such? - Jarno
IDE backup on single host (was: Re: Software backup)
> We're using rsync to mirror a hot drive in our main server to a cold drive > (one that is only mounted when backing up, and is briefly mounted read only > for per file restoration). ...which reminds me of a related problem of mine. On my own system, I'm using a fixed spare IDE hard drive for backups. Every night, Backup2l automatically mounts it, makes an incremental backup and then unmount it again. While not a remote backup scheme, this protects the system from most common destructive mistakes and malfunctions like "sudo rm -rf * - whoops, What whas I thinking?!!" or software that goes wild and does similar things. But: all the backups can be erased with one simple line: "dd if=/dev/zero of=/dev/". :( Does anyone know any way to make this more difficult without introducing a remote host? Are there, for example, any Linux kernel options for "device access passwords" or such? - Jarno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
