Re: [DNG] ascii 2.0 installation confused by mount points
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 "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. It occurs to me that I could simply disconnect the SATA cable from my sda and then partition sdc and after installation reconnect sda and run update-grub on the disks. But I hesitate to do it because then the sda/sdc identity of the disk would change and I might end up unable to boot either disk. Another approach might be to boot sda run fdisk on sdc and then do an installation on sdc without partitioning it. Incidentally, on sdb I have have installed an old Debian (Etch?). When I try to partition sdc it does not want to use its root partition. only the root partition of sda. I suspect something has changed between Jessie and Ascii. The partitioner in devuan install I suppose is parted, but not sure. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)
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
Re: [DNG] ascii 2.0 installation confused by mount points
On 06/09/2018 01:13 PM, Haines Brown wrote: I'm installing ascii on a disk, sdc, in a machine that has two other disks, one of which, sda already has a bootable devuan jessie on it. The installation goes well until I go to write my partitioning of sdc to disk. I get the error message: "Two file systems are assigned to the same mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), partition #1, (sdc). It is true that partition 1 of sda is a bootable primary partition, and I want to do the same for sdc. I've always had multiple independently bootable disks with their own GRUB on a machine. This is the first time I've run into trouble with it. In installation options for sdc, I did ask to have a MBR installed. Why does an installation on one disk care about what happens to be on another unmounted disk? You are using fstab and assigning the partitions how you want them to be used? -- Jimmy Johnson Devuan ASCII - TDE Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263 ___ 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: > 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. ___ 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 Sat, Jun 09, 2018 at 10:19:01PM +0200, Didier Kryn wrote: > Le 09/06/2018 à 22:13, Haines Brown a écrit : > >I'm installing ascii on a disk, sdc, in a machine that has two other disks, > >one of which, sda already has a bootable devuan jessie on it. > > > >The installation goes well until I go to write my partitioning of sdc to > >disk. I get the error message: "Two file systems are assigned to the same > >mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), > >partition #1, (sdc). > > > >It is true that partition 1 of sda is a bootable primary partition, and > >I want to do the same for sdc. I've always had multiple independently > >bootable disks with their own GRUB on a machine. This is the first time > >I've run into trouble with it. In installation options for sdc, I did > >ask to have a MBR installed. > > > >Why does an installation on one disk care about what happens to be on > >another unmounted disk? > > First, check carefull y what you do in the partitionning dialog. sda > shouldn't be used at all by the system you install, but I suspect you have > maybe marked it as used in some way. Thanks, Didier, In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary partition that is bootable and the mount point /. When I edit this partition, it says it is on sda. Disk sdc is ST1000MN0011, and it also has a bootable partition #1. When I edit it, it says I'm editing disk ST1000MN0011 partition #1 of sdc. I give it / as mount point, make it bootable, and the label "root". Partition #1 on sda is has mount point /, the mount options I leave as the defaults, label I left out the label, but now label it "root". This should make no difference as far as I can see. I leave typical usage as "stardard". I don't know what standard options refers to, but I should think standard option would not cause this disk to interfere with others. But I get the error, "Identical mount points for two file systems." 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
Le 09/06/2018 à 22:13, Haines Brown a écrit : I'm installing ascii on a disk, sdc, in a machine that has two other disks, one of which, sda already has a bootable devuan jessie on it. The installation goes well until I go to write my partitioning of sdc to disk. I get the error message: "Two file systems are assigned to the same mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), partition #1, (sdc). It is true that partition 1 of sda is a bootable primary partition, and I want to do the same for sdc. I've always had multiple independently bootable disks with their own GRUB on a machine. This is the first time I've run into trouble with it. In installation options for sdc, I did ask to have a MBR installed. Why does an installation on one disk care about what happens to be on another unmounted disk? First, check carefull y what you do in the partitionning dialog. sda shouldn't be used at all by the system you install, but I suspect you have maybe marked it as used in some way. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ascii 2.0 installation confused by mount points
I'm installing ascii on a disk, sdc, in a machine that has two other disks, one of which, sda already has a bootable devuan jessie on it. The installation goes well until I go to write my partitioning of sdc to disk. I get the error message: "Two file systems are assigned to the same mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), partition #1, (sdc). It is true that partition 1 of sda is a bootable primary partition, and I want to do the same for sdc. I've always had multiple independently bootable disks with their own GRUB on a machine. This is the first time I've run into trouble with it. In installation options for sdc, I did ask to have a MBR installed. Why does an installation on one disk care about what happens to be on another unmounted disk? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [OT] Re: (forw) [GoLugTech] Microsoft buys GitHub
On Sat, 9 Jun 2018 19:56:50 +1000, Andrew wrote in message : > On 09/06/18 15:49, Jimmy Johnson wrote: > > There's something fishy about this story. > > https://www.bbc.co.uk/news/technology-44368813 > > It was first published on June 5th and now dated June 6th, I first > > read the story on June 5th at the same link. Not recoverable, not > > repairable or so they say ..not true, that yellow wire flange design looks like it made for ROV intervention, which makes those white cylinder easily accessible for submarines from e.g. North Korea, Russia or the US, who knows... ;o) > > and who's data will be stored there? ...not to mention "who's expert-banned technology"... ;o) > > I don't know abut you but the only one I trust to store my data is > > me and I'm backed-up since '94 on 3 external and 2 internal drives > > with no problems and it's safe to say I'm a pack rat. > > archive.org has 30 different snapshots so far. > > https://web.archive.org/web/*/https://www.bbc.co.uk/news/technology-44368813 > > Your earliest "5th June" version may be one of the earlier 6th June > entries depending on your timezone. ..try go thru all 30(?) captured versions to see how the narrative evolves, the first version mentioned impact on global warming, some versions mention how corrosion is [hopefully] avoided in the absense of water vapors and oxygen (it should slow, and change character), no version mentions any use of pressurization to keep water out, nor on how such pressurization impacts cooling and coolant fan performance, disk motor power use with any extra "air" drag, so I doubt we have seen the final version of BBC's story here. -- ..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 2.0.0 stable
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! Yet another important milestone on the (init) freedom road. A big thank you to all the fine folks that made this happen!!! Gochisōsama deshita! ;^P -- Sapere aude! signature.asc Description: OpenPGP digital 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
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 > >
Re: [DNG] Devuan ASCII 2.0.0 stable
On Sat, 9 Jun 2018 at 07:05:12 +0200 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. I did notice: $ lsb_release -d Description:Devuan GNU/Linux 2.0 (ascii) [...] > We would like to thank the entire Devuan community for the continued > support, feedback, and collaboration. Great job! Thank you to all the team members and supporters! Alessandro ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [OT] Re: (forw) [GoLugTech] Microsoft buys GitHub
On 09/06/18 15:49, Jimmy Johnson wrote: > There's something fishy about this story. > https://www.bbc.co.uk/news/technology-44368813 > It was first published on June 5th and now dated June 6th, I first read > the story on June 5th at the same link. Not recoverable, not repairable > or so they say and who's data will be stored there? I don't know abut > you but the only one I trust to store my data is me and I'm backed-up > since '94 on 3 external and 2 internal drives with no problems and it's > safe to say I'm a pack rat. archive.org has 30 different snapshots so far. https://web.archive.org/web/*/https://www.bbc.co.uk/news/technology-44368813 Your earliest "5th June" version may be one of the earlier 6th June entries depending on your timezone. Cheers A. signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
