SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 Re: Off Topic / General Chat » Debian Sid upgrade intervals » 2015-07-14 19:32:58

It depends. I upgrade them every time I boot into one. So the installs that I like the best, gets updated a lot more than the installs I use less. At any given time I have at least 10 installs running. Often a lot more.

But if you want to know how often I recommend doing it, so every 2 days or so. At least for the first few months in the cycle. After a year or so, doing it once weekly is more than fine.

In regards to holding packages, this is also potentially a dangerous practice, and I wouldn't recommend it unless you absolutely need to upgrade. It's better to hold off the entire upgrade for 3-4 days or so, to see if the warnings disappear. Also, holding some packages are totally risk-free, while holding others are pretty reckless behavior. Make sure you don't hold packages for a long periond of time, not unless you are 100% sure that those packages doesn't in any way depend on any system-critical packages.

#2 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2) » 2015-07-14 00:12:37

porkpiehat wrote:
spacex wrote:

Lots of new users are scared and intimidated by those kind of turials, especially if they involve the use of a terminal app, or any kind of chroot'ing.

What is a turial? It sounds scary and intimidating, but I don't know what it is.

ROFL. Tutorial big_smile

#3 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2) » 2015-07-13 23:29:13

Sector11 wrote:
spacex wrote:

This was the kind of tutorial that you can not offer to any newbies or unskilled users. Tell them how to do grub-efi, and don't confuse them with this stuff. The ones who should be doing it your way, are already doing it. tongue

WRONG!  The ones that don't know how to do it and have a test distro/HDD/computer - or have a great backup system in place and dare to try - can learn tons with "hands on".

And that's me.  A "hands on" guy!

Yes, but you are not the average user. And you are old school. Lots of new users are scared and intimidated by those kind of turials, especially if they involve the use of a terminal app, or any kind of chroot'ing. The tutorials for that stuff exists. The people who want to learn it, will always be able to, but for all the rest, we have to supply the easiest way to do it. And let's put it this way. UEFI boot by "grub-efi" offers more than enough of a challenge for most people. They are used to grub, and grub-efi will be familiar to them. We don't need to confuse them anymore than necessary. The use of rEFInd and EFI stub is way beyond what you could expect most users to learn, understand and handle.

The Debian installer installs grub-efi by default. You boot in efi-mode, create a efi-partition, and if asked by the installer, choose to force an efi-installation. That's as easy as it has to be. There is no reason why Bunsen should be doing it any different.

#4 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2) » 2015-07-13 22:03:50

Head_on_a_Stick wrote:
Head_on_a_Stick wrote:

I can write up a tutorial on how to convert a non-EFI BunsenLabs system to pure EFISTUB booting if there is any demand.

Silly me...

I forgot about this:
http://crunchbang.org/forums/viewtopic.php?id=39256

This was the kind of tutorial that you can not offer to any newbies or unskilled users. Tell them how to do grub-efi, and don't confuse them with this stuff. The ones who should be doing it your way, are already doing it. tongue

#5 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2) » 2015-07-13 22:01:15

Head_on_a_Stick wrote:

@spacex -- I don't use GRUB for UEFI booting.

I much prefer direct booting of the kernel using it's CONFIG_EFI_STUB capability  cool

I can write up a tutorial on how to convert a non-EFI BunsenLabs system to pure EFISTUB booting if there is any demand.

EDIT: At any rate, I would prefer a live ISO using UEFI 'cos then I can use it for my internet banking.



grub-efi is much more handy when you multiboot lot's of distros. Which I always do smile

#6 Re: Artwork & Screenshots » July 2015 Screenshot Thread » 2015-07-13 16:01:51

hhh wrote:

A couple I've missed...

smacz wrote:

Nice bunsen ASCII art @hhh

It's 2ion',s just modified a bit...
http://crunchbang.org/forums/viewtopic.php?id=39723

spacex wrote:

You are the only one I've seen that has made the xfce4-panel look this good smile

Between your admiration of the dark Bunsen themes, your support of the new Bunsen ISOs and this comment, I owe you a sincere thank you! I'll post my config (probably Tuesday). Don't be surprised if I hit you up with a PM for live-build tips one of these days. smile

Oh, I'll help if I can. But I'm no expert on live-build myself. Like you, I took the crash course a little while ago, and pretty much learn new things as I need to implement something I haven't done before. But now I'm working with live-build for testing and unstable, and that has thrown me quite a few curveballs. But I'm getting there, my last build was fine.

As for uefi-support, there is a chance that it could be implemented in live-build quite soon, so that there is no need to find an alternative way to do it. This is the reply I got from the live-build project when I asked them about uefi-support:

It's on my todo list. I started implementing it a few months back, and
got a very messy set of working code implemented, but I haven't gotten
around to finishing it yet, I've had a lot of other things to work on.
I don't know if/when I'll finish it; perhaps sometime over the next
several weeks when I should hopefully be finished with the things that
I've been working on in the mean time.

#7 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2) » 2015-07-13 15:50:30

@twoion

I guess they are working with it for live-build. Here you see the response I got when I asked them about uefi for live-build:

It's on my todo list. I started implementing it a few months back, and
got a very messy set of working code implemented, but I haven't gotten
around to finishing it yet, I've had a lot of other things to work on.
I don't know if/when I'll finish it; perhaps sometime over the next
several weeks when I should hopefully be finished with the things that
I've been working on in the mean time.

#8 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2) » 2015-07-13 11:20:53

KrunchTime wrote:
Head_on_a_Stick wrote:

The only problem I can see so far is that the ISO image in non-EFI sad

Another reason to go the netinstall route.

But it's really easy to workaround. The long and tricky uefi-guides is scary for some. But I have a very easy way to do it. No cli-experience needed.

DISCLAIMER: NO GUARANTEES, but it works for me. YOU may BLOW up your computer!!!

1. Install any kind of Debian install in uefi-mode. Let the efi partition be sda1, but reserve partitition 2 for Bunsen or whatever. Put Debian below in the chain, so you can remove it later.

2. After successfully created a Debian uefi-install, then install Hydrogen as normal, write grub to PARTITION.

3. Reboot and run sudo update-grub in the Debian-install you created in point 1.

4. Now reboot, and boot into Bunsen. Add something like this to fstab: (Of course replace it with your UUID)

 /boot/efi was on /dev/sda1 during installation
UUID=9977-5E48  /boot/efi       vfat    umask=0077      0       1

5. Now then, reboot into Bunsen once again, but this time the efi-partition will be mounted.

Open a terminal, run

sudo apt-get install grub-efi

Let it replace grub-pc, just accept and go for it.

Then,

 sudo grub-install /dev/sda

update-grub should automatically be run in  the previous step, if not, do it manually.

That should be it..., reboot, and Bunsen should now be in charge of the uefi-boot. The Debian Bootloader is still there. Remove it if you want to, but it doesn't hurt if it only sleeps in the efi-partition.

#9 Re: Artwork & Screenshots » July 2015 Screenshot Thread » 2015-07-13 02:18:29

Nothing special. Just started on the sequel to colors. A testing-release with the codename "redbug".

2015-07-13--14367534901366x768scrot.png

#10 Re: Development » BunsenLabs Development Team and current status » 2015-07-12 23:19:28

Nice to see him banned. Those guys never give up though, so expect him back again. Anyway, I'm starting to get so pissed about all the nagging about continuing CrunchBang that I'm going to remove any images that are close to CrunchBang from my own project. And me who thought about offering a Waldorf-suite on top of TweakOs, but enough is enough. Let CrunchBang be dead, as Corenominal wanted.

But who cares, those wannabees creating clones will soon be forgotten anyway. Nobody succeeds in the long run by just copying others. You succeed if you can offer something new and unique. If you actually have something to contribute, besides copying stuff. There are probably 400000 people able to make a clone of CrunchBang. It isn't a big achievement.

Well, off I go. To delete Wilma and the Waldorf-snapshot. Because I won't participate in feeding this stupid obsession about CrunchBang. Don't read me wrong. CrunchBang was a very nice release, and had/has an awesome community. But the last couple of years there has been very little development, and not much happening until Bunsen. So let's drop the ball dead at once. CrunchBang is dead, and will remain dead no matter how many clones that pop up. Actually, they are a waste of space, and adds nothing of value to either Debian or Linux.

PS, the last part doesn't apply to Bunsen, because Bunsen isn't a clone, and Bunsen do have something to offer.

There, now I got it out. Finally  smile

#12 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO 32 & 64 bit (alpha2) » 2015-07-12 20:03:43

phle wrote:
iMBeCil wrote:

How comes amd64 is smaller by 100MB compared to i386? What's missing?

I guess nothing's "missing", but rather "added": see #1: (my boldings)

hhh wrote:

BunsenLabs GNU/Linux 8.1 (Hydrogen)

The 64 bit build should fit on a CD. The 32 bit build will not as it includes 2 kernels, 686-pae (for most computers) and 586 (for older machines). If you install the 32 bit ISO, it will install both kernels. For more info, see this post and the following one...
http://crunchbang.org/forums/viewtopic. … 44#p434144

There is a way to avoid it. Use linux-flavour 686-pae and remove the 586 kernel from the pool. Because the kernel will still be in the pool, even if linux-flavour is used. But of course, that's probably not a good idea, unless you are going to make a special image for old pc's. But I guess that one slightly bigger image is better than having three different iso's smile

