Yeah, I think I did that.

1 members found this post helpful.

Sorry, I'm a slackwarecn developer, and last year I tweeted to the great Volkerding that I was working on a slackwareloong port, and BDFL replied [I've seen the posts on LQ. Nice work! ](https://twitter.com/volkerdi/status/...vKw&s=19)Thank you to BDFL for encouraging me.

slackwareloong is built by slacwkarecn developers and is not owned by Loongson.

The purpose of transplanting slackwareloong is to run slackware on LoongArch. slackwareloong is unofficial slackware.

---
SlackwareCN: The Slackware Linux CN Community
slackwareCN：https://github.com/slackwarecn
slackwareCN：http://www.slackwarecn.cn
slackwareloong doc ：https://github.com/slackwarecn/slackbook_cn_loongarch64
slackwareloong web doc : https://slackwarecn.gitbook.io/slackbook_cn_loongarch64

1 members found this post helpful.

I am not very sure.
My LoongArch machine and server are old computers I bought online as slackwareloong compilation and testing machines.
Do you need to experience the LoongArch environment? I will ask my friend nearby to see if he has a way for you to experience it.
I will promote this matter so that more people can use and like slackware.

---
SlackwareCN: The Slackware Linux CN Community
slackwareCN：https://github.com/slackwarecn
slackwareCN：http://www.slackwarecn.cn
slackwareloong doc ：https://github.com/slackwarecn/slackbook_cn_loongarch64
slackwareloong web doc : https://slackwarecn.gitbook.io/slackbook_cn_loongarch64

I'm sorry for causing trouble to you because of my recklessness. I'm really sorry.

I am a slackware enthusiast. I learned about the LoongArch architecture a few years ago and wanted to run slackware on LoongArch. Then I started to transplant "Slackware for LoongArch" locally:
Then I started transplanting "slackware for LoongArch" locally in 2021. The transplant was basically successful at the end of 2021, and slackware can run on LoongArch.
In 2022, I published a post on LQ and wanted to tell everyone that I transplanted and adapted "slackware for LoongArch". I would like to listen to your suggestions and opinions before deciding on the subsequent development plan of "slackware for LoongArch". I saw everyone's comments. He taught me a lot and gave me a lot of advice.
https://www.linuxquestions.org/quest...-a-4175716218/

I'm sorry for causing trouble to you because of my reckless behavior. I'm really sorry. I hope to hear your suggestions on what I should do next. I look forward to your reply. Thank you.

---
SlackwareCN: The Slackware Linux CN Community
slackwareCN：https://github.com/slackwarecn
slackwareCN：http://www.slackwarecn.cn
slackwareloong doc ：https://github.com/slackwarecn/slackbook_cn_loongarch64
slackwareloong web doc : https://slackwarecn.gitbook.io/slackbook_cn_loongarch64

Oh, no no no. You've caused no trouble at all, and I'm happy to see your enthusiasm for Slackware on this platform. Just keep doing what you're doing.

Don't let LuckyCyborg disturb you. We're mostly used to him around here.

4 members found this post helpful.

Thank you for your encouragement. I will continue to update "slackware for LoongArch", so that slackware can be played happily on the LoongArch architecture.
without Patrick Volkerding, Slackware for LoongArch would cease to exist.

Best regards
---
SlackwareCN: The Slackware Linux CN Community
slackwareCN：https://github.com/slackwarecn
slackwareCN：http://www.slackwarecn.cn
slackwareloong doc ：https://github.com/slackwarecn/slackbook_cn_loongarch64
slackwareloong web doc : https://slackwarecn.gitbook.io/slackbook_cn_loongarch64

3 members found this post helpful.