Recent Posts

61

TCB Talk / Re: Thinking of using Tiny Core; advice please?

« Last post by JunkYard on May 14, 2026, 02:51:51 PM »

Hi JunkYard
First of all, I deleted your last post. All you did was quote a bunch
of other posts without saying anything else.

That is because the first quoted poster said that I did not post any information regarding the issue I have had with not being able to open the drives. Then I quoted myself showing the terminal error codes that I had

There is nothing wrong with the terminal. I works just fine.

Did you plug a network cable into your machine?
You can't download any extensions without a network connection.

I dont have a network cable or internet connect for said motherboard/ machine. However I am weight for a delivery in the post of a USB dongle that you insert a sim card into it to get internet from. Do you know if Tiny core O.S would understand this or not. It is to my knowlage that driver hunting is a windonws thing

62

TCB Talk / Re: Tiny Core v17.0 upgrade issues

« Last post by Stefann on May 14, 2026, 01:35:10 PM »

I just notice my 2nd system has tc16 core.gz and vmlinuz that was working until I upgraded to tc17.
I will put those on my production system tomorrow. I expect that will work.
“Failing to boot TC16” is likely something stupid.

63

TCB Talk / Re: Tiny Core v17.0 upgrade issues

« Last post by Stefann on May 14, 2026, 10:36:14 AM »

to add,
I'm chatting with my brother, who is a bit of linux guru..

He also thinks these are suspicious:

<    guard(mutex)(&usb_dynids_lock);
---
>    spin_lock(&drv->dynids.lock);
711a712
>          spin_unlock(&drv->dynids.lock);
714a716
>    spin_unlock(&drv->dynids.lock);
1178a1181

Especially because the "spin_lock()" seems to be replaced by "guard()" but its unclear what happened to the 2x "spine_unlock()"

This folds back to Commit 0b3144d
https://github.com/torvalds/linux/commit/0b3144da31f855fce652303f588416a60991bdef

USB: make single lock for all usb dynamic id lists
There are a number of places where we accidentally pass in a constant
structure to later cast it off to a dynamic one, and then attempt to
grab a lock on it, which is not a good idea.  To help resolve this, move
the dynamic id lock out of the dynamic id structure for the driver and
into one single lock for all USB dynamic ids.  As this lock should never
have any real contention (it's only every accessed when a device is
added or removed, which is always serialized) there should not be any
difference except for some memory savings.

Note, this just converts the existing use of the dynamic id lock to the
new static lock, there is one place that is accessing the dynamic id
list without grabbing the lock, that will be fixed up in a follow-on
change.

tty-check change folds back to Commit 2b5eac0
https://github.com/torvalds/linux/commit/2b5eac0f8c6e79bc152c8804f9f88d16717013ab

tty: introduce and use tty_port_tty_vhangup() helper
This code (tty_get -> vhangup -> tty_put) is repeated on few places.
Introduce a helper similar to tty_port_tty_hangup() (asynchronous) to
handle even vhangup (synchronous).

And use it on those places.

In fact, reuse the tty_port_tty_hangup()'s code and call tty_vhangup()
depending on a new bool parameter.

I traced the code on this. As far as I can see the new code does no longer have the check on "tty being existing"

64

Off-Topic - Tiny Core Lounge / Don't output the code. Keep it in context and provide a detailed error report.

« Last post by xor on May 14, 2026, 09:24:31 AM »

Try this to use artificial intelligence more efficiently.

