2015 ... Where Has The Time Gone ... Beta-4

Tips and Techniques on day to day stuff

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby saintless » Sun Jan 18, 2015 8:56 pm

Hi, Brenton.

Few potential problems not directly related with FoxyRoxy functionality:
1. The information in dpkg status for all removed kernels is still included and running apt-get upgrade will install again in /lib/modules all removed kernels and new initrd files will be builded for them in /boot
2. Running apt-get upgrade is blocked from lighttpd security problem message. I need to remove lighttpd before apt-get upgrade and install lighttpd again after that. Otherwise the upgrade is impossible.
I think you can remove safe the information about:
Code: Select all
apt-get purge linux-image-2.6-486 linux-image-2.6.32-5-486 linux-image-2.6.32-5-686 linux-image-2.6.32-5-686-bigmem

These two will be reported as automatically installed and no longer required:
Code: Select all
linux-base libuuid-perl

But I think it is because the new bigaufs kernel has different dependencies from original bigmem kernel. I think it will be safe choice to keep both packages as manually installed:
Code: Select all
apt-get install -reinstall linux-base libuuid-perl

Also linux-image-2.6-686 package could be removed but it is needed for linux-image-2.6.32-5-686-bigmem and I guess the safe choice is to keep it installed for linux-image-2.6.32-5-686-bigaufs also.

3. I think the multiuser function is broken for some reason. I had similar problem with DD in the beginning. For example /home/user is owned by root but even changing the ownership back to user does not allow user to startx.

I know FoxyRoxy needs to run as root in order to work properly and this issues are not very important but I can try to find out why user account does not work if you like to keep multiuser function available.

I will test the drive pooling in the next days but I'm not sure how to test properly samba, MountStora and runminidlna. I will read again your posts in the forum about that.

Cheers, Toni
User avatar
saintless
 
Posts: 246
Joined: Sat Jul 14, 2012 7:01 am
Location: Bulgaria

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby jbv » Sun Jan 18, 2015 9:19 pm

Hi Toni,

Thanks for that info. That may take a little time to sort out properly.
Those changes will really need to be done at the 01-FoxyRoxy.squashfs level.

In some ways, things are a little messier to do at that level, as I need to follow-through what happens when 02-FoxyDesktop gets overlaid, and I've become quite used to working with the Desktop/GUI :)

The kernel dependencies should be the same, although as the source-package downloaded may have been a slightly later revision (I think it was), anything is possible.
Dependency trees are a real pain. Getting the FFmpeg stuff updated was a slog. I needed to remove more than half of the multi-media stuff and put it back in.

Once again, I will look into that also - Thanks.
I may not get to do much until the weekend, so I'll break it down to small chunks and sort out the first lot of feedback you gave me first :)

Cheers, Brenton
jbv
 
Posts: 600
Joined: Sat Jul 14, 2012 2:02 am
Location: Sydney, Australia

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby jbv » Mon Jan 19, 2015 10:44 am

Hi Toni,

Thanks for the pointers on policykit-1
I had avoided installing it because it also installed some of the basics of consolekit and when I last played with consolekit, things went from ugly to horrible, very fast ... like in a heart-beat :)

Anyway, with consolekit installed and the updated dbus package (dbus was already installed - we use dbus for the automagicmount and a heap of other stuff), gnome-disks now behaves.

It took a bit of putzing around to test properly, but fortunately I have quite a few spare drives and a decent hot-swap bay. I still hope I didn't blow anything away :)

There is a bit of a glitch that I can't fix, and that is if you use gnome-disks to mount/unmount drives, it does not send messages back through udev so the DrivePool and auto-magic mounting is not 100% right, but at least it mounts it properly, so I may need to just add this to the "notes" about quirks and idiosyncrasies :)

gnome-disks ... as in ... [system tools] --> [Disk Utility] can't cope with a drive that is part of a DrivePool and it "barfs" telling you that the drive is busy, which is to be expected, but it is basically working and working properly.

I think I've also fixed the initramfs thing, but I haven't tested that yet ... Another 13 hour day today and I'm pretty beat :(

So ... I'll call it quits for now, and look at the other bits later this week or on the weekend.

Thanks mate, You're a legend :)

Cheers, Brenton

Note to self ... Items from previous page are sorted. All items on this page are still outstanding.... Test the whole freaking lot again when you are finished (on red stick)
jbv
 
Posts: 600
Joined: Sat Jul 14, 2012 2:02 am
Location: Sydney, Australia

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby saintless » Mon Jan 19, 2015 9:02 pm

Glad to help, Brenton :)

