This is a discussion on duplicate Linux installation within the Linux Operating System forums, part of the Unix Operating Systems category; --> Erik T. wrote: > Hi, > > For a classroom setup, I am asked to install multiple copies of ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Erik T. wrote: > Hi, > > For a classroom setup, I am asked to install multiple copies of Linux > (Fedora Core 3) on the same machines in a classroom. Is there a (easy) > way to duplicate one system to a new partition, without having to > (re)install the complete system? Can I just duplicate the root partition > and modify /etc/fstab of the copied system accordingly? Will there be > network issues (we use dhcp on our network, so I don't think that will > be a problem). Anything else to take into account? > > In short: > step 1. install 1 linux system > step 2. duplicate installed linux system on same machine > ==> How do i go about this? > > tnx, > E.T. Just for info: SchoolLinux thin client solution. http://www.skolelinux.org/portal/ // mm http://www.futuredesktop.org/how2burn.html#mirrors |
| |||
| On 2005-02-08, moma <moma@example.net> wrote: > > SchoolLinux thin client solution. > http://www.skolelinux.org/portal/ This looks more like a distro for users of a linux distro, not for configuring a lab for a class on administering linux. Quote: "Moreover, it eases administration, as you have one server to maintain." But the OP wants his students to maintain one server each. --keith -- kkeller-usenet@wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom see X- headers for PGP signature information |
| |||
| Erik T. wrote: > >> all this begs the question: why are you wanting to create two >> additional "images" of an installation on other partitions? > > It is for a classroom environment, were several (3) different student > groups are being taught the linux principles. To prevent one student > from messing up the system for all groups, each group would use it's own > dedicated linux partition. .... maybe instead of trying to physically protect each users partition from each other, you should be teaching proper system administration and *Nix use. first rule, right, is they shouldnt be logging in as root, so being a normal user, they shouldnt be able to muck up the system TOO much :O teach them the rules of the *Nix road and they'll be better computer users. create a hidden partition which contains a copy of the pristine image of the REAL partition - so if the time every came when something catastrophic happens, you can simply copy the image back over. teach them how to do backups too. -- << http://michaeljtobler.homelinux.com/ >> Do not believe in miracles -- rely on them. |
| |||
| "Erik T." <et@homeplanet.universe> wrote in message news:cuajf7$vjl$1@ikaria.belnet.be... > >> all this begs the question: why are you wanting to create two additional >> "images" of an installation on other partitions? > > It is for a classroom environment, were several (3) different student > groups are being taught the linux principles. To prevent one student from > messing up the system for all groups, each group would use it's own > dedicated linux partition. Ahh. Hmm. What you probably want, then, is not quite what you think. You need chroot cages for an active system, where the chroot cage has a particular deployed implementation of the system. |
| |||
| Nico Kadel-Garcia wrote: > "Erik T." <et@homeplanet.universe> wrote in message >> >>> all this begs the question: why are you wanting to create two additional >>> "images" of an installation on other partitions? >> >> It is for a classroom environment, were several (3) different student >> groups are being taught the linux principles. To prevent one student from >> messing up the system for all groups, each group would use it's own >> dedicated linux partition. > > Ahh. Hmm. What you probably want, then, is not quite what you think. You > need chroot cages for an active system, where the chroot cage has a > particular deployed implementation of the system. .... might be excessive, but SELinux might be applicable. -- << http://michaeljtobler.homelinux.com/ >> Adler's Distinction: Language is all that separates us from the lower animals, and from the bureaucrats. |
| |||
| Erik T. wrote: > It is for a classroom environment, were several (3) different student > groups are being taught the linux principles. To prevent one student from > messing up the system for all groups, each group would use it's own > dedicated linux partition. Use something like systemimager to keep the images on a server and install them on the student machine at need. Update the image on the server when the student logs off. You could also keep backups so that if they hopelessly hose themselves you can roll them back. -- John Hasler john@dhh.gt.org Dancing Horse Hill Elmwood, WI USA |
| |||
| John Hasler wrote: > Erik T. wrote: > >>It is for a classroom environment, were several (3) different student >>groups are being taught the linux principles. To prevent one student from >>messing up the system for all groups, each group would use it's own >>dedicated linux partition. > > > Use something like systemimager to keep the images on a server and install > them on the student machine at need. Update the image on the server when > the student logs off. You could also keep backups so that if they > hopelessly hose themselves you can roll them back. I will give systemimager a try. Skimming through the docs, it looks very promising! tnx! |
| |||
| > ... maybe instead of trying to physically protect each > users partition from each other, you should be teaching > proper system administration and *Nix use. first rule, > right, is they shouldnt be logging in as root, so being > a normal user, they shouldnt be able to muck up the > system TOO much :O yes, I know that. But I'm not the teacher classroom as student-proof as possible. And on the other hand, to do system administration, sometimes you need root access, and accidents tend to happen (learn from your mistakes). > teach them the rules of the *Nix road and they'll be > better computer users. I agree. > create a hidden partition which contains a copy of the > pristine image of the REAL partition - so if the time > every came when something catastrophic happens, you > can simply copy the image back over. Will do (as long as disk space permits) tnx! |
| ||||
| Erik T. wrote: >> ... maybe instead of trying to physically protect each >> users partition from each other, you should be teaching >> proper system administration and *Nix use. first rule, >> right, is they shouldnt be logging in as root, so being >> a normal user, they shouldnt be able to muck up the >> system TOO much :O > > yes, I know that. But I'm not the teacher oops. i didnt realize that [snip] >> create a hidden partition which contains a copy of the >> pristine image of the REAL partition - so if the time >> every came when something catastrophic happens, you >> can simply copy the image back over. > > Will do (as long as disk space permits) .... that will take a lot less space than have THREE images -- << http://michaeljtobler.homelinux.com/ >> Remember: Silly is a state of Mind, Stupid is a way of Life. - Dave Butler |