Re: [DNG] no display of GRUB menu
Am 2. Juni 2018 01:55:43 MESZ schrieb Haines Brown : > I assume that "i386-pc" is appropriate for my 64bit system. > > [...] > > Incidentally, I also rechecked the UUID numbers for the / and boot > partitions. "i386-pc" is correct. Did you flag your boot partition "bootable"? lg, f. -- [message sent mobile] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] no display of GRUB menu
On Fri, Jun 01, 2018 at 11:21:06PM +0200, Florian Zieboll wrote: > Am 1. Juni 2018 22:24:47 MESZ schrieb Haines Brown : > > > I installed Jessie on a new disk on a new machine. I can boot it from > > the GRUB menu on another disk on that machine, but when I try to boot > > the new disk directly, all I get is a blinking cursor at upper left. > > Holding down SHFT or ESC during post did not bring up its menu. > > > > I tried redoing # update-grub. > > > Depending on how you finished the installation routine, you might need to not only "update-grub", but also run "grub-install /dev/sdx", where "x" is the drive letter (without partition number) of your new disk. Florian, thanks for the suggestion. I ran # grub-install /dev/sda and this was returned: installing for i386-pc platform Installation Finished. No errors reported. I assume that "i386-pc" is appropriate for my 64bit system. The GRUB2 grub-common on this old machine (Devuan Jessie) is same version as that on the new machine. Doing Ctl-Alt-F2 while the cursor was blinking did nothing. Incidentally, I also rechecked the UUID numbers for the / and boot partitions. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] no display of GRUB menu
Am 1. Juni 2018 22:24:47 MESZ schrieb Haines Brown : > I installed Jessie on a new disk on a new machine. I can boot it from > the GRUB menu on another disk on that machine, but when I try to boot > the new disk directly, all I get is a blinking cursor at upper left. > Holding down SHFT or ESC during post did not bring up its menu. > > I tried redoing # update-grub. Depending on how you finished the installation routine, you might need to not only "update-grub", but also run "grub-install /dev/sdx", where "x" is the drive letter (without partition number) of your new disk. libre Grüße, Florian -- [message sent mobile] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Screenshots
"https://paste.pics/; To post a screenshot you don't need to be a member, you don't need to use java and there are no ads. paste.pics is great! Cheers! -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] no display of GRUB menu
On 06/01/2018 01:24 PM, Haines Brown wrote: I installed Jessie on a new disk on a new machine. I can boot it from the GRUB menu on another disk on that machine, but when I try to boot the new disk directly, all I get is a blinking cursor at upper left. Holding down SHFT or ESC during post did not bring up its menu. I tried redoing # update-grub. I find that /boot/grub/grub.cfg has a fully developed menu in which is: set root='hd0,mddos2'. This seems correct. BIOS sees this disk as number 0. In \ is a vmlinuz symlink that points to the vmlinuz file in a broken out /boot. Parted print shows partition 1 to be primary and flagged bootable. Partition 2 is also primary. It seems that one way to display the menu is to change to these values in these lines in /etc/default/grub to: GRUB_HIDDEN_TIMEOUT=10 GRUB_HIDDEN_TIMEOUT_QUIET=false in /etc/default/grub, but these lines do not appear and what I have instead is: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 Try 'ctrl+alt+F2 to see if you can get a console. Cheers, -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] no display of GRUB menu
I installed Jessie on a new disk on a new machine. I can boot it from the GRUB menu on another disk on that machine, but when I try to boot the new disk directly, all I get is a blinking cursor at upper left. Holding down SHFT or ESC during post did not bring up its menu. I tried redoing # update-grub. I find that /boot/grub/grub.cfg has a fully developed menu in which is: set root='hd0,mddos2'. This seems correct. BIOS sees this disk as number 0. In \ is a vmlinuz symlink that points to the vmlinuz file in a broken out /boot. Parted print shows partition 1 to be primary and flagged bootable. Partition 2 is also primary. It seems that one way to display the menu is to change to these values in these lines in /etc/default/grub to: GRUB_HIDDEN_TIMEOUT=10 GRUB_HIDDEN_TIMEOUT_QUIET=false in /etc/default/grub, but these lines do not appear and what I have instead is: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ubuntu w/out systemd?
On 05/31/2018 06:22 PM, goli...@dyne.org wrote: On 2018-05-31 17:40, Jimmy Johnson wrote: On 05/31/2018 01:30 PM, Fungal-net wrote: Q4OS has dome alot of work on trinity, maybe you should use their repositories to pick things up. It is a systemd distribution, I have a friend using it, I can get the sources.list from her if you need it. First, please do not send me your email, unless you ask me first period, and if it's a emergence call 911. You're kidding right. I'm all about not touching systemd, if I could I would use it for target practice. My feelings are, anyone volunteering to work, for free, on a OS with systemd is a Sucker and anyone getting paid to work on a OS with systemd is my Enemy. Just an FYI . . . Fungal-net emailed you because he is in moderation on this list and with good reason. Unfortunately, there is no way to prevent him from contacting individual list members. Let me know if he persists in bothering you. golinux I saw your post yesterday, I'm wordless and in shock over this incident. Thank you for your followup. -- Jimmy Johnson Devuan Jessie - KDE 4.14.2 - AMD A8-7600 - EXT4 at sda5 Registered Linux User #380263 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Systemd introduces "Portable Services"
systemd won't be done until it can read mail, apparently. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Systemd introduces "Portable Services"
Arnt Karlsen - 01.06.18, 15:07: > > https://soylentnews.org/article.pl?sid=18/05/30/0147216 > > > > Mozilla isn't alone in "innovating", sigh! > > > > "The past several months Lennart Poettering has been working on a > > "portable services" concept and that big ticket new feature has now > > landed in Systemd. Portable services are akin to containers but > > different." > > ..more details on said difference: > https://www.phoronix.com/scan.php?page=news_item=Systemd-Portable-S > ervices To me that reads like a somewhat extended version of chroot´ed services all stuffed together into the same monolithic binary called (/usr|)/lib/ systemd/systemd. -- Martin ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Systemd introduces "Portable Services"
On Thu, 31 May 2018 17:09:26 +0200, Alessandro wrote in message <20180531170926.1072b13e@ayu.localdomain>: > https://soylentnews.org/article.pl?sid=18/05/30/0147216 > > Mozilla isn't alone in "innovating", sigh! > > "The past several months Lennart Poettering has been working on a > "portable services" concept and that big ticket new feature has now > landed in Systemd. Portable services are akin to containers but > different." ..more details on said difference: https://www.phoronix.com/scan.php?page=news_item=Systemd-Portable-Services ..coupla more "239" releases... just stating verified facts... ;o) https://en.wikipedia.org/wiki/Plutonium-239 https://en.wikipedia.org/wiki/Isotopes_of_uranium#Uranium-239 -- ..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] Creating .deb packages with jenkins-debian-glue
On Thu, 31 May 2018 16:33:06 +0200, KatolaZ wrote in message <20180531143306.fmu656thmuzgx...@katolaz.homeunix.net>: > On Thu, May 31, 2018 at 03:29:30PM +0200, KatolaZ wrote: > > On Thu, May 31, 2018 at 09:16:27PM +0900, Olaf Meeuwissen wrote: > > > Hi Tom, > > > > > > Tom writes: > > > > > > > Hi, > > > > > > > > I'm trying to use dh_virtualenv and and jenkins-debian-glue to > > > > package a python app into a .deb using jenkins. > > > > > > > > I followed all the instructions on > > > > https://jenkins-debian-glue.org, updating the steps where > > > > required for differences in the latest Jenkins release, but I > > > > see errors when running the jenkins-debian-glue-binaries job. > > > > > > > > It looked like it was failing due to the output of 'lsb_release > > > > --short --codename' returning "n/a" on Devuan Ascii, so I > > > > created /etc/lsb-release with the relevant details. It's now > > > > showing a different error. > > > > > > The "n/a" sounds like you've also been hit by > > > > > > http://bugs.devuan.org/cgi/bugreport.cgi?bug=199 > > > > > > Try using packages.devuan.org. > > > > Please hold on on that. We are working to solve it. > > > > > Thanks to parazyd who has just fixed it. If you are using > pkgmaster.devuan.org, please `apt-get update` and then lsb_release > will work correctly: > > $ lsb_release -a > No LSB modules are available. > Distributor ID: Devuan > Description:Devuan GNU/Linux 2.0 (ascii) > Release:2.0 > Codename: ascii > $ > > If you are on deb.devuan.org it might take up to one hour to > propagate. Please report any undesired behaviour. > > HTH > > KatolaZ > ..this means OP (Tom) can go back to his plan A (using dh_virtualenv, jenkins-debian-glue and jenkins) because parazyd fixed the bugs there so Tom's plan A will now work? ..I also got the impression "Tom's plan A" is the easier and better way when joining devuan.org as a packager and package maintainer, while dpkg-buildpackage is a better and easier way for people who just rarely needs custom built packages on his own home boxes. -- ..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] Devuan ascii installer netinstall iso UPDATE
Hi Stefan, Stefan Krusche writes: > Am Donnerstag 31 Mai 2018 schrieb Stefan Krusche: >> Good day everyone, >> >> while starting the devuan installer from >> devuan_ascii_2.0.0-rc_amd64_netinst.iso and initiating to continue with ssh >> remote install (in graphic expert install mode) the installer showed its >> fingerprint as SHA256:xxx, which was new to me. It used to be an RSA key >> fingerprint. >> >> Problem: when I try to connect from my other machine which is a devuan >> jessie system to the one I'm gonna set up: >> ssh installer@192.168.19.3 >> ssh still shows an RSA fingerprint from the installer, so I don't know how >> to verify it (which was easy with the jessie installer just by looking). >> >> Not that I don't trust my own computer here but I'd like to know if I need >> a more recent version of ssh or if there's a way to get a visual match or >> something. Found nothing about SHA256 host keys in man ssh. >> >> Can anyone clarify about this to me, please? >> > > So, I just found this: > https://superuser.com/questions/929566/sha256-ssh-fingerprint-given-by-the-client-but-only-md5-fingerprint-known-for-se#929567 > according to which fingerprint of the sshd server defaults to SHA256 from some > version on and I'd expect it to be sent as such to the client. > > My older version can't seem to process option "-o FingerprintHash=sha" as > suggested in the posting on superuser.com to get the SHA256 key fingerprint > which is shown on the screen of the installer. My understanding is that on your remote client you should specify md5, not sha. That is, "-o FingerprintHash=md5". > Now, I don't know if the RSA key fingerprint of the sshd server of the > installer, which my ssh client shows, is sent that way from the server (should > be so, right?) or my ssh client is to old and with a newer one it would show > the SHA256 key fingerprint like on the installer screen. Maybe, the installer > has to be configured to send SHA256 key fingerprint and it isn't? If things don't work on the remote client side and you can execute a shell on the machine you're installing on, you can get the MD5 hash with ssh-keygen -l -E md5 -f $file where $file is one of the SSH server's keyfiles in the installation target. IIRC, these should be below /target/etc/ssh/. There is an option to execute a shell in the installer itself or you can switch virtual terminals with one of the Alt-Fn key combos. Don't quite remember for which value of n, but in the F1 through F4 range. Hmm, or was that Ctrl-Alt-Fn? Anyway, just try a couple of combinations ;-) 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