3. I think the multiuser function is broken for some reason. I had similar problem with DD in the beginning. For example /home/user is owned by root but even changing the ownership back to user does not allow user to startx.

Here is the fix for this:
Code: Select all
chown -R user:user /home/user
apt-get install xserver-xorg-core

Then startx for user works.

Toni
User avatar
saintless
 
Posts: 246
Joined: Sat Jul 14, 2012 7:01 am
Location: Bulgaria

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby jbv » Sat Jan 24, 2015 1:07 pm

Hi Toni,

Thanks for finding those glitches. I think I have nailed them all today. From my first-pass testing everything is working great.
While I fixed the permission on /user/home, I did not load the xserver-xorg-core package.

I have also downloaded and complied the latest source from Intel for their Network Cards.
As this is GPL, it will now be part of the FoxyRoxy base.
e1000 has been updated from 7.3.21 to 8.0.35
e1000e has been updated from 1.2.20 to 3.1.02

These provide support for Intel's newest Ethernet Chips as used in the latest INTEL NUCs
... I have tested this on 4 machines (with and without Intel Network Interfaces) and everything works.
Tomorrow I will be testing it on a NUC that requires the latest drivers.
... I have the NUC, but I know that testing that tonight will mean no sleep, so I will leave the final test until tomorrow :)

I have also added a couple of more tools:
ethtool (great for probing and poking at your network card)
lshw (great for working out what hardware the system has)

With regard to apt-get update
I ran that today and it worked. I'm not sure why you had an issue with lighttpd, as it did not cause me any grief. I checked the start-up script in /etc/init.d and it looked fine. It calls the appropriate init-lib so the update should have been able to shut-it down and restart it after the update, which it did on my machine. It is quite strange that you needed to un-install it. At worst, I would have thought that you may need to stop it, but in-installing doesn't sound right. Along similar lines, I didn't need to re-install linux-base or libuuid-perl. I had already played with the dpkg database a little, so that may have been why. I have also [i]tweaked[/b] the dpkg database entry for the new kernel, so this should all be okay now.

The whole apt-get update thing is a bit of an issue though. It works and it works perfectly, the problem is that when you run an update is pulls in packages from both 01-FoxyRoxy and 02-FoxyDesktop. The problem is that I'm not sure how to create the script to fix up both of the base packages. Well, that's not strictly true, I do know how to create the script, but just thinking about it makes my head hurt. I can't imagine how painful it will be to create the darn thing.

While it still wont' be trivial, it would be a lot simpler if I just merge 01-FoxyRoxy and 02-FoxyDesktop.
Now that you've got your own distro, I am really starting to re-think the whole thing about keeping the core and desktop split.

When I (We) first started this journey, I don't think either of us truly understood how *nix dependencies are far worse than the Windoze DLL hell. Back then, I thought that if we kept the core (pre-X) split from the desktop (X+) we would have a layer of insulation. We both now know better :lol:

Oh, another little thing I did today was to split the /etc/init.d from the base packages and all of that now live in 05-FoxyConfig where it belongs :)

So, back to the update thing ... while it will work and you can do it, you will need to take a 95-create snapshot. If you don't clean up the snapshot, you effectively blow away all the work I've done to keep dpkg valid. I'm going to ponder this one for a little while, before I jump in and sort it.

I hope to have a Beta-4a ISO replacing the current Beta-4 in the next day or two.
I just want to test a few more things.

Thanks for you help mate, it is sincerely appreciated.

Cheers, Brenton
jbv
 
Posts: 600
Joined: Sat Jul 14, 2012 2:02 am
Location: Sydney, Australia

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby saintless » Sat Jan 24, 2015 6:42 pm

Hi, Brenton.

Please, wait for a while with Beta-4a iso. Exploring dpkg database files shows some dpkg related things might need fixing.
I don't know how important is for you to keep the installed packages registered in /var/lib/dpkg/status but from my experience keeping important packages hidden could create problems later.
For example xserver-xorg-core is a dependency of xserver-xorg which is a dependency of xorg package. But it seems xorg packages are not included in 02-FoxyDesktop status file (02-status.new). But you can see xserver-xorg-core files included in 02-FoxyDesktop /var/lib/dpkg/info folder.
Edit: Checking again /var/lib/dpkg/info in 01-FoxyRoxyINTEL.squashfs contains files for xserver-xorg-core but they should be in 02-FoxyDesktop.
If you need help sorting out the hidden packages I can look at it and suggest some solution.

I also think merging 01-FoxyRoxy and 02-FoxyDesktop is the best way to go and will make your work easier. I think you can keep without problems the configuration files in 05-FoxyConfig as long as 05-FoxyConfig does not include /var/lib/dpkg files inside.

