3.7.10-antix.5-486-smp
Debian GNU/Linux 7 (wheezy)
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
CPU MHz: 3201.000
On-line CPU(s) list: 0-3
Ram 2.86G
1. System is booted into the Live CD environment from a DVD drive."AntiX Full"
2. System has no hard drive, or USB stick functionality to use for installation or booting.
3. There is no other method available to obtain a new CDROM image.
Agenda:
Burn an ISO of the latest version of AntiX.
Boot into and customize it.
I see that AntiX has a"snapshot" script. So after customization, use this to make a final ISO for the system.
Mission complete.
demo@antiX1:~
$ eject
umount: /live/boot-dev: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
eject: unmount of `/live/boot-dev' failed
Questions:
Is there a way to unmount and eject while antix is still running?
Assuming yes, what method can we use to burn an ISO while the Live CD is no longer available to the system?
Thanks.
Last edited by ophase on 17 Jul 2014, 06:56, edited 1 time in total.
ophase wrote:Is there a way to unmount and eject while antix is still running?
This is what the"F4 Options" -->"to ram" feature is for.
Assuming yes, what method can we use to burn an ISO while the Live CD is no longer available to the system?
If snapshot works without toram then it will work with toram as well. The problem is that you could easily run out of RAM before you are done. Even worse, the standard tools will not reflect the true RAM usage. I suggest you use"free -m" and ignore the"-/+ buffers/cache" line. When RAM is used as a file system (both with"toram" and when you make the iso file) it is reported as"cached" not"used".
You could just try it and see if you run out of RAM or not. If you do run out of RAM then I suggest you start with antiX-base instead of antiX-full.
ophase wrote:Is there a way to unmount and eject while antix is still running?
Assuming yes, what method can we use to burn an ISO while the Live CD is no longer available to the system?
A couple of other ideas in case your system runs out of RAM when booting antiX in RAM mode as described by BitJam.
They might be covered by
ophase wrote:3. There is no other method available to obtain a new CDROM image.
if so just ignore them. Both are untested. Either might avoid the potential RAM problem, and they might be used when booted from Live CD in standard or RAM modes. Neither, require the unmounting of antiX so ejecting the media should not be needed. Both are possible with antiX-13.2-Full.
Idea 1
If you have some form of network storage you could mount that and use it as a destination for your customised ISO. antiX-13.2 ships with various ways of attaching to remote shares e.g. Connectshares can attach to Samba (Windows) shares of NFS shares.
User guide
========= SCRAPER REMOVED AN EMBEDDED LINK HERE =========== url was:"http://www.mepisimo.com/antix/Released/antiX-13.1/FAQ/connectshares.html" linktext was:"http://www.mepisimo.com/antix/Released/ ... hares.html" ====================================
Idea 2
If you have access to another system (Linux, or Mac, or Windows) that has a working wireless or wired network connection, you might be able to use an antiX app named Droopy. It was added to the antiX-13.2-Stable repo after the ISO was released so will need to be installed after booting via 13.2 Live CD.
Droopy allows a folder on the antiX system to made available to any other system that has a web browser and enables files to be transferred between the two systems. In this way you might create your customised ISO in the live antiX system, crank up web browser in the other (Linux, or Mac, or Windows) system and download the ISO to this second system.
User guide:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE =========== url was:"http://www.mepisimo.com/antix/Released/antiX-13.1/FAQ/droopy.html" linktext was:"http://www.mepisimo.com/antix/Released/ ... roopy.html" ====================================
"To ram" works as advertised, allowing me to eject optical media and burn as necessary.
Booting (not using toram) into 13.2 x64 full, conky reports 7.60G of RAM, and Root: 6.03G. Free -m confirms it. So we've got quite a bit more RAM to work with in the 64-bit environment.
I haven't tried to make a snapshot yet, as tweaking and configuration will take some time. I'm hoping the additional RAM available will increase my chances of a successful snapshot and ISO burning procedure.
I consider the thread solved as the primary concern was to get ISO burning functionality, with snapshotting a secondary concern.
I'm quite pleased with the AntiX distribution, both in terms of performance and selection of software (particularly the inclusion of icewm, as it is my go-to wm regardless of distro).