Re: [DNG] Devuan Rpi2 Lxde

[Daniel Reurich]

On 07/03/16 21:19, Arnt Karlsen wrote:
> On Mon, 7 Mar 2016 07:39:13 +, KatolaZ wrote in message 
> <20160307073913.gn13...@katolaz.homeunix.net>:
> 
>> On Sun, Mar 06, 2016 at 10:53:51AM -0600, Nate Bargmann wrote:
>>> * On 2016 06 Mar 02:51 -0600, aitor_czr wrote:
 Hi all,

 I just uploaded an image of Devuan for Raspberry Pi 2 with LXDE.
>>>
>>> My guess is this will not run on the original Pi model B?
>>>
>>> - Nate
>>>
>>
>> It probably won't, since rpi2 is armhf, while rpi1 and rpi0 are midway
>> between armel and armhf. I have been running a few test with a custom
>> toolchain to make a bootable image for rpi0/1. The base system works
>> (single-user with bash and busybox, now I might play a bit around to
>> have coreutils instead), even if there are a few tweaks to
>> implement. 
>>
>> The problem is that this would be an almost completely independent
>> port, for which we might not have enough energy though. It would be
>> good to have a pivuan for armv6 + FP2 for rpi0, but it is true that
>> with the new rpi3 it would be far better and easier to invest time in
>> a pivuan for armhf, which is what aitor is rightfully doing. The
>> packages are already there, and there is no need to support another
>> port...
> 
> ..this means Devuan is _not_ the answer for the millions of 
> armv6+FP2/rpi0/1 users out there.  
> Pity, we could have used them here.
> 

For jessie you're probably right, but I am keen once Jessie is out to
look at building the entire debian archive, and that would make it
possible to have a native arm6+FP2 (arm6hf??) build of devuan as a side
effect.


-- 
Daniel Reurich
Centurion Computer Technology (2005) Ltd.
021 797 722



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan Rpi2 Lxde

[Dr. Nikolaus Klepp]

Am Samstag, 12. März 2016 schrieb KatolaZ:
> On Mon, Mar 07, 2016 at 09:19:14AM +0100, Arnt Karlsen wrote:
> 
> [cut]
> 
> > > good to have a pivuan for armv6 + FP2 for rpi0, but it is true that
> > > with the new rpi3 it would be far better and easier to invest time in
> > > a pivuan for armhf, which is what aitor is rightfully doing. The
> > > packages are already there, and there is no need to support another
> > > port...
> > 
> > ..this means Devuan is _not_ the answer for the millions of 
> > armv6+FP2/rpi0/1 users out there.  
> > Pity, we could have used them here.
> > 
> 
> 
> I haven't said I gave up on the rpi0/1 port of Devuan. I have said
> that it would be difficult to maintain it, if we ever get to put it in
> place. 

I might miss the whole point of this discussion, but I have a RPi 1 A + fvwm + 
devuan running without any problem. But it started with the "official" wheezy 
raspbian image ...

Nik



-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Testing vdev with Busybox

[Didier Kryn]

Le 12/03/2016 14:30, aitor_czr a écrit :

Hi all,

On 02/20/2016 06:03 PM, Didier Kryn wrote:

Le 19/02/2016 17:27, aitor_czr a écrit :

Hi Didier,

El 19/02/16 16:00, Didier Kryn escribió:


Everything but fs compiles and links both dynamically or 
statically and both with glibc or musl. This is very satisfactory.


With  'make -C fs' , I have a compilation error:

/home/kryn/Applications/vdev-plus/include/fskit/common.h:63:20: 
fatal error: iostream: No such file or directory


however such a file exists in the include tree of gcc.

I'm not used to include files without a .h extension. Is it a 
C++ feature? 


Did you try including  instead of  in the 
headers?


Cheers,

  Aitor.


"fskit/common.h" *is* the file which is included, and it is 
found. But this file itself includes . I found iostream 
somewhere in C++ system headers; therefore I would expect the C++ 
compiler to find it automatically. I suspect some trick is necessary 
to help the C compiler find it also. But, as I wrote, I've no 
experience in C++ and mixing C and C++. I tried to include  
with its whole path, but it just displaces the problem.