Here is the problem I have with apt-get upgrade:
After installing firmware-linux-nonfree and running apt-get update:
Code: Select all
root@debian:~# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  at base-files bind9-host dbus dbus-x11 debian-archive-keyring dnsutils dpkg
  exim4 exim4-base exim4-config exim4-daemon-light file firmware-linux-free
  gnupg gpgv grep gzip host initscripts isc-dhcp-client isc-dhcp-common
  libaudio2 libbind9-60 libcups2 libcurl3-gnutls libdbus-1-3 libdbus-glib-1-2
  libdns69 libexif12 libexpat1 libgc1c2 libgcrypt11 libgl1-mesa-glx
  libglu1-mesa libgnutls26 libgssapi-krb5-2 libgssrpc4 libicu44 libisc62
  libisccc60 libisccfg62 libk5crypto3 libkadm5clnt-mit7 libkadm5srv-mit7
  libkdb5-4 libkrb5-3 libkrb5support0 libldap-2.4-2 liblwres60 libmagic1
  libmms0 libmtp8 libnautilus-extension1 libnspr4-0d libnss3-1d libopenjpeg2
  libpixman-1-0 libpoppler5 libproxy0 librsvg2-2 librsvg2-common libsmbclient
  libssl0.9.8 libtasn1-3 libtiff4 libvte-common libvte9 libwbclient0 libx11-6
  libx11-data libxcb-render0 libxcb1 libxcursor1 libxext6 libxfixes3 libxi6
  libxinerama1 libxml2 libxml2-dev libxp6 libxrandr2 libxrender1 libxres1
  libxt6 libxtst6 libxv1 libxvmc1 libxxf86dga1 libxxf86vm1 lighttpd
  linux-base linux-image-2.6.32-5-486 linux-image-2.6.32-5-686
  linux-image-2.6.32-5-686-bigmem locales mutt openssh-client openssh-server
  openssl perl perl-base perl-modules procps python python-minimal python-vte
  samba samba-common ssh sudo sysv-rc sysvinit sysvinit-utils tzdata udisks
116 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 144 MB of archives.
After this operation, 13.0 MB disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://cdn.debian.net/debian/ squeeze/main base-files i386 6.0squeeze10 [64.0 kB]
***   many lines like this one  ***
Get:116 http://cdn.debian.net/debian/ squeeze/main ssh all 1:5.5p1-6+squeeze5 [1,248 B]
Fetched 144 MB in 1min 57s (1,225 kB/s) 

Then I get this message:
Code: Select all
lighttpd (1.4.28-2+squeeze1.3) stable-security; urgency=high

  The default Debian configuration file for PHP invoked from FastCGI was
  vulnerable to local symlink attacks and race conditions when an attacker
  manages to control the PHP socket file (/tmp/php.socket up to 1.4.31-3)
  before the web server started. Possibly the web server could have been
  tricked to use a forged PHP.

  The problem lies in the configuration, thus this update will fix the problem
  only if you did not modify the file /etc/lighttpd/conf-available/15-fastcgi-php.conf
   If you did, dpkg will not overwrite your changes. Please make sure to set

        "socket" => "/var/run/lighttpd/php.socket"

  yourself in that case.

 -- Arno Töll <arno@debian.org>  Thu, 14 Mar 2013 01:57:42 +0100

lighttpd (1.4.28-2+squeeze1.1) stable-security; urgency=high

  To fix a security vulnerability in the design of the SSL/TLS protocol
  (CVE-2009-3555), the protocol had to be extended (RFC 5746). By default,
  session renegotiation is no longer supported with old clients that do not
  implement this extension. This breaks certain configurations with client
  certificate authentication. If you still need to support old clients, you
  may restore the old (insecure) behaviour by adding the configuration option

      ssl.disable-client-renegotiation = "disable"

  to /etc/lighttpd/lighttpd.conf.

 -- Thijs Kinkhorst <thijs@debian.org>  Thu, 14 Feb 2013 19:42:19 +0100

~
(END)

Then I stop lighttpd and run apt-get upgrade again:
Code: Select all
root@debian:~# /etc/init.d/lighttpd stop
Stopping web server: lighttpd.
root@debian:~#apt-get upgrade

And I get the same lighttpd message.
The only way to upgrade is removing lighttpd, apt-get upgrade and installing lighttpd again.
Tested several times and I get the same result.

I read the same problem here:
http://www.unix.com/debian/236087-vulnerable-symlink-attack-notice-while-trying-upgrade-lighttpd.html

Cheers, Toni
User avatar
saintless
 
