Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


hybrid last won the day on April 7 2015

hybrid had the most liked content!

Community Reputation

189 Excellent

1 Follower

About hybrid

  • Rank
    Linux-Noob Frequent Member

Previous Fields

  • Distribution
    Debian, CentOS, others!

Profile Information

  • Gender
  • Location
    Hampshire, UK
  • Interests
    Passionate about building great things — code, writing, user experiences and more. Slightly obsessed with Macs, Linux, computer security and fonts.

Recent Profile Visitors

3,509 profile views
  1. What you've described looks like a great way to partition your hard drive! To get access to your NTFS files, as feedmebits says, you should be able to just click it and (possibly) enter your password and see the files right away. Do you see it (if it has a name, or something like '1TB volume') listed in the sidebar when you are looking at your files? Who is telling you to install pysdm?
  2. hybrid

    Hi Everyone

    Hello and welcome! Thanks for your introduction -- we're quite the 'small' community at the moment, but we hope we'll prove more helpful and less RTFM-focused than others! I've found the best way to learn new stuff is to pick little projects for yourself. Get excited about some cool thing, play around with it, break it, fix it, break it again, fix it, until you really understand what you're doing. I've been following that sort of cycle since I started with Linux -- over time you start to pick up a wide body of knowledge, and more importantly, get a sense of where to look when things go wrong. So, if there's anything you're playing with on Linux, or any crazy ideas, do let us know, and we'll see if we can help! If I'm a little slow in responding to another thread you make, poke me in this one, as I'll now get email updates. Again, a very warm welcome. Let's play Linux!
  3. The first thing I would do here is temporarily set debug_options in the Squid configuration file to a higher level. I played with Squid a while back now, but I always found that it did tend to spit out a lot of useful information in the log file. If you set that and restart Squid and try to access the site in question, we will then get a lot more information that might help track down what actions Squid is taking, and in what order. Also, could we see the whole squid config file (redacted, if necessary)? Perhaps this particular ACL is working, but it is being overridden by something else that is being given higher priority due to where it is in the file.
  4. Apparently, it isn't possible to map multiple Samba users to one Unix user while also having separate passwords for the Samba users. https://lists.samba.org/archive/samba/2011-March/161335.html Separate accounts and force group works well for me, though. Yes, you have to create the Unix users one time, but they are locked down appropriately with /sbin/nologin as their shell, and any user with the right group membership can access files anyone has dropped in the folder.
  5. So the first thing we need to identify is where the SSH port is being made unavailable -- is it in SSH itself, or a firewall? What port are you expecting SSH to be running on? The default, port 22? In rescue mode, you can examine the SSH config file by typing this at the prompt, and pressing Enter: less /etc/ssh/sshd_config You can use Space to scroll down a screen, and press 'q' to quit looking at the file and go back to the prompt. We're looking for the 'Port' line to verify what port SSH thinks it's running on. We should check to see if SSH is enabled. Running: update-rc.d ssh enable Were any firewall changes made by you, or the hosting provider?
  6. Potentially stupid question on my part -- did you go through an install, or just boot into Ubuntu to try it out when the CD was in? If you did go through an install, it sounds like Ubuntu might be installed, but there is no boot loader. The boot loader would give you the list of choices as to which operating system you want to use when you start up. This isn't too difficult to fix in terms of what you actually need to do, but it's a little bit fiddly. (If it's too fiddly, maybe a reinstall will help. Perhaps we can help you pick the options and notice if there are any problems installing the bootloader.) To see if Ubuntu is installed, could you, from Windows, do Start > Run > compmgmt.msc > OK. Then if you look for Disk Management in the left, could you screenshot what you get there? We'd be looking for a partition of a reasonable size that you created where Ubuntu is hiding. (Windows will probably see it as 'unknown' in some way).
  7. Just out of interest, can you configure RDP on the Windows side to not drop the connection on 'logout'? In my testing, when I log out of Windows inside the RDP session, the session itself closes. Perhaps I'm missing something obvious; avoiding the connection dropping at all and just making it look like a 'Windows machine' for all intents and purposes would seem ideal.
  8. Perhaps removal of the LXDE panel (commenting out the @lxpanel line above), combined with re-enabling pcmanfm for the desktop, and just having desktop shortcuts for reconnecting or shutting down might solve your issues around people fiddling. Once LXPanel is disabled and a 'blank' desktop background chosen, it really does feel barren (and scary?), such that it might look like nothing is 'there' to play with, except the two shortcuts you leave on the desktop.
  9. I've had some success with LXDE and Remmina to make the Pi a RDP client straight from switch-on. There is a caveat -- once the user disconnects the RDP session, they might need to double-click an icon on the LXDE desktop to re-establish the connection. Install Remmina Remote Desktop client sudo apt-get install remmina Configure the Connection Open up Remmina, and set up a 'connection' to your RDP server (Connection > New). Check it works by connecting, then close Remmina. Browse to the ~/.remmina folder to find the name of the new .remmina file for this connection. You can rename it to something more friendly - I'll call it server.remmina. Configure Remmina for Autostart Edit the file /etc/xdg/lxsession/LXDE/autostart, so that it reads: @lxpanel --profile LXDE #@pcmanfm --desktop --profile LXDE @xscreensaver --no-splash /bin/sh -c "remmina -c ~/.remmina/server.remmina" Configure the Pi to boot to GUI Use raspi-config to configure the Pi to boot straight to the GUI. Also use these instructions to configure auto-login for the user account. (For security, consider adding a separate user account for the RDP login use that does not have sudo privileges, and auto-login to that user instead of the admin-capable one.) --- Now we have a Pi that boots straight to the GUI, logs in, and immediately launches Remmina which connects over RDP to the target system we set up earlier. The caveat, as I mentioned, is that once Remmina quits, the user is left at the LXDE screen. Perhaps a shortcut/launcher to Remmina, called 'Reconnect', needs to be left on the desktop, which launches remmina -c ~/.remmina/server.remmina. Also, users may need to be educated about how to shut down the thin client. Perhaps another desktop shortcut which shuts down the Pi could solve that?
  10. Welcome! I'm just wondering how far you've got so far with LXDE -- is it working, but you're just wondering if there's something more lightweight? If it does work right now, is it that the performance is too slow, or that there are other desktop-y things getting in the way of it just loading up immediately and swiftly? I'm happy to meddle with this on my own Pi, but I'd love to know how far you've got and what the goal is. My thoughts are perhaps Window Maker, to avoid a whole desktop environment and just have a window manager, which auto-starts RDesktop. If this sounds interesting, I'll have a play on my Pi and let you know how it goes.
  11. hybrid

    Hello Everyone

    Welcome Darshik; it's great to have you here! When first investigating the terminal, doing some simple file management is often a good place to start. If you open up the Terminal, you'll be in your home folder normally, which we represent with a ~ character. You might see in the terminal window something like: your_username@your_machinename:~$ This is the prompt -- and the ~ tells us we are in your home folder. The $ just tells us that the prompt is finished; the next thing you type will be a command. So, when you see a $ sign in people's tutorials involving the command line (like my snippets below), that means you don't type it in. It's just there to show you which bits are commands (lines that start with $) and which bits aren't! The first command to explore is pwd, which stands for print working directory. This tells you, more clearly than the ~, which folder you're currently in. I might see this: $ pwd /home/hybrid To see the contents of the current working directory, we can use ls to get a list: $ ls (You'll see what's in your home directory.) If I want to move into another folder, I use cd (for change directory): $ cd Documents (you may have to spell it with the right capitalisation, too!) Now, pwd again shows I have moved: $ pwd /home/hybrid/Documents We can create an empty file by touching it. After typing the name of the touch program, I press space, and the next thing it expects is the name of the file to create or update. I'll make one called new_document. $ touch new_document (I'm avoiding the complications of files with spaces and special characters in them for now!) To see the files in this folder, I can, again, ls it: $ ls The new file should appear in the list! You could also play with cp for copying the file, or even a simple text editor in the command line like nano (the keyboard shortcuts are listed at the bottom of the screen, where ^ means Ctrl+. So, to quit nano, you press Ctrl+X.) If you have any particular ideas about where you want to go next with the command line, let's hear 'em! We'd love for you to share your experiences with learning this cool stuff.
  12. Welcome to the forums! We're glad to have you here! sysctl net.ip4v.tcp_syncookies You've already noticed and pointed out that the issue here was mistyping ipv4 as ip4v, but I thought I'd clarify that was the issue here for anyone else reading. It happens to us all.
  13. Interesting that you've used NFS for file storage. I'm always in a multi-OS environment so Samba is the file sharing standard I need to use to get the required level of compatibility! How are you getting on with NFS for accessing your media? Was setting it up anything like this, or have things changed since then?
  • Create New...