1. English: Don't output code. Keep in context and provide a detailed error report.
2. Chinese: 不要输出代码。将其保留在上下文中并提供详细的错误报告。
3. Hindi: कोड आउटपुट न करें। इसे संदर्भ में रखें और विस्तृत त्रुटि रिपोर्ट दें।
4. Spanish: No imprimas el código. Mantenlo en contexto y da un informe de errores.
5. French: N'affiche pas le code. Garde-le en contexte et fais un rapport d'erreurs.
6. Arabic: لا تخرج الكود. ابقِهِ في السياق وقدم تقريرًا مفصلاً عن الأخطاء.
7. Bengali: কোড আউটপুট করবেন না। এটি প্রেক্ষাপটে রাখুন এবং বিস্তারিত ত্রুটি রিপোর্ট দিন।
8. Portuguese: Não exiba o código. Mantenha no contexto e dê um relatório de erros.
9. Russian: Не выводите код. Держите в контексте и дайте подробный отчет об ошибках.
10. Urdu: کوڈ آؤٹ پুট نہ کریں۔ اسے سیاق و سباق میں رکھیں اور تفصیلی غلطی کی رپورٹ دیں۔
11. Indonesian: Jangan keluarkan kode. Simpan dalam konteks dan beri laporan error.
12. German: Code nicht ausgeben. Im Kontext behalten und Fehlerbericht erstellen.
13. Japanese: コードを出力しないで。文脈を保持し、詳細なエラー報告をして。
14. Nigerian Pidgin: No komot di code. Keep am for context, give full error report.
15. Marathi: कोड आउटपुट करू नका. संदर्भात ठेवा आणि तपशीलवार त्रुटी अहवाल द्या.
16. Telugu: కోడ్ అవుట్‌పుట్ చేయవద్దు. సందర్భంలో ఉంచి వివరణాత్మక లోప నివేదిక ఇవ్వండి.
17. Turkish: Kodu yazdırma. Bağlamda tut ve detaylı bir hata raporu sun.
18. Tamil: குறியீட்டை வெளியிட வேண்டாம். சூழலில் வைத்து விரிவான பிழை அறிக்கையைத் தருக.
19. Yue Chinese: 唔好輸出代碼。保留喺上下文入面並提供詳細嘅錯誤報告。
20. Vietnamese: Không xuất mã. Giữ trong ngữ cảnh và cung cấp báo cáo lỗi chi tiết.
21. Tagalog: Huwag i-output ang code. Panatilihin sa konteksto at magbi ng report.
22. Wu Chinese: 勿输出代码。保留于上下文中并提供详细错误报告。
23. Korean: 코드를 출력하지 마세요. 컨텍스트를 유지하고 상세 오류 보고서를 주세요.
24. Iranian Persian: کد را خروجی ندهید. در متن نگه دارید و گزارش خطا بدهید.
25. Hausa: Kada ka fitar da lambar. Ajiye ta a cikin mahallin ka ba da rahoton kuskure.
26. Swahili: Usitoe msimbo. Weka kwenye muktadha na utoe ripoti ya kina ya hitilafu.
27. Javanese: Aja ngetokake kode. Simpen ing konteks lan wenehi laporan kesalahan.
28. Italian: Non emettere il codice. Mantieni il contesto e dai un rapporto errori.
29. Punjabi: ਕੋਡ ਆਉਟਪੁੱਟ ਨਾ ਕਰੋ। ਇਸਨੂੰ ਸੰਦਰਭ ਵਿੱਚ ਰੱਖੋ ਅਤੇ ਵਿਸਤ੍ਰਿਤ ਗਲਤੀ ਰਿਪੋਰਟ ਦਿਓ।
30. Kannada: ಕೋಡ್ ಔಟ್‌ಪುಟ್ ಮಾಡಬೇಡಿ. ಸಂದರ್ಭದಲ್ಲಿರಿಸಿ ಮತ್ತು ವಿವರವಾದ ದೋಷ ವರದಿ ನೀಡಿ.
31. Gujarati: કોડ આઉટપુટ કરશો નહીં. તેને સંદર્ભમાં રાખો અને વિગતવાર ભૂલ અહેવાલ આપો.
32. Thai: อย่าแสดงโค้ด เก็บไว้ในบริบทและรายงานข้อผิดพลาดอย่างละเอียด
33. Amharic: ኮዱን አታውጣ። በዐውደ-ጽሑፉ ውስጥ ያቆዩት እና ዝርዝር የስህተት ሪፖርት ይስጡ።
34. Bhojpuri: कोड आउटपुट मत करीं। संदर्भ में रखीं आ विस्तृत त्रुटि रिपोर्ट दीं।
35. Southern Min: 免輸出代碼。保留佇上下文中並提供詳細嘅錯誤報告。
36. Jin Chinese: 勿输出代码。保留于上下文中并提供详细错误报告。
37. Yoruba: Má ṣe gbé kòòdù jáde. Fi sínú àyíká kí o sì fún mi ní ìròyìn àṣìṣe.
38. Hakka Chinese: 毋好輸出代碼。保留在上下文中並提供詳細嘅錯誤報告。
39. Burmese: ကုဒ်ကိုထုတ်မပြပါနဲ့။ အကြောင်းအရာထဲမှာထားပြီး အသေးစိတ်အမှားအစီရင်ခံစာပေးပါ။
40. Oromo: Koodii hin baasin. Haala keessa tursiisi gabaasa dogoggoraa kenni.
41. Pashto: کوډ مه وباسئ. په متن کې یې وساتئ او د غلطۍ تفصیلي راپور ورکړئ.
42. Maithili: कोड आउटपुट नहि करी। संदर्भ में राखू आ विस्तृत त्रुटि रिपोर्ट दियौ।
43. Ukrainian: Не виводьте код. Тримайте в контексті та надайте звіт про помилки.
44. Sundanese: Ulah ngaluarkeun kodeu. Simpen dina kontéks sarta bikeun laporan kasalahan.
45. Polish: Nie wyświetlaj kodu. Zachowaj kontekst i podaj raport o błędach.
46. Uzbek: Kodni chiqarmang. Uni kontekstda saqlang va xato hisobotini bering.
47. Malayalam: കോഡ് ഔട്ട്പുട്ട് ചെയ്യരുത്. സന്ദർഭത്തിൽ വെച്ച് പിശക് റിപ്പോർട്ട് നൽകുക.
48. Sindhi: ڪوڊ آئوٽ پٽ نه ڪريو. ان کي سياق و سباق ۾ رکو ۽ غلطي جي رپورٽ ڏيو.
49. Amharic: ኮዱን አታውጣ። በዐውደ-ጽሑፉ ውስጥ ያቆዩት እና ዝርዝር የስህተት ሪፖርት ይስጡ።
50. Fula: Woto yaltin koodo on. Moofte ɗum e ngonka, hokku raporto aybe.
51. Romanian: Nu afișa codul. Păstrează-l în context și oferă un raport de erori.
52. Oromo: Koodii hin baasin. Haala keessa tursiisi gabaasa dogoggoraa kenni.
53. Azerbaijani: Kodu çıxarmayın. Kontekstdə saxlayın və ətraflı xəta hesabatı verin.
54. Manipuri: কোড থোকহনগনু। মসি কন্টেক্সটতা থম্মু অমসুং অকুপ্পা ইরোড রিপোর্ট পীয়ু।
55. Polish: Nie wyświetlaj kodu. Zachowaj kontekst i podaj raport o błędach.
56. Burmese: ကုဒ်ကိုထုတ်မပြပါနဲ့။ အကြောင်းအရာထဲမှာထားပြီး အသေးစိတ်အမှားအစီရင်ခံစာပေးပါ။
57. Hakka Chinese: 毋好輸出代碼。保留在上下文中並提供詳細嘅錯誤報告。
58. Serbo-Croatian: Ne ispisuj kod. Zadrži u kontekstu i daj izvještaj o greškama.
59. Malagasy: Aza mamoaka kaody. Tehirizo ao anatin'ny tontolon'ny ary omeo tatitra.
60. Saraiki: کوڈ آؤٹ پুট نہ کرو۔ اینکوں سیاق و سباق وچ رکھو تے غلطی دی رپورٹ ڈیو۔
61. Nepali: कोड आउटपुट नगर्नुहोस्। यसलाई सन्दर्भमा राख्नुहोस् र त्रुटि रिपोर्ट दिनुहोस्।
62. Sinhala: කේතය නිමැවුම් නොකරන්න. සන්දර්භය තුළ තබා සවිස්තරාත්මක දෝෂ වාර්තාවක් දෙන්න.
63. Chittagonian: কোড আউটপুট ন গরিও। ইত্তে কনটেক্সটত রাকি ডিটেইল এরর রিপোর্ট দিও।
64. Zhuang: Moij soutsied代码。 Bauhndoi mbeu gvidingz caeuq bauhgao loihfuk.
65. Khmer: កុំបញ្ចេញកូដ។ រក្សាទុកក្នុងបរិបទ ហើយផ្តល់របាយការណ៍កំហុសលម្អិត។
66. Turkmen: Kody çykarmaň. Ony kontekstde saklaň we jikme-jik ýalňyş hasabat beriň.
67. Assamese: ক'ড আউটপুট নকৰিব। ইয়াক প্ৰসংগত ৰাখক আৰু বিতং ত্ৰুটিৰ প্ৰতিবেদন দিয়ক।
68. Madurese: Jha' parowa kodenna. Simpen e dhalem konteks ban berris laporan dusa.
69. Somali: Ha soo saarin koodka. Ku hay macnaha guud oo bixi warbixin qalad ah.
70. Marwari: कोड आउटपुट मत करजो। इणने संदर्भ में राखजो अर त्रुटि रिपोर्ट दीजो।
71. Magahi: कोड आउटपुट मत करी। संदर्भ में राखी आ विस्तृत त्रुटि रिपोर्ट दी।
72. Haryanvi: कोड आउटपुट ना करियो। इसे संदर्भ में राखियो अर विस्तृत त्रुटि रिपोर्ट दियो।
73. Hungarian: Ne írd ki a kódot. Tartsd kontextusban és adj hibajelentést.
74. Dutch: Voer code niet uit. Houd in context en geef een gedetailleerd foutrapport.
75. Greek: Μην εξάγεις κώδικα. Κράτα το πλαίσιο και δώσε αναφορά σφαλμάτων.
76. Czech: Nevypisuj kód. Ponechej v kontextu a podej zprávu o chybách.
77. Magahi: कोड आउटपुट मत करी। संदर्भ में राखी आ विस्तृत त्रुटि रिपोर्ट दी।
78. Chhattisgarhi: कोड आउटपुट झन करबे। संदर्भ में राखबे अउ विस्तृत त्रुटि रिपोर्ट देबे।
79. Belarusan: Не выводзьце код. Трымайце ў кантэксце і дайце справаздачу аб памылках.
80. Kazakh: Кодты шығармаңыз. Мәнмәтінде сақтаңыз және қате туралы есеп беріңі즈.
81. Swedish: Skriv inte ut koden. Behåll i sammanhanget och ge en felrapport.
82. Zulu: Ungakhiphi ikhodi. Igcine kumongo bese unikeza umbiko wephutha.
83. Shona: Usaburitsa kodhi. Ichengetedze mumashoko upe ripoti yekukanganisa.
84. Uyghur: كودنى چىقارماڭ. ئۇنى مەزمۇن ئىچىدە ساقلاڭ ۋە تەپسىلىي خاتالىق دوكلاتى بېرىڭ.
85. Hilinon: Indi i-output ang code. Itago sa konteksto kag maghatag sang report.
86. Bulgarian: Не извеждай код. Задръж в контекст и дай отчет за грешки.
87. Hebrew: אל תציג קוד. שמור בהקשר וספק דוח שגיאות מפורט.
88. Lombard: Stampà minga el codes. Tegn el contest e dà on rapòrt de error.
89. Balochi: کوڈ ءَ در مکن۔ آیان ءَ سیاق ءُ سباق ءَ بدار ءُ ردیانی رپوٹ بہ دے۔
90. Konkani: कोड आउटपुट करचें न्हय. संदर्भांत दवरात आनी त्रुटी अहवाल दयात.
91. Akan: Mpue koodu no. Fa hyɛ ne mu na ma mfonini kɛseɛ wɔ mfomsoɔ ho.
92. Tatar: Кодны чыгармыйча, контекстта саклагыз һәм хаталар отчетын бирегез.
93. Hebrew: אל תציג קוד. שמור בהקשר וספק דוח שגיאות מפורט.
94. Norwegian: Ikke skriv ut koden. Behold i kontekst og gi en feilrapport.
95. Armenian: Կոդը մի արտածեք: Պահեք այն համատեքստում և տվեք սխալների զեկույց:
96. Minangkabau: Jan kaluakan kode. Simpan dalam konteks dan agiah laporan eror.
97. Kabyle: Ur d-ssufegh ara akud. Hezz-it deg umawal n tseddast s wul-ik.
98. Santali: ᱠᱳᱰ ᱟᱞᱳᱢ ᱩᱰᱩᱠᱟ ᱾ ᱥᱟᱶᱛᱮ ᱫᱚᱦᱚᱭ ᱢᱮ ᱟᱨ ᱵᱷᱩᱞ ᱨᱮᱭᱟᱜ ᱨᱤᱯᱳᱨᱴ ᱮᱢ ᱢᱮ ᱾
99. Albanian: Mos e shfaq kodin. Mbaje në kontekst dhe jep raport gabimesh.

