05-13-2024, 08:47 PM
(This post was last modified: 05-14-2024, 04:39 PM by grindstone.
Edit Reason: Add url to text mode thread
)
You have a lot going on at once.
1. A: Wired connection. What it meant to be connected at install is with a wired connection.
Maybe John can weigh-in, but I believe the best order to go at things is to get the "DSL File Restore" files, then apt-get update && apt-get upgrade, and then begin installing things such as the build-essentials, etc.
2. A: You've already found the cli-installer, but for the benefit of others, it's:
/usr/local/bin/cli-installer
5. In the case of starting w/o X, poking around in the flux menu entries reveals the equivalent "DSL File Restore" to be
/usr/local/bin/restore
which will pull down 17XMB which extracts to 5XXMB of man pages and useful things.
3. Again, you're past this point, but for the benefit of others (corrections welcome too), do the restore, then update and upgrade, THEN you can install "build-essential" to get gcc to build things (but it'll probably eat every ounce of that hardware alive for a good while--make sure you have swap active).
4. Good point. I think John had a workaround to start single user mode that will appear in a future release.
As for inittab, we feel your pain but this is runit and not SystemV init and you will not be the only person to have these questions. To get a rough handle on switching runlevels (and everything else), look here and on this page.
< Maybe a condensed version belongs in some cli-visible README type thing for those that need to start scaffolding w/o X working??? Or maybe runit basics and whatever other stuff need to be added as pages in /usr/share/dsl/FAQ/index.html??? perhaps that FAQ becomes text and chucked in /skel ??? Just ideas... >
Pragmatically, the RAM requirements for usage amount to what your browser needs. DSL as you can see boots in considerably less than 512MB and, if you can tolerate limitations in browsing and stick the the lightweight browsers (netsurf/dillo/links) etc, one can live in 256MB running X. For firefox, double that and more would be better IMO.
What about the framebuffer driver? Have you tried passing
xorg=fbdev
to the kernel at boot?
Otherwise, don't forget DSL is downstream from AntiX so there's more history/knowledge there (antixforum.com) as well. AntiX resources are a bit distributed, so again for benefit of others, some detail about live system boot parameters can be found at a tuxfamily url.
< Maybe another set of info to be included in FAQ or txt README or ??? >
The xproto, xorg naming requires more investigation than can happen for me right now. Those may be questions resolvable upstream (read: AntiX, MX, Debian) as you may view your DSL packages with something like:
sudo dpkg --get-selections | grep xorg
to see that there certainly is an xorg server, it just has a different expected name, etc.
1. A: Wired connection. What it meant to be connected at install is with a wired connection.
Maybe John can weigh-in, but I believe the best order to go at things is to get the "DSL File Restore" files, then apt-get update && apt-get upgrade, and then begin installing things such as the build-essentials, etc.
2. A: You've already found the cli-installer, but for the benefit of others, it's:
/usr/local/bin/cli-installer
5. In the case of starting w/o X, poking around in the flux menu entries reveals the equivalent "DSL File Restore" to be
/usr/local/bin/restore
which will pull down 17XMB which extracts to 5XXMB of man pages and useful things.
3. Again, you're past this point, but for the benefit of others (corrections welcome too), do the restore, then update and upgrade, THEN you can install "build-essential" to get gcc to build things (but it'll probably eat every ounce of that hardware alive for a good while--make sure you have swap active).
4. Good point. I think John had a workaround to start single user mode that will appear in a future release.
As for inittab, we feel your pain but this is runit and not SystemV init and you will not be the only person to have these questions. To get a rough handle on switching runlevels (and everything else), look here and on this page.
< Maybe a condensed version belongs in some cli-visible README type thing for those that need to start scaffolding w/o X working??? Or maybe runit basics and whatever other stuff need to be added as pages in /usr/share/dsl/FAQ/index.html??? perhaps that FAQ becomes text and chucked in /skel ??? Just ideas... >
Pragmatically, the RAM requirements for usage amount to what your browser needs. DSL as you can see boots in considerably less than 512MB and, if you can tolerate limitations in browsing and stick the the lightweight browsers (netsurf/dillo/links) etc, one can live in 256MB running X. For firefox, double that and more would be better IMO.
What about the framebuffer driver? Have you tried passing
xorg=fbdev
to the kernel at boot?
Otherwise, don't forget DSL is downstream from AntiX so there's more history/knowledge there (antixforum.com) as well. AntiX resources are a bit distributed, so again for benefit of others, some detail about live system boot parameters can be found at a tuxfamily url.
< Maybe another set of info to be included in FAQ or txt README or ??? >
The xproto, xorg naming requires more investigation than can happen for me right now. Those may be questions resolvable upstream (read: AntiX, MX, Debian) as you may view your DSL packages with something like:
sudo dpkg --get-selections | grep xorg
to see that there certainly is an xorg server, it just has a different expected name, etc.