> X-Yandex-FolderName: Inbox > Received: from postback4b.mail.yandex.net (postback4b.mail.yandex.net > [2a02:6b8:c02:900:1:45:d181:da04]) > by s2aesvjp6okmqy6k.sas.yp-c.yandex.net (notsolitesrv/Yandex) with > LMTPS id XC5rmRsrAb1Z-PHFe1YVW > for <ba...@yandex.ru>; Fri, 02 May 2025 18:28:20 +0300 > Received: from mail-nwsmtp-mxfront-production-main-89.sas.yp-c.yandex.net > (mail-nwsmtp-mxfront-production-main-89.sas.yp-c.yandex.net > [IPv6:2a02:6b8:c11:43b9:0:640:cd42:0]) > by postback4b.mail.yandex.net (Yandex) with ESMTPS id 25937609C4 > for <ba...@yandex.ru>; Fri, 2 May 2025 18:28:20 +0300 (MSK) > Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com > [2a00:1450:4864:20::630]) > by mail-nwsmtp-mxfront-production-main-89.sas.yp-c.yandex.net > (mxfront/Yandex) with ESMTPS id bRaJJ18ExOs0-fILp2w5s; > Fri, 02 May 2025 18:28:19 +0300 > X-Yandex-Fwd: 1 > Authentication-Results: > mail-nwsmtp-mxfront-production-main-89.sas.yp-c.yandex.net; spf=pass > (mail-nwsmtp-mxfront-production-main-89.sas.yp-c.yandex.net: domain of > gmail.com designates 2a00:1450:4864:20::630 as permitted sender, > rule=[ip6:2a00:1450:4000::/36]) smtp.mail=icepic...@gmail.com; dkim=pass > header.i=@gmail.com > X-Yandex-Spam: 1 > Received: by mail-ej1-x630.google.com with SMTP id > a640c23a62f3a-ace94273f0dso467988466b.3 > for <ba...@yandex.ru>; Fri, 02 May 2025 08:28:19 -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20230601; t=1746199699; x=1746804499; darn=yandex.ru; > h=content-transfer-encoding:cc:to:subject:message-id:date:from > :in-reply-to:references:mime-version:from:to:cc:subject:date > :message-id:reply-to; > bh=T+FTcU5Xo+HrGQ5TLZdq7sR4aQHC2XitEf2OYB8xA5M=; > b=A2Nti+x4GZt/bRvpOtZh1/ibKasJgurp7ieUFMgaYtqIP68MIkrDsjyO8w96HIRVqf > 2q9sO/j/ke6cHPWjUvqKtq4IOWqxjyR/nBPQBMwOMHscWxnHL5YVmd8QQ0UkVaz6SPXd > 7sKGh/e2kMHcf1+MaUoZTKaNzt8cZFfFVZQRgwY4MhokjijAw8QcwnS29m7C6hL51j5i > bpeK0ZsG+aVgYA7i8JD2LvDloRSh9QdJy/eAi+yRommoyBCs9eNLPyWN028Esci+Ogqt > 98WcnS/QlDB5AsEW73dFnWeMKqbiXONK8IX3jnqONAN7vUenV4J9M1LE/QofXGSPRQJq > lf3g== > X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=1e100.net; s=20230601; t=1746199699; x=1746804499; > h=content-transfer-encoding:cc:to:subject:message-id:date:from > :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc > :subject:date:message-id:reply-to; > bh=T+FTcU5Xo+HrGQ5TLZdq7sR4aQHC2XitEf2OYB8xA5M=; > b=jzB5vx33ck3gtXewLzN9fI2Fj8N1/lgt0OVVi4H2kil/DCRUCTD6g2ksa7C7Q57S7U > MyyrrhXdRMJZAX8CmVIjtLn0iLrvg09/irkpobPV09dUPO0r12M1Cu0dJvo/H81rTtk3 > b4QdpL291+RPWpiaNcX8KcCG17oUiABe1z7UjqBP7knZXx/y2lBVH5roTGeL0J0hhqpa > N0r+LjNUPPydEmgJsZ7ESQah+xdfdgGHPzzGLccEwcHYUK85ggG1cR2NRzK8QRJ48z5G > vLrJb+V9Xcg5ljnaISQQ8ck0vI/WpIjUNG+scHwsHvxPdoiRbuLoAyrg84egJIS+Bax1 > AS0w== > X-Gm-Message-State: AOJu0YzfJDLTOWPnOynsYSWRGOLeJW7UrXh6D4s/P/XOJbfRGTJuQXMr > > I0CJlsWJ+zdoJaId5xum9y94KeAbqVTPLByO4NxVvigANMfIE5Bm5srQAgygcc1exn4gZFHWH5i > uwKbZeC8IRhcjTx+bjkxgUQeggJKO4A== > X-Gm-Gg: ASbGnct2/x6u9mphomzS1FJ10/DFcGqTryzHj5x2lIJCbKC9AosEA23rFcJs4oNdH5n > > bAh/uOd1qDjeuLw/2dAMo60sYzE4iz+8USpGd33f7jFiRuaK0IySIhYnXDGo/G5lLRCzqieepvw > 2DL2IU1vepkN2VJWM1JRANeTbPkrfFLkIOWJc+DF9hlruXvICW/zh1jusVDGg+vvX1Swc= > X-Google-Smtp-Source: > AGHT+IFcTII2AAZV5kgimf+f3YMmRa9JfKaaq2mZ3Mm/Gk9lzb/SnpbZ4SDXrJ7Yra48XlLUZhTQfTa/0JpYZGiqleU= > X-Received: by 2002:a17:907:1999:b0:acb:b966:3a8f with SMTP id > a640c23a62f3a-ad17af47f9fmr313158266b.39.1746199699138; Fri, 02 May 2025 > 08:28:19 -0700 (PDT) >> when smtpd starts, but there are some problems with dns(i fixed it, so i >> don’t know what exactly the problem was), then a complete stop of the os >> loading is another brilliant find or is daemon_timeout still needed there by >> default? > If the daemon needs dns to work, like smtpd, then waiting for dns > before moving on seems like a decent idea. If you don't depend on dns, > or want to make sure you can move past during boot, then feed > /etc/hosts with needed info so it doesn't have to resolve externally > in order to get the answers it needs while starting up. the problem is that i do not know what exactly smtpd wanted. running with the -dv keys showed nothing and nowhere- it was very informative, an excellent debugging implementation. but i assumed it was the dns and guessed right. i'm very dumb, and therefore it doesn't seem like a good idea to me that any optional daemon can stop the operating system boot process. especially when the mission-critical sshd is not loaded first and we simply lose access to the system.
>> ps: i take this opportunity to congratulate everyone on the new version. >> with the new version, in which ugen is still broken, and when installing >> applications and transferring settings from 7.6 i got a kernel panic out of >> the blue- this hasn't happened for a long time ^.^ > It could just be slightly helpful for people to spend less time > talking about crashes they have gotten and quote the crash text more, > at least if one wants to pretend to care about improvements for this > OS. i realized that no one is interested in improving this os. look at ugen- the problem has been described, there have been attempts to solve it, but for several years now the problem has been moving from release to release. i'm really afraid that pointing out the problem won't lead to fixing it, but to deleting everything it's related to. because this is the way. i've seen it more than once
