WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Norestore restores anyway?  (Read 1967 times)

Offline smilebot

  • Newbie
  • *
  • Posts: 10
Norestore restores anyway?
« on: July 31, 2010, 06:36:19 PM »
Every boot, the contents of /mnt/hda1/home/tc/ are being copied to /home/tc/ . If I understand correctly, /home is in RAM.

I don't see a point to having user documents in hda1/home/tc/ copied to RAM, but maybe there is one.

My menu.lst includes: kernel /boot/bzImage quiet norestore opt=hda1 home=hda1 tce=hda1

filetool.lst does not contain any mention of home.

How can I prevent RAM from being populated with user documents that live on hda1?
All boundaries are for practical purposes only

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Norestore restores anyway?
« Reply #1 on: July 31, 2010, 06:52:11 PM »
Your opt and home boot options are re-defining their location to be on the hard disk.
Home is not being copied, it is being mounted.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Norestore restores anyway?
« Reply #2 on: July 31, 2010, 07:01:57 PM »
Here is an easy way to test that:
Code: [Select]
touch /home/tc/dirtest
ls -l /mnt/hda1/home/tc/dirtest
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline smilebot

  • Newbie
  • *
  • Posts: 10
Re: Norestore restores anyway?
« Reply #3 on: July 31, 2010, 07:29:24 PM »
Thank you!
All boundaries are for practical purposes only