#14 Re: Development » RELEASED: BunsenLabs 8.1 (Hydrogen) Live ISO (alpha) » 2015-07-12 12:31:43

For the next builds, why not get the iso's up at sourceforge. Because there are some people that doesn't touch torrents or torrent-clients. Just a suggestion.

#15 Re: Help & Support (Testing/Unstable) » BL Under Sid/Unstable » 2015-07-11 23:44:52

Sector11 wrote:

Incorporating "grave" and "serious" bugs of Debian apps that are NOT Bunsen specific means you are not really testing Bunsen but testing Debian8

None of the bug you show have anything to do with Bunsen but they do have to do with Debian.

hold and unhold are SID's best friends to keep SID running properly.

Yes, if you create a production-system, surely it is. But grave and serious bugs doesn't mean that it will effect all users in all hardware-configurations, so it kind of depends whether you want to take the risk or not. Actually, playing it safe with Sid, kind of contradicts the whole purpose of Sid. Which is to install it with bugs and all, and then help to fix it. If everyone played it safe, then Sid pretty much would be left in a stand still mode...

As for Bunsen, obviously it includes the whole compilation as such, and not only the Bunsen-configs. As with my release. If things doesn't work properly with Debian, I don't say that it has to do with Debian, so I'll just have to wait for it to be fixed. Nope, obviously I look for the solutions myself. Always. I'm not waiting for Debian to solve anything, and if I'm not able to fix the Debian-issue, then I work around it. Waiting and holding isn't for me. I do this for fun and entertainment, and putting myself in difficult situations with lots of issues, is actually where all the fun is.

Bunsen is OS number 8 on this PC, and I have it installed twice. To play with it. Bunsen is in alpha-state or sub-alpha state. Being afraid of wrecking a install at this time is meaningless, as there will be lots more happening, and the fact that it isn't the finished build yet. So people will be reinstalling Bunsen many more times in the next month or so.

Therefore, don't even think of using Bunsen as your main OS and production system at this point. Install it to test and play with it, without any worry about wrecking anything, and if you keep holding stuff for to long, then it also could potentially become a issue later. Unless there are something major that will make your system unusable, just go for it. The fixes will come soon, and in the meantime, work around it.

So you see, we approach Sid in a totally different manner. I have no interest of staying safe with Sid. I'm not using Sid because I have hardware that needs it. I use it because I get issues. And I do want issues. The more, the merrier. Nothing is more boring than something that just works. Actually, a computer without issues are completely useless to me.

But obviously, with 8 different OS and distros on one computer, there will always be some of them who are functional wink

#16 Re: Help & Support (Testing/Unstable) » BL Under Sid/Unstable » 2015-07-11 19:55:45

@Sector11

Yes, but the whole point of this was to test Bunsen on Sid, and then I can't wait or put packages on hold. I knew the risk, and it doesn't matter at all if the whole install gets borked or broken. It's just a testinstall anyway smile

But I assume that I will be able to fix the network-issue, so all in all, I will say that the upgrade went just fine.

#17 Re: Help & Support (Testing/Unstable) » BL Under Sid/Unstable » 2015-07-11 14:53:46

Ok. Going for it now. Have changed sources to Sid, and installed "apt-listbugs".

Ok, apt-listbugs gives this report:

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of gstreamer1.0-libav (→ 1.4.4-2) <Outstanding>
 b1 - #767423 - tracker-extract SIGSEGV
grave bugs of iceweasel (31.8.0esr-1~deb8u1 → 38.1.0esr-2) <Outstanding>
 b2 - #788708 - iceweasel: GStreamer causes segmentation fault
serious bugs of bash-completion (1:2.1-4 → 1:2.1-4.1) <Outstanding>
 b3 - #785271 - dh_bash-completion script/file list autodetection fails hiding bugs which can become RC
serious bugs of liblognorm2 (→ 1.1.1-1) <Outstanding>
 b4 - #788852 - liblognorm2: removal of liblognorm2 makes files disappear from liblognorm1
serious bugs of openssl (1.0.1k-3+deb8u1 → 1.0.2d-1) <Outstanding>
 b5 - #768476 - openssl: Removes symbol without SONAME bump
   Merged with: 768522 769023 770278 770605 771169 771993 781094 781929 787712
grave bugs of libxml2 (2.9.1+dfsg1-5 → 2.9.2+dfsg1-3) <Forwarded>
 b6 - #766884 - libxml2: "validity error : ID ... already defined" errors with xmllint --noent
grave bugs of iceweasel (31.8.0esr-1~deb8u1 → 38.1.0esr-2) <Forwarded>
 b7 - #790498 - iceweasel: upgrading from jessie makes all passwords in the password manager invalid