65

TCB Talk / Re: Tiny Core v17.0 upgrade issues

« Last post by Stefann on May 14, 2026, 09:19:52 AM »

Ok... lots to say...

Yesterday I was off. Today the crash program was still running. I manually stopped it

Code: [Select]

mon day:  5 10 | hh:mm:ss: 13:49:56 | Still alive after 0k + 1 loops
.....
mon day:  5 14 | hh:mm:ss: 13:19:37 | Still alive after 878k + 109 loops
So:
- with crashprogram that no longer has "stress inducing interrupts" and "TC17 with text boot option" I see no crash in 4 days.

Next step I tried:
- install TC16
However... Install worked, but I did not get it running.
I tried TC16.0 and TC16.1 but for some reason I could not get them to run.

syslog did start but it looks like it stalls when trying to load core.gz.

I noticed that on my MacBook TC16 core.gz is downloaded as core.cpio. I tried booting core.cpio but without success.
I changed name in syslog.conf to core.cpio; I also tried renaming core.cpio to core.gz but neither worked.
>> I abandon that path.

Next step..
I downloaded sources from TC15, TC16 and TC17 and looked into ./drivers/usb/serial
I did run a diff on usb-serial.c
>> note, I have no clue whether this is the file I need, I just guessed based on filename.

The most suspicious difference I did see:

Code: [Select]

TC15:
> tty = tty_port_tty_get(&port->port);
> if (tty) {
> tty_vhangup(tty);
> tty_kref_put(tty);
> }

TC17:
< tty_port_tty_vhangup(&port->port);
This (I think) means that TC15 is testing tty to be valid before doing tty_vhangup() by calling tty while TC17 directly closes the port without testing whether the associated tty exists.

I did some google and found on https://docs.kernel.org/driver-api/tty/tty_port.html:

The tty port has a different lifetime to the tty so must be kept apart. In addition be careful as tty -> port mappings are valid for the life of the tty object but in many cases port -> tty mappings are valid only until a hangup so don’t use the wrong path.

please understand, I have no clue about the logic of this code, but I "can" imagine a hangup_command that is run in kernel mode on a non-existant port to cause a crash.

Next.....
- for now I started the crash-test again including stress commands and including gui. With a little luck it fails again in 45hr and than I can see whether I can jump out the gun with CNTR-ALT-F1 as suggested by @Rich.

Followup, and I could use some help here...
1/
It would be nice if I could understand why TC16 does not run. The diff between TC16 and TC17 on usb-serial.c is almost nothing.
> its above mention tty check
> and also use of "guard" instead of "spin_lock"
So if TC16 runs without crash it is a further evidence that the issue is in one of above 2 changes.

