Just a quick one, is there a top level script / slackbuild esq script that
starts a build of a complete Slackware distro ?..
The build order of Slackware is not deterministic - the distribution evolves
upon itself.
There is no sort of 'make world' type script.
Eric's documenting his build
Incidentally Eric mentions the Chromebook as one of the reasons to port the
hf. I did install a full rootfs of Armedslack (sf) on the Chromebook and it
did work. I then gave up because of lack of feedback and because my unit
was faulty.
Yep I'm writing this using WindowMaker with Slackware
I wish I hadn't thrown away my work in progress tutorial about slackware on
chrome book as it contained some good tips about audio hacking.
On Mar 31, 2013 10:12 PM, Ottavio Caruso ottavio2006-usenet2...@yahoo.com
wrote:
Are you using the default chrome os kernel or is it a native one?
On Mar
Are you using the default chrome os kernel or is it a native one?
The default one at the moment but if I make the work public, I'll have
built my own 3.4.0 from the ChromeOS Git repo.
I do keep my notes in the 'slackwarearm-devtools/chromebook' dir on the
FTP site though. It's a bit random at
The default method now is to untar a rootfs, there's no point using an
installer. That is a remainder of the pc world. I did try it though and may
recall it didn't work.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
On Sun, 31 Mar 2013, Ottavio Caruso wrote:
The default method now is to untar a rootfs, there's no point using an
installer. That is a remainder of the pc world. I did try it though and may
recall it didn't work.
For me, the reasons to use the installer are:
1 - Someone has to provide
On Mar 31, 2013 23:03 Ottavio Caruso
ottavio2006-usenet2...@yahoo.com wrote:
On the other hand if you release a new rootfs say every month, all
that a smart user has to do is umount /home and untar the new rootfs
over the old one and some post install cleanup. Alternatively they can
be
