[Dorset] Writing a Boot sector to a CD
Hi, Things have moved on with the discovery that unlike other bigger Live CDs, Tiny Core unmounts the CD after booting. This means that all we have to do is to write our additional files to the disc alongside the normal files produced by the TinyCore tools. We can then mount the disc again from the running system and read off all our files. There is only one problem. I can stick a CD in the hole and open it using any decent burning program, such as k3b or Brasero on Linux or Nero or Roxio on Winblows. I can then add my files and burn a new image. What I don't know is how to copy the boot sector of the original image. If I copy the CD in its entirety, that comes as part of the deal. If I build a new image as described above, all I get is a data CD. Does anyone know how this is done? Terry Coles -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Adding files to a Live Disc, separate to the core image
On Wednesday 08 Dec 2010, Ralph Corderoy wrote: > Earlier you were talking about having your files outside the TC ISO. Is > that because you want to ship the big ISO once and then ship your little > files often? Or do you want to append a new set of your files to the > end of an existing CD with the TC ISO plus old sets of your files > already on it? We want to do the former, but allow others to build a CD from the sum of the parts. > If neither of these then what Sean suggests seems easiest. Produce your > own TC ISO that includes your things. > > http://wiki.tinycorelinux.com/Remastering > > (They seem confused towards the end. The mkisofs is one logical line, > as they say, but someone's saying there were slases on their own, they > would of been, or should have been, backslashes to say that the physical > line is continued logically on the next one.) There's a GUI tool called 'ezremaster' (http://wiki.tinycorelinux.com/Remastering+with+ezremaster) which makes the whole job fairly straightforward. The problem is that it takes a while to fill in all the blanks, just to end up with almost the same thing each time. Also, it would be nice to stitch the scripts into the ISO 'off line' so to speak. -- Terry Coles 64 bit computing with Kubuntu Linux -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Adding files to a Live Disc, separate to the core image
On Wednesday 08 Dec 2010, Sean Gibbins wrote: > On 08/12/10 17:36, Terry Coles wrote: > > I think I asked the wrong question (or the right question asked wrongly). > > What we really want to do is to burn a disc that consists of the TC ISO > > (which will rarely change) and add some additional scripts/config files > > (which will change frequently) at the same time. > > So presumably one possible solution is that you simply re-author the ISO > image for each updated version? That's how we were thinking when started this. The trouble is that authoring the ISO for TC is a bit convoluted and we don't want to do it every time we change a script. We also want it to be posible for others to add the modified scripts using the TC core ISO as the starting point. These 'others' may only have access to WinBlows, so we really need a simple way of creating an image by somehow drilling into the core ISO. > Or am I missing the point again? Nope, I just don't explain myself very well. What we want to end up with is an almost bog-standard TC Live disk that includes those packages (extensions in TC speak that we need by default. The half a dozen or so scripts will then be included somehow so that they run when the Live disc boots. We will then harvest the O/Ps for processing on a separate machine. -- Terry Coles 64 bit computing with Kubuntu Linux -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Adding files to a Live Disc, separate to the core image
Hi Terry, > I think I asked the wrong question (or the right question asked > wrongly). What we really want to do is to burn a disc that consists > of the TC ISO (which will rarely change) and add some additional > scripts/config files (which will change frequently) at the same time. Earlier you were talking about having your files outside the TC ISO. Is that because you want to ship the big ISO once and then ship your little files often? Or do you want to append a new set of your files to the end of an existing CD with the TC ISO plus old sets of your files already on it? If neither of these then what Sean suggests seems easiest. Produce your own TC ISO that includes your things. http://wiki.tinycorelinux.com/Remastering (They seem confused towards the end. The mkisofs is one logical line, as they say, but someone's saying there were slases on their own, they would of been, or should have been, backslashes to say that the physical line is continued logically on the next one.) Cheers, Ralph. -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Adding files to a Live Disc, separate to the core image
On 08/12/10 17:36, Terry Coles wrote: > I think I asked the wrong question (or the right question asked wrongly). > What we really want to do is to burn a disc that consists of the TC ISO > (which > will rarely change) and add some additional scripts/config files (which will > change frequently) at the same time. So presumably one possible solution is that you simply re-author the ISO image for each updated version? Once you establish a method it shouldn't be too difficult to set aside a directory for your scripts, which is updated while the OS remains untouched. As long as the scripts use established static names, tinkering with the OS portion would be largely unnecessary. Or am I missing the point again? ;-) Sean -- music, film, comics, books, rants and drivel: www.funkygibbins.me.uk -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Adding files to a Live Disc, separate to the core image
On Wednesday 08 Dec 2010, John Carlyle-Clarke wrote: > On 08/12/10 11:41, StarLion wrote: > >> 1. Is it possible to physically burn an ISO that consists of the ISO > >> created in Tiny Core, plus the additional files added later? If so, > >> how is it done? > > > > Gnome's Brasero writer has the option to burn an image to a physical > > medium, but leave it open to add more things to the compilation after > > the image is burnt. > > How one goes about adding them afterwards I'm not certain though, as > > I've never needed to do it myself. > > Puppy linux has this ability. It can boot off a live CD, and on shut > down all changes made to the file system are written to an incremental > diff file that is then burned on to the end of the CD if it is not > fixed. Those files can also be written onto a USB stick if booting from > USB. You can also specify any arbitrary location, e.g. the hard disc of > the machine you're working on. I think I asked the wrong question (or the right question asked wrongly). What we really want to do is to burn a disc that consists of the TC ISO (which will rarely change) and add some additional scripts/config files (which will change frequently) at the same time. -- Terry Coles 64 bit computing with Kubuntu Linux -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Adding files to a Live Disc, separate to the core image
On 08/12/10 11:41, StarLion wrote: 1. Is it possible to physically burn an ISO that consists of the ISO created in Tiny Core, plus the additional files added later? If so, how is it done? Gnome's Brasero writer has the option to burn an image to a physical medium, but leave it open to add more things to the compilation after the image is burnt. How one goes about adding them afterwards I'm not certain though, as I've never needed to do it myself. Puppy linux has this ability. It can boot off a live CD, and on shut down all changes made to the file system are written to an incremental diff file that is then burned on to the end of the CD if it is not fixed. Those files can also be written onto a USB stick if booting from USB. You can also specify any arbitrary location, e.g. the hard disc of the machine you're working on. -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Adding files to a Live Disc, separate to the core image
> 1. Is it possible to physically burn an ISO that consists of the ISO created > in > Tiny Core, plus the additional files added later? If so, how is it done? Gnome's Brasero writer has the option to burn an image to a physical medium, but leave it open to add more things to the compilation after the image is burnt. How one goes about adding them afterwards I'm not certain though, as I've never needed to do it myself. -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] My Identity
Hi Terry, On 8 December 2010 10:05, d-...@hadrian-way.co.uk wrote: > I just realised that when I post through Webmail from work, you have no > idea who > I am ;-( > Some of us guessed ;-) > > I've just added a Sig. > > Terry Coles > -- > Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 > Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ > How to Report Bugs Effectively: http://goo.gl/4Xue -- best regards, Victor Churchill, Bournemouth -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
[Dorset] My Identity
I just realised that when I post through Webmail from work, you have no idea who I am ;-( I've just added a Sig. Terry Coles -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
[Dorset] Adding files to a Live Disc, separate to the core image
Hi, My experiments with Tiny Core are progressing reasonably well, but I have a more generic query about Live Discs in general and creating ISOs in particular. Ideally, what we would like to do is to create a core distro, based on Tiny Core, but with some custom scripts and apps included as part of the distro. So far so good; this is exactly what Tiny Core is designed to do and although I haven't quite sorted out the wrinkles, I'm getting there. However, we don't want to change the core distro very often; maybe just provide updates from time to time as the packages in Tiny Core itself get updated. Again, Tiny Core provides the tools to do that too. However, one thing we would like to do then is to include some files that will be in a separate directory outside of the loop mounted filesystem created by the live system and then access them from within the running code. In other words, we want to be able to build a core ISO with additional files that are not part of the main system. The questions therefore are: 1. Is it possible to physically burn an ISO that consists of the ISO created in Tiny Core, plus the additional files added later? If so, how is it done? 2. Is it possible for a running Live distro to access an area of the Live Disc that isn't mounted as a loop device? Or is there another way? -- Next meeting: The Broadway, Bournemouth, Tuesday 2010-12-14 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue