Slackware on a USB stick...
I want to install a slack on a stick and use it as a live usb...
My only problem is that I want to do it on a NTFS usb so I can be able to write data on it from Windows ...
I was wondering if it's possible to do that as like KUbuntu where you install it on your windows partition....
If it's possible will somebody be willing to give me some information what should I look for and how to do it ?
Thanks in advance,
Have a look at this:
It may be of some use.
But installing on NTFS is probably going to be harder, since Linux ntfs support can be fuzzy sometimes. Try using fat32 instead, it's more supported, and can be written by Windows
Ya know. I have 5 usb drives with slackware installed on each (they keep making larger drives). Anyway, the thought has never occurred to me to format the drive ntfs first. I will try this and see what comes of it. I suspect the only roadblock would be making sure that the drivers immediately load on boot. Maybe you would have to recompile the kernel or make a initrd ... or maybe do nothing.
I'm going to try this tomorrow and report back with what I find.
I just found this link that allows you to make a live cd/dvd/usb Slackware that runs in a ramdisk. Maybe it will help you.
Why not have a separate NTFS partition which can be seen
by Windows and also can be mounted by Slack on ext3 or ext4?
Just install ext3 as the main OS partition and have another partition that is fat32. Store stuff that you need to access in both OSes on the fat partition.
You could also place a copy of explore2fs on the fat32 partition. It will allow you to access the ext3 partition from Windows should you need to.
Alternatively, there is this:
Probably plenty of others as well
Porteus, which is a derivative of Slackware, is supposed to be able to run live off NTFS USB or HDD.
You could also use a aufs-patched kernel and a hack of Linux-Live that I use to create a true live Slackware persistent USB/CD that basically runs just like Porteus/Slax but would be almost 100% Slackware depending upon which packages and from where (Salix, etc).
For instance I have a live version of Slackware -current with Fluxbox and kernel 3.1.4-smp that is 200MB and has copy2ram, persistence, etc. and Firefox 8, and some apps like Beep media player, Ted notepad, etc.
I understand lately aufs got to mainline kernel tree? No patch needed anymore?
And I do second the Porteus folks are running a decent OS there :)
ok, you need a few things to turn a install into a live-media (CD/DVD/USB)
1) a version of Linux-Live scripts appropriate to the kernel/aufs/squashfs versions because there are differences between them
2) a aufs patched kernel thats setup for squashfs xz compression or lzma for older kernels (requires squashfs-lzma patch)
3) scripts taken from Slax and Salix live that run certain thins during live session, boot, etc
the aufs2 patch for kernel 2.** and aufs3 patch for kernel 3.** are here
I can upload the other stuff somewhere for you, including kernel configs etc
I have a pre-made i686 3.1.4-smp kernel and modules also, and other versions
Porteus is right now a singular effort to keep alive and provide an upgraded Slax-6.1.2 as Slax went dormant and some people wanted to see a continuation of it, thus Porteus.
It is very up-to-date but is not so closely attached to Slackware in terms of making packages, no slackpkg, etc
But like I said you can take any Slackware 13.1/13.37 or current install and turn it into a live-media that is also reinstallable, so its a back-up system as well. its persistent also if you choose and as long as you have all the x drivers installed it will boot just like Slax/Porteus
The SalixOS live CD's are quite different in some ways.
below is a screenshot of 242mb liveusb I just made from a 1.2GB 13.37 install
make it alive! :-)
I assume squashfs can be "fuse-d" in? but aufs can't as the ability to make layers is mandatory?
Also, I miss the stage where we go from a initrd to a live-initrd:
the one "enriched" with setting up the aufs layers before we do regular the init
And most of all I miss time right now, so forgive me if I fall suddenly out of sync?
The concept of layering packages is simply excellent, sadly the idea received only small attention so far?
I.E. imagine each boot the OS makes a separate RW package it writes all to,
On next insertion, it becomes RO, and the next one gets created.
All changes ever incrementally (l(x(tg)))z-ipped ever ;-)
So, I list(-en)
|All times are GMT -5. The time now is 11:52 AM.|