serious bugs of libgtk2-perl (2:1.2492-4 → 2:1.2495-1) <Forwarded>
 b8 - #790532 - FTBFS: Failed 1/228 test programs
serious bugs of udev (215-17+deb8u1 → 222-1) <Resolved in some Version>
 b9 - #787364 - ifup@.service does not start any more with systemd 220 (Fixed: systemd/220-3)
   Merged with: 787263
Summary:
 bash-completion(1 bug), libxml2(1 bug), udev(1 bug), liblognorm2(1 bug), openssl(1 bug), gstreamer1.0-libav(1 bug), iceweasel(2 bugs), libgtk2-perl(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] 

OK, I'm going for it anyway, will report back later....

Update. Turned out just fine. I had to reboot 3 times to get a wifi-connection. That's the only thing I've noticed this far. Could be a coincidense, as my laptop does this sometimes, when I reboot from another distro. Or related to bug9(b9). Don't know yet. Will have to test a few more times to see.

OK. tried rebooting again, and no wifi. The tried again and got reported as connected but didn't work. Then rebooted once more, and then it worked. So I get a working wifi every three times I boot. It seems that if I wait a little at the grub-screen and at the lightdm-login, it is a better chanche to have a working wifi when I'm up. This is a very fast ssd. Too fast it seems smile

I haven't checked which version of systemd I have.

OK, systemd-version 222-1 and openssl 1.0.2d-1. So it should be fine, but I still have some kind of network-issue. Will research it more.

#18 Re: Help & Support (Stable) » BunsenLabs alpha - movie night gone? » 2015-07-11 11:30:42

Head_on_a_Stick wrote:
KrunchTime wrote:

Here's another way to install libdvdcss2.  If you're using Debian Unstable, substitute unstable for stable in the apt source links.

If repositories are to be added, using deb-multimedia makes more sense than a third-party repo, IMO.

I do think the best solution is to avoid adding any repositories at all and just use the .deb package if all the user wants is DVD-playback capability but maybe that's just because I'm a purist  O:)

+1

#19 Re: Help & Support (Testing/Unstable) » BL Under Sid/Unstable » 2015-07-11 00:38:26

KrunchTime wrote:
spacex wrote:

What is most useful for the project? Doing it from the live-cd version, or the netinstall? I have both of them installed.

I don't think it matters, although I'm partial to netinstalls now after using them for my last four install experiences.

Ok, I'll try that tomorrow. It's 2.37 AM here, so it's a little bit late to start on it now smile

#20 Re: Help & Support (Testing/Unstable) » BL Under Sid/Unstable » 2015-07-10 23:52:47

KrunchTime wrote:

@Sector11:  Thank you, but I was looking more for the experiences of other users who may already be using BL tracking Sid/Unstable and I've experienced Xorg bug warnings on my Wally install tracking Sid/Unstable.  I held the packages back for a couple of weeks, tried again, and everything was fine.

I haven't yet, but I have with TweakOS, and have no issue with Sid there, so I can't see why there would be any with Bunsen. But I'll try tomorrow. I'm waiting for my sid-based live-build to complete, so I can't do much right now. I'll give it a go. What is most useful for the project? Doing it from the live-cd version, or the netinstall? I have both of them installed.

#21 Re: News & Announcements » A community continuation: BunsenLabs » 2015-07-10 23:42:08

Sector11 wrote:

Too late now it's gone and I'm happy.

The main advantage for me with pulseaudio is that I get more power out of the speakers. I get to go above 100%. But that's needed on this crappy laptop-speakers smile

#22 Re: Help & Support (Stable) » BunsenLabs alpha - movie night gone? » 2015-07-10 22:59:55

Nah. I just stream Netflix in Chrome with html5, so everything is fine for me. No need for any codecs. But of course, other people have other needs:)

#24 Re: Feedback & Suggestions » What is BunsenLabs? » 2015-07-10 22:47:17

Already tried it as you know. But it got there because YOU took the matters in your own hands, and made it happen. I didn't expect that smile But anyway, now I'm drinking Captain Morgan and watching The Boss live in Dublin, while I'm building a sid-version of TweakOs-Colors, so don't expect me to make much sense today  tongue

#25 Re: News & Announcements » A community continuation: BunsenLabs » 2015-07-10 22:42:53

Sector11 wrote:

"Zero sound" - on #! Waldorf - #! Wheezy and now on Bunsen.  I'm use to it ... went NUTZ with Waldorf trying to get it to work.  NADA! until I finally took it out and went ALSA!   wink

Others I know swear by it.

EDIT:  And another few distros I've tried over time.

Did you try "sudo alsactl init"? That solves it for me, but I have never any issues with Pulseaudio on any of my hardware. But I only use Intel. Always. Maybe that's got something to do with it?

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo