I first installed Ubuntu 4 or 5 on a Thinkpad T42 with 512 MB of RAM. I used it until about version 10, when they forced everyone to use left-handed window controls. It all ran about as well as XP did on that machine. Might be unsafe to bring online, nowadays, but if it gets borked do you really care?
Are they installed on separate drives? Depending on the exact setup, Linux and windows both generally support legacy as a boot method, so you may be able to just BIOS to select a boot drive.
Looking up the specs of a D270, looks like the memory is upgradable.
It also looks like the Intel Atom N2600 it has (from my reading) is actually a 64-bit processor
I’d probably say you shouldn’t have much trouble finding a bigger DDR3 memory stick for it for dirt cheap or free from an e-wasted notebook
Ultimately it depends if the performance loss you’re finding is memory limited or CPU limited right now, but I would think that giving it 2 or 4GB + giving it 64-bit would go a long way
Hey man, I think this is a perfectly valid question to ask here. Also I was one of the people who replied on the other thread as well.
So, let’s start with the why. I imagine you want to have ~/Downloads be inside your large disk so files get automatically downloaded there, I imagine ~/Documents is to have access to the same documenta on both OSs. If that’s not the why or there’s something else let me know as I’ll be basing my answer on this assumption.
Last time we told you about how you can mount things wherever you want to, I imagine by now you have an entry on your fstab that automatically mounts that NTFS drive somewhere. I’ll call that somewhere /ntfs just to give it a name/path, but any other path should be the same.
If you wanted your ENTIRE NTFS partition to be on ~/Downloads it’s as easy as changing that fstab entry from /ntfs to /home/gpstarman/Downloads (or whatever your username is). But I imagine you want something more complex, you want to have /ntfs/downloads and ~/Downloads to be the same directory.
Like you found out there are two ways to do this, the first and most easy one is to create a link. To do so graphically just open whatever file explorer you use right click and drag from one path to the other and you should have an option link here or something similar. Note that you might need to delete or rename your existing ~/Downloads folder to have the link be named that. If you wanted to do it by command line it’s ln -s <target> <link name>, so in your hypothetical case ln -s /ntfs/downloads ~/Downloads
This should work for 99% of cases and honestly I don’t think you should care too much about mounting. I’ll reply to this comment with the steps for mounting and explaining why it’s different just to be on the safe side.
For mounting it’s a bit trickier, just like you added an entry to fstab to say that you wanted to mount (for example ) /dev/sdb2 on /ntfs you would need to add another one saying you want to mount /ntfs/downloads to /home/<username>/Downloads. If you want to run this as a one off the command is mount --bind /ntfs/downloads /home/<username>/Downloads (but note that running this with a command will become undone when you reboot, the only way to preserve it after reboots is to have an fstab entry)
What this does is essentially at the kernel level say that one path is the other. How is this different from a link? Well, a link is just a file that points to the other place, whereas a mount is the other place. A couple of examples on how this is different:
If you had a Download folder you would need to rename or delete it before making a link there. Mounting on the other hand necessitates that the Downloads folder exists, and will obfuscate anything inside it while the other folder is mounted. This means that if you had files inside Downloads and you mounted the other folder on top those files are still in the disk, but you have no way of accessing them until you unmount the folder.
Links can’t go outside of your system. This is likely not important to you, but if you for example are doing things with chroot or docker this can become a problem.
In short, a link is like a door that when you open it tells you “go to the other door”, whereas the mount is replacing the room behind that door with another one. Most programs are smart enough to go to the other door, and on most cases the other door exists so all is good. On some edge cases (like I said, docker, chroot, etc) the “go to door X” could be a problem if inside the client system X doesn’t exist.
Ps: I don’t know of any way of doing this graphically, this is advanced stuff so likely it’s expected that people who want to mount folders know enough to do it in a terminal
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.