So... any advice on "why boot gets stuck on TC16" is welcome

2/
would there be any way that I could recompile the core with usb-serial.c fixed for the tty check?
Please understand that I have zero experience in compiling core.
I would also be very happy to test a core that someone prepared for me.

3/
Can anyone confirm that usb-serial-6.18.2-tinycore.tcz is indeed the usb-serial.c file??
Note,... would simply using  usb-serial-6.6.8-tinycore.tcz  (TC15) or  usb-serial-6.12.11-tinycore.tcz  (TC16) have any potential to work??
Especially the TC16 should have potential as the only difference is in the tty_vhangup() and the spinlock.

And/or... any way I could get a usb-serial-x.y.z-tinycore.tcz compiled for TC17 based on TC16 usb-serial.c?

For information
diff of usb-serial.c TC17 TC15

Code: [Select]

$$ TC17 crash work % diff TC17_drivers_usb_serial/usb-serial.c TC15_drivers_usb_serial/usb-serial.c
709c709
< guard(mutex)(&usb_dynids_lock);
---
> spin_lock(&drv->dynids.lock);
711a712
> spin_unlock(&drv->dynids.lock);
714a716
> spin_unlock(&drv->dynids.lock);
1178a1181
> struct tty_struct *tty;
1193c1196,1200
< tty_port_tty_vhangup(&port->port);
---
> tty = tty_port_tty_get(&port->port);
> if (tty) {
> tty_vhangup(tty);
> tty_kref_put(tty);
> }
1455c1462
<  * __usb_serial_register_drivers - register drivers for a usb-serial module
---
>  * usb_serial_register_drivers - register drivers for a usb-serial module
1457d1463
<  * @owner: owning module
1464,1466c1470,1472
< int __usb_serial_register_drivers(struct usb_serial_driver *const serial_drivers[],
<   struct module *owner, const char *name,
<   const struct usb_device_id *id_table)
---
> int usb_serial_register_drivers(struct usb_serial_driver *const serial_drivers[],
> const char *name,
> const struct usb_device_id *id_table)
1511d1516
< (*sd)->driver.owner = owner;
1519c1524
< rc = driver_attach(&udriver->driver);
---
> rc = driver_attach(&udriver->drvwrap.driver);
1530c1535
< EXPORT_SYMBOL_GPL(__usb_serial_register_drivers);
---
> EXPORT_SYMBOL_GPL(usb_serial_register_drivers);
diff of usb-serial.c TC17 TC16

