Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.


Messages - pooky2483

Pages: [1] 2 3 ... 140
1
Programming / I want to learn machine/assembly language
« on: Yesterday at 06:08:48 pm »
Many years ago, When I had a Commodore 16 (which had a built in 6502 assembler) I used to hack into games and edit them.
What I'd like to do is try and continue where I left off, but obviously on a modern up-to-date processor.
Where do I begin, what do I need to install to start writing/editing machine assembly language, where can I download any documentation/manuals to help refresh my memory?

2
General Help & Advice / Re: [SOLVED] Unable to boot to desktop
« on: November 30, 2018, 11:15:31 pm »
It looks like it's a common problem.

3
General Help & Advice / Re: Unable to boot to desktop
« on: November 30, 2018, 01:29:52 pm »
Managed to fix the problem.
I Googled 'ubuntu has booted to busybox' and viewed a few results and found the command to fix the error...

While still in 'Busybox', I typed the command below
Code: [Select]
fsck /dev/sda1
NOTE: Change the sda1 to where ever you have your OS installed.

4
General Help & Advice / Re: Unable to boot to desktop
« on: November 29, 2018, 11:22:22 pm »
Good god, a million drives....

There's a few not connected, I've got 6 external HD's in total.
2 * 3Tb
2 * 4Tb
2 * 8Tb

2 * 2Tb internal
1 * 120Gb boot drive

5
General Help & Advice / Re: Unable to boot to desktop
« on: November 29, 2018, 11:18:39 pm »
The boot device is sda , the 120gb drive

6
You could always force dolphin back to 4.15 .. but if you have the backports repo installed (which is **supposed** to seamlessly move you to the latest KDE), I can't guarantee that won't give you other problems.

As we can see, it doesn't as shouldn't I have the latest version of Dolphin installed?
Quote
As dolphin 4.16 now doesn't appear to require dolphin-dbg, it might be worth seeing what would happen if you simply uninstalled dolphin-dbg .. what's the output from dolphin-dbg

According to the reply from someone dealing with the bug report I filed, the info that dolphin-dbg provides was not included in my debug info which was automatically uploaded, so it looks like dolphin-dbg is not included in the installation of dolphin 16.04.
Quote
Code: [Select]
sudo apt-get -s remove --purge dolphin-dbg
As I am unable to provide you with the output from my desktop version (as it's currently crashed), I can provide you with the output from my laptop, which I am having the same problem;

Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package dolphin-dbg

Quote
the above command is only a "simulated dry run", nothing will actually get uninstalled .. it'll just tell us what would happen if we ran it without the "-s" option, so we can check if it'd be safe.

7
General Help & Advice / Re: Unable to boot to desktop
« on: November 27, 2018, 02:12:44 pm »
Have you got a LiveUSB ?
(really you should always have one of these)

I have, you've probably forgot you helped me install Multiboot (I think it was written by someone French).
Well, I've got the boot repair, gparted and multiple os'es and lots of other stuff.

Quote
If so, boot to it, and post the output from:
Code: [Select]
df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             16G  4.0K   16G   1% /dev
tmpfs           3.2G  1.6M  3.2G   1% /run
/dev/sdi1       117G   38G   80G  33% /isodevice
/dev/loop0      1.1G  1.1G     0 100% /cdrom
/dev/loop1      1.1G  1.1G     0 100% /rofs
/cow             16G  342M   16G   3% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
tmpfs            16G   12K   16G   1% /tmp
none            5.0M  4.0K  5.0M   1% /run/lock
none             16G   76K   16G   1% /run/shm
none            100M   20K  100M   1% /run/user

Code: [Select]
mount
/cow on / type overlay (rw)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
/dev/sdi1 on /isodevice type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 on /cdrom type iso9660 (ro,noatime)
/dev/loop1 on /rofs type squashfs (ro,noatime)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)                                                   
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)                                                         
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)                                 
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)

Code: [Select]
sudo fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0007593a

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048   234438655   117218304   83  Linux

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xd1567197

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  3907028991  1953513472   83  Linux

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009b408

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048  3907028991  1953513472   83  Linux

WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdd: 8001.6 GB, 8001563221504 bytes
255 heads, 63 sectors/track, 972801 cylinders, total 15628053167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disk identifier: 0x9a9c01c5

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

WARNING: GPT (GUID Partition Table) detected on '/dev/sdg'! The util fdisk doesn't support GPT. Use GNU Parted.

Note: sector size is 4096 (not 512)

Disk /dev/sdg: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 45600 cylinders, total 732566646 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1               1   732566645  2930266580   ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdh'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdh: 8001.6 GB, 8001563221504 bytes
255 heads, 63 sectors/track, 972801 cylinders, total 15628053167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdi: 125.1 GB, 125061562368 bytes
255 heads, 63 sectors/track, 15204 cylinders, total 244260864 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe921f7a6

   Device Boot      Start         End      Blocks   Id  System
/dev/sdi1   *        1953   244260863   122129455+   c  W95 FAT32 (LBA)

8
General Help & Advice / Re: Unable to boot to desktop
« on: November 27, 2018, 12:18:18 pm »
Just tried booting to a previous kernel and still the same problem...

9
General Help & Advice / [SOLVED] Unable to boot to desktop
« on: November 27, 2018, 12:14:20 pm »
I have just rebooted my computer* and all seemed well until just after the splash screen, when I got this...

BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) _ <--- flashing cursor

I have already tried boot repair disk and then rebooted and it booted to the same state as above.


* Just before shut-down of the system to reboot, a couple of warnings popped up telling me that it was unable to write to disk, probably something to do with writing the state of the system to disk!

10
News and Events / Trojan miner for Linux removes antiviruses
« on: November 24, 2018, 04:52:52 am »
Found this story on exploit.in (a Russian site)

The Doctor Web specialists have discovered a trojan designed for the extraction of cryptocurrency, which can infect other network devices and remove antiviruses running in the system. The threat received the identifier Linux.BtcMine.174 and is a large script written in the command shell language containing more than 1000 lines of code.

Malware consists of several components. So, when launching, the trojan checks the availability of the server from which it subsequently downloads other modules, and searches for a folder on the disk with write permissions into which these modules will then be loaded. After this, the script is moved to a previously selected folder named diskmanagerd and re-launched as a daemon. For this, the trojan uses the nohup utility. If it is not in the system, it automatically downloads and installs the coreutils utilities package, including nohup.

If the installation is successful on the device, the malicious script downloads one of the versions of the Linux.BackDoor.Gates.9 Trojan. The backdoors of this family allow you to execute commands from attackers and carry out DDoS attacks.

After installation, malware looks for competing miners in the system and, upon detection, completes their processes. If the trojan was not launched on behalf of the superuser (root), it uses a set of exploits to escalate its privileges on the infected system. Analysts of Doctor Web have identified at least two problems exploited by him: these are CVE-2016-5195 (aka DirtyCow ) and CVE-2013-2094 . At the same time, the sources of the exploit for DirtyCow are downloaded from the Internet by the Trojan compiles directly on the infected machine.

After this, the malware tries to find antivirus services running under the names safedog, aegis, yunsuo, clamd, avast, avgd, cmdavd, cmdmgd, drweb-configd, drweb-spider-kmod, esets and xmirrord. If they are detected, the malware does not just end the antivirus process, but with the help of package managers, deletes its files and the directory in which the anti-virus product was installed.

Then the trojan registers itself at startup, downloads and launches a rootkit on an infected device. This module is also designed as a sh script and is based on source code that was previously published in the public domain. Among the functions of the rootkit module, you can highlight the theft of user-supplied passwords for the su command, hiding files in the file system, network connections and running processes. The trojan collects information about network nodes that were previously connected via the ssh protocol and tries to infect them.

After completing all these steps, the Trojan finally launches the miner, designed for the production of Monero cryptocurrency (XMR), in the system. At intervals of one minute, the malware checks to see if this miner is running, and automatically restarts it if necessary. It also connects to the managing server in a continuous loop and downloads updates from there, if they are available.

Source: https://xakep.ru/2018/11/20/linux-btcmine-174/

Source of the above story...
https://translate.google.com/translate?hl=en&sl=ru&u=https://exploit.in/&prev=search

11
That's strange as I've not forced  the installation of 16.04, it may be because I've got backports repo loaded, even then, the backports repo is installed on a fresh install. So, I'm stuck!!!

12
Is there a way I can force install the latest version of Dolphin. I've had a Google but I could not find any specifics on how to install other versions.

13
General Help & Advice / Re: Problem removing a source
« on: November 22, 2018, 01:51:35 am »
I get the error when I execute the following...
Code: [Select]
sudo apt-get update
(click to show/hide)

14
General Help & Advice / Re: Problem removing a source
« on: November 20, 2018, 12:55:39 am »
I'm not sure how to ask or do it, what I need to do is remove owncloud which is causing problems.

15
Lol Mark, you sound like my dad  ;)
The PPA's didn't cause the problem as they came after the installation of Dolphin as that was installed upon installation of the OS ages ago.

Recent versions don't have external PPA's, so what you're saying is that from version XX the dbg is built in?
So, if I want to escape this bug, how can I install the latest (or higher) version?

Pages: [1] 2 3 ... 140

SimplePortal 2.3.3 © 2008-2010, SimplePortal