New functions and..

I installed openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20150318-Media.iso. I had a lot of problems. Partitions and…

Well I shouldn’t comment Thumbleweed, but I got very irritated when I was ask “top command”:

http://www.jodo.nu/pic/pic2/snapshot55.jpeg

Htop? Dident serve what I to used to and cant evaluate on this information.

Well I have been right on a:
-problems brtfs and winxp
-problems about brtfs and snapshot
-problems about systemd, I was questing the function(yearly) up and it ain’t getting any better. Who will understand/decode (above screenshot)?

regards

There seem to be an increasing number of color freaks. These are people who want plain text to be colored, and prefer color choices that are hard to read.

The man pages for top seem to indicate that you can turn this off with a command line option, and I suppose you could use a shell alias to make that your default.

The top in tumbleweed is like this by default, and it is horrible. : ( I’ve moved to htop.

fwiw

in terminal mode, with the user background default color set to white,
the top cmd display looks ok

On 03/22/2015 01:56 AM, nightwishfan wrote:
>
> nrickert;2700885 Wrote:
>> There seem to be an increasing number of color freaks. These are people
>> who want plain text to be colored, and prefer color choices that are
>> hard to read.
> The top in tumbleweed is like this by default, and it is horrible. : (
> I’ve moved to htop.
>
>

I have to agree, it is horrible. But you can change the colors.

Ken

My post was not about colors in Konsole.

My post was about that systemD have attracted its way in (now even by top) to become a default in next version.

As I mentioned, “now I have foresee”. Oh When will systemD=Linux?

As long as it works (it doesn’t), I hate to find solutions/research (my opinion) tool for read inf in binary logs. I have experience when I was troubleshooting MySQL a couple of mount’ ago.

regards

I think you are misreading that.

You are seeing the output sorted by PID. You are used to seeing it sorted by %CPU, and you can change it to show that.

If sorted by PID, then of course systemd will be at the top (process 1).

Sorry, but you’re talking nonsense here.

Systemd is already the default init system since 12.1. And it is the only option since 12.3.
It is not on its way “to become a default in next version”.

What you see in your screenshot is the process tree. You’d see something similar if you’d choose “Processes (tree view)” in KDE’s system monitor or run “htop”, even in 13.1/13.2 (well, even in 12.1, 12.2, and 12.3). And in earlier versions you would see the same too, but just with “init” instead of “systemd”.
When you are booting, the kernel only runs “init” (which is systemd). All other processes are started by init (systemd) then, so they are children of init (systemd). This is how Linux works since it was invented, nothing new there.

Why the tree view is now default in top I don’t know. You can switch to other views easily (press ‘<’ e.g.), and I’m sure you can change the default as well somehow though.

If you don’t like the new defaults, you should better file a bug report.

As long as it works (it doesn’t), I hate to find solutions/research (my opinion) tool for read inf in binary logs. I have experience when I was troubleshooting MySQL a couple of mount’ ago.

Then install rsyslog or some other syslog daemon and browse your text log files again…

Dear nrikert and wolfi323.

I’m about to take out my tin-foilhat from the wardroup and stand in the nearest corner for at least 10 minutes.

Why? Because I cant make my point. Mea culpa. Mea maxima culpa.

Oh I would like to make a bugzilla report on systemd. I would like to report the totally unnecessary info in YaST installation when set up a disk at install. Now even at “top” in Thumbleweed. If I’m are lost how will newbies feel?

Yupp! Wait at least another 18 month and hear/read “live with it”. For me top is essential and I can read out mem info like total/free/cached.

regards

What “totally unnecessary info in YaST installation” do you mean here? And how this is related to systemd?

If you mean the list of subvolumes in the default partitioning when using btrfs, that’s totally unrelated to systemd either.
So it makes no sense to report a bug against systemd regarding this.

Now even at “top” in Thumbleweed. If I’m are lost how will newbies feel?

Again, all processes are children of init (i.e. systemd nowadays in openSUSE) since ever Linux exists, and even before that in Unix.
Nothing to do at all with systemd.
Just that the init process (PID 1) is called systemd now, because systemd is the init system.
And top only displays the running processes, that’s its purpose. If systemd is running, it will of course display systemd. It’s not that systemd “invaded” top or something.

But that’s the problem with you “systemd-haters”… You read systemd somewhere and immediately it’s a new conspiracy by systemd to take over the world… :stuck_out_tongue:
(this sentence is not meant particularly serious though… :wink: )

Regarding your comment about “newbies”, I wonder how many newbies even know about top…

Yupp! Wait at least another 18 month and hear/read “live with it”. For me top is essential and I can read out mem info like total/free/cached.

Again, there surely is a way to configure the default view in top. Have a look at “man top” maybe.
And also again, you should file a bug report against top if you don’t like top’s default, not systemd…

To see the configuration options for top, press “?”.

To save your current config, press “W”.

You can change all of the stuff that you don’t like this way, including disabling colors and hiding the CPU/memory bar graphs.