Code: [Select]

$$ diff TC17_drivers_usb_serial/usb-serial.c TC16_drivers_usb_serial/usb-serial.c
709c709
< guard(mutex)(&usb_dynids_lock);
---
> spin_lock(&drv->dynids.lock);
711a712
> spin_unlock(&drv->dynids.lock);
714a716
> spin_unlock(&drv->dynids.lock);
1178a1181
> struct tty_struct *tty;
1193c1196,1200
< tty_port_tty_vhangup(&port->port);
---
> tty = tty_port_tty_get(&port->port);
> if (tty) {
> tty_vhangup(tty);
> tty_kref_put(tty);
> }

66

TCB Talk / Re: Thinking of using Tiny Core; advice please?

« Last post by CNK on May 14, 2026, 02:43:05 AM »

You can use the extension browser to search by keywords. Searching for "file manager" finds many. If you install a graphical one (pcmanfm, emelfm, nautilus...) , it'll appear as an icon you can launch like the extension browser. Repeat as desired to install all the programs you want.

So you are saying I have to donwload it onto the machine from the terminal right?

No, as Rich already said.

You said you read the Tiny Core Linux book. Re-read chapter 3 "Basic Package Management via GUI", it's only a few pages.

67

TCB Talk / Re: Thinking of using Tiny Core; advice please?

« Last post by Rich on May 13, 2026, 12:05:40 PM »

Hi JunkYard
First of all, I deleted your last post. All you did was quote a bunch
of other posts without saying anything else.

There is nothing wrong with the terminal. I works just fine.

Did you plug a network cable into your machine?
You can't download any extensions without a network connection.

There is an icon for a GUI based extension downloader/installer:

It won't work without a network connection either.

A few more items:
1. You will need to manage your expectations. If you expect to
   point and click your way to a fully equipped system, then you
   picked the wrong Linux distro.

2. You are confusing:
      "this is rubbish and nothing works"
   with:
      "I don't know or understand how things work"
   Your current issue is the latter.

3. Stop quoting entire posts. If you need to address an issue from
   a post, just quote the sentence that mentions that issue.

68

TCB Talk / Re: Thinking of using Tiny Core; advice please?

« Last post by JunkYard on May 13, 2026, 10:57:47 AM »

The OP is looking to install on a Pentium 4 with 512 Meg of RAM.

Hi Rich. All the more reason the OP should learn to love the TCL way of doing things
Opening up a terminal and running tce-load -wi xfe (or pcmanfm or rox-filer or spacefm) is not that hard.

As we say from my earlier post about trying to read the drives. The terminal is rubish and dose not work!

69

TCB Talk / Re: Thinking of using Tiny Core; advice please?

« Last post by JunkYard on May 13, 2026, 10:55:49 AM »

Then is there a file manager program that I can download and install onto it, as you can see from above trying to open the drives, I can not work with the Terminal command line

You can use the extension browser to search by keywords. Searching for "file manager" finds many. If you install a graphical one (pcmanfm, emelfm, nautilus...) , it'll appear as an icon you can launch like the extension browser. Repeat as desired to install all the programs you want.

Where Tiny Core might not be for you is you need to know what programs you want, and some might need a little setting up. Other distros pick ones for you that come installed by default, hence they're often very big (including many things you might never use).

So you are saying I have to donwload it onto the machine from the terminal right?

70

TCB Talk / Re: Thinking of using Tiny Core; advice please?

« Last post by gadget42 on May 12, 2026, 02:56:28 PM »

I seem to have managed to install the CD onto a USB stick this afternoon and the USB stick does actually boot!
...
I have another drive connected to the machine as well and I would like to read what is on it from the tiny core O.S. Do you know how to do it please?

here OP describes success in booting TCL via a USB stick. also, the OP wishes to mount and read "another drive connected to the machine" but does not offer further details regarding drive/filesystem(s)/partition(s)/etc.