As far as I know the long red flash is the USA gov...the short flashing is the Israeli gov and the middle is the Arab gov along with the Chinese and Russians so no need to worry....it's just the "Watcher".

I had this as well to be honest....If you don't mind, then, they won't mind.

It's a browser thing.

Eric

PS...I run without a hdd so no matter to me...you see._________________Be not afraid to grow slowly, only be afraid of standing still.
Chinese Proverb

In former times i have read , that the linux kernel created a virtual ramdisk of a fixed size,
that can be adjusted at kernel compile time,
( also the amount of automatically created ramdisks in /dev/ram* )
to load the initrd.gz into.
That's where the bootparameter root=/dev/ram0 derives from.

Puppy's older kernels up to 2.6.33.2 and above had a ramdisk size of 12-13KiB .

Very recent kernel configurations have that increased since such a ramdisk is used for full installations to perform the file system check,
since a full installation does not use an initrd.gz,
so loads all the needed programs and libraries into that ramdisk,
unmounts the partition and performs the filesystem check ending with a reboot,
but the sizes of the libraries have incresed already from 4.3 to Lupu
and now they wont fit anymore into the 12-13kib ramdisk .

I worked around it myself by using two ramdisks : one for /lib and one for all the other programs in /etc, /bin, /sbin .

The point is now, that the kernel nowerdays loads the initrd.gz directly into a temporary tmpfs filesystem, that has no fixed size,
so no "real physical ramdisk" is used anymore by default and the kernel manages this all in ram and discards the initrd.gz after it had finished switching root.

I believe that since the HDD LED in the front side of a computer case is attached to the mobo, the BIOS/CHIP/CPU is sending the impulses to that joint, not the HDD directly. Whatever the real cause is, it might be that the BIOS simply is programmed to expect a HDD and therfore sends signals, or the cable is wrongly attached/damaged .

Sorry for the thread resurrection, but I'm having a similar issue, except my HD access is a lot more intense, about once per second. I can hear the heads move as something accesses data. I have a 2GB swap partition, but according to swapon -s it is currently mounted but not being used.

Q5sys wrote:

Here they are. But as I mentioned.. iotop requires python to run. (its a python script)

According to the package manager it is installed, but running iotop returns:

Code:

bash: /bin/iotop: /usr/bin/python: bad interpreter: No such file or directory

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum