WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core 3.0 Alpha 8 Testing  (Read 9295 times)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7915
Re: Tiny Core 3.0 Alpha 8 Testing
« Reply #30 on: July 03, 2010, 01:18:22 PM »
@Xianwen Chen: Xorg.0.log and dmesg please. If this is an Intel chip, try disabling framebuffer compression in xorg.conf.

@neonix: dmesg, device name, can you mount manually?
The only barriers that can stop you are the ones you create yourself.

Offline neonix

  • Jr. Member
  • **
  • Posts: 50
Re: Tiny Core 3.0 Alpha 8 Testing
« Reply #31 on: July 03, 2010, 07:58:08 PM »
@neonix: dmesg, device name, can you mount manually?
dmesg doesn't show any errors. I can't mount manually because /mnt is empty.
Code: [Select]
scsi 0:0:0:0: Direct-Access     USB 2.0  SD MMC Reader         PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 62720 512-byte logical blocks: (32.1 MB/30.6 MiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda:
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: Tiny Core 3.0 Alpha 8 Testing
« Reply #32 on: July 03, 2010, 08:36:56 PM »
neonix: Are you sure that there is a partition on the device? Maybe a fdisk -l /dev/sda and blkid /dev/sda* can provide some insight.

Offline Xianwen Chen

  • Full Member
  • ***
  • Posts: 139
Re: Tiny Core 3.0 Alpha 8 Testing
« Reply #33 on: July 04, 2010, 05:14:23 AM »
Hi Robert,

When updating TCE, does the script check .dep file? What I have experienced is that the script only checked md5 sum files. For example, wireless_tools.tcz in 2.x and 3.x have the same md5sum, but with different dependencies. This can mix up the TCE for different major versions without warning users.

Best regards,

Xianwen

Offline Xianwen Chen

  • Full Member
  • ***
  • Posts: 139
Re: Tiny Core 3.0 Alpha 8 Testing
« Reply #34 on: July 04, 2010, 05:15:10 AM »
@Xianwen Chen: Xorg.0.log and dmesg please. If this is an Intel chip, try disabling framebuffer compression in xorg.conf.

@neonix: dmesg, device name, can you mount manually?

Hi curaga,

Thanks a lot! I've falled back to 2.11.6 because stability is crucial to me.

Best regards,

Xianwen

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: Tiny Core 3.0 Alpha 8 Testing
« Reply #35 on: July 04, 2010, 05:36:35 AM »
Hi Robert,

When updating TCE, does the script check .dep file? What I have experienced is that the script only checked md5 sum files. For example, wireless_tools.tcz in 2.x and 3.x have the same md5sum, but with different dependencies. This can mix up the TCE for different major versions without warning users.

Best regards,

Xianwen
Check for an update to an extension proper is based on md5 change.
Dependencies are handled via appsaudit "Check for Missing Dependencies" as it updates all .dep files.

10+ Years Contributing to Linux Open Source Projects.

Offline Xianwen Chen

  • Full Member
  • ***
  • Posts: 139
Re: Tiny Core 3.0 Alpha 8 Testing
« Reply #36 on: July 04, 2010, 05:40:47 AM »
Hi Robert,

When updating TCE, does the script check .dep file? What I have experienced is that the script only checked md5 sum files. For example, wireless_tools.tcz in 2.x and 3.x have the same md5sum, but with different dependencies. This can mix up the TCE for different major versions without warning users.

Best regards,

Xianwen
Check for an update to an extension proper is based on md5 change.
Dependencies are handled via appsaudit "Check for Missing Dependencies" as it updates all .dep files.



Hi Roberts,

I see. Thanks a lot for clarification!

Would it be possible to add dependency check to the update script? I believe that it is necessary.

Best regards,

Xianwen
« Last Edit: July 04, 2010, 05:59:48 AM by Xianwen Chen »