tuxd3v | hello guys, | 03:34 |
---|---|---|
tuxd3v | I wanted to know if there are any guidelines about users, and passwords by default for devuan? | 03:35 |
tuxd3v | the idea, to streamline everything :9 | 03:35 |
tuxd3v | :) | 03:35 |
yeti | only using de??an? | 04:02 |
yeti | I hate when the default install of (e.g. RasPIan) uses ID 1000 for a default user. | 04:03 |
yeti | then I wanted to use 999 instead... as my main nonRootish admin user | 04:04 |
yeti | it had gropup 999 == SPI | 04:04 |
yeti | stuff should grow upwards, so I expected it to be free on every resonnable debian sibling | 04:04 |
yeti | reasonnable and raspian in one sentence might have benn the problem | 04:05 |
yeti | :-Þ | 04:05 |
yeti | and mixing oses is the next problem | 04:05 |
yeti | PkgSrc allocates users for server and similar in the range 1000++ | 04:05 |
yeti | NetBSD's default range for (real existing?) users? | 04:06 |
yeti | only base system stuff is below 1000 | 04:06 |
yeti | so currently I'm #10000 on BSDs and #1000 on reasonable de??an siblings | 04:06 |
yeti | *sigh!* | 04:06 |
yeti | a more portable strategy would be nice | 04:07 |
yeti | like FHS but for useraccounts | 04:07 |
yeti | wait a bit and we'll all be UUIDs only... | 04:10 |
yeti | :-/ | 04:10 |
tuxd3v | ifconfig | 04:10 |
tuxd3v | damm sorry.. :/ | 04:10 |
tuxd3v | Well that is yet a broader subject indeed, interesting and I feel a necessity.. | 04:11 |
tuxd3v | Nowadays majority of Linux distros alocate normal users 1000++ | 04:11 |
tuxd3v | and system users till 999 | 04:12 |
tuxd3v | but yes, not all system users in all distros have the same uid, its yet a mess, some standard on that would be nice, even tought that we already have lots of them fixed.. | 04:13 |
tuxd3v | what are the BSD you use? :) | 04:13 |
yeti | systemd-coredump:x:996:996:systemd Core Dumper:/:/usr/sbin/nologin <<< raspian | 04:13 |
tuxd3v | well.. yes with systemd.. things get nasty | 04:14 |
yeti | spi, i2c, gpio, systemd-coredump (groups) from 999 downwards | 04:15 |
yeti | so already a mess in the de??an dimension | 04:15 |
yeti | other systemd-accounts are in the 100+ range therew | 04:16 |
yeti | why systemd-coredump gets a special treatment is unknown to me | 04:16 |
yeti | otherwise I'd have said they allocate hardware related stuff 999-downwards | 04:16 |
yeti | for standard users and services we need a global consensus like for port numbers and such | 04:17 |
yeti | or ugly UUIDs for everything | 04:18 |
yeti | put users in the DNS too | 04:18 |
yeti | @datakraken-14.0 | 04:18 |
yeti | meh... | 04:18 |
yeti | I'm sooo damn happy not to work in IT any more... it luckily is hobby only! | 04:19 |
onefang | All you need to do is get everyone to agree on this new standard of yours. | 04:19 |
yeti | https://xkcd.com/927/ | 04:19 |
yeti | debian has something like that | 04:20 |
* yeti demands that raspian be based on gentoo instead | 04:21 | |
yeti | far far away from me | 04:21 |
onefang | That would be rasptoo then. | 04:22 |
yeti | systemd-coredump:x:998: <<< debian10 | 04:22 |
yeti | so != rasPIan | 04:22 |
yeti | mess^mess | 04:23 |
yeti | that really shalt not happen in the same "flavour" of OS | 04:23 |
tuxd3v | Now deal with raspberry ethernet interface name 'enxb757bc88e596' in my case... nuts | 04:26 |
yeti | horror sapiens breaks everything. | 04:27 |
tuxd3v | now imagine you administrating a park of machines that all of them have names like that...be happy remembering all them.. :) | 04:27 |
tuxd3v | you need a dns resolver only for that :D | 04:28 |
yeti | or a.l.f.r.e.d. | 04:28 |
yeti | :-D | 04:28 |
yeti | https://www.open-mesh.org/projects/alfred/wiki | 04:29 |
yeti | ok... but if there is a non-root-default-user, please dont put that on #1000 | 04:35 |
yeti | maybe even debian should add that in a wenn known location of their default passwd/group files | 04:36 |
yeti | weLL | 04:36 |
yeti | hunter2:*:1337:1337:... | 04:37 |
yeti | mwhuahahahahahaaa.... | 04:37 |
amesser | Jenkins server complains early during the build, that it cant connect to gitea | 11:49 |
amesser | https://ci01.dev1.cloud/view/failing/job/devuan-package-builder/478/console | 11:49 |
gnu_srs2 | Hello, what is the link for how to issue a build? | 21:06 |
gnu_srs2 | eudev-3.2.9-9~beowulf1 | 21:06 |
golinux | gnu_srs2: Maybe it's in here https://git.devuan.org/devuan/documentation/src/branch/master/maintainers | 21:26 |
gnu_srs2 | golinux: Thanks, I found the link to build there: https://git.devuan.org/devuan/documentation/src/branch/master/maintainers/JenkinsAutobuild.md | 21:46 |
gnu_srs2 | Problem is I could not build for Label: beowulf-proposed-updates: eudev-3.2.9-9~beowulf1. Instead eudev-3.2.9-9 is built again when choosing Label:unstable. | 21:49 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!