The "Linux questions (and other stuff)" thread


Last Updated: 2015-05-27 11:42:02
  1. Speed Daemon

    Speed Daemon Disabled

    One good reason is because not everyone uses Linux, so being able to scrub out malware in a relatively secure environment is a good practice. Linux powers many file and web servers that Windows and Macintosh computers connect to. I know that I wouldn't want to find out from an irate client that I gave them some malware!

    While Linux itself is relatively secure (if you patch it religiously and practice good basic security protocols), there have been some Linux exploits. (The word "virus" is hopelessly out of date.) I'd rather have ClamAV scan my Linux machines' filesystems from time to time just in case.

    Advertisement
  2. Speed Daemon

    Speed Daemon Disabled

    By practicing the same basic security protocols on my Windows NT machines, I've never had any of those infected with any malware either. A little common sense can do a lot of good.
  3. saptech

    saptech Well-Known Member

    Also if you're using linux desktop and connecting or trading files with Windows machine, it wouldn't hurt to have an antivirus program installed.

    I've never had a virus on my linux machines since the mid 1990s, but I've never had one on my Windows machines either. Well once, my teenage son did get one visiting porn sites. I've never ran a virus scanner on linux but did try ClamAV just to see how it ran.
  4. mikedt

    mikedt 你好 Guide

    Most those seem to be experimental or proof of concepts from the late 90s. Or they involve the users doing something, like opening a malicious document, code injection. Hopefully no Linux users are running something like OpenOffice, or internet browser, or IM, or e-mail client with root privileges, e.g. "$ sudo openoffice" :rolleyes: Which is something Windows does by default. all software runs with admin/root privileges. Although MS have tried to stop that.

    As a teacher in China, I'm always opening potentially malicious and dangerous documents. I'm using Linux, but if LibreOffice or MS Office on Wine, suddenly asked for my root password, because of some document trying to do something to the system. I'd immediately know, something is wrong here.

    This why logging in as root is always a bad idea. I've never had to do that. Login as root is sometimes hidden in certain distros, to protect novice users from themselves, and you don't need it anyway.
  5. MoodyBlues

    MoodyBlues - Crazy peacock person - Guide

    How does NT compare to *nix in terms of its inherent security, vis-
  6. mikedt

    mikedt 你好 Guide

  7. nickdalzell

    nickdalzell Well-Known Member Contributor

    if i double click on a JPG in Ubuntu, it opens up whatever picture viewer is default, just like windows. i don't believe executable exists in Linux--everything is a file!

    Now our college used and we were required to have our own version (trial) of WinNT 4 and Win2K and i do know the Guest account cannot even set the system time! much less change sensitive info. a 'user' in Linux (i do not recall there being sub-groups in *nix such as guest, power user, and so on just user and root) has more power. a 'user' can use his own user password (Ubuntu does not set a separate root password in its installer ) to sudo anything. there is no security when a person can simply use a generic user password to gain even temporary root priviledge, which can be dangerous in itself. but i don't see too many Linux users complaining about problems the way Windows does.
  8. mikedt

    mikedt 你好 Guide

    Oh it definitely does. :) Appications are certainly executable on Linux, e.g. Chrome. Just that they don't usually have any file suffix. .bin might be used sometimes, to indicate a binary/executable file.

    Here's the file permissions for a JPG, it's actually my AF avatar. This is on Mint, which is Ubuntu based.
    [​IMG]

    Everyone can open it and look at it, but they can't change or modify it, or change the file permissions. The only users who can do that are "michael" (me) and root. Note that "make the file executable" is unchecked. The OS would never try to run it, even if there was code hidden inside.


    You are the "administrator" for your own system, in the absence of a corporate sysadmin. And so the user password is the sudo and root password for your own system. You can set a seperate, password and admin/root account if you want for Ubuntu. There's nothing stopping you from doing that. Which is what enterprise users would do.
  9. MoodyBlues

    MoodyBlues - Crazy peacock person - Guide

    That's not what mikedt is referring to. Automatically opening a JPEG in the default image viewer is not the same thing as executing a JPEG. It's the image viewer that's being executed in this scenario, not the image FILE.

    Nope! Want a quick, very brief, and not all-inclusive lesson on Linux file attributes?

    Every file--and this includes directories, because they're files, too--can have three types of permissions, for three sets of users: read/write/execute for user/group/others. So let's say you have a bash script saved as a file named do_this in your home directory, and its permissions look like this:

    Code (Text):
    1. -rwxr-xr-x 1 nick users 248600 2013-01-17 22:45 do_this
    See the rwx? Those are the permissions for you (user), and they signify read, write, and execute. Then see the two r-xs? Those are for group and others, and they signify read and execute permission only. You can do anything you want to this file, including editing it or deleting it, while everyone else can look at its contents and can execute it, but they can't modify or delete it.

    Just keep in mind that [just about] anything micro$oft has is [probably] a rip-off, and [usually] a very POOR implementation, of something that originated in *nix. :eek:

    *nix has always...always provided for different levels of authority, everything from who could write to tape drives to who could log in only on a terminal and not the server. Again, anything m$ has likely originated in UNIX.

    No, that's not how it works. Only a user who has been granted the right to use sudo can use it. Typically, that person would be the one in charge of administering the system.

    Ubuntu and its offspring decided that making it harder to enable a true root login would lead to less catastrophe from windows converts. While I certainly see their point, I still think it's a stupid, unnecessary step. As I've said elsewhere, as soon as I install any *buntu or derivative on a new computer, I give root a password AND I enable root logins. I'm a big girl. I don't need hand holding at this point! :laugh:
  10. nickdalzell

    nickdalzell Well-Known Member Contributor

    and what if that user tried to use the sudo command and entered his/her own password? same problem
  11. palmtree5

    palmtree5 Sunny Vacation Supporter! Moderator

    If they just typed sudo, they would get usage instructions
  12. MoodyBlues

    MoodyBlues - Crazy peacock person - Guide

    No, that's not how it works. As I said, a user has to be granted the right to use sudo in order to use it. If they're not in the sudoers file, they can't use the command.
    palmtree5 likes this.
  13. nickdalzell

    nickdalzell Well-Known Member Contributor

    BTW Moody how is this thread going to work when it has like three different subjects going at once? how do you sort it in one thread?
  14. saptech

    saptech Well-Known Member

    You're a female and know a great deal about Linux??? Wow, I'm in luv! :rolleyes:
  15. MoodyBlues

    MoodyBlues - Crazy peacock person - Guide

    Good question! Unfortunately, I don't have a good answer. In fact, I don't have ANY answer. :D I guess people who either have a question about, or think they can answer questions about, Linux will pop in here and see what's up.
  16. saptech

    saptech Well-Known Member

    It is a cli command to backup partitions to another device or partition.

    http://www.fsarchiver.org/QuickStart

    example command:

    Thnx.
  17. saptech

    saptech Well-Known Member

    Can it be a subfolder under the Lounge folder like the others there? Then when someone have a certain question, they can create a new Thread. Similar to how the Politics, Computer & IT, and the others are designed.

    Just a thought!
  18. Prinny

    Prinny Resident Linux Nutcase Guide

    Posting in this so I can keep up with it on TT ;)

    I do have a question though. This is more generic than having to do with bash and whatnot. Well sort of. Anyway!

    Source based distros (Gentoo, Sourcery, etc.) Do you think that they are better than distros such as Ubuntu? I understand that Gentoo and the like are not for your average/novice Linux user. I tried Gentoo, and I for the life of me could not get it to work.

    Regardless. Which do you think is better for the most part? Or is it one of those "case to case" things?
  19. mikedt

    mikedt 你好 Guide

    This why we "quote" whom we're responding to. So everyone can follow a particular subject or conversation. If not, I'd just assume it's a response to the OP, or the post above, or it's just a general comment for the thread. It's something we've always done for usenet and mailing lists, and forums are not really any different.

    Your post mentioned Moody, but I felt it needed an answer that I could give. :)
  20. saptech

    saptech Well-Known Member

    I think Source based distros are relevant to those that only want to install what they need. In a server operation this could work out for the benefit if you need specific compilation on the hardware you're using.

    The average users really don't need it, plus with newer hardware may not be worth it.

    Sourcemage is my favorite SBD, but I haven't messed with it a couple of years.
  21. MoodyBlues

    MoodyBlues - Crazy peacock person - Guide

    Yep, last time I looked, I was female! :eek: :laugh: And I've been a *nix-ster since 1985. I actually switched career paths because of UNIX. Long story, but I needed a break before starting medical school, one thing led to another, and I ended up in a created-just-for-me position at the furniture store chain where I worked [doing data entry] while in college. I transitioned them off their IBM System/3s, creating a multi-location and, of course, multi-user UNIX system. I did everything--installing hardware, administering the system, programming, all of it. That was my favorite job ever.

    I occasionally ruminate over the fact that I always intended to be a physician, and I essentially blew 5 years of hard work [A student, with honors] in pre-med, but for the most part I'm fine with it. When something comes up, like the brain tumor I had, I do find myself wishing I had gone on with med school so I could be more involved in my care, but those thoughts are few and far between.
    saptech likes this.
  22. nickdalzell

    nickdalzell Well-Known Member Contributor

    i started when i was in college, heard about this 'Free' OS for awhile and found linux.org (site seems to have changed owners and looks completely different now) and downloaded Basiclinux, my first distro--had to compile everything. X windows actually booting up without a WM or DE was at the time something to be proud of at least for me, and using the links browser in frame buffer graphics mode was a feat in engineering in BL. but unfortunately it was not ready to replace Windows. that did not end up happening 100% until a few days ago. but i did distro hop in and out of Windows space a bit, i bought the complete Red Hat 7 set, six discs with a couple for source code, every app that was available in the repos at time of release. wow. but eventually Netscape couldn't keep up so back to Windows i went. also, RH 7 wouldn't run Bearshare--it would load the app but it would not connect. and that was a heavy used app at the time. also, my CD Burner refused to play nice with the old software it had. suddenly having every app released at the time of the disc set was not as impressive as it was when i bought it. i later burned the first Ubuntu, of course being stupid, as a deer lover myself i liked the name Feisty Fawn. but it really had zero support for a very used Compaq 1200 series. no support for PCMCIA, USB wifi, or anything i used. but it did have sound and the video going. but without internet was essentially useless. back to Windows. then came Mandriva. hard disc decided to go into an infinite activity loop and the distro refused to boot, couldn't fsck either as it woule auto reboot when entering root password. back to Windows. well you can see what ended up happening by my past threads here.
  23. argedion

    argedion The TechnoFrog VIP Member

    recently working on a project that called to find out if a file existed or not I had no idea of how to do this in Linux. Not being always the sharpest tool in the shed I tried several ways and failed miserably. I searched a little but since I suck at searching (never know really what to ask) somehow though i seemed to have found my way and its really simple.

    here is a test condition to find if a file exist or not using bash

    if [[ -e "filename" ]] ; then
    true
    else
    false
    fi

    just thought I would share for those who didn't know :D
  24. nickdalzell

    nickdalzell Well-Known Member Contributor

    there is also the 'whereis' command that is a lot less complicated:

    $>whereis startx

    bash: /usr/X11/startx

    if the file did not exist it would be like:

    $>whereis foo

    bash: no such file or directory
  25. MoodyBlues

    MoodyBlues - Crazy peacock person - Guide

    Is it okay if I post the contents of your PM here? Do you even still need help with it? Putting it here will benefit others, too, plus someone besides me can chime in! :D

Share This Page