-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cybis install issue. #116
Comments
As mentioned in the thread, the cybis install script uses fixed user index numbers beginning at 30B or 31B, yet creating users using defaults (k.c,username) after install basic, but before cybis, with UI=0 during creation, defaults to user index 30B. Fixes: adjust UI numbers for cybis into something that won't conflict on an installed/running system with local user accounts, not defaults, if cybis is installed as an afterthought. Alternately, the initial default UI for modval could be changed to not conflict with an after-the-fact install of cybis. I am actually wondering if by following basic->everything else->cybis build order, things aren't in some other account like netadm or any other that was created with said hardcoded UIs, and just not in my personal account, after rebuilding and having to do users and files on three instances, instead of one instance, built minimal, loaded with users and files, the, built up into two chains, with and without cybis, propagating the initial user/file load. |
Historically, special/privileged user accounts tended to be assigned low UI
values, so it's not surprising that CYBIS wants 30B and 31B. I'll create a
modset for MODVAL that starts auto-assigned user UI's at a higher value,
e.g., 100B.
…On Sat, Jan 6, 2024 at 10:30 AM KC5VDJ ***@***.***> wrote:
As mentioned in the thread, the cybis install script uses fixed user index
numbers beginning at 30B or 31B, yet creating users using defaults
(k.c,username) after install basic, with UI=0 during creation, defaults to
user index 30B.
Fixes: adjust UI numbers for cybis into something that won't conflict on
an installed/running system with local user accounts, not defaults, if
cybis is installed as an afterthought.
Alternately, the initial default UI for modval could be changed to not
conflict with an after-the-fact install of cybis.
—
Reply to this email directly, view it on GitHub
<#116 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABALGRLXV5LSPI2INTVQ7LYNFNX5AVCNFSM6AAAAABBPS2SBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZG4YTGNBQGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sounds like a fix! Thanks. |
New modset NCCAUI has been added to the collection of NOS modifications. NCCAUI ensures that automatically selected UI's begin at 171B. To apply this modset to a previously installed NOS 2.8.7:
Then shutdown NOS 2.8.7, rename tapes/newds.tap to tapes/ds.tap, and re-deadstart NOS 2.8.7 |
Discussed in #115
Originally posted by KC5VDJ January 4, 2024
The green highlighted files appeared in my personal account after adding cybis and just cybis. Apparently this happens in the following build orders: basic -> ses, cybis, everything else; and, basic -> everything else, cybis.
This is based on Jan 2 after the textmode console commit.
The first build order, I may have been logged in during install, the second, definitely not (wasn't sure about the first time, so I didn't, not that I can see how it would make any diff).
Accounts and my PFs (cyan, except opllist and syslist, which are itemize listings of opl871 and system after all was said and done) added after basic was installed, before any optional installs.
If it matters: node install-product -s -f cybis
Without it previously having been installed; after install basic, and adding local accts by x.modval on the console, local pfs into the local accts (doubt this part matters), followed by optionals beginning with ses first, followed by the cybis install, apparently without regard to optionals installed between ses and cybis.
The text was updated successfully, but these errors were encountered: