Re: [DNG] ascii 2.0 installation confused by mount points
Le 10/06/2018 à 14:55, Haines Brown a écrit : On Sun, Jun 10, 2018 at 10:05:48AM +0200, Didier Kryn wrote: Le 10/06/2018 à 04:01, Haines Brown a écrit : On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: Haines Brown wrote: In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary partition that is bootable and the mount point /. You probably want to set this partition to unused (or whatever it's called, it's a looong time since I last did this) so that it doesn't appear in the mount point table (eventually in fstab of the new install). I think what you are telling it is that you want sda1 to mounted as / IN THIS INSTALLATION and that then clashes with your new / (on sdc) that you're trying to install to. In the partitionner (which is not only a partitionner, but generates the fstab and the filesystems), you should select "dont use the partition"on every partition which is not in sdc. Click on "use partition as" and select "dont use the partition". Didier, that seems to have done the trick. I apologize for having been too hasty. Where the partitioner asks what to use a partition as, because the top options were simply file systems, I interpreted it to be merely for selecting file system and did not notice the "don't use" option at the bottom. When I marked sda partitions not to be used, I was able to save the sdc partition table and proceed with the installation. Now that installation of ascii 2.0 on sdc is underway and before going further I must figure out how to recover a use of partitions on sda. I assume that were I to use the menu to revert to partitioning and restore usage of sda partitions I'll just end up with the same problem of a competition of sda and sdc for use of /. When I execute a shell toward the end of installation, can I use it to run the command "parted /dev/sda set 1 boot on" both to enable sda1 and to make it bootable at the same time? Would the command "parted /dev/sda set 2 on" simply re-enable the second partition? I found the parted manual unclear on this point. I guess you don't want to use sda from your sdc OS. Therefore don't do anything more. When you boot the OS on sda, then, this one won't use sdc. And vice-versa. Isn't this what you want? Or do you haved changed the partition table on sda, or erased some partitions there which you want to recover? This can be difficult. If you want to share a partition (say home) between different OSes, then, of course you have to mention it, but it's not recommendable because config files of several applications are not backward compatible between versions. Also private applications using dynamically linked libraries might not find the proper version of the libraries. But of course, it is convenient to mount the old home from another disk to copy it to the new one to start from. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
Le 10/06/2018 à 16:08, Rowland Penny a écrit : On Sun, 10 Jun 2018 08:55:55 -0400 Haines Brown wrote: When I execute a shell toward the end of installation, can I use it to run the command "parted /dev/sda set 1 boot on" both to enable sda1 and to make it bootable at the same time? Would the command "parted /dev/sda set 2 on" simply re-enable the second partition? I found the parted manual unclear on this point. I am fairly sure you will need to set up grub2 to do this, try reading this: https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk Or failing that, google for the answer ;-) When your installation is almost finished, one of thevery last steps is installing the Grub bootloader. Just do it: it will automatically detect all OSes on all disks (which don't need to be mounted in any way), and generate a boot list which enables all them. You will have the currently installed OS on top of the list, then a rescue mode for this OS, then all the other detected OSes. You decide on which disk you want to install the Grub bootloader. I suggest you install it on all disks as explained below. You can install the Grub bootloader on other disks as well, either by re-running the bootloader installation step (I didn't check but I don't see why it would fail), or by invoking install-grub from the command-line (install-grub /dev/sda; install-grub /dev/sdb; etc..). Grub does not use internally the device names sda2, sdb1 sdc5, etc... but the UUIDs of the partitions to boot from, therefore you can permute your disks as you like if you have installed the bootloader on all of them. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan ASCII 2.0.0 stable
Quoting info at smallinnovations dot nl (i...@smallinnovations.nl):
> Discussion at slashdot is a waste of time nowadays (I do have a 5 digit
> uid from the time ./ had some merits).
{ahem} FWIW:
rickmoen (1322)
Karma: Excellent
;->
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan ASCII 2.0.0 stable
Quoting Jaromil (jaro...@dyne.org): > this weekend the news of our release made a splash on community fora, > namely hackernews https://news.ycombinator.com/item?id=17274623 where > our effort was always heavily denigrated and mocked, now starts > emerging some reasonable feedback. And last not least slashdot where > Bruce Perens declared his endorsement for Devuan 8^D > https://linux.slashdot.org/story/18/06/10/0321233/systemd-free-devuan-20-ascii-officially-released Bruce rises to the occasion and does things of sterling character when you least expect it. ;-> (As the Aussies say, 'Good on ya, Bruce.') Quoting info at smallinnovations dot nl: > info at smallinnovations dot nl Discussion at slashdot is a waste of > time nowadays (I do have a 5 digit uid from the time ./ had some merits). Take it from someone who was employed at VA Linux Systems during and after the time we acquired Andover.net (Slashdot's itty-bitty corporate entity): Slashdot was _always_ a poster child for Sturgeon's Law, overwhelmingly a place for bored pseudonymous nobodies to exercise poor impulse control and the maturity of frat boys. One of life's many ironies is that after VA Research^W^W VA Linux Systems^W^W^W SourceForge, Inc.^W^W^W withered away so much from basic business ineptitude that its remaining husk could no longer _even_ afford to pay the 401(k) retirement fund fees, and sold off _everything_ including SourceForge and Slashdot, the tiny remaining ember entity, GeekNet, Inc. is sort of like an embryonic Andover.net -- so the tail has ended up wagging the dog. (Dice Holdings initially bought Slashdot and SourceForge.net in 2015, but recently offloaded them to a small and obscure investment firm.) > > Gochisōsama deshita! ;^P -- Sapere aude! I now dare to know how to conduct myself the next time I have lunch in Kyoto! ;-> (Arigatō gozaimasu.) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On 2018-06-10 17:31, Renaud (Ron) OLGIATI wrote: On Sun, 10 Jun 2018 12:45:36 -0500 goli...@dyne.org wrote: > Just have to keep a post-it on the monitor, to remind you which HD has > what ;-3) I actually keep a small sticky label on the drive itself. ;) Might not be very useful at boot time ;-3) Cheers, Ron. It does if you take a drive out for some reason or move drives around. ;) My gigabyte boards allow me to choose which drive I want to boot from a list that pops up with F12. golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 12:45:36 -0500 goli...@dyne.org wrote: > > Just have to keep a post-it on the monitor, to remind you which HD has > > what ;-3) > I actually keep a small sticky label on the drive itself. ;) Might not be very useful at boot time ;-3) Cheers, Ron. -- Television has proved that people will look at anything rather than each other. -- Ann Landers -- http://www.olgiati-in-paraguay.org -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
On Sun, Jun 10, 2018 at 11:44:56PM +0200, k...@aspodata.se wrote: > KatolaZ: > > On Sun, Jun 10, 2018 at 11:15:18AM -0500, Peter Vachuska wrote: > ... > > > I know that my setup is atypical and console users won't > > > influence the direction of X. Still > > > Dear Peter, > > > > please have a look at the ASCII Release Notes: > > > > https://files.devuan.org/devuan_ascii/Release_notes.txt > > > > which provide an explanation of the whole X.org matter and of the > > solutions available in Devuan ASCII. > > That doesn't explain why, it just says something like: > we do like this and you can adjust to that by doing ... > So basically you exchanged suid X with suid consolekit/elogind ? > And if I don't need a session manager, I have been inconvenienced. Except we (Devuan) didn't. Debian did. > > > I understand the frustration, but > > the best way to get out of it is to do something to solve the > > problem. Whatever you can. > ... > > Can't you just do (don't have an ascii system to test on for the moment) > chmod 4711 /usr/bin/Xorg > and then just run it as you whish ? > It's not as easy as it looks to you. The main reason is the interaction with login and session managers. 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] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
KatolaZ: > On Sun, Jun 10, 2018 at 11:15:18AM -0500, Peter Vachuska wrote: ... > > I know that my setup is atypical and console users won't > > influence the direction of X. Still > Dear Peter, > > please have a look at the ASCII Release Notes: > > https://files.devuan.org/devuan_ascii/Release_notes.txt > > which provide an explanation of the whole X.org matter and of the > solutions available in Devuan ASCII. That doesn't explain why, it just says something like: we do like this and you can adjust to that by doing ... So basically you exchanged suid X with suid consolekit/elogind ? And if I don't need a session manager, I have been inconvenienced. > I understand the frustration, but > the best way to get out of it is to do something to solve the > problem. Whatever you can. ... Can't you just do (don't have an ascii system to test on for the moment) chmod 4711 /usr/bin/Xorg and then just run it as you whish ? Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 15:08:31 +0100, Rowland wrote in message <20180610150831.64627...@devstation.samdom.example.com>: > https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk > > Or failing that, google for the answer ;-) ..https://www.dedoimedo.com/computers/grub-2.html has e.g. 8. GRUB 2 recovery A. Recover from failed boots -- ..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] Postgresql problem
Am 2018-06-10 21:12, schrieb Steve Litt: If the error is being thrown by something Debian added, well, it's Holloween code, and we can take it out. Looks like it is some Debian script: # print a list of PostgreSQL versions that are supported for the platform this # script runs on. # Note: Newer installed versions than the highest one listed here are always # considered supported, so that backports will not cause an "obsolete" warning. # # /usr/share/postgresql-common/supported-versions decides which PostgreSQL # server versions are supported. This information is used # 1) for notifying users of obsolete versions, suggesting to upgrade # 2) by postgresql-common itself (in debian/rules) to determine the #dependencies of the postgresql meta packages (default version), and to #generate the list of postgresql-server-dev-* packages #postgresql-server-dev-all depends on # 3) by the pg_buildext tool to decide which server versions to build extension #modules for # # The *last* version returned here will be considered the default version, the # remaining lines list other supported versions in an undefined order. # # * PG_SUPPORTED_VERSIONS # * DEB_PG_SUPPORTED_VERSIONS # * ~/.pg_supported_versions # * /etc/postgresql-common/supported_versions # (in that order) can be used to override the defaults. (Tokens separated by # newlines.) # # Recognized tokens: # default: use the appropiate defaults for the current distribution and release # (as determined by os-release or lsb_release) # debian [release]: use Debian defaults # debian-backports [release]: use Debian Backports defaults # ubuntu [release]: use Ubuntu defaults # pgdg [release]: use defaults for apt.postgresql.org # installed: consider all installed versions supported (determined by #postgresql-server-dev-X.Y packages) # X.Y: consider this version supported # # (C) 2005-2016 Martin Pitt # (C) 2012-2017 Christoph Berg I don't know what it's purpose is. I think it is called by some installation script and influences creation of config files. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
On Sat, 9 Jun 2018 13:52:06 -1000 Joel Roth wrote: > Colleagues! > > Earlier in this thread, we learned that installing xserver-xorg-legacy > allows you to run X the old way, as a setuid script. > > The default upgrade path from jessie -- in which X11 was > setuid-only -- migrates to a new xserver-xorg in which the > setuid mechanism is replaced. In order to run X with user > permissions in the dist-upgrade'd environment one needs to > pull in a stack of dependencies including dbus, polkit, > libpam-elogind, and elogind. Hi Joel, I've noted that suggested documentation already solved your problem and the problem of the person whose X no longer opened on Ctrl+Alt+F7, so my post is just for contemplation... I don't know if the new method really runs X as a normal user, but the setuid method ran it as root, but enabled a normal user to run it. I'd imagine a line in /etc/sudoers would accomplish the same thing. I imagine that if you boot to a Display Manager like slim, xdm, lxdm and the like, this problem is already solved for you because the init runs the Display Manager as root. I'd imagine the "run as root" problem occurs only when you boot up in CLI and then run startx to go X. Again, /etc/sudoers should cover the problem. Or, perhaps, have X be a service in the init, so it can be started by root at boot (without a Display Manager). In runit the X directory can have a file named "down" so it doesn't automatically run: You could run it like: sv up X The preceding would need to be run as root, but again, /etc/sudoers. Or you could have a setuid shellscript called "togglex" that would alternate sv up X and sv down X: No /etc/sudoers, just run it. In the preceding several paragraphs, runit doesn't need to be the init: It can be run simply be a process supervisor like daemontools. I haven't tried these ideas, but I *think* they should work. SteveT Steve Litt June 2018 featured book: Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 02:08:29PM -0400, Haines Brown wrote: > The suggestion to disconnect the sda drive while I install the same > version of the operating system on sdc occurred to me, but I worried > about the effect of the resulting change in drive designations. In my > case, by disconnecting sda my sdb becomes sda and my sdc becomes sdb. > Will all of this sort itself out when I reconnect the old sda drive and > boot it? After installing ascii on sdc I probably will have to select > sda as the drive to boot in BIOS and then run update-grub after it is > up. This is exactly why modern d-i and grub use those unsightly UUIDs instead of user-friendly "sda". You don't want the system to break just because you removed one of the disks, or this time one of them took a few seconds longer to spin up and thus lost a race. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts ⣾⠁⢰⠒⠀⣿⡁ productivity. You can read it, too, you just need the ⢿⡄⠘⠷⠚⠋⠀ right music while doing so. I recommend Skepticism ⠈⠳⣄ (funeral doom metal). ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Postgresql problem
On Sun, 10 Jun 2018 10:40:44 +0200 "J. Fahrner" wrote: > Am 2018-06-10 09:26, schrieb Ralph Ronnquist: > > The first google match suggests adding > > ID_LIKE=Debian > > to /etc/os-release > > > > Worth a try perhaps? > > Sounds good. > Before: > - > supported-versions: WARNING! Unknown distribution: devuan > /usr/share/postgresql-common/supported-versions: 66: > /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter > not set > /usr/share/postgresql-common/supported-versions: 69: > /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter > not set > Please submit this as a bug report to your distribution. > -- > > After (ID_LIKE=Debian): > -- > supported-versions: WARNING! Unknown distribution: devuan > Please submit this as a bug report to your distribution. > -- > > After (ID_LIKE=debian): > -- > supported-versions: WARNING! Unknown distribution: devuan > debian found in ID_LIKE, treating as Debian > -- > > Looks like debian must be written in lower case. > Would be nice if Devuan could add this in base-files package. Why is the distro one is using Postgres' business? I'd imagine if I want to run Postgres on Steve's Midnight Escape distribution, I should be able to, without an error message. If this error is thown by Postgres itself, I think it should be submitted as a bug report to Postgres. If it's not a bug, it sounds like a poor design decision. If the error is being thrown by something Debian added, well, it's Holloween code, and we can take it out. SteveT Steve Litt June 2018 featured book: Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
KatolaZ wrote: > please have a look at the ASCII Release Notes: > > https://files.devuan.org/devuan_ascii/Release_notes.txt > > which provide an explanation of the whole X.org matter and of the > solutions available in Devuan ASCII. Thank you (and the author) for this reference. Somehow I'd missed it. -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 04:07:17PM +0100, Rowland Penny wrote: > What you are talking about doing is akin to dual-booting, just on > different disks i.e. you will only be able to boot one distro. > > Rowland Yes. In the past I've always had multiple hard drives in one machine, each with an operating system and its own boot menu. This because I've become paranoid over the years and always want the option of which drive on the machine to boot. I suspect, though, that these disks always had at least different versions of the operating system, and what I'm doing now is trying to install ascii 2.0 on a disk in a system that already has a disk with ascii-rc on it. Do you know if I wouldn't have had the problem had I tried to install devuan testing or experimental on sdc with ascii on sda? The suggestion to disconnect the sda drive while I install the same version of the operating system on sdc occurred to me, but I worried about the effect of the resulting change in drive designations. In my case, by disconnecting sda my sdb becomes sda and my sdc becomes sdb. Will all of this sort itself out when I reconnect the old sda drive and boot it? After installing ascii on sdc I probably will have to select sda as the drive to boot in BIOS and then run update-grub after it is up. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] [OT] Future codename proposal (was: Devuan ASCII 2.0.0 stable)
Irrwahn wrote on 09.06.2018 14:34: > Omedetō gozaimasu, Devuan ASCII! I wonder if someone could sweet-talk the CSBN of the IAU into creating the precondition for us to dub Devuan 21.0.0 UTF-8. -- SCNR, I see myself out. signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On 2018-06-10 11:07, Renaud (Ron) OLGIATI wrote: On Sun, 10 Jun 2018 10:48:28 -0500 goli...@dyne.org wrote: > A work-around for your problem: > Install each OS individually on a HD (disconnecting the other bootable > ones if need be) and install Grub on the mbr of that HD. > When booting, press F8 (or whichever your BIOS uses) to bring up the > Boot Menu, and choose there the HD you want to boot from. I have done exactly that more than once. No chance of an 'oops' when only one disk is available for install. Just make sure it's the disk you want to write to. Just have to keep a post-it on the monitor, to remind you which HD has what ;-3) Cheers, Ron. I actually keep a small sticky label on the drive itself. ;) golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
On Sun, Jun 10, 2018 at 11:15:18AM -0500, Peter Vachuska wrote: > I really wish I had paid more attention to this thread and others warning > about the changes to X before attempting to upgrade to ascii. My preferred > way of working is out of a console running byobu and GNU screen and starting > X only when needed. This no longer works as both screen and X use virtual > terminals and instead of X starting on F7-F9, it is on F1; so that the > console terminal is unusable. So after hours of frustration yesterday trying > to get ascii working, I gave up and today reinstalled jessie only to find > that xserver-xorg-legacy had been removed from the available packages; so I > had the same problem. I had been using Devuan jessie for months and was very > happy with it. (I should remember not to try to fix things that are not > broke.) Fortunately, I had an old Debian wheezy installation which I'm now > using. > > While any suggestions would be appreciated, I'm mostly just venting > frustration. I know that my setup is atypical and console users won't > influence the direction of X. Still Dear Peter, please have a look at the ASCII Release Notes: https://files.devuan.org/devuan_ascii/Release_notes.txt which provide an explanation of the whole X.org matter and of the solutions available in Devuan ASCII. I understand the frustration, but the best way to get out of it is to do something to solve the problem. Whatever you can. Devuan has proven that we are all potential Devuan developers. This is exactly what happened with elogind, just to make an example. It was pushed into reality within a couple of months by the stubborness and committment of a few fellow devuaner. Each of them put what they had (knowledge, time, patience, attention to detail, etc.), and the result is that we all can choose among more DE alternatives in Devuan ASCII. Devuan is really what we want it to become. HH 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] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
On 06/10/2018 12:15 PM, Peter Vachuska wrote: > I really wish I had paid more attention to this thread and others warning > about the changes to X before attempting to upgrade to ascii. My preferred > way of working is out of a console running byobu and GNU screen and starting > X only when needed. This no longer works as both screen and X use virtual > terminals and instead of X starting on F7-F9, it is on F1; so that the > console terminal is unusable. If you're working on tty1, then alt-F2, log in and run startx. ctrl-alt-F1 to get back to your console. alt-F2 again to get back to your desktop. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
I really wish I had paid more attention to this thread and others warning about the changes to X before attempting to upgrade to ascii. My preferred way of working is out of a console running byobu and GNU screen and starting X only when needed. This no longer works as both screen and X use virtual terminals and instead of X starting on F7-F9, it is on F1; so that the console terminal is unusable. So after hours of frustration yesterday trying to get ascii working, I gave up and today reinstalled jessie only to find that xserver-xorg-legacy had been removed from the available packages; so I had the same problem. I had been using Devuan jessie for months and was very happy with it. (I should remember not to try to fix things that are not broke.) Fortunately, I had an old Debian wheezy installation which I'm now using. While any suggestions would be appreciated, I'm mostly just venting frustration. I know that my setup is atypical and console users won't influence the direction of X. Still 09.06.2018, 18:52, "Joel Roth" : > Colleagues! > > Earlier in this thread, we learned that installing xserver-xorg-legacy > allows you to run X the old way, as a setuid script. > > The default upgrade path from jessie -- in which X11 was > setuid-only -- migrates to a new xserver-xorg in which the > setuid mechanism is replaced. In order to run X with user > permissions in the dist-upgrade'd environment one needs to > pull in a stack of dependencies including dbus, polkit, > libpam-elogind, and elogind. > > I think it may be a bug that in the case of my upgrade > experience, neither xserver-xorg-legacy (a wrapper that > enables setuid X) nor this pam stack were installed, so > startx failed for me. Perhaps the experience is different > with a display manager installed. > > I have and use dbus apps on my system, However, as far as > I'm aware, none of these programs has root privileges. > > As the pam/dbus/elogind/polkit mechanism is capable of > handing out root authority, and as all software has bugs, I > think we _can_ anticipate that bugs that create security holes > will be uncovered in this stack. How much scrutiny did the > developers devote? Did anyone ever consider security at > through the whole stack? Probably the developers of each > component do consider security in their own code. > > openssl had a big hole for years, and before that debian's random > number generator was broken. Showstopping > holes, but the show goes on... > > Will someone who scrutinizes closer have a back door, > is that likely be true for the foreseeable future? > > In a way, running others' code is like driving: putting > oneself in the hands of strangers you've never met and > might not trust for minute in person. > > I read about the art of "fuzzing" programs with various > combinations of random inputs, to discover bugs such as > buffer overflows. This technique has been used to find bugs > and improve security in many languages. It was also used to > find hidden instructions and other attributes of > microprocessors. > > https://github.com/xoreaxeaxeax/sandsifter/blob/master/references/domas_breaking_the_x86_isa_wp.pdf > > I see fuzzing tools for dbus also available. > > I think it's an interesting security question, since the default > state of a distribution is so influential. > > That PAM is finely grained, I get, so on the surface, it > looks superior to the big club of root permissions. > > I'd be interested to links to any discussions of these > topics. I see the CVEs are published, in this example, > smb4k is being careless in arguments it passes to dbus, > leading to an exploit. > > https://nvd.nist.gov/vuln/detail/CVE-2017-8849 > > cheers > > -- > Joel Roth > > ___ > 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] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 10:48:28 -0500 goli...@dyne.org wrote: > > A work-around for your problem: > > Install each OS individually on a HD (disconnecting the other bootable > > ones if need be) and install Grub on the mbr of that HD. > > When booting, press F8 (or whichever your BIOS uses) to bring up the > > Boot Menu, and choose there the HD you want to boot from. > I have done exactly that more than once. No chance of an 'oops' when > only one disk is available for install. Just make sure it's the disk > you want to write to. Just have to keep a post-it on the monitor, to remind you which HD has what ;-3) Cheers, Ron. -- Dieu créa l'homme, et ne le trouvant pas assez seul, il lui donna une compagne pour lui faire mieux sentir sa solitude. -- Paul Valéry -- http://www.olgiati-in-paraguay.org -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan ASCII 2.0.0 stable
Congratulations to all, great work!! \o/ Antonio On 09/06/2018 14:08, Daniel Reurich wrote: Thanks to the work of my friends and fellow hackers we have another blow for freedom. An OS to truly be proud of, beautifully stable and just as it should be. Big shout out to (in no particular order) golinux, KatolaZ, fsmithred, gnu_srs, jaromil, parzyd, Evilham, NewGNUguy and many others. Superb work, and a pleasure to interact with. Eat your heart out haters and systemd fan bois!! Devuan is here to stay!!! Centurion_Dan! On 09/06/18 17:05, Veteran Unix Admins wrote: Dear Init Freedom Lovers Once again the Veteran Unix Admins salute you! We are happy to announce that Devuan GNU+Linux 2.0 ASCII Stable is finally available. Devuan is a GNU+Linux distribution committed to providing a universal, stable, dependable, free software operating system that uses and promotes alternatives to systemd and its components. Devuan 2.0 ASCII runs on several architectures. Installer CD and DVD ISOs, as well as desktop-live and minimal-live ISOs, are available for i386 and amd64. Ready-to-use images can be downloaded for a number of ARM platforms and SOCs, including Raspberry Pi, BeagleBone, OrangePi, BananaPi, OLinuXino, Cubieboard, Nokia and Motorola mobile phones, and several Chromebooks, as well as for Virtualbox/QEMU/Vagrant. The Devuan 2.0 ASCII installer ISOs offer a variety of Desktop Environments including Xfce, KDE, MATE, Cinnamon, LXQt, with others available post-install. The expert install mode now offers a choice of either SysVinit or OpenRC as init system. In addition, there are options for "Console productivity" with hundreds of CLI and TUI utils, as well as a minimal base system ideal for servers. The minimal-live image provides a full-featured console-based system with a particular focus on accessibility. The desktop-live images are the recommended option for people wanting to explore and easily install Devuan 2.0 ASCII Stable, and also for the press and those interested in reviewing the default Xfce desktop. The efforts of Devuan developers are now focused on the third Devuan release codenamed Beowulf (Planet nr. 38086). Preliminary installer images should be ready for testing soon. We would like to thank the entire Devuan community for the continued support, feedback, and collaboration. ## Download Devuan 2.0 ASCII images are available for download at: http://files.devuan.org/devuan_ascii/ and from the ISO mirrors listed at: http://devuan.org/get-devuan The latter URL also includes information about the official Devuan package repositories. ## Release Notes Devuan 2.0 Stable Release notes include brief installation and upgrading instructions, as well information on desktop session management with the introduction of eudev and elogind, and on the new mirror network accessible through "deb.devuan.org". The Devuan ASCII release notes are available at: https://files.devuan.org/devuan_ascii/Release_notes.txt ## Upgrade Direct and easy upgrade paths from Devuan Jessie, Debian Jessie, and Debian Stretch to Devuan 2.0 ASCII are available. Upgrade from Devuan Jessie: https://devuan.org/os/documentation/dev1fanboy/upgrade-to-ascii Migrate from Debian Jessie or Stretch: https://devuan.org/os/documentation/dev1fanboy/migrate-to-ascii The following will be enough to upgrade if you are already using Devuan ASCII Beta or Devuan ASCII RC: apt-get update && apt-get dist-upgrade ## Devuan Derivatives Devuan is a reliable base system chosen as a base by many derivative distributions. We are proud of the growing community of enthusiastic developers benefiting from Devuan, and would like to acknowledge some recent efforts based on Devuan ASCII: Refracta: an installable live for home computing and rescue tasks http://sf.net/projects/refracta MIYO: featuring an Awesome desktop https://sf.net/projects/miyolinux/ FluXuan: built around Fluxbox http://fluxuan.sourceforge.io/ Maemo Leste: for mobile phones and tablets, including Nokia N900/N950, Motorola Droid 4, Allwinner, and more https://maemo-leste.github.io/ DecodeOS: to build micro-services on anonymous network clusters over hidden Tor services https://decodeos.dyne.org/ A list with more Devuan derivatives can be found at: https://devuan.org/os/partners/devuan-distros ## Services offering Devuan Devuan is a snappy, stable base for virtual server applications. Several providers offer ready-to-install Devuan images on their platforms, including: Data Center Light: operated by a bunch of cool folks keen to give back to the Devuan community. They have organised Devuan hackatons and have had special offers in place on Devuan VMs https://devuanhosting.com OpenNebula: which offers Devuan ASCII guest images off their marketplace and for free http://marketplace.opennebula.org ## Contact Mailing list: https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng IRC: #devuan #devuan-dev (Freenode) Forum:
Re: [DNG] ascii 2.0 installation confused by mount points
On 2018-06-10 10:08, Renaud (Ron) OLGIATI wrote: A work-around for your problem: Install each OS individually on a HD (disconnecting the other bootable ones if need be) and install Grub on the mbr of that HD. When booting, press F8 (or whichever your BIOS uses) to bring up the Boot Menu, and choose there the HD you want to boot from. Cheers, Ron. I have done exactly that more than once. No chance of an 'oops' when only one disk is available for install. Just make sure it's the disk you want to write to. golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
A work-around for your problem: Install each OS individually on a HD (disconnecting the other bootable ones if need be) and install Grub on the mbr of that HD. When booting, press F8 (or whichever your BIOS uses) to bring up the Boot Menu, and choose there the HD you want to boot from. Cheers, Ron. -- All true wisdom is found in sig-files. -- http://www.olgiati-in-paraguay.org -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 10:18:24 -0400 Haines Brown wrote: > On Sun, Jun 10, 2018 at 12:36:02PM +0100, Simon Hobson wrote: > > > I think you may be confused about what this section is doing. You > > are telling the installer a) what to do with a disk & it's > > partitions (eg, should it format a partition), and b) where they > > should be mounted. So for your partitions on sda, you tell it NOT > > to format them and not to mount them anywhere - I certainly recall > > those being options in the Debian installer, you may need to go > > into expert mode. Alternatively, tell the installer NOT to format > > them and set a different mount point > > (eg /jessie, /jessie/boot, ...) When you set a mount point, it's > > telling the installer two things : where to mount the filesystem > > during the install, and what to put in the installed system's > > fstab. If you tell it to do nothing with the partitions/filesystems > > on sda, then they will simply be left alone - but watch put for > > grub install later on, you don't want to damage the grub that's > > already installed. So don't format the partitions on sda, don't > > mount them anywhere, and you'll end up with a new install on sdc > > that just ignores the system already on sda - but as mentioned, be > > careful when it comes to grub install time. Then (I assume through > > the system BIOS) you'll be able to boot using the old system & it's > > grub on sda, or the new system & it's grub on sdc. > > Don't underestimate my ability to get confused, especially when a > practice I've followed for years no longer works. It may be the > difficulty arises now because two of the machine's disks are for ascii > (one rc and the other stable), and jessie is on sdb. Does the conflict > over use of \ only happen if operating system versions happen to be > the same? If so, I wonder if an expert installer could be warned of > this and what to do about it. For example, the error message that > pops up could be more informative. > > In the partitioner, when I go to edit a partition, one option is to > "use as:" If I specify to use as ext4, then the additional > settings become available of whether to format the partition and set > its mount point. If instead I chose "do not use", I no longer have the > option to format and define a mount point. > > That is as you say, but your comment about watching out for GRUB later > on in the installation worries me. You warn me that I should not allow > grub to "damage" (confuse?) the grub on sda, but the installer asks a > question that I do not find to be clear. When installing GRUB and > after the installer discovers what operating systems happen to be > accessible for the installation, it tells me it is safe to install > GRUB in the mbr of the first drive, which in my case is sda. My > intent is to leave GRUB as it is on sda and to install it instead on > sdc. However, it then asks whether to install it in the mbr. To which > drive does this refer? Is it asking if I want to install GRUB in the > mbr of the first drive, sda, or is it asking simply whether to > install GRUB the mbr on whatever drive I next install GRUB? > What you are talking about doing is akin to dual-booting, just on different disks i.e. you will only be able to boot one distro. Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 12:36:02PM +0100, Simon Hobson wrote: > I think you may be confused about what this section is doing. You are > telling the installer a) what to do with a disk & it's partitions (eg, > should it format a partition), and b) where they should be mounted. > So for your partitions on sda, you tell it NOT to format them and not > to mount them anywhere - I certainly recall those being options in the > Debian installer, you may need to go into expert mode. Alternatively, > tell the installer NOT to format them and set a different mount point > (eg /jessie, /jessie/boot, ...) When you set a mount point, it's > telling the installer two things : where to mount the filesystem > during the install, and what to put in the installed system's > fstab. If you tell it to do nothing with the partitions/filesystems on > sda, then they will simply be left alone - but watch put for grub > install later on, you don't want to damage the grub that's already > installed. So don't format the partitions on sda, don't mount them > anywhere, and you'll end up with a new install on sdc that just > ignores the system already on sda - but as mentioned, be careful when > it comes to grub install time. Then (I assume through the system > BIOS) you'll be able to boot using the old system & it's grub on sda, > or the new system & it's grub on sdc. Don't underestimate my ability to get confused, especially when a practice I've followed for years no longer works. It may be the difficulty arises now because two of the machine's disks are for ascii (one rc and the other stable), and jessie is on sdb. Does the conflict over use of \ only happen if operating system versions happen to be the same? If so, I wonder if an expert installer could be warned of this and what to do about it. For example, the error message that pops up could be more informative. In the partitioner, when I go to edit a partition, one option is to "use as:" If I specify to use as ext4, then the additional settings become available of whether to format the partition and set its mount point. If instead I chose "do not use", I no longer have the option to format and define a mount point. That is as you say, but your comment about watching out for GRUB later on in the installation worries me. You warn me that I should not allow grub to "damage" (confuse?) the grub on sda, but the installer asks a question that I do not find to be clear. When installing GRUB and after the installer discovers what operating systems happen to be accessible for the installation, it tells me it is safe to install GRUB in the mbr of the first drive, which in my case is sda. My intent is to leave GRUB as it is on sda and to install it instead on sdc. However, it then asks whether to install it in the mbr. To which drive does this refer? Is it asking if I want to install GRUB in the mbr of the first drive, sda, or is it asking simply whether to install GRUB the mbr on whatever drive I next install GRUB? Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 08:55:55 -0400 Haines Brown wrote: > On Sun, Jun 10, 2018 at 10:05:48AM +0200, Didier Kryn wrote: > > Le 10/06/2018 à 04:01, Haines Brown a écrit : > > >On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: > > >>Haines Brown wrote: > > >> > > >>>In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a > > >>>primary partition that is bootable and the mount point /. > > >>You probably want to set this partition to unused (or whatever > > >>it's > > > called, it's a looong time since I last did this) so that it > > > doesn't appear in the mount point table (eventually in fstab of > > > the new install). I think what you are telling it is that you > > > want sda1 to mounted as / IN THIS INSTALLATION and that then > > > clashes with your new / (on sdc) that you're trying to install to. > > > In the partitionner (which is not only a partitionner, but > > generates the fstab and the filesystems), you should select "dont > > use the partition" on every partition which is not in sdc. Click on > > "use partition as" and select "dont use the partition". > > Didier, that seems to have done the trick. I apologize for having been > too hasty. Where the partitioner asks what to use a partition as, > because the top options were simply file systems, I interpreted it to > be merely for selecting file system and did not notice the "don't > use" option at the bottom. When I marked sda partitions not to be > used, I was able to save the sdc partition table and proceed with the > installation. > > Now that installation of ascii 2.0 on sdc is underway and before going > further I must figure out how to recover a use of partitions on sda. I > assume that were I to use the menu to revert to partitioning and > restore usage of sda partitions I'll just end up with the same > problem of a competition of sda and sdc for use of /. > > When I execute a shell toward the end of installation, can I use it to > run the command "parted /dev/sda set 1 boot on" both to enable sda1 > and to make it bootable at the same time? Would the command > "parted /dev/sda set 2 on" simply re-enable the second partition? I > found the parted manual unclear on this point. > I am fairly sure you will need to set up grub2 to do this, try reading this: https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk Or failing that, google for the answer ;-) Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan ASCII 2.0.0 stable
On 10-06-18 14:27, Jaromil wrote: > > this weekend the news of our release made a splash on community fora, > namely hackernews https://news.ycombinator.com/item?id=17274623 where > our effort was always heavily denigrated and mocked, now starts > emerging some reasonable feedback. And last not least slashdot where > Bruce Perens declared his endorsement for Devuan 8^D > https://linux.slashdot.org/story/18/06/10/0321233/systemd-free-devuan-20-ascii-officially-released > > I recommend those who like can participate to the discussions with > maturity and respect for other people ideas, as much as we claim > respect for our own ideas, which we have shown being able to follow > with clear action. > Discussion at slashdot is a waste of time nowadays (I do have a 5 digit uid from the time ./ had some merits). Most common argument is all distro's are using systemd so it must be good. Which is a poor argument without much hope for some usefull discussion anyway. Grtz. Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 10:05:48AM +0200, Didier Kryn wrote: > Le 10/06/2018 à 04:01, Haines Brown a écrit : > >On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: > >>Haines Brown wrote: > >> > >>>In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary > >>>partition that is bootable and the mount point /. > >>You probably want to set this partition to unused (or whatever it's > > called, it's a looong time since I last did this) so that it doesn't > > appear in the mount point table (eventually in fstab of the new > > install). I think what you are telling it is that you want sda1 to > > mounted as / IN THIS INSTALLATION and that then clashes with your new > > / (on sdc) that you're trying to install to. > In the partitionner (which is not only a partitionner, but generates the > fstab and the filesystems), you should select "dont use the partition" on > every partition which is not in sdc. Click on "use partition as" and > select "dont use the partition". Didier, that seems to have done the trick. I apologize for having been too hasty. Where the partitioner asks what to use a partition as, because the top options were simply file systems, I interpreted it to be merely for selecting file system and did not notice the "don't use" option at the bottom. When I marked sda partitions not to be used, I was able to save the sdc partition table and proceed with the installation. Now that installation of ascii 2.0 on sdc is underway and before going further I must figure out how to recover a use of partitions on sda. I assume that were I to use the menu to revert to partitioning and restore usage of sda partitions I'll just end up with the same problem of a competition of sda and sdc for use of /. When I execute a shell toward the end of installation, can I use it to run the command "parted /dev/sda set 1 boot on" both to enable sda1 and to make it bootable at the same time? Would the command "parted /dev/sda set 2 on" simply re-enable the second partition? I found the parted manual unclear on this point. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Postgresql problem
On Sun, Jun 10, 2018 at 10:40:44AM +0200, J. Fahrner wrote: [cut] > > After (ID_LIKE=debian): > -- > supported-versions: WARNING! Unknown distribution: devuan > debian found in ID_LIKE, treating as Debian > -- > > Looks like debian must be written in lower case. > Would be nice if Devuan could add this in base-files package. > Just fixed in base-files 9.9+devuan2.5. Already available from the repos. Please update. 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
[DNG] Devuan package information
Dear D1rs, just to let you know that the Devuan infrastructure include a new service: https://pkginfo.devuan.org which allows to access information about the package available in Devuan. It's very basic, and we plan to improve it with time, but gets the job done, somehow. 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] Devuan ASCII 2.0.0 stable
ahoy! On Sat, 09 Jun 2018, Irrwahn wrote: > Veteran Unix Admins wrote on 09.06.2018 07:05: > > Dear Init Freedom Lovers > > > > Once again the Veteran Unix Admins salute you! > > > > We are happy to announce that Devuan GNU+Linux 2.0 ASCII Stable is > > finally available.[...] > > Omedetō gozaimasu, Devuan ASCII! to the list of thanks Daniel mentions, I'd like to add you as well Irrwahn for all the patient help you offered to this release and together with your also Andreas Messner. Yours is the merit of Devuan's desktop being less and less entangled by DMs/policykit mess. this weekend the news of our release made a splash on community fora, namely hackernews https://news.ycombinator.com/item?id=17274623 where our effort was always heavily denigrated and mocked, now starts emerging some reasonable feedback. And last not least slashdot where Bruce Perens declared his endorsement for Devuan 8^D https://linux.slashdot.org/story/18/06/10/0321233/systemd-free-devuan-20-ascii-officially-released I recommend those who like can participate to the discussions with maturity and respect for other people ideas, as much as we claim respect for our own ideas, which we have shown being able to follow with clear action. Since the release was made just at the beginning of a weekend, tomorrow a press release will be circulated on the devuan-announce list, hoping it will be easier for journalists to pick it up on office hours. > Gochisōsama deshita! ;^P -- Sapere aude! -- Denis Roio a.k.a. Jaromil http://Dyne.org think tank Ph.D, CTO & co-foundersoftware to empower communities Book keynotes, lectures, workshops: https://jaromil.dyne.org ⚷ crypto κρυπτο крипто गुप्त् 加密 האנוסים المشفره GnuPG: 6113D89C A825C5CE DD02C872 73B35DA5 4ACB7D10 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] I wish good things for Devuan
Just wanted to drop the maintainers a note. Keep up the great work. I've been dealing with some really crazy issues during OS installs and upgrades of **NON** Devuan systems in the past couple months. Its hard to believe how broken, discombobulated and simply messed up things have become. From unintelligible error messages to inexplicable stability issues, it's like going through a syslog from the late 90s. At work, Unfortunately, one of our main stacks runs a modified Linux distro so I don't get to pick the OS it runs on. After one particular day, and several failed attempts at upgrading and installing, I pulled the Devuan ISO onto the box. It installed, booted, initialized, mounted, started and shutdown perfectly. I was concerned all the issues I was having may have been hardware related, but they weren't. They are simply due to a system which is built on a house of cards. Keep up the great work. Devuan has picked up where Linux left off. -- Sent from a Mobile device.___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
Haines Brown wrote: >> You probably want to set this partition to unused (or whatever it's >> called, it's a looong time since I last did this) so that it doesn't >> appear in the mount point table (eventually in fstab of the new >> install). I think what you are telling it is that you want sda1 to >> mounted as / IN THIS INSTALLATION and that then clashes with your new >> / (on sdc) that you're trying to install to. > > In "typical usage:" option when configuring the root partition, there is > no option that would disable it. In any case, I don't want to disable > it, but to be able to boot any disk and use its grub menu to boot it or > any other disk. I've always been able to do that. I think you may be confused about what this section is doing. You are telling the installer a) what to do with a disk & it's partitions (eg, should it format a partition), and b) where they should be mounted. So for your partitions on sda, you tell it NOT to format them and not to mount them anywhere - I certainly recall those being options in the Debian installer, you may need to go into expert mode. Alternatively, tell the installer NOT to format them and set a different mount point (eg /jessie, /jessie/boot, ...) When you set a mount point, it's telling the installer two things : where to mount the filesystem during the install, and what to put in the installed system's fstab. If you tell it to do nothing with the partitions/filesystems on sda, then they will simply be left alone - but watch put for grub install later on, you don't want to damage the grub that's already installed. So don't format the partitions on sda, don't mount them anywhere, and you'll end up with a new install on sdc that just ignores the system already on sda - but as mentioned, be careful when it comes to grub install time. Then (I assume through the system BIOS) you'll be able to boot using the old system & it's grub on sda, or the new system & it's grub on sdc. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Postgresql problem
Am 2018-06-10 09:26, schrieb Ralph Ronnquist: The first google match suggests adding ID_LIKE=Debian to /etc/os-release Worth a try perhaps? Sounds good. Before: - supported-versions: WARNING! Unknown distribution: devuan /usr/share/postgresql-common/supported-versions: 66: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set /usr/share/postgresql-common/supported-versions: 69: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set Please submit this as a bug report to your distribution. -- After (ID_LIKE=Debian): -- supported-versions: WARNING! Unknown distribution: devuan Please submit this as a bug report to your distribution. -- After (ID_LIKE=debian): -- supported-versions: WARNING! Unknown distribution: devuan debian found in ID_LIKE, treating as Debian -- Looks like debian must be written in lower case. Would be nice if Devuan could add this in base-files package. Jochen ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Postgresql problem
J. Fahrner wrote on 10/06/18 17:20: Hi, when installing/upgrading postgresql packages, there is the following warning: supported-versions: WARNING! Unknown distribution: devuan /usr/share/postgresql-common/supported-versions: 66: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set /usr/share/postgresql-common/supported-versions: 69: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set Please submit this as a bug report to your distribution. Any ideas where to fix this? The first google match suggests adding ID_LIKE=Debian to /etc/os-release Worth a try perhaps? Ralph. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Postgresql problem
Hi, when installing/upgrading postgresql packages, there is the following warning: supported-versions: WARNING! Unknown distribution: devuan /usr/share/postgresql-common/supported-versions: 66: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set /usr/share/postgresql-common/supported-versions: 69: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set Please submit this as a bug report to your distribution. Any ideas where to fix this? Regards Jochen ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