I'm compiling against a version of fskit I built in may 2015 and 
it might be obsolete. I might try to download the latest version.


Anyway vdev proper doesn't depend on this special filesystem, so 
that this is a minor problem and isn't at all a blocker for vdev 
deployment. For me the primary problem is the failure to create disk 
devices. There might be other problems but the log is very verbose 
and I better wait until Jude is available to analyse it.


The compilation is going well and I'm convinced that the problems 
are caused by details. It might be that they are related to the way 
I've configured or invoked vdevd, or the way I've laid out the files. 
Therefore, if you are willing to debianize the package, I think you 
could start now.


Vdev in the initramfs is absolutely not critical. Busybox comes 
with its own mdev hotplugger, which doesn't depend on dbus or 
systemd, and there is no need for the hotplugger to be the same in 
the initramfs and the final system. Actually I think it would make 
sense to use mdev inside the initramfs, this way initramfs would be 
independant of the choice of hotplugger for the final system -- to be 
discussed. My efforts with Busybox are rather meant for tiny OSes 
based on Busybox and musl.


Cheers.
Didier 


I will focus on vdev.

Where is the latest git repository?

  Aitor.


Following Jude's instruction:

 https://git.devuan.org/pkgs-utopia-substitution/vdev/blob/master/how-to-test.md
Also available at 
https://github.com/jcnelson/vdev/blob/master/how-to-test.md


Ready to help - with my limited skills :-)

Didier

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] X forwarding over SSH over ADSL

[Rainer Weikusat]

Brad Campbell  writes:
> On 08/03/16 04:41, Simon Hobson wrote:
>>
>> VNC is lousy over anything but a very fast link, it's just a remote
>> framebuffer - anything painted to the screen is bit copied to the
>> client which is bandwidth intensive.
>
> Whereas tightvnc works quite well over almost anything, and if you are
> willing to drop to a small colour pallete

Considering that tightvnc is Windows-only software it seems a bit out of
place here. I also seriously doubt this claim (but can't verify that)
because it uses the exact same protocol as VNC. I have some experience
with similar technology outside of the domain of "Windows freeware",
namely, SunRay thin clients. Sun used to recommend a dedicated, 100MBit
LAN for these, with 'using a VLAN of a non-dedicated LAN' as 'you can do
that if you really want to but be prepared to suffer' option.

Regardless of that, the "remote desktop access" model is also very
limiting/ annoying when compared with possibilty to enable applications
running on different computers to use a single display.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan Rpi2 Lxde

[Arnt Karlsen]

On Mon, 7 Mar 2016 07:39:13 +, KatolaZ wrote in message 
<20160307073913.gn13...@katolaz.homeunix.net>:

> On Sun, Mar 06, 2016 at 10:53:51AM -0600, Nate Bargmann wrote:
> > * On 2016 06 Mar 02:51 -0600, aitor_czr wrote:
> > > Hi all,
> > > 
> > > I just uploaded an image of Devuan for Raspberry Pi 2 with LXDE.
> > 
> > My guess is this will not run on the original Pi model B?
> > 
> > - Nate
> > 
> 
> It probably won't, since rpi2 is armhf, while rpi1 and rpi0 are midway
> between armel and armhf. I have been running a few test with a custom
> toolchain to make a bootable image for rpi0/1. The base system works
> (single-user with bash and busybox, now I might play a bit around to
> have coreutils instead), even if there are a few tweaks to
> implement. 
> 
> The problem is that this would be an almost completely independent
> port, for which we might not have enough energy though. It would be
> good to have a pivuan for armv6 + FP2 for rpi0, but it is true that
> with the new rpi3 it would be far better and easier to invest time in
> a pivuan for armhf, which is what aitor is rightfully doing. The
> packages are already there, and there is no need to support another
> port...

..this means Devuan is _not_ the answer for the millions of 
armv6+FP2/rpi0/1 users out there.  
Pity, we could have used them here.

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Testing vdev with Busybox

[aitor_czr]

Hi all,

On 02/20/2016 06:03 PM, Didier Kryn wrote:

Le 19/02/2016 17:27, aitor_czr a écrit :

Hi Didier,

El 19/02/16 16:00, Didier Kryn escribió:


Everything but fs compiles and links both dynamically or 
statically and both with glibc or musl. This is very satisfactory.


With  'make -C fs' , I have a compilation error:

/home/kryn/Applications/vdev-plus/include/fskit/common.h:63:20: 
fatal error: iostream: No such file or directory


however such a file exists in the include tree of gcc.

I'm not used to include files without a .h extension. Is it a 
C++ feature? 


Did you try including  instead of  in the 
headers?


Cheers,

  Aitor.


"fskit/common.h" *is* the file which is included, and it is found. 
But this file itself includes . I found iostream somewhere 
in C++ system headers; therefore I would expect the C++ compiler to 
find it automatically. I suspect some trick is necessary to help the C 
compiler find it also. But, as I wrote, I've no experience in C++ and 
mixing C and C++. I tried to include  with its whole path, 
but it just displaces the problem.


I'm compiling against a version of fskit I built in may 2015 and 
it might be obsolete. I might try to download the latest version.


Anyway vdev proper doesn't depend on this special filesystem, so 
that this is a minor problem and isn't at all a blocker for vdev 
deployment. For me the primary problem is the failure to create disk 
devices. There might be other problems but the log is very verbose and 
I better wait until Jude is available to analyse it.


The compilation is going well and I'm convinced that the problems 
are caused by details. It might be that they are related to the way 
I've configured or invoked vdevd, or the way I've laid out the files. 
Therefore, if you are willing to debianize the package, I think you 
could start now.


Vdev in the initramfs is absolutely not critical. Busybox comes 
with its own mdev hotplugger, which doesn't depend on dbus or systemd, 
and there is no need for the hotplugger to be the same in the 
initramfs and the final system. Actually I think it would make sense 
to use mdev inside the initramfs, this way initramfs would be 
independant of the choice of hotplugger for the final system -- to be 
discussed. My efforts with Busybox are rather meant for tiny OSes 
based on Busybox and musl.


Cheers.
Didier 


I will focus on vdev.

Where is the latest git repository?

  Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] The repository has old OpenSCAD package.

