Skip to main content ↑ ↓
Topic: Wrong memory reported on terminal screens (Read 3384 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Wrong memory reported on terminal screens

I've noticed that when I switch virtual temrinal CTL F4 for example, it has this nice little diagram of the Artix 'A'  and some stats on the machine and they are wrong.  They have only half my ram.

neofetch when I run it by hand, however, is correct.

Re: Wrong memory reported on terminal screens

Reply #1 –
I guess the /etc/issue file was generated a long time ago (during the installation?) and was never updated after the amount of RAM changed.

Re: Wrong memory reported on terminal screens

Reply #2 –
so it is lieing to me :)

Re: Wrong memory reported on terminal screens

Reply #4 –
Quote
neofetch >| /etc/issue' in /etc/rc.local


why the bar?

Re: Wrong memory reported on terminal screens

Reply #6 –
Quote from: Ambie – on
Quote from: mrbrklyn – on
why the bar?
This form of output redirection always rewrites existing file no matter how configured noclobber option.


OK - teach me something new.  How do you do a no clobber option on a file other than chmod 000

I was interesing because I didn't use the bar and it said, despite using sudo, that I didn't have permision.  I had to su - in to overide it.  So there is some wrinkle in file permissions I failed to understand.

Re: Wrong memory reported on terminal screens

Reply #7 –
noclobber isn't a file permission, it's a shell option (see man 1 set, -C option). What you're experiencing isn't related to any permissions on the file itself, but to the fact that redirections like > and >> are done by the user's shell, before sudo is executed. Since sudo is an external command while the angled brackets are keywords, the latter get processed first.

For instance, despite echo running as root, file is created under my user because it was created at the shell's permission level.

Code: [Select]
$ sudo echo > file
$ ls -la file
-rw-r--r-- 1 carlos carlos 1 abr 15 20:24 file

That's you you had to switch to su, which gives you a root shell; with it, the redirections are done as root. Another way is to embed the redirection into a sh snippet that is then called with sudo.

Code: [Select]
$ sudo sh -c 'echo > root_file'

Online guides tell you to something | sudo tee root_file instead of just using the redirection operators for a similar reason: tee runs as root, and then opens the file for writing.


As an s6 fan, I can't not mention one could use execline's chain-loading commands (which can replace shell operators) alongside sudo:

Code: [Select]
$ sudo redirfd -w 1 root_file echo

Re: Wrong memory reported on terminal screens

Reply #8 –
Neofetch is discontinued. Fastfetch would be a better choice.

Re: Wrong memory reported on terminal screens

Reply #9 –
Quote from: Caramon2 – on
Neofetch is discontinued. Fastfetch would be a better choice.

Code: [Select]
Optional dependencies for fastfetch
    chafa: Image output as ascii art
    dbus: Bluetooth, Player & Media detection [installed]
    dconf: Needed for values that are only stored in DConf + Fallback for
    GSettings [installed]
    ddcutil: Brightness detection of external displays
    directx-headers: GPU detection in WSL
    glib2: Output for values that are only stored in GSettings [installed]
    hwdata: GPU output [installed]
    imagemagick: Image output using sixel or kitty graphics protocol [installed]
    libdrm: Displays detection [installed]
    libelf: st term font detection and fast path of systemd version detection
    [installed]
    libpulse: Sound detection [installed]
    libxrandr: Multi monitor support [installed]
    ocl-icd: OpenCL module [installed]
    python: Needed for zsh and fish completions [installed]
    vulkan-icd-loader: Vulkan module & fallback for GPU output [installed]
    xfconf: Needed for XFWM theme and XFCE Terminal font [installed]
    zlib: Faster image output when using kitty graphics protocol [installed]

That is NOT encouraging.  There is  NO REASON for all of this.
 
Code: [Select]
flatbush:[ruben]:~$ sudo pacman -S neofetch
warning: neofetch-7.1.0-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) neofetch-7.1.0-2

Total Download Size:   0.08 MiB
Total Installed Size:  0.33 MiB
Net Upgrade Size:      0.00 MiB

Yeah that is MUCH more sensible of a design.  no depenecies

Re: Wrong memory reported on terminal screens

Reply #10 –
Quote from: mrbrklyn – on
There is  NO REASON for all of this.
There is a reason. To add features. If those features are desired some would say it's folly to reinvent the wheel and completely replicate/rewrite the code needed to implement them, hence the dependancies. Some would disagree and prefer to have total control over the code used.
From what little I know about yourself, and your distrust of the progression of the the Linux ecosystem, I'd say stick with neofetch.
This is in no way intended as criticism .

Re: Wrong memory reported on terminal screens

Reply #11 –
Quote from: gripped – on
Quote from: mrbrklyn – on
There is  NO REASON for all of this.
There is a reason. To add features.

There are no system characteristics that can't be read by either reading the proc directory or other system source.

There is no logical reason for this spaghetti dependency for a simple commandline program. 
The emotional reason is because if you are Nat Freidman or Miguel de Icaza  et al ... it is a hammer/nail problem.  Everything is a dependency because  if  your a free desktop coder you learned all this dependency and you probably don't even know how to read proc files or the system libs.  It is not just feature bloat... it is bad programming design being covered up as a "new" way to do it.

Quote
Neofetch is discontinued.

FWIW - and it is not worth all that much, where is it written that neofetch is discontinued.  It seems active enough in the repo.

Quote
This is in no way intended as criticism .

It is appreciated, but I am way past worrying about personal criticism.   I stopped worrying about these things when I was targeted by a large group of people who wanted to kill me and my entire family for being Jewish.  It was a sobering moment about the overall state of humanity.  You merely have an opinion which I disagree with based on deep history and lifetime of learning about how to a execute technological problem to create a pretty picture on the boot up of a workstation.  I would never hate you for your opinion.  I do appreciate you being a gentleman about it.

Re: Wrong memory reported on terminal screens

Reply #12 –
Are you honestly comparing fastfetch's optional dependencies (most of which are already needed for a desktop anyway, and you've already got installed) with neofetch's mandatory dependencies?

fastfetch + yyjson is an order of magnitude smaller than neofetch + bash.

BTW, try looking into the dependencies of the programs neofetch calls sometime. You'll be horrified to find... fastfetch's optional dependencies.

Quote
FWIW - and it is not worth all that much, where is it written that neofetch is discontinued.  It seems active enough in the repo.

...the very top of the upstream URL. Last commit was to bid farewell in 2024, and the second to last commit was 4 years prior.

https://github.com/dylanaraps/neofetch

Re: Wrong memory reported on terminal screens

Reply #13 –
Quote from: mrbrklyn – on
There are no system characteristics that can't be read by either reading the proc directory or other system source.
Add 'easily' to that and you are right. Clearly the dependencies are achieving it programmatically.
IMHO not all dependencies are evil attempts to sully my system but I respect your right to disagree.