|
|
Post by ylee on Oct 30, 2020 14:11:36 GMT
I've noticed that the Bodhi Live USB (for 5.1 & 6.0) doesn't come with gparted (parted is there). Do you think there's value in having this system tool available on the LIVE USB to aid installation / recovery etc - I'm pretty sure it's part of the standard Ubuntu Live USB offering and size isn't horrendous. This would be just for pre install LIVE USB use - not post installation. The way we build the ISO and the way ubiquity works what is installed in the ISO ends up installed. I have wondered if there is any way to do stuff like this without having to run some uninstall script on the first boot of the installed system. ... given there are quite a few issues with broadcom wifi card - is there value in shipping the new distro (for post installation inclusion) with firmware-b43-installer (not sure if this requires an active network connection to run though so may be non starter anyhow?) and & linux-firmware too - to aid "offline" broadcom wifi setup, or is this simply muddying the distro maintainability waters unnecessarily without much gain (addressing edge cases)? At one time Bodhi had this, back in the BL1.x days. There is a repo of a sort on the ISO, in a folder called dists. One could in fact install the broadcom driver from that repo, but there are some technical problems with making the ISO that are unsolved at the moment. So it would be a little bit of work to do so with the current ISO or the BL5.x ISOs. I currently have 6 outstanding issues that in a ideal world I would like to solve, that being one of them. But I also have to balance that with time constants. I was aware of the issue when I released BL 5.1 and was aware of the issue with Jeffs prior releases. But I did not investigate it with Jeffs releases and with the release of 5.1 I found myself spend too much time unfruitly trying to solve it, so I released it anyway with the issue still present. So i can make no promises the issue will be resolved on the actual release of 6.0. This is a learn as you experience for me and contrary to public opinion I don't know everything  lol |
|
riban
Member
Posts: 10
Likes: 1
|
Post by riban on Oct 30, 2020 14:12:03 GMT
The environmental variable TERM is set to xterm but xterm is not installed by default. Is this appropriate?
|
|
|
|
Post by ylee on Oct 30, 2020 14:15:07 GMT
The environmental variable TERM is set to xterm but xterm is not installed by default. Is this appropriate? Probably not, lol. I will check all the default environmental variables before the final release and make sure they are reasonable. Thanks for reminding me. |
|
|
|
Post by fidoedidoe on Oct 30, 2020 15:10:02 GMT
The way we build the ISO and the way ubiquity works what is installed in the ISO ends up installed. I have wondered if there is any way to do stuff like this without having to run some uninstall script on the first boot of the installed system. Okay - I understand. I think Ubuntu has gparted on the LIVE USB and is not installed by default (from memory), so maybe there's a clue in the way they build their LIVE USB / Installer - but TBH it's not a real issue (edge case - let's move on) This is a learn as you experience for me and contrary to public opinion I don't know everything lol It can't be true, dreams shattered |
|
|
|
Post by ylee on Oct 30, 2020 15:14:09 GMT
Further investigation reveals it is rather complex figuring out what sets the TERM environmental variable. On the GUI side of things and using installed terminal emulators like terminology and lxterminal and so on, these apps modify or set themselves the value of this variable. On Bodhi if you switch to a tty you will find it is set to 'linux.' As a result, I am not messing with the TERM environmental variable. I think the variable is used to specify what a terminal is capable of not the exact app installed. On the ISO I think it should be set to xterm-256color tho, unsure why on the ISO it is not. I will look into that. The actual default app for a terminal emulator should be x-terminal-emulator. That is set by update-alternatives, and on our ISO it should be terminology. If it is not I will fix that. I don't really think Bodhi needs xterm installed by default, but I will look over past ISOs and see if we ever did have that installed by default.
|
|
|
|
Post by fidoedidoe on Oct 30, 2020 15:25:52 GMT
Hi fido Anyway, there is no problem in installing gparted in live session with Wifi or cable connection. firmware-b43-installer. I followed your wiki instructions to enable wifi and this way does not work for me. My card is BCM 4352 and only bcmwl-kernel-source work for me. Yep - agreed, edge case relating to gparted (mine was no-wifi, offline linux partition resize and i had to hand a Bodhi Live USB - ), it wasn't a major issue and completed the task using a GParted LIVE USB in the end. broadcom firmware - thanks for feeding back - I'll adjust asap. Can you give me the Vendor & Device PCI IDs for your specific hardware so I can validate the steps and correct as/where necessary  |
|
|
|
Post by thewaiter on Oct 30, 2020 15:28:49 GMT
Of course
stefan@pc:~$ lspci -nn -d 14e4:
03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
Maybe I missed something. I never played with this. I always install bcmwl and it works.
S
|
|
|
|
Post by fidoedidoe on Oct 30, 2020 16:06:12 GMT
Of course stefan@pc:~$ lspci -nn -d 14e4: 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Maybe I missed something. I never played with this. I always install bcmwl and it works. S The installation instructions suggest that with a vendor:device id of: [14e4:43b1] install method should be bcmwl-kernel-source (this is established in Step #2 of the instructions - TL;DR? ) however if you went wrong the instructions are not working as intended. I have now refined, can you revisit (just step #2 was modified) and try again - or conceptually review and feedback?? Link: www.bodhilinux.com/w/quick-faq/networking-wi-fi-faqs/ |
|
|
|
Post by thewaiter on Oct 30, 2020 16:12:59 GMT
oh, OK, thanx That is what I mentioned. I missed it Stefan |
|
|
|
Post by wolfgangblack on Oct 31, 2020 0:20:04 GMT
The reason for using pure Enlightenment as opposed to Moksha would be personal, mostly a matter of preference. I am releasing this for three reasons, one I get asked to do quite often. Two, to see how popular it will be, how many of our users migrate to it. And three, to give enlightenment better exposure, better testing and perhaps attract more users -- those that prefer enlightenment. Maybe even gain more support from some of e-devs themselves. I'd love to see a good pure Enlightenment version and think it is a great idea to release a Moska and a E24 version. Used E way way back and the bugs and usability were terrible as everyone knows but I have to admit that Moska is pretty nice. Not sure pure E24 will be better than Moska.... |
|
zuul
Member
Posts: 49
Likes: 45
|
Post by zuul on Oct 31, 2020 10:13:19 GMT
Hello,
I have installed BL6 with Moksha desktop. I never thought that a prealpha release could be so stable. It appears obvious to me : BL6 will be the only Linux distribution on my all machines.
|
|
|
|
Post by Hippytaff on Oct 31, 2020 10:16:23 GMT
Our devs are meticulous, apart from a few things, such adding a BL6 repo I agree it feels as stable as any other distros stable release.
|
|
yrjo
Member
Posts: 1 
Likes: 0
|
Post by yrjo on Oct 31, 2020 11:24:26 GMT
pulled git but:
sudo apt install ./moksha_0.3.2-2_amd64.deb
The following packages have unmet dependencies:
moksha : Depends: libedbus-dev (>= 1.7.10) but it is not installable
Depends: libefl (>= 1.25.1) but it is not installable
Recommends: terminology but it is not going to be installed
|
|
|
|
Post by ylee on Oct 31, 2020 11:53:37 GMT
pulled git but: sudo apt install ./moksha_0.3.2-2_amd64.deb The following packages have unmet dependencies: moksha : Depends: libedbus-dev (>= 1.7.10) but it is not installable Depends: libefl (>= 1.25.1) but it is not installable Recommends: terminology but it is not going to be installed First install libefl from the same repo and then install libedbus-dev from the same repo. then install moksha |
|
|
|
Post by serendipity7000 on Nov 4, 2020 15:24:39 GMT
I'd like to second (or third or fourth) - a 32 bit version. I have a lot of 32 bit machines and netbooks. I buy, fix and sell them. Many people buy 32 bit netbooks on a well known auction site are very happy to buy a small netbook for a very low price, when they can't afford a pc or laptop and I like the idea that anyone can afford a computer. Some of these machines just keep going and need very little repair.
|
|
lol