[aitor_czr]

On 03/12/2016 01:00 PM, Hughe Chung wrote:

>Hi,
>
>The latest stable version of OpenSCAD is 2015.03-3.
>When I installed openscad, it was old version.
>openscad:amd64/jessie 2014.03+dfsg-1 uptodate
>
>Regards,
>Hughe
>
>PS: Are there any 3D Printer users?


I have experience programing CNC machines (numerical control computers). 
So, i'm interested in this field


  Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Dng Digest, Vol 18, Issue 31

[aitor_czr]

On 03/12/2016 01:00 PM, dng-requ...@lists.dyne.org wrote:

Hi,
>
>The latest stable version of OpenSCAD is 2015.03-3.
>When I installed openscad, it was old version.
>openscad:amd64/jessie 2014.03+dfsg-1 uptodate
>
>Regards,
>Hughe
>
>PS: Are there any 3D Printer users?


I have experience programing CNC machines (numerical control computers). 
So, i'm interested in this field :)


  Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] The repository has old OpenSCAD package.

[info at smallinnovations.nl]

On 11-03-16 22:03, dng-requ...@lists.dyne.org wrote:

Date: Sat, 12 Mar 2016 02:11:45 +0900
From: Hughe Chung
To:dng@lists.dyne.org
Subject: [DNG] The repository has old OpenSCAD package.
Message-ID:<5989ed20949751ca1015ad0763815...@riseup.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed

Hi,

The latest stable version of OpenSCAD is 2015.03-3.
When I installed openscad, it was old version.
openscad:amd64/jessie 2014.03+dfsg-1 uptodate

Regards,
Hughe

PS: Are there any 3D Printer users?
I am using a 3D printer (from family) but do not own one. My part in it 
was to implement a Pi 2 as printerserver with Repetier Server on Raspbian.
This works quite well with webinterface and the Repetier host software. 
The biggest advantage is after sending the printfile you can shutdown 
your PC.

Next goal is to replace Raspbian with Devuan.

Nick
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng