bizdelnick

joined 1 year ago
[–] bizdelnick@lemmy.ml 35 points 2 months ago* (last edited 2 months ago) (1 children)

What does an ordinary RHEL admin do when something does not work?

answersetenforce 0

[–] bizdelnick@lemmy.ml 1 points 2 months ago

"Easy to use" means that you do less and get more. Learning doesn't count if you learn something once and then use the skills you obtained many times.

[–] bizdelnick@lemmy.ml 0 points 2 months ago (2 children)

No, some piano plays are still harder than others, mo matter how long you practice. Editing text with vim is easier than with nano after some practice.

[–] bizdelnick@lemmy.ml 1 points 2 months ago

Why do you think so?

[–] bizdelnick@lemmy.ml -4 points 2 months ago (6 children)

It is easier after you learn basics. Learning is not easy, but usage is.

[–] bizdelnick@lemmy.ml 14 points 2 months ago (2 children)

Every day in my case, except holidays.

[–] bizdelnick@lemmy.ml 36 points 2 months ago (23 children)

Vim (or emacs, or any other advanced text editor) is much easier to use than nano when you need to do something more complex than type couple of lines.

[–] bizdelnick@lemmy.ml 6 points 2 months ago (2 children)

What error you get exactly?

[–] bizdelnick@lemmy.ml 8 points 2 months ago

If you didn't push your changes yet, you can use git filter-branch to remove it from all your commits. If you already pushed (or figured out that someone committed and pushed a key), you can do the same with force-push, but also revoke the key.

[–] bizdelnick@lemmy.ml 1 points 3 months ago

There are few fdisk options that work non-interactively, like -l (list partitions). It is impossible to create or delete partitions this way.

From the sfdisk man page:

Since version 2.26 sfdisk supports MBR (DOS), GPT, SUN and SGI disk labels

[–] bizdelnick@lemmy.ml 3 points 3 months ago (2 children)

fdisk is completely interactive, not suitable for scripting. sfdisk is a "scriptable fdisk".

[–] bizdelnick@lemmy.ml 2 points 4 months ago (1 children)

Technically, no. Until you want to mount something but find /mnt is busy or simply forget about this and mount something there, losing access to previously mounted stuff. The only problem is that you have to remember which mountpoint you use for particular filesystem, while the FHS is designed to avoid this and abstract from physical devices as much as possible.

view more: ‹ prev next ›