Posts: 246
Joined: Sat Jul 14, 2012 7:01 am
Location: Bulgaria

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby jbv » Sun Jan 25, 2015 2:04 am

Hi Toni,

As you know, I have worked hard from day-1 to keep the dpkg database up to date and correct. I'm not sure where/when things got messed up and/or out of sync.
My intent has been that nothing was to ever be hidden and that everything was known by dpkg.

The only compelling reason to keep FoxyRoxy split across the two (2) sqf files was/is support for Native NVIDIA drivers, and previously I was looking to allow for a setup that did not force you to have X11 loaded/installed.

The Intel Network drivers now work on the NUC, but the NUC won't shutdown or let you exit openbox - it hangs.
I think I will just do the merge, try to sort out the dpkg database and then review things.

Cheers, Brenton
jbv
 
Posts: 600
Joined: Sat Jul 14, 2012 2:02 am
Location: Sydney, Australia

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby jbv » Mon Jan 26, 2015 7:36 am

Hi Toni,

Brief update ...

It is currently Monday afternoon.
We had a public-holiday today, so I threw caution (and any free time I had to the wind) and I started down a tunnel on Friday night ... :lol:

Short-Story, medium ... I started messing around with merging 01-FoxyRoxy and 02-FoxyDesktop while also attempting to bring FoxyRoxy up to Debian 2.6.32-lts (long-term-support)

Things started out pretty well. I cleaned up a few things and everything was looking promising.
Somewhere along the way, something happened and things started getting ugly.
Needless to say, at about 2am this morning, when I couldn't see any light, I realized I wasn't in a tunnel - I was actually digging a hole :)

I learnt years ago, that when you're in a hole and you're the one digging the hole, it's usually best to stop digging :) so I went to bed.

I've decided to go back to 01-FoxyRoxy before I built the kernel.
I will get it running with Debian Squeeze 2.6.32-lts (which is 48squeeze10) - this is already working quite nicely.
I've done a full dist-upgrade and an upgrade to 01-FoxyRoxy and everything is fine.
Then I will pull the latest xorg stuff from squeeze-backports - this is currently downloading (my network speed is horrible this weekend)

Once I've got that sorted, I will create a new build environment (from squeeze-lts), then download the latest drivers I need (sound/network/possibly Intel Video)and rebuild them into the 48squeeze10(lts) package.

Then I will look to merge 02-FoxyDesktop and get that clean.
Once I've got that all sorted, I will check to see if need to recompile the kernel and if so, then I will make the "tweaked" kernel.

I want to get the base and at least an overlaid 02-FoxyDesktop sorted tonight if possible.

BTW, the message you got from lighttpd was not an error. It was a warning. As FoxyRoxy hadn't messed with the thing they were warning you about, you simply needed to press Esc or Q (I forget which one) to keep going and everything would have been fine :) Anyway, once I'm finished here, you won't need to do anything, as everything will be updated to either the latest from LTS, backports (if appropriate) or squeeze-update :)

Cheers, Brenton
jbv
 
Posts: 600
Joined: Sat Jul 14, 2012 2:02 am
Location: Sydney, Australia

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby saintless » Mon Jan 26, 2015 9:59 am

Hi, Brenton.

Just for information there is much newer kernel linux-image-3.2.0-0.bpo.4-686-pae in squeeze backports that runs fine on my older machines and has support for newer hardware (+ support for xz compressed squashfs modules on boot). I'm using the -486 version but -686-pae also works well for me.

Cheers, Toni
User avatar
saintless
 
Posts: 246
Joined: Sat Jul 14, 2012 7:01 am
Location: Bulgaria

Re: 2015 ... Where Has The Time Gone ... Beta-4

Postby jbv » Thu Jan 29, 2015 10:58 am

Hi Toni,

Thanks for the info, but I've become a little cautious of taking stuff from backports. I've been having a heck of a time with the xorg packages from backports.
I've decided to stay with the core squeeze-lts, squeeze-updates, and squeeze. I will try co compile the latest Intel video xf86 drivers once I'm 100% sure that 48squeeze10 (lts) is solid using the standard xorg base. It should be okay. If I run into anything, I will address/re-assess it then. I really don't want to create a Frankenstein and want to stay as close to the standard squeeze as possible.

I'm pretty sure I've got the base updated properly and fully to 48squeeze10 (lts).
I just want to do some more testing which I should have completed in the next few days.

Cheers, Brenton
jbv
 
Posts: 600
Joined: Sat Jul 14, 2012 2:02 am
Location: Sydney, Australia

PreviousNext

Return to Using FoxyRoxyLinux



Who is online

Users browsing this forum: No registered users and 1 guest

cron