Re: problem with nvidia on debian buster

[Alexander V. Makartsev]

On 08.11.2020 22:05, Vinko Tosevski wrote:

Hi Brad,

Thanks for the quick reply, this is my first experience with the 
debian-user mailing list and it makes for a positive one.


I ran nvidia-detect every now and then and it doesn't tell me exactly 
which version to install. Instead, it tells me that my card is "OK" 
(not legacy, GTX-1070 Ti) and that I should simply go and install 
nvidia-driver. I did that both times, once running from the standard 
debian repo, which installs version 418, and once also from 
debian-backports, which installs version 450 (both is OK per Debian 
wiki here ). Previously 
this worked fine, but now those processes fail me as well, so 
something is different this time, I just don't know what.


Nvidia GTX1060 owner here. Currently running 450.80 nvidia-driver 
version from buster-backports on kernel 4.19 from stable and XFCE as 
desktop environment.
I want to stay on stable branch for as long as I can, so I found that 
installation of nvidia-driver (with myriad of its additional relevant 
packages) from buster-backports is a bit tricky.
Personally, I had to setup apt preferences [1], so that only nvidia 
driver packages are installed from "buster-backports" and also their 
updated versions once they become available for installation.

Show us output of:
    apt-cache policy linux-image-amd64 linux-headers-amd64 dkms 
nvidia-driver nvidia-kernel-dkms nvidia-kernel-source



[1] man 5 apt_preferences

--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀https://www.debian.org
⠈⠳⣄

Re: problem with nvidia on debian buster

[Andrei POPESCU]

On Ma, 10 nov 20, 13:32:13, Alexander V. Makartsev wrote:
> I want to stay on stable branch for as long as I can, so I found that
> installation of nvidia-driver (with myriad of its additional relevant
> packages) from buster-backports is a bit tricky.
> Personally, I had to setup apt preferences [1], so that only nvidia driver
> packages are installed from "buster-backports" and also their updated
> versions once they become available for installation.

This should work fine in the default stable + backports configuration.

Care to provide more details?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Local shared storage configuration

[Andrei POPESCU]

On Ma, 03 nov 20, 17:34:48, Joe wrote:
> 
> Those of us who use NTFS do so deliberately to provide compatibility
> with Windows. It's not that long ago that Linux NTFS support was a bit
> flaky, so we don't do it solely by our own choice. 

One use case that is significantly easier with NTFS is setting up a 
shared local storage for several users on the same system.

With NTFS one can just use mount options to ensure all files/directories 
have the correct ownership and permissions[1].

With native file systems one has to mess around with umasks for each 
user and environment (console, X session and systemd --user, possibly 
also Wayland).

Or configure some daemon (cron job, systemd timer, inotify, etc.) to fix 
ownership and permissions in the background. Yuck!

I'd be interested to know if there are better ways to do this.

[1] uid, gid, fmask and dmask mount options

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: problem with nvidia on debian buster

[Alexander V. Makartsev]

On 10.11.2020 14:04, Andrei POPESCU wrote:

On Ma, 10 nov 20, 13:32:13, Alexander V. Makartsev wrote:

I want to stay on stable branch for as long as I can, so I found that
installation of nvidia-driver (with myriad of its additional relevant
packages) from buster-backports is a bit tricky.
Personally, I had to setup apt preferences [1], so that only nvidia driver
packages are installed from "buster-backports" and also their updated
versions once they become available for installation.

This should work fine in the default stable + backports configuration.

Care to provide more details?

Kind regards,
Andrei
At some point in the past I had to build backports to buster for nvidia 
drivers from unstable, because newer versions were not yet available in 
buster-backports.
The whole build and install procedure was a bit messy, because I need 
both AMD64 and i386 packages and updating nvidia drivers later from 
buster-backports using Synaptic wasn't straight forward either.
So now, after I setup apt preferences, I can see if updated nvidia 
drivers are available in buster-backports via Synaptic and I also can 
see and update nvidia-cuda-toolkit in same manner.



--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Terminal window shrinks into title bar.....

[Carl Fink]

On 11/10/20 1:58 AM, Charlie wrote:

Sometimes I press some key combination by accident and the terminal
window shrinks back into the title bar.

I must have the terminology wrong, because am unable to discover how to
reverse this behaviour. no matter what wordage is used to google.

If anyone has an idea, it would be appreciated.


When I annoy myself by doing that, it's by accidentally using the
mouse scroll wheel over the title bar. Scroll down over the title
bar to reverse.

It's called "roll window up" and "roll window down," by the way.
--
Carl Fink   nitpick...@nitpicking.com

Read my blog at blog.nitpicking.com.  Reviews!  Observations!

Re: Terminal window shrinks into title bar.....

[David]

On Tue, 10 Nov 2020 at 18:21, Charlie  wrote:

> FVWM window manager

On Tue, 10 Nov 2020 at 22:55, Carl Fink  wrote:
> On 11/10/20 1:58 AM, Charlie wrote:

> > Sometimes I press some key combination by accident and the terminal
> > window shrinks back into the title bar.

> > I must have the terminology wrong, because am unable to discover how to
> > reverse this behaviour. no matter what wordage is used to google.

> > If anyone has an idea, it would be appreciated.

> It's called "roll window up" and "roll window down," by the way.

I don't usually talk about things that I'm completely ignorant of
(I don't use fvwm) but here we go ...

I did a quick search for a fvwm manpage and found:
  https://manpages.debian.org/buster/fvwm/fvwm.1.en.html
"""
WindowShade [bool]
  Toggles the window shade feature for titled windows.
  Windows in the shaded state only display a title-bar.
"""
so I guess you need to unbind whatever changes that
state from your mouse button and key bindings.

Re: Terminal window shrinks into title bar.....

[Greg Wooledge]

On Tue, Nov 10, 2020 at 11:31:22PM +1100, David wrote:
> I did a quick search for a fvwm manpage and found:
>   https://manpages.debian.org/buster/fvwm/fvwm.1.en.html
> """
> WindowShade [bool]
>   Toggles the window shade feature for titled windows.
>   Windows in the shaded state only display a title-bar.
> """
> so I guess you need to unbind whatever changes that
> state from your mouse button and key bindings.

Very interesting.  A whole entire feature that I never knew about because
I'm using my legacy fvwm config file (which predates this feature and
doesn't make use of it), and because my mouse doesn't have a scroll
wheel in the first place.

Looking at what I believe to be the default Debian fvwm config file
(/usr/share/fvwm/default-config/config) I find this chunk:

#   TitleBar: Click to Raise, Move, Double Click to Maximize
# Mouse Wheel Up/Down to WindowShade On/Off
#   Borders: Click to raise, Move to Resize
#   Root Window: Left Click - Main Menu
#Right Click - WindowOps Menu
#Middle Click - Window List Menu
#   Right click TitleBar/Borders for WindowOps Menu
Mouse 1 TA RaiseMoveX Move Maximize
Mouse 1 FS   A RaiseMove Resize
Mouse 4 TA WindowShade True
Mouse 5 TA WindowShade False
Mouse 1 RA Menu MenuFvwmRoot
Mouse 2 RA WindowList
Mouse 3 RA Menu MenuWindowOpsLong
Mouse 1 IA RaiseMoveX Move "Iconify off"
Mouse 3 TA Menu MenuWindowOps
Mouse 3 IA Menu MenuIconOps

So, if you comment out the "Mouse 4" and "Mouse 5" lines there (and
restart fvwm), I bet that would disable the WindowShade binding to
the scroll wheel.  You could still activate or deactivate it through
the menus, assuming you leave those in place.

Re: Terminal window shrinks into title bar.....

[Greg Wooledge]

On Tue, Nov 10, 2020 at 07:46:37AM -0500, Greg Wooledge wrote:
> So, if you comment out the "Mouse 4" and "Mouse 5" lines there (and
> restart fvwm), I bet that would disable the WindowShade binding to
> the scroll wheel.  You could still activate or deactivate it through
> the menus, assuming you leave those in place.

In case it wasn't clear, when I say "comment out", what I really
mean is "copy this config file to ~/.fvwm/config if you haven't already,
and then edit ~/.fvwm/config".

Don't make changes to /usr/share/fvwm/*.

Re: Is there such a thing as a Debian blend for a MacBook Air 1,1 and/or Mac boxes in general? ...

[Albretch Mueller]

 OK, here is the whole log of the script I ran to install the b43 drivers.

 It is a bit long, but you will certainly be able to quickly visually
scan it and see where teh error is/might be.

 Yes, I am descending onto init 2 after I used a live DVD. I am OK
with doing that every time. I can't connect my work computer to the
Internet. I know it sounds "crazy"

 Thank you

// __ $_DIR: |/media/sda1/turk/fw/firmware-b43-installer|
/media/sda1/turk/fw/firmware-b43-installer/b43-fwcutter-018
make: Nothing to be done for 'all'.
0.00user 0.02system 0:00.18elapsed 11%CPU (0avgtext+0avgdata 2192maxresident)k
214inputs+0outputs (1major+128minor)pagefaults 0swaps
install -d -o 0 -g 0 -m 755 /usr/local/bin/
install -o 0 -g 0 -m 755 b43-fwcutter /usr/local/bin/
install -d -o 0 -g 0 -m 755 /usr/local/man/man1/
install -o 0 -g 0 -m 644 b43-fwcutter.1 /usr/local/man/man1/
0.00user 0.01system 0:00.16elapsed 9%CPU (0avgtext+0avgdata 2836maxresident)k
258inputs+0outputs (1major+828minor)pagefaults 0swaps
/media/sda1/turk/fw/firmware-b43-installer
// __ $FIRMWARE_INSTALL_DIR: |/lib/firmware|
// __ before installation: ls -l "/lib/firmware/b43"
ls: cannot access '/lib/firmware/b43': No such file or directory
This file is recognised as:
  filename   :  wl_apsta.o
  version:  666.2
  MD5:  e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
Extracting b43/n0bsinitvals25.fw
Extracting b43/n0bsinitvals17.fw
Extracting b43/ucode17_mimo.fw
Extracting b43/ucode16_lp.fw
Extracting b43/sslpn1initvals27.fw
Extracting b43/lp2bsinitvals19.fw
Extracting b43/sslpn3bsinitvals21.fw
Extracting b43/ucode16_sslpn.fw
  ucode time: 01:15:07
Extracting b43/ucode25_lcn.fw
Extracting b43/ucode21_sslpn.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/ucode20_sslpn.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/lp1initvals20.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp2initvals19.fw
Extracting b43/n2bsinitvals19.fw
Extracting b43/sslpn4bsinitvals22.fw
Extracting b43/ucode16_sslpn_nobt.fw
  ucode date: 2011-02-23
Extracting b43/n1bsinitvals20.fw
Extracting b43/n1initvals20.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/ucode22_sslpn.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/ht0initvals26.fw
Extracting b43/ucode33_lcn40.fw
Extracting b43/sslpn1bsinitvals20.fw
Extracting b43/lcn400bsinitvals33.fw
Extracting b43/ucode14.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/lp1bsinitvals22.fw
Extracting b43/n16initvals30.fw
Extracting b43/lp0bsinitvals16.fw
Extracting b43/lcn1bsinitvals25.fw
Extracting b43/lcn400initvals33.fw
Extracting b43/n0bsinitvals24.fw
Extracting b43/lcn2bsinitvals26.fw
Extracting b43/lcn1initvals26.fw
Extracting b43/n0bsinitvals22.fw
Extracting b43/n18initvals32.fw
Extracting b43/lcn2initvals26.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/lcn2initvals24.fw
Extracting b43/lcn0initvals26.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/ucode21_sslpn_nobt.fw
  ucode time: 01:15:07
Extracting b43/ucode26_mimo.fw
Extracting b43/n2initvals19.fw
Extracting b43/sslpn3initvals21.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/sslpn4initvals22.fw
Extracting b43/pcm5.fw
Extracting b43/ucode22_mimo.fw
Extracting b43/ucode9.fw
Extracting b43/lcn2initvals25.fw
Extracting b43/lp1initvals22.fw
Extracting b43/sslpn1bsinitvals27.fw
Extracting b43/lcn0initvals24.fw
Extracting b43/ucode32_mimo.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/n18bsinitvals32.fw
Extracting b43/n0initvals24.fw
Extracting b43/n0initvals25.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/ucode24_lcn.fw
Extracting b43/n0initvals17.fw
Extracting b43/n0bsinitvals16.fw
Extracting b43/lp0initvals15.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/ucode20_sslpn_nobt.fw
Extracting b43/lcn1initvals24.fw
Extracting b43/sslpn0initvals16.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/lp1bsinitvals20.fw
Extracting b43/sslpn2initvals19.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/lcn1bsinitvals24.fw
Extracting b43/ucode5.fw
Extracting b43/lcn2bsinitvals24.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/n0initvals16.fw
Extracting b43/ucode19_sslpn_nobt.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/ucode11.fw
Extracting b43/lp0initvals16.fw
Extracting b43/ucode16_mimo.fw
Extracting b43/lcn0bsinitvals26.fw
Extracting b43/ht0initvals29.fw
Extracting b43/lcn2bsinitvals25.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/ucode29_mimo.fw
Extracting b43/lcn0bsinitvals24.fw
Extracting b43/ucode19_sslpn.fw
Extracting b43/lcn1initvals25.fw
Extracting b43/ucode30_mimo.fw
Extracting b43/n16bsinitvals30.fw
Extracting b43/ucode25_mimo.fw
Extracting b43/ucode24_mimo.fw
Extracting b43/ucode27_sslpn.fw
Extracting b43/lp0initvals13.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/ht0bsinitvals26.fw
Extracting b43/ucode13.fw
Extracting b43/sslpn2bsinitvals19.fw
Extracting b43/ucode15.fw
Extracting b43/

Re: problem with nvidia on debian buster

[Andrei POPESCU]

On Ma, 10 nov 20, 15:02:42, Alexander V. Makartsev wrote:
> On 10.11.2020 14:04, Andrei POPESCU wrote:
> > On Ma, 10 nov 20, 13:32:13, Alexander V. Makartsev wrote:
> > > I want to stay on stable branch for as long as I can, so I found that
> > > installation of nvidia-driver (with myriad of its additional relevant
> > > packages) from buster-backports is a bit tricky.
> > > Personally, I had to setup apt preferences [1], so that only nvidia driver
> > > packages are installed from "buster-backports" and also their updated
> > > versions once they become available for installation.
> > This should work fine in the default stable + backports configuration.
> > 
> > Care to provide more details?
> > 
> At some point in the past I had to build backports to buster for 
> nvidia
> drivers from unstable, because newer versions were not yet available in
> buster-backports.
> The whole build and install procedure was a bit messy, because I need both
> AMD64 and i386 packages and updating nvidia drivers later from
> buster-backports using Synaptic wasn't straight forward either.
> So now, after I setup apt preferences, I can see if updated nvidia drivers
> are available in buster-backports via Synaptic and I also can see and update
> nvidia-cuda-toolkit in same manner.

In the default configuration backports is automatically assigned a 
priority of 100, which is the same as already installed packages.

This enables you to install packages and their dependencies from 
backports with 'apt install -t buster-backports ' and such 
packages will also be automatically upgraded should a new version become 
available in backports.

This should work with synaptic as well (though you must find out what is 
the equivalent of '-t buster-backports').

So it's still unclear for me why pinning backports was ever necessary.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: problem with nvidia on debian buster

[Alexander V. Makartsev]

On 10.11.2020 18:18, Andrei POPESCU wrote:

On Ma, 10 nov 20, 15:02:42, Alexander V. Makartsev wrote:

On 10.11.2020 14:04, Andrei POPESCU wrote:

On Ma, 10 nov 20, 13:32:13, Alexander V. Makartsev wrote:

I want to stay on stable branch for as long as I can, so I found that
installation of nvidia-driver (with myriad of its additional relevant
packages) from buster-backports is a bit tricky.
Personally, I had to setup apt preferences [1], so that only nvidia driver
packages are installed from "buster-backports" and also their updated
versions once they become available for installation.

This should work fine in the default stable + backports configuration.

Care to provide more details?


At some point in the past I had to build backports to buster for
nvidia
drivers from unstable, because newer versions were not yet available in
buster-backports.
The whole build and install procedure was a bit messy, because I need both
AMD64 and i386 packages and updating nvidia drivers later from
buster-backports using Synaptic wasn't straight forward either.
So now, after I setup apt preferences, I can see if updated nvidia drivers
are available in buster-backports via Synaptic and I also can see and update
nvidia-cuda-toolkit in same manner.

In the default configuration backports is automatically assigned a
priority of 100, which is the same as already installed packages.

This enables you to install packages and their dependencies from
backports with 'apt install -t buster-backports ' and such
packages will also be automatically upgraded should a new version become
available in backports.

This should work with synaptic as well (though you must find out what is
the equivalent of '-t buster-backports').

So it's still unclear for me why pinning backports was ever necessary.

Kind regards,
Andrei
This is probably the case, because afaik there is no straight forward 
way to make Synaptic to upgrade already installed packages from "buster" 
to "buster-backports", some of them will appear as broken and complain 
about some dependencies being unavailable for installation, because they 
were not yet marked to be installed from backports.
Also as I mentioned before, I need foreign architecture packages (i386) 
too, and those are not dependencies of "nvidia-driver" meta package and 
have to be manually installed.
I wish I could provide exact messages and refrain from vaguely 
describing the problem from my poor memory, but it's all updated now and 
works.
I'll probably test in near future if removing my apt preferences file 
won't make any difference now, because all necessary packages already 
installed from backports.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Junta de Conciliacion y Arbitraje Cierra sus Puertas

[Miguel Angel Ruiz Gutierrez]

A partir de este mes en algunos estados de la república nace el Centro Federal 
de Conciliación y Registro Laboral (CFCRL)...

Especialista en
RELACIONES LABORALES:
Contratos, Sindicatos y el Nuevo Sistema de Justicia Laboral en México

Entrenamiento Online en Vivo
Fecha de inicio: 27 de Noviembre 2020

CONOCE LOS PRINCIPIOS FUNDAMENTALES DE LAS RELACIONES INDIVIDUALES Y CONTRATOS 
COLECTIVOS DE TRABAJO, CÓMO HACER NEGOCIACIONES SINDICALES EXITOSAS Y TODO LO 
QUE DEBEMOS SABER DEL NUEVO SISTEMA DE JUSTICIA LABORAL QUE ENTRÓ EN VIGOR EN 
MÉXICO A PARTIR DE ESTE MES DE NOVIEMBRE.
 
DESCARGAR INFORMACIÓN COMPLETA
 Mayor información a través de WhatsApp
O para información mucho más detallada comuníquese al:


Ciudad de México / 55 2450 6187
Monterrey, N.L. / 81 2974 7731
Guadalajara, Jal. / 33 2005 0994




Este boletín informativo tiene como objetivo generar valor en usted y su 
Organización. Para darse de baja de este tipo de información conteste con la 
palabra BAJALABORAL737.
O en su defecto haga click en el siguiente enlace: unsubscribe from this list

Re: xfce widget problem

[Ben Caradoc-Davies]

On 11/11/2020 11:26, ghe2001 wrote:

How can I remove a widget that doesn't have a right-button xfce menu (the one 
with 'Remove' in it)?
There's lots of info on the web about sticking one in the panel, but I can't 
find anything about removing one.


Right-click / Panel / Panel Preferences / Items to see what you have in 
that panel. If it has no Remove option, it likely is a child of 
Notification Area that has been added by a process. I do not recommend 
removing Notification Area. Most applications that do this have an 
option to disable showing an icon in the "System Tray" (Xfce 
Notification Area is an implementation of this concept). As a last 
resort, you can exit the application or stop it starting in Sessions / 
Settings and Startup.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Building my own packages

[Victor Sudakov]

Linux-Fan wrote:

[dd]

> 
> Here is the documentation of all components:
> 
> * https://masysma.lima-city.de/32/masysmaci_main.xhtml
> * https://masysma.lima-city.de/32/masysmaci_build.xhtml
> * https://masysma.lima-city.de/32/masysmaci_pkgsync.xhtml
> * https://masysma.lima-city.de/11/maartifact.xhtml

Thank you, Linux-Fan, I've read the documentation and your CI/CD system
seems impressive ... and a bit overwhelming. I don't think I need such a
degree of automation. But speaking of its educational value, thanks
again.

It's strange that there is nothing (or I have not found yet) as
intuitive and working mostly OOTB like FreeBSD's poudriere.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature

Re: Building my own packages

[Victor Sudakov]

deloptes wrote:
> 
> > The problem is I don't need a ton of information :-) I need to hear from
> > someone who has already done that for themselves: "I use such and such
> > tools, and publish my repo this way..."
> 
> Well, I use debuild to build and reprepro to maintain a local repository of
> former KDE3 now called TDE.

I've already tried reprepro and it seems to do its job well in publishing
the packages I feed to it. Now it's building time.

> I do not build automatically but from time to time I pull changes and build
> the packages. Because there are dependencies it depends which package
> changes this affects other packages. For that reason I created a Makefile
> (actually few of them that complement each other).
> You have to rebuild all dependencies if you rebuild one package. You simply
> can not just build and replace a package in production environment without
> testing it, making a backup or whatever.

There lies the point which I don't completely understand yet. If I want
to build a php or exim4 package with my own build options, to what
extent should I also build their dependencies? And how do I name those
packages so that they coexist with the default Debian ones?

OTOH, sometimes I would want my package (e.g. tcpdump with my patch) to
override Debian's one.

> I guess the answer to your question is that there is no such out of the box
> tool, but you need something specific to your setup.

Pity. I wonder what those people and companies use who publish their own
repos/products for Debian (Hashicorp, PostgreSQL, Zabbix etc).

> Also consider the number of debian packages - You surely need a small
> subset - again you have to configure this for yourself.
> I guess all here would agree that with the release model of Debian you have
> a lot of freedom (stable-testing-experimental) to save time on rebuilding
> packages, otherwise it is called Gentoo.

Can I use some of the Gentoo ecosystem on Debian, for a few selected
packages? Or maybe snap is for me?

> On top of that don't forget that debian packages include patches and fixes
> specific to debian.

I hoped to download Debian's source packages (already including all
Debian-specific stuff) and just rebuild them with minimal
changes/patches.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature

Re: Local shared storage configuration

[Didar Hossain]

On Tue, Nov 10, 2020 at 11:59:52AM +0200, Andrei POPESCU wrote:
> On Ma, 03 nov 20, 17:34:48, Joe wrote:
> > 
> > Those of us who use NTFS do so deliberately to provide compatibility
> > with Windows. It's not that long ago that Linux NTFS support was a bit
> > flaky, so we don't do it solely by our own choice. 
> 
> One use case that is significantly easier with NTFS is setting up a 
> shared local storage for several users on the same system.
> 
> With NTFS one can just use mount options to ensure all files/directories 
> have the correct ownership and permissions[1].

I have kind of similar requirements with respect to shared folder under Samba.

> With native file systems one has to mess around with umasks for each 
> user and environment (console, X session and systemd --user, possibly 
> also Wayland).
> 
> Or configure some daemon (cron job, systemd timer, inotify, etc.) to fix 
> ownership and permissions in the background. Yuck!
> 
> I'd be interested to know if there are better ways to do this.

How about Linux ACL? Will that help? 

I plan to explore ACL for my requirements.

> [1] uid, gid, fmask and dmask mount options
> 
> Kind regards,
> Andrei
> -- 
> http://wiki.debian.org/FAQsFromDebianUser

Cheers,
Didar


-- 
Committees have become so important nowadays that subcommittees have to
be appointed to do the work.

Re: Building my own packages

[deloptes]

Victor Sudakov wrote:

>> Well, I use debuild to build and reprepro to maintain a local repository
>> of former KDE3 now called TDE.
> 
> I've already tried reprepro and it seems to do its job well in publishing
> the packages I feed to it. Now it's building time.
> 
>> I do not build automatically but from time to time I pull changes and
>> build the packages. Because there are dependencies it depends which
>> package changes this affects other packages. For that reason I created a
>> Makefile (actually few of them that complement each other).
>> You have to rebuild all dependencies if you rebuild one package. You
>> simply can not just build and replace a package in production environment
>> without testing it, making a backup or whatever.
> 
> There lies the point which I don't completely understand yet. If I want
> to build a php or exim4 package with my own build options, to what
> extent should I also build their dependencies? And how do I name those
> packages so that they coexist with the default Debian ones?
> 
You just put here questions that one can not answer. Answer of these
questions will help you define your use case and this will help you define
the steps to complete the requirements.
In general you should build so that there is compatibility and no a
coexistence but replace the original package (read the debian packaging
doc)
If you want coexistence of packages you should change for example the
install prefix. Now for exim you can not have two exim processes running
the same time on same port. You should also consider modifying ports etc.

> OTOH, sometimes I would want my package (e.g. tcpdump with my patch) to
> override Debian's one.
> 

yes - it depends on the use case

>> I guess the answer to your question is that there is no such out of the
>> box tool, but you need something specific to your setup.
> 
> Pity. I wonder what those people and companies use who publish their own
> repos/products for Debian (Hashicorp, PostgreSQL, Zabbix etc).
> 

It is not the tools, but the final product that matters. At the end you get
a package to install. The packagers take care of the details. There are
many ways to reach the goal.

>> Also consider the number of debian packages - You surely need a small
>> subset - again you have to configure this for yourself.
>> I guess all here would agree that with the release model of Debian you
>> have a lot of freedom (stable-testing-experimental) to save time on
>> rebuilding packages, otherwise it is called Gentoo.
> 
> Can I use some of the Gentoo ecosystem on Debian, for a few selected
> packages? Or maybe snap is for me?
> 

I do not think so. I don't know snap. I learn  recently flatpack appeared,
but never tried it.

>> On top of that don't forget that debian packages include patches and
>> fixes specific to debian.
> 
> I hoped to download Debian's source packages (already including all
> Debian-specific stuff) and just rebuild them with minimal
> changes/patches.

Then I would advice to start with https://wiki.debian.org/Packaging

but remember it depends which package you change. If it is library all the
packages depending on this library might need recompiling which is not
exactly easy task.

I hope you do it in a test environment like virtual machine first. I build
in chroot, publish the packages with reprepro and install to test first in
a VM. If it works well I have tftp boot setup where I install the packages
in chroot on the server, I boot the machine from tftp and test. If this
works I boot from disk and install the packages for production use.
This is industry quality process for testing and acceptance.