![]() |
2010-10-30
, 23:31
|
|
Posts: 511 |
Thanked: 128 times |
Joined on Aug 2010
@ Trinidad and Tobago
|
#22
|
![]() |
2010-10-30
, 23:58
|
Posts: 256 |
Thanked: 92 times |
Joined on Oct 2010
|
#23
|
![]() |
2010-10-31
, 00:03
|
|
Posts: 511 |
Thanked: 128 times |
Joined on Aug 2010
@ Trinidad and Tobago
|
#24
|
![]() |
2010-10-31
, 00:08
|
|
Posts: 511 |
Thanked: 128 times |
Joined on Aug 2010
@ Trinidad and Tobago
|
#26
|
![]() |
2010-10-31
, 00:11
|
Posts: 256 |
Thanked: 92 times |
Joined on Oct 2010
|
#27
|
![]() |
2010-10-31
, 00:12
|
|
Posts: 511 |
Thanked: 128 times |
Joined on Aug 2010
@ Trinidad and Tobago
|
#28
|
![]() |
2010-10-31
, 00:16
|
Posts: 256 |
Thanked: 92 times |
Joined on Oct 2010
|
#29
|
![]() |
2010-10-31
, 00:18
|
|
Posts: 511 |
Thanked: 128 times |
Joined on Aug 2010
@ Trinidad and Tobago
|
#30
|
The filesystem wouldn't be mounted read-only without a reason, either filesystem errors or a hardware error, though if it had been mounted read-only you could check "dmesg" to look for any relevant error messages telling why the kernel remounted it read-only.