Man, I keep adding more and more to my plate.
Been doing it for six years here, and it never seems to end. And whatever install or upgrade scripts you make for jessie to ascii, there will be things that break in them when it's time to go ascii to beowulf. I'm not trying to discourage you. Just letting you know what to expect so you won't get discouraged when it happens.
]]>Same issue with my ASCII Refracta install using nox 9 version - have to logout and shutdown from lightdm.
Thanks for the confirm.
For shutdown and reboot, check that you have consolekit, policykit-1, libpam-ck-connector, and maybe policykit-1-gnome. Maybe something else, too, and that might depend on what desktop you're using.
For dns, I just set it in my router. To set it in the system, you can put it in /etc/resolv.conf (nameserver) or /etc/dhcp/dhclient.conf (prepend domain-name-servers) or /etc/network/interfaces.
Thank you for the troubleshoot advice, I'll try that out on my next ASCII upgrade test. I vaguely recall someone building a CK/PK1 independent shutdown into LXDE who had encountered a similar issue (which was pretty barebones but it worked). Can't recall where I saw it though.
I've got DNS set in my router, but the OS wasn't referencing it for some reason (it's what my normal machine uses).
DNS configuration information should be useful, will have to devise a list of DNS services for users to choose from, perhaps even region specific.
Man, I keep adding more and more to my plate.
]]>For dns, I just set it in my router. To set it in the system, you can put it in /etc/resolv.conf (nameserver) or /etc/dhcp/dhclient.conf (prepend domain-name-servers) or /etc/network/interfaces.
]]>There's no LXDE shutdown or reboot option (terminal also doesn't acknowledge shutdown or reboot as commands.) [edit: using VM to send a shutdown signal results in nothing happening. Does the dist-upgrade pull across all appropriate options, or has this been disabled due to systemd madness?]:
Same issue with my ASCII Refracta install using nox 9 version - have to logout and shutdown from lightdm.
]]>curl https://raw.githubusercontent.com/JoshuaFlynn/Modules/master/Download-Github.sh > Download-Github.sh
Or, if you just want to get the Modules system to immediately download (and not leave a Download-Github.sh hanging):
curl https://raw.githubusercontent.com/Joshu … -Github.sh | bash
Above pipe command does not work (unless the first command has been run), apologies.
]]>There's no LXDE shutdown or reboot option (terminal also doesn't acknowledge shutdown or reboot as commands.) [edit: using VM to send a shutdown signal results in nothing happening. Does the dist-upgrade pull across all appropriate options, or has this been disabled due to systemd madness?]:
There's no internet connectivity (ping successfully reaches targets specified as IPs, but dig, with URLs does not: does the ASCII dist-upgrade correctly set the DNS?):
Also, minor visual error in King-Pigeon logout image isn't present but that issue is my end.
For clarification: These issues do not exist in the Jessie King-Pigeon conversion, and only appear after a dist-upgrade is executed.
]]>A lot of sites suggest the usage of rsync, but from what I recall of my systemd contamination investigation, rsync indirectly had hovering references (will need to double-check that) to libraries that indirectly pointed to systemd. Naturally, if I want King-Pigeon to be systemd-free, I got to avoid relying on items and services that might pull in systemd or it's relatives.
So naturally, I wrote my own bash script that does a recursive copy (available under HelperScripts if anyone is interested in using it). Yes, it handles notorious newlines and 'bizarro characters' in filenames, and calls itself again if it encounters a new directory, passing additional arguments.
It also prints the data quite nicely (or at least I think so). Even returns colour codes for success/failure of the copy event:
Those of you on different colour terminal backgrounds (IE white, bright green, etc) will be pleased to know that the background of the coloured characters should be black (regardless of terminal background colours), so it should remain ideally visible even on differently coloured terminals.
Script is a bit hacky in that the print characters (the nice spacing you're seeing) is passed as an argument so it can recursively stack, but without doing super complex code, there's no straight way of solving it.
Query:
Is there some way to pass a subset of supplied terminal arguments to another bash script that is dynamic in numbers?
It'd be really useful if the Recursive-Copy script became a generic 'run this command' Recursive-Command type script where the command to run is passed to the script itself along with any arguments to said command. Lots of useful possibilities. Also sounds kinda tacky.
Further edit:
For anyone wondering about the functionality of Download-Github.sh, it switches mode. If Modules doesn't already exist, it simply uses a mv command (less expensive), which means first time it's run it shouldn't need Recursive-Copy.sh to deploy Modules. Subsequent calls will do, but Recursive-Copy.sh should be included in Modules by then. If not, simply delete the directory (and report the bug).
]]>4. File-roller? Gonna drag in a lot of gnome crap isn't it? Maybe some nasty gtk3? I would try Engrampa, same thing but more Mate-ish than Gnome-ish.
Bad news my friend.
I did a dependency check in King-Pigeon ASCII comparing Engrampa and File-roller:
Engrampa:
engrampa
Depends: bzip2
Depends: caja-common
Depends: engrampa-common
Depends: gzip
Depends: p7zip-full
Depends: tar
Depends: libatk1.0-0
Depends: libc6
Depends: libcairo-gobject2
Depends: libcairo2
Depends: libcaja-extension1
Depends: libgdk-pixbuf2.0-0
Depends: libglib2.0-0
Depends: libgtk-3-0
Depends: libjson-glib-1.0-0
Depends: libmagic1
Depends: libpango-1.0-0
Depends: libpangocairo-1.0-0
Breaks: engrampa-common
Recommends: gvfs
Recommends: mate-icon-theme
Recommends: unzip
Recommends: xz-utils
Recommends: zip
Suggests: arj
Suggests: binutils
Suggests: cpio
Suggests: <lha>
jlha-utils
lhasa
Suggests: lzip
Suggests: lzma
xz-utils
Suggests: lzop
Suggests: ncompress
Suggests: rar
Suggests: rpm2cpio
Suggests: rzip
Suggests: sharutils
Suggests: unace
Suggests: unalz
|Suggests: unrar-free
|Suggests: unar
|Suggests: unrar
Suggests: p7zip-rar
Suggests: zoo
File-roller:
file-roller
Depends: bzip2
Depends: p7zip-full
|Depends: dconf-gsettings-backend
Depends: <gsettings-backend>
gconf-gsettings-backend
dconf-gsettings-backend
Depends: libarchive13
Depends: libc6
Depends: libcairo2
Depends: libgdk-pixbuf2.0-0
Depends: libglib2.0-0
Depends: libgtk-3-0
Depends: libjson-glib-1.0-0
Depends: libmagic1
Depends: libnotify4
Depends: libpango-1.0-0
Recommends: gvfs
Recommends: yelp
Suggests: arj
Suggests: <lha>
jlha-utils
lhasa
Suggests: lzip
Suggests: lzma
xz-utils
Suggests: lzop
Suggests: ncompress
Suggests: rpm2cpio
Suggests: rzip
Suggests: sharutils
Suggests: unace
Suggests: unalz
Suggests: unar
Suggests: unzip
Suggests: xz-utils
Suggests: zip
Suggests: zoo
Both pull in libgtk-3-0 as a dependency.
I'll have to eyeball some other archiver at some point.
Edit, forgot to mention:
Good news for everyone:
The standalone Upgrade-to-ASCII.sh works on King-Pigeon (Jessie). However at present it requires manual input, and seems to take an extremely long time. It (the upgrade) also installs a couple of unwanted extras (EG gnome-screenshot), however I will build custom scripts for King-Pigeon etc to remove that.
As a status update:
In the meantime I'm redesigning the github script deployment system because github is no friend to non-empty directories (which is a nightmare if you need to update files without trashing useful ones), and their command structure gets messy and problematic, so I'm building a 'Download-Github.sh' script whose sole purpose is to download from, as you guessed, github.
Because I want to follow a 'keep it simple' approach, this script will become a central focus point. So instead of downloading a specific Blueprint script, you'd run this, which it will then download all of the Blueprints locally (it basically calls... itself). Eventually I'd like to make it into a User Interface where the script, when first run, asks you what blueprint or module you want to deploy.
As a result of this major github change, all of the scripts are being internally rewritten to call through this, so bear with me.
(This is what testing is for!)
]]>JoshuaFlynn wrote:greenjeans wrote:I kept thinking about this project yesterday, and it struck me that the very detailed listings in that script would be perfect for a live-sdk "blend" file too, that may be something to look at.
I've never heard of a live-sdk blend file before, could you tell me more about it?
Simple Distro Kit (SDK) is a Devuan thing. There's a lot on info on the devuan.org site.
Yep, and still in development though it works now, here's the link to Fsmithred's tutorial: https://dev1galaxy.org/viewtopic.php?id=551
In short, it's a semi-automated live-build system for rolling your own distro/iso. Blend files are similar to your script in that they list packages/programs to be installed on the iso, as well as customizations to be applied.
]]>greenjeans wrote:I kept thinking about this project yesterday, and it struck me that the very detailed listings in that script would be perfect for a live-sdk "blend" file too, that may be something to look at.
I've never heard of a live-sdk blend file before, could you tell me more about it?
Simple Distro Kit (SDK) is a Devuan thing. There's a lot of info on the devuan.org site.
]]>Maybe this will help? https://devuan.org/os/etc/apt/sources.list
Yep. I still got a lot of things to learn about Devuan.
I kept thinking about this project yesterday, and it struck me that the very detailed listings in that script would be perfect for a live-sdk "blend" file too, that may be something to look at.
I've never heard of a live-sdk blend file before, could you tell me more about it?
I probably could run off and do a search but I often find Linux documentation to be patchy at the best of times.
Your basic template you have up now works pretty good as a base, i'm trying to document the changes I make to things better so I can write a blend myself at some point, not necessarily for my own project but something more targeted at just basic improvements, connecting installed programs and making the user environment better, dotting the i's and crossing the T's so to speak.
Let me know if you find any 'garbage' programs/packages that need removal or possible improvements for King-Pigeon.
I totally get using file-roller over x-archiver, I swapped it too with engrampa mainly because engrampa supported more file types out-of-the-box and the user interface seems a tad better too.
I'll definitely try it out at some point. I am looking to reduce GNOME dependencies ever since they opted to sell out and move towards systemd so this should be helpful, although as this will be older GNOME I'm not too worried (yet!). With 47,000+ packages plus the ability to build from external git, it should be possible to develop workarounds for this. My main concern is systemd at this stage, and I encourage people to change their copy of King-Pigeon how they see fit, as it's kinda like <insert your own packages here>.
The version of yad (0.38) in the ascii repo uses gtk3 and does not work will with refracta tools - buttons are off-screen. I made gtk2 verions in jessie, but they seem to be working fine in ascii -
http://distro.ibiblio.org/refracta/file … _packages/Or, you could package them yourself. I already made the one or two small changes for gtk2.
https://git.devuan.org/fsmithred/yad
I previously posted on your forum under the username Gravimetric after I had issues with the Liveboot portion.
The text version works nicely from manual install, but my concern is both maintainability and usability. How does one update a manual install? And is a user going to want to use text?
Without trying to be rude (but written text always does sound like it), Devuan dev team might want to sort out Refracta so it's more consistent on Jessie/ASCII, because as I mentioned on fsmithred's forum, Refracta is secretly Devuan's biggest strong point, and whilst it is technically external to Devuan, it's allowing for so many spin-off OSes based on Devuan to be made, which is fundamentally drawing power away from systemd OSes, which is, of course, what we want. We have to show that a monolithic, all-encompassing monstrosity is beaten out with adaptability and flexibility.
Ideally Devuan should aim to draw both disgruntled developers who have been shunned by systemd and users likewise (more users, more visibility; more visibility, more developers), and Refracta is definitely enabling that. I wouldn't be here without it, as ISO creation kits are notoriously difficult to find or use, and Refracta is one of the better designed ones I've seen so far. Sure, I could learn to build an OS from scratch but the complexities involved consume vast amounts of time, and why reinvent the wheel?
Anyway, getting off-topic there, for current purposes King-Pigeon does what it needs to (regarding Devuan ISO deployment choice), just wanted to answer the queries of why I didn't do things a particular way. Believe me, I prefer easier routes, I usually only divert via scenic if the easy route isn't easy or isn't available.
]]>Actually it's in the devuan ascii repo (or so says this pkg list) http://devuanpackages.viralds.it/ascii/package/yad
The version of yad (0.38) in the ascii repo uses gtk3 and does not work will with refracta tools - buttons are off-screen. I made gtk2 verions in jessie, but they seem to be working fine in ascii -
http://distro.ibiblio.org/refracta/file … _packages/
Or, you could package them yourself. I already made the one or two small changes for gtk2.
https://git.devuan.org/fsmithred/yad
Your basic template you have up now works pretty good as a base, i'm trying to document the changes I make to things better so I can write a blend myself at some point, not necessarily for my own project but something more targeted at just basic improvements, connecting installed programs and making the user environment better, dotting the i's and crossing the T's so to speak.
I totally get using file-roller over x-archiver, I swapped it too with engrampa mainly because engrampa supported more file types out-of-the-box and the user interface seems a tad better too.
]]>That's what got me confused, when people say experimental I'm thinking Ubuntu style of a tag you'd append in the repositories (which I tried and naturally it threw angry errors at me), as opposed to ASCII. I realise ASCII is where all the fun is at, however in trying it (updating sources.list and apt-get update) I was a bit confused as I couldn't see eudev or vdev, is there something I'm missing?
Maybe this will help? https://devuan.org/os/etc/apt/sources.list
]]>