You are not logged in.
I happen to have Google Earth installed, first the CE, now the Pro version. But since a few weeks/months it's broken. I can launch the application just fine as root, but as normal user, it hangs/crashes. This indicates a permissions issue. It started after upgrading GE via the Google repo 2 versions ago. Upgrading to the latest version didn't help, it probably made it worse. I'm aware Google wants GE phased out and everyone using Maps instead, so they can kill GE like everything else they've launched ![]()
As it happens, I have downloaded version 7.3.3.7786-r0 (Juli 2020) but alas, installing that didn't solve the issue either. I also have version 6.something, from April 2012 (!!) but that relies on the ia32 libs.
Any ideas solving this?
you can install nginx as a standalone package, as are other server-related packages like mariadb, PHP, etc
nginx and apache can safely co-exist on the same machine, but require careful configuration to avoid competing for port access
Not used Timeshift, so can't advise you on that, but the partitioning looks OK to me. ![]()
Not using EFI. Works fine, all my systems work w/o EFI. The installer recognizes there's no EFI partition, so Grub will use a regular MBR-style install instead.
EFI mandates an M$ file system (FAT). They made sure (read as: paid sh#tloads of money) only FAT was specified in the EFI standard, so until the standard changes to allow non-M$ file systems, I refuse to use EFI.
But that's just me being old school I guess ![]()
Yeah, that'll be good. I didn't take account of EFI, as I'm not using it myself.
Is there valuable data on that LVM partition that needs saving? If not, wipe the whole lot (i.e. delete all partitions on sda).
Partition sda as follows:
sda1: 512MB for /boot
sda2: 48GB for /
sda3: 8GB for swap
sda4: remainder for /home
Partitions sda1, sda2 and sda4 need a file system, choose one from the list: ext4, jfs or btrfs. You can mix different file systems, just ensure the appropriate tool package is installed (ie.e jfsutils, btrfs has a similar package). This allows the kernel to control and check the file system.
CPU and RAM are not particularly connected to JFS, but being a journaling file system the required checks take time if you have low RAM and/or a low capacity CPU. Make sure you have the jfsutils package installed, but given you can boot eventually I think it already is.
Modprobe is usually a symlink to kmod. See if that's the case on your system:
ls -l /sbin/modprobeThe output should look like this:
lrwxrwxrwx 1 root root 9 Jan 8 2021 /sbin/modprobe -> /bin/kmodIf it doesn't, see if kmod itself is there:
ls -l /bin/kmodThat should show this:
-rwxr-xr-x 1 root root 170168 Jan 8 2021 /bin/kmodNote that the numbers&dates shown will differ from your system, that's not important. If you don't get the first output but do get the second one, create the required symlink so modprobe will work:
ln -s /bin/kmod /sbin/modprobeOf course, all of the above commands as root!
However, I'm beginning to wonder if you're installing in a container, like Docker, Proxmox, Unraid or similar? If so, your network connections should be done in a whole different way.
Your modprobe command probably needs to be 'sudo modprobe ...'
No, he's already root. Modprobe should already be installed, as it's a core functionality of a kernel, any kernel.
Do note that ethernet NIC's are named ethX where X is a digit, not a letter. You've written etho, not 0, in that command and yes, then it's totally expected the NIC can't be found.
Anyway, your system supports 64-bit while you're running a 32-bit OS. As stated earlier, you may want to re-install using the amd64 ISO.
From the aforementioned Ubuntu forum:
As root, obviously:
dmesg | grep e1000e
modprobe e1000eWhat results does that yield?
Further down that thread there's a link to the Intel drivers site, try building it from scratch as per the instructions.
HTH!
No. I'm using JFS on all my partitions/disks and it boots pretty quickly. Having said that, I had some issues with one drive (with a JFS partition) but that turned out to be a hardware failure. Fortunately I already had anticipated said failure coming so I had saved my data to a different drive and after a last sync between them the failed drive is now out of my desktop.
In any case, I don't see the JFS warnings/issues you mentioned in your posted dmesg abstract.
For starters, post the contents of the /etc/fstab file. I'm also interested in your CPU make/model and installed RAM capacity.
The western media has completely glossed over and hidden the fact that Neo Nazi militias actually rule Ukraine, through a puppet. And when I say "Neo Nazi militias", that's precisely what I mean - i.e. fanatics who style themselves on the SS, worship Adolph Hitler and would ethnically cleanse most of Europe in a heartbeat if they had the chance.
Yeah, these fanatical Ukrainian SS-militia, worshiping Hitler and probably provoking a dirty war with your KGB-President Vladimir Putin are ruled by a puppet.
A
JEWISH
puppet
Yeah right... ![]()
In case you're wondering, you're completely contradicting yourself by your statements. Never mind, I didn't expect anything less from Russian trolls.
Some of you need need to turn off the fucking TV news / put down the biased tabloids, which only ever repeat the state sponsored narrative and start thinking for yourselves.
I already do, hence my stance on Russia, in particular your spectacularly failing president and his criminal cronies, sorry (not really!) businessmen ![]()
Russia is rotten to the core and it will be a matter of time before it crumbles.
Again.
Like it did in the 1990's. Because the cause of the rot hasn't gone: greedy criminals are still in charge, the real puppet is Putin.
And that's my final word on it.
Welcome!
Unfortunately, due to events instigated in Moscow, Russia isn't very popular right now. Nothing personal, but it seems you've chosen the wrong time for this adventure. Consider putting it on hold while the situation improves. That might be a while though.
For starters, you need to install the build-essential package. It doesn't have any code itself, but its dependencies create a complete build-environment.
You can fix that with the following (and it should be in the instructions too!)
echo "ALWAYS_SET_PATH yes" >> /etc/default/suThis forces the shell to set the root path if you elevate permissions from a regular user to root, using su. It works, even skeptical me was converted. This was default behavior until upstream Debian changed it, citing "this was originally as intended under Unix" or something of that nature ![]()
There's always the wayback archive ![]()
Mind, you cannot create a copy of a running system, you need to run from a live-CD when you create the image.
I'm not sure it'll work as you want, so proceed at own risk!
Investigate the use of the apt options --get-selections and --set-selections in the apt man page
man apt
apt --get-selections > selection.txt
apt --set-selections < selection.txtBtw, do NOT use dd to backup your disk to an existing backup drive. Unless you don't care about the data that's already on it :-\
1. install an SSD
2. upgrade your hardware
You're welcome ![]()
It's probably better to use dmesg:
{sudo} dmesg | tailwill give you the last 10 lines, usually enough to find which drive letter the kernel has assigned to the USB stick you've just inserted.
(The root user has the ID of 0.)
Errmmm, oops ![]()
Don't. Root requires a UUID of 1.
This is the latest version for yt-dl:
# youtube-dl -U
youtube-dl is up-to-date (2021.12.17)Meaning that the dev has now resumed work on this project.
I'm using a different method of keeping yt-dl current. After installing via apt, somebody advised me to "overwrite" (re-link) the executable with a later version and then use the -U functionality (as root!) to keep said executable at the latest version. I can't recall ATM where I got it from, maybe on these forums?
Not pretty, but it works ![]()
For startx to work, you need the xinit package. And if it's not pulled in as dependency, the xdm package as well.