Re: [DNG] Ascii LVM Encrypted Issue
Thanks for the reply, but at no point during the install do I see an option to install the “necessary” drivers? I just ran through the install once more and still don’t see any prompt or indication asking about supporting USB drivers. I did the install using a USB keyboard on both the VM instance and the dedicated hardware. Thanks again, Mike > On Jun 14, 2018, at 5:04 PM, KatolaZ wrote: > > On Thu, Jun 14, 2018 at 10:44:10PM +0200, Stefan Krusche wrote: >> Am Donnerstag 14 Juni 2018 schrieb Michael McConnell: >>> Thanks for confirming I am not going crazy (: I've been googling around >>> to see if USB is a non-free firmware element and from what I can tell >>> since loading firmware via USB seems to be the recommended way to load >>> non-free drivers I doubt this is a licensing issue. From what I've read >>> it appears intel and a few others gave USB 100% license free. Sooo is >>> this just an overlooked driver from the release? >>> >>> Cheers, >>> Mike >> >> The driver for USB is in the standard kernel. It just wasn't included in the >> initrd created during my installation, at least not the one for the USB >> keyboard, as I did the installation with another, old PS2 keyboard *and* >> chose "only necessary drivers", not "generic", which includes all the >> available drivers into the initrd, if I understand correctly. So, as no USB >> was being used during install the installer included no USB drivers in >> initrd, I think. In my case the problem didn't have anything to do with >> licensing or non-available non-free software or something like that. >> > > Hi Stefan, > > if you choose to install only the necessary drivers, you will be > guaranteed to have only the drivers needed for the hardware present in > the system at install time. That's the reason why you don't get USB > modules in the initrd (which is exactly what I would expect to happen > if I asked to include only the necessary drivers, TBH). > > I guess there is genuinely no bug here, just a feature ;) I am sure > you get the point. > > HND > > KatolaZ > > -- > [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] > [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] > [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] > [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] > [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] X11RDP-o-Matic Information - Scarygliders
On Thu, 14 Jun 2018 12:22:12 -0500, goli...@dyne.org wrote in message : > On 2018-06-14 10:53, Andrew McGlashan wrote: > > https://scarygliders.net/x11rdp-o-matic-information/ > > > > > > Interesting quote from the above link: > > > > NOTE: I am no longer actively spending days/hours of my time to > > maintain > > this script – there are too many different variations of Linux > > Distributions and they come out so frequently and always include > > changes > > in the way they do things, that it became utterly impractical for > > me to try to test o-Matic for every possible “gotcha” in every new > > and wonderful distribution. Systemd is another reason why I simply > > cannot spend any more time on o-Matic. It broke an awful lot of > > things when Debian decided to include it in their distributions, > > and I refuse to spend any more time dealing with this malware. If > > anyone wants to, they can feel free to submit pull requests to the > > o-Matic repository at Github, and if I have time I will review the > > changes and merge them with > > the main o-Matic branch. > > > > Regards. > > > > Cheers > > A. > > ___ > > > > Priceless! Repeated for truth . . . ..another priceless sort of scary gliding: http://rcspeeds.com/ ;o) http://rcspeeds.com/pastrecords -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ascii LVM Encrypted Issue
On Thu, Jun 14, 2018 at 10:44:10PM +0200, Stefan Krusche wrote: > Am Donnerstag 14 Juni 2018 schrieb Michael McConnell: > > Thanks for confirming I am not going crazy (: I've been googling around > > to see if USB is a non-free firmware element and from what I can tell > > since loading firmware via USB seems to be the recommended way to load > > non-free drivers I doubt this is a licensing issue. From what I've read > > it appears intel and a few others gave USB 100% license free. Sooo is > > this just an overlooked driver from the release? > > > > Cheers, > > Mike > > The driver for USB is in the standard kernel. It just wasn't included in the > initrd created during my installation, at least not the one for the USB > keyboard, as I did the installation with another, old PS2 keyboard *and* > chose "only necessary drivers", not "generic", which includes all the > available drivers into the initrd, if I understand correctly. So, as no USB > was being used during install the installer included no USB drivers in > initrd, I think. In my case the problem didn't have anything to do with > licensing or non-available non-free software or something like that. > Hi Stefan, if you choose to install only the necessary drivers, you will be guaranteed to have only the drivers needed for the hardware present in the system at install time. That's the reason why you don't get USB modules in the initrd (which is exactly what I would expect to happen if I asked to include only the necessary drivers, TBH). I guess there is genuinely no bug here, just a feature ;) I am sure you get the point. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] A message from Patrick J. Volkerding
Quoting Jaromil (jaro...@dyne.org): > FTR: after early experiments on yggdrasyl and sunsite ftp mirror, > slackware has been the first gnu/linux distro I've ever used as my > main computing platform, besides having NetBSD on a laptop. I believe > this is also the case for Katolaz and Nextime. 'yggdrasil'. Old Norse is easy to spell once you get the hang of it. Just practice using modest examples like 'Eyjafjallajökull'. ;-> True story: Upon my friend Don Marti (later longtime editor of _Linux Journal_) co-founded with Jim Gleason an open source software consultancy called 'Electric Lichen, LLC', Adam Richter of Yggdrasil Computing commented 'That's a difficult name.' And Don replied '_You_ should talk!' -- Cheers, The Viking's Reminder: Rick Moen Pillage first, _then_ burn. r...@linuxmafia.com McQ! (4x80) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ascii LVM Encrypted Issue
Am Donnerstag 14 Juni 2018 schrieb Michael McConnell: > Thanks for confirming I am not going crazy (: I've been googling around > to see if USB is a non-free firmware element and from what I can tell > since loading firmware via USB seems to be the recommended way to load > non-free drivers I doubt this is a licensing issue. From what I've read > it appears intel and a few others gave USB 100% license free. Sooo is > this just an overlooked driver from the release? > > Cheers, > Mike The driver for USB is in the standard kernel. It just wasn't included in the initrd created during my installation, at least not the one for the USB keyboard, as I did the installation with another, old PS2 keyboard *and* chose "only necessary drivers", not "generic", which includes all the available drivers into the initrd, if I understand correctly. So, as no USB was being used during install the installer included no USB drivers in initrd, I think. In my case the problem didn't have anything to do with licensing or non-available non-free software or something like that. Regards, Stefan ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] X11RDP-o-Matic Information - Scarygliders
On 2018-06-14 10:53, Andrew McGlashan wrote: https://scarygliders.net/x11rdp-o-matic-information/ Interesting quote from the above link: NOTE: I am no longer actively spending days/hours of my time to maintain this script – there are too many different variations of Linux Distributions and they come out so frequently and always include changes in the way they do things, that it became utterly impractical for me to try to test o-Matic for every possible “gotcha” in every new and wonderful distribution. Systemd is another reason why I simply cannot spend any more time on o-Matic. It broke an awful lot of things when Debian decided to include it in their distributions, and I refuse to spend any more time dealing with this malware. If anyone wants to, they can feel free to submit pull requests to the o-Matic repository at Github, and if I have time I will review the changes and merge them with the main o-Matic branch. Regards. Cheers A. ___ Priceless! Repeated for truth . . . golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] X11RDP-o-Matic Information - Scarygliders
https://scarygliders.net/x11rdp-o-matic-information/ Interesting quote from the above link: NOTE: I am no longer actively spending days/hours of my time to maintain this script – there are too many different variations of Linux Distributions and they come out so frequently and always include changes in the way they do things, that it became utterly impractical for me to try to test o-Matic for every possible “gotcha” in every new and wonderful distribution. Systemd is another reason why I simply cannot spend any more time on o-Matic. It broke an awful lot of things when Debian decided to include it in their distributions, and I refuse to spend any more time dealing with this malware. If anyone wants to, they can feel free to submit pull requests to the o-Matic repository at Github, and if I have time I will review the changes and merge them with the main o-Matic branch. Regards. Cheers A. signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] howto localize slim welcome screen
Le 14/06/2018 à 17:12, Didier Kryn a écrit : You have the choice between three themes: default and devuan-curve-darkpurpy. Sorry only two! The third one is a double symlink to the second. Thsi is why I only listed two (-: ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] howto localize slim welcome screen
Hi Devuaneers using the default display manager, slim. You have the choice between three themes: default and devuan-curve-darkpurpy. Of course you might want to make your own theme from scratch. But here I just explain how to just change the language. Slim doesn't take care of the current locale, but it is easy to change because it only says two things: "Username" and "Password". You can do it by creating a new theme. Suppose you want to re-use devuan-curve-darpurpy (not my choice (-:) and make it speak another language, eg French. # cd /usr/share/slim/themes # mkdir devuan-curve-darpurpy-fr # I chose this name because the trailing -fr tells it's just the french version of the theme. # rsync -a devuan-curve-darpurpy/ devuan-curve-darpurpy-fr # beware: don't forget the trailing slash We now have a new theme which is identical to the original one but we can modify it # cd devuan-curve-darpurpy-fr Open slim.theme with your favourite editor and change the fields username_msg and password_msg to your convenience. Save the file. We now have a brand new theme and just need to tell Slim to use it. Open /etc/slim.conf with your favourite editor. change the value of the field current_theme with the name of your new theme, eg devuan-curve-darpurpy-fr logout. see your new slim screen now speaking your language (-: Happy hacking. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ascii LVM Encrypted Issue
Thanks for confirming I am not going crazy (: I've been googling around to see if USB is a non-free firmware element and from what I can tell since loading firmware via USB seems to be the recommended way to load non-free drivers I doubt this is a licensing issue. From what I've read it appears intel and a few others gave USB 100% license free. Sooo is this just an overlooked driver from the release? Cheers, Mike On 06/14/2018 02:15 AM, Stefan Krusche wrote: Am Donnerstag 14 Juni 2018 schrieb Michael McConnell: Hello All, I've run this test both on Hyper-V VM install and a dedicated hardware install using a Dell R210ii, and the results are the same. If I do a new install using ASCII and use the default full disk encryption with LVM option - everything goes good, until the initial first boot. Upon boot up no matter what I do key presses don't register and no way to unlock the disk. I am using a USB keyboard, and I’ve tried a couple different models and the keyboard and configs i’m using have been fine going as far back as Ubuntu 12.04. I will try this with a legacy PS2 device if I can track one down this week, but my guess is no USB support from the busybox side. Cheers, Mike -- Michael McConnell WINK Streaming; email: mich...@winkstreaming.com toll free: 877-GO-4-WINK x 7400 direct: +1 312 281-5434 cell: +506 8706-2389 skype: wink-michael web: http://winkstreaming.com Hello Michael, I had this very same phenomenon. The reason in my case was, that the USB driver (general or for the keyboard I don't know) wasn't included in the initrd as I had used an old PS2 keyboard during installation. When the installer was about to generate initrd and asked wether to create a "generic" ramdisk or to use only the necessary drivers, I chose the latter. When later I restarted the machine with my plugged in shiny USB keyboard it wouldn't work as you described. With the old keyboard again I could enter crypt passphrase etc. and start the machine. I Plugged in the USB keyboard and recreated the initrd which solved the issue for me. Hope this helps, Stefan ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan from scratch?
Hi Jaromil, Jaromil writes: > re all, > > today I've noticed this interesting experiment from the news of > Distrowatch: > > https://github.com/scottwilliambeasley/debian-from-scratch/blob/master/README.md > > it's interesting because it provides an alternative "new" way to > bootstrap a new apt based system in addition to the classical > debootstrap method. I also noticed the instructions have no mention of > systemd, wonder where that will sneak in later... > > however I believe this approach works flawlessly on Devuan too. > > what would be useful for? besides learning how the system is made.. After a quick scan of that README.md, I concur with Didier's observations: nothing much beyond learning how to put together a minimal Debian(-based) distribution. The debootstrap *shell script* already does that for you. Want to learn how it works? Use the Source, Luke. The nice part about the README.md is that it explains (some of) the *why* behind steps. That is arguably missing from the Source. BTW, that README.md follows a somewhat different road as debootstrap (building some bits from source for example) but it's not wildly different. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ASCII installation static IP problem
Hi Don, Don Wright writes: > [ ... ASCII using Expert (text) from devuan_ascii_2.0.0_amd64_dvd-1.iso ...] > > Upon successful boot into the system things looked good locally, until I > tried to SSH to the box. Not there! While /etc/network/interfaces has the > settings I expected, the GUI showed wicd had ignored them and called DHCP to > create all new and mostly wrong settings. > > #apt remove wicd soon cleaned that up, but who the systemd thought it was a > good idea to ignore! working! static! IP! settings! and install an unwelcome > network mangler in the first place? Take a purgative, get your heads out of > your ASCII, and stop your wicd ways from overriding traditional handcrafted, > all-natural, artisanal, text-based config files. The output of `apt-cache rdepends wicd` using various combinations of the --recurse and --no-* options indicate that just about any, if not all, of the task-*-desktop packages recommend it, either directly or indirectly. Some may even prefer network-manager ... putting you between a rock and a hard place. > The guilty parties should lose an inch of *nix beard each in penance. The guilty parties would mostly be the task-*-desktop packagers ;-) but if you are comfortable with the installer's Expert mode, why not forego the installation of a desktop and run apt install task-desktop wicd- after the initial system install? > [ Semi-humorous howls of rage aside: Does the installed system ignore static > IP by design? ] Not if you don't install a desktop ;-) # You mentioned installing on a Lenove Think*Server*. I *never* put a # desktop on my servers ... Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ascii LVM Encrypted Issue
Am Donnerstag 14 Juni 2018 schrieb Michael McConnell: > Hello All, > I've run this test both on Hyper-V VM install and a dedicated hardware > install using a Dell R210ii, and the results are the same. If I do a new > install using ASCII and use the default full disk encryption with LVM option > - everything goes good, until the initial first boot. Upon boot up no matter > what I do key presses don't register and no way to unlock the disk. I am > using a USB keyboard, and I’ve tried a couple different models and the > keyboard and configs i’m using have been fine going as far back as Ubuntu > 12.04. > I will try this with a legacy PS2 device if I can track one down this week, > but my guess is no USB support from the busybox side. > Cheers, > Mike > > -- > Michael McConnell > WINK Streaming; > email: mich...@winkstreaming.com > toll free: 877-GO-4-WINK x 7400 > direct: +1 312 281-5434 > cell: +506 8706-2389 > skype: wink-michael > web: http://winkstreaming.com > > Hello Michael, I had this very same phenomenon. The reason in my case was, that the USB driver (general or for the keyboard I don't know) wasn't included in the initrd as I had used an old PS2 keyboard during installation. When the installer was about to generate initrd and asked wether to create a "generic" ramdisk or to use only the necessary drivers, I chose the latter. When later I restarted the machine with my plugged in shiny USB keyboard it wouldn't work as you described. With the old keyboard again I could enter crypt passphrase etc. and start the machine. I Plugged in the USB keyboard and recreated the initrd which solved the issue for me. Hope this helps, Stefan ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ASCII installation static IP problem
Installed ASCII using Expert (text) from devuan_ascii_2.0.0_amd64_dvd-1.iso. I'm very familiar with the Debian Installer interface from years of using it. Selected a static IP for the network setup and a local apt-cacher-ng proxy of us.deb.devuan.org for a faster response when (re)installing my test boxes. Other than that the choices were pretty much the defaults, including the Desktop packages, plus SSH host for remote access later. Had some difficulty with the EFI system partition not booting, which was solved by ignoring the advice to force the install to the EFI removable media location. Sounded like it would put files in both places, but that didn't work for my Lenovo ThinkServer. Upon successful boot into the system things looked good locally, until I tried to SSH to the box. Not there! While /etc/network/interfaces has the settings I expected, the GUI showed wicd had ignored them and called DHCP to create all new and mostly wrong settings. #apt remove wicd soon cleaned that up, but who the systemd thought it was a good idea to ignore! working! static! IP! settings! and install an unwelcome network mangler in the first place? Take a purgative, get your heads out of your ASCII, and stop your wicd ways from overriding traditional handcrafted, all-natural, artisanal, text-based config files. The guilty parties should lose an inch of *nix beard each in penance. [ Semi-humorous howls of rage aside: Does the installed system ignore static IP by design? ] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan from scratch?
Le 14/06/2018 à 08:27, Jaromil a écrit : re all, today I've noticed this interesting experiment from the news of Distrowatch: https://github.com/scottwilliambeasley/debian-from-scratch/blob/master/README.md it's interesting because it provides an alternative "new" way to bootstrap a new apt based system in addition to the classical debootstrap method. I also noticed the instructions have no mention of systemd, wonder where that will sneak in later... however I believe this approach works flawlessly on Devuan too. what would be useful for? besides learning how the system is made.. ciao Dear Jaromil, I'm not sure this project is really interesting - I mean debian-from-scratch. The advantage of building Linux from scratch is to learn what the internals are and what are the fundamental building blocks of the OS. Doing then a debotstrap step by step, which is, in reality, the process described in this manual, does only drop the educational part of LSF. And what is LSF if not educational? It is clear that, people following the LSF manual don't do it for educational reasons but for the sake of building themself their own OS (the DIY motivation). But, at the end, or in the middle, they realize it is not practical, and *only* educational. I followed a similar path when I started building my own Linux all compiled from source, statically linked against Musl libc. I started it at a time when there was no distro based upon Musl. It has been an enormous job, which I could do because I had enough free time and I could use powerfull servers to compile and recompile many time a cross-compiler and then a native one, then compile applications from sources. I stopped: it takes too much time but I have learned it is possible for a well organised group of people to do it and maintain it, and discovered this "distro" I wanted to do myself now exists (Alpine). Everyone can build a Debian system with debootstrap, even for a different architecture. I started my first Debian install on Powerpc SBCs 10 years ago, working from an i386 desktop. Debootstrap is just an executable wich downloads a hardcoded minimal set of packages and then runs some of the installed applications. I guess the version of debootstrap shipped by Devuan does the same for Devuan. It's exactly what Debian-from-scratch suggests to do step by step. It is certainly quick, and therefore not educational - in contradiction with the necessary preliminary steps of LSF. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] devuan from scratch?
re all, today I've noticed this interesting experiment from the news of Distrowatch: https://github.com/scottwilliambeasley/debian-from-scratch/blob/master/README.md it's interesting because it provides an alternative "new" way to bootstrap a new apt based system in addition to the classical debootstrap method. I also noticed the instructions have no mention of systemd, wonder where that will sneak in later... however I believe this approach works flawlessly on Devuan too. what would be useful for? besides learning how the system is made.. ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] A message from Patrick J. Volkerding
On Wed, Jun 13, 2018 at 11:43:40AM +0200, Jaromil wrote: > On Tue, 12 Jun 2018, Jimmy Johnson wrote: > > > Devuan or Trinity can borrow anything they find useful from the current > > tree. > > Well, we all have learned SO MUCH from Patrick's good work all our > life: I think we can already consider Devuan borrows from Slackware. > > FTR: after early experiments on yggdrasyl and sunsite ftp mirror, > slackware has been the first gnu/linux distro I've ever used as my > main computing platform, besides having NetBSD on a laptop. I believe > this is also the case for Katolaz and Nextime. I came to Linux a little later (around 1997) but yes, the first Linux I ever used was Slackware with twm and fvwm. Apart from a brief interlude with RH and the switch to De??an, my computing has not changed that much since then, TBH. I agree we have all learned a lot from Slackware, and probably still have to learn more ;) HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
