Re: Sound problems (mpd, mpv mainly)
On Sun, Apr 2, 2017 at 1:14 PM, Dan Hitt wrote: > /etc/debian_version says '9.0' for me, and i think it is called > 'stretch' (it is not in the list of debian versions in the wikipedia, > which stops at 8, 'jessie'). FWIW, you can get this information even without going to wikipedia. % sudo apt-get install distro-info-data % cat /usr/share/distro-info/debian.csv version,codename,series,created,release,eol 1.1,Buzz,buzz,1993-08-16,1996-06-17,1997-06-05 1.2,Rex,rex,1996-06-17,1996-12-12,1998-06-05 1.3,Bo,bo,1996-12-12,1997-06-05,1999-03-09 2.0,Hamm,hamm,1997-06-05,1998-07-24,2000-03-09 2.1,Slink,slink,1998-07-24,1999-03-09,2000-10-30 2.2,Potato,potato,1999-03-09,2000-08-15,2003-07-30 3.0,Woody,woody,2000-08-15,2002-07-19,2006-06-30 3.1,Sarge,sarge,2002-07-19,2005-06-06,2008-03-30 4.0,Etch,etch,2005-06-06,2007-04-08,2010-02-15 5.0,Lenny,lenny,2007-04-08,2009-02-14,2012-02-06 6.0,Squeeze,squeeze,2009-02-14,2011-02-06,2014-05-31 7,Wheezy,wheezy,2011-02-06,2013-05-04 8,Jessie,jessie,2013-05-04,2015-04-25 9,Stretch,stretch,2015-04-25 10,Buster,buster,2018-07-01 11,Bullseye,bullseye,2020-11-05 ,Sid,sid,1993-08-16 ,Experimental,experimental,1993-08-16 -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: If Linux Is About Choice, Why Then ...
On 04/07/2017 08:19 PM, Patrick Bartek wrote: [snip] Why no one looks at their project and sees the people involved when making a statistic up for the amount of dissatisfied systemd users I don't know. That's an argument for another day. Back when the systemd FLAME WAR was prominent, I followed a link to a justification link written by someone on the systemd development team. My take-away was that systemd was aimed at *AND* had advantages for multi-user system. I never saw anything addressing potential advantages for a specific organic user owning a discrete laptop. Systemd *MAY* have technical advantages. I am *NOT* qualified to say. HOWEVER, in one sense, it is a marketing disaster. 'They' never told us, owners of single user laptops, why we should chose it. YMMV ;/ OWL once more "ducks fer cover" ;/
Re: If Linux Is About Choice, Why Then ...
On Fri, 7 Apr 2017 14:27:40 -0400 David Niklas wrote: > On Mon, 13 Mar 2017 12:30:11 -0700 > Patrick Bartek wrote: > > The Linux mantra has always been "choice," plethoras of choices. So > > why at install time, is there no choice for the init system? You > > get what the developers decide. Yes, you can install a new one -- > > I've done it and it works -- but only after the install. It'd be a > > lot easier, if there were a choice to begin with just like whether > > you want a GUI and which one. > > > > Now, I know with LFS, you get to choose everything, etc. But is a > > choice of init at install time so outrageous that no one ever > > considered it or is it technically unfeasible or something else. > > > > Just curious. > > > > Because this reply is so late I'm CC'ing you off list. > > I sympathize, I run Gentoo Linux and us OpenRC. I plan on running > Devuan, a Debain derivative that supports lots of different init I considered Devuan initially, but it's based off Jessie; is still in Beta, and in a few months Jessie will be oldstable. Not the criteria I'm looking for to replace my aging Wheezy system or install on a new notebook I plan to get soon. I've looked at other systemd-less Debian-based distros like AntiX and mx16, but extraordinary measures must be taken to keep them free of systemd components like using third party repos. And I fear that will ultimately affect whether they are truly Stable in the Debian sense. I have no interest in rolling releases. Been there; done that. Currently, I'm looking into a hybrid-Stretch with the init and supervisor system I want -- easy enough to do -- disemboweling systemd and relegating it to an innocous eunuch to satisfy dependencies. That way I don't need any special repos and update/upgrade will work as it should. Shows promise right now. More reading needed. I have Plans B and C just in case. > systems. Why no one looks at their project and sees the people > involved when making a statistic up for the amount of dissatisfied > systemd users I don't know. That's an argument for another day. Thanks for your response. B
Re: If Linux Is About Choice, Why Then ...
On Fri, 7 Apr 2017 14:27:40 -0400 David Niklas wrote: > On Mon, 13 Mar 2017 12:30:11 -0700 > Patrick Bartek wrote: > > The Linux mantra has always been "choice," plethoras of choices. So > > why at install time, is there no choice for the init system? You get > > what the developers decide. Yes, you can install a new one -- I've > > done it and it works -- but only after the install. It'd be a lot > > easier, if there were a choice to begin with just like whether you > > want a GUI and which one. > > > > Now, I know with LFS, you get to choose everything, etc. But is a > > choice of init at install time so outrageous that no one ever > > considered it or is it technically unfeasible or something else. > > > > Just curious. > > > > Because this reply is so late I'm CC'ing you off list. > > I sympathize, I run Gentoo Linux and us OpenRC. I plan on running > Devuan, a Debain derivative that supports lots of different init > systems. Why no one looks at their project and sees the people involved > when making a statistic up for the amount of dissatisfied systemd users > I don't know. > > Sincerely, > David Oops, The topic may be old but it does appear to be alive and well. Also I sent to the list instead of CC'ing. Sincerely, David
Re: How to change where PXE booting looks for files with UEFI
On Fri, Apr 7, 2017 at 12:31 PM, David Niklas wrote: > As someone who is curious about PXE, did you ever figure this out? > > Unfortunately I was not able to spend too much time on this and have not yet figured out how to set UEFI PXE booting options like where to look for files. If I figure this out I will post a reply to the list. Thanks, Joshua
How to change where PXE booting looks for files with UEFI
On Wed, 15 Mar 2017 13:53:08 -0600 Joshua Schaeffer wrote: > Ahoy, > > I've been learning how to setup PXE booting to install an OS image on a > 100% UEFI system (CSM completely disabled). I use Debian 8 as my DHCP > server (ISC DHCP) and as my TFTP server (tftpd-hpa). I also use the > Debian netboot installer to provide the PXE environment including the > bootnetx64.efi file (I use it to serve pxelinux.0 as well). > > I'm able to get to menu screens with PXE on UEFI and BIOS, but I have to > have specific files in certain directories for UEFI and I don't know > how to change the defaults. With BIOS I'm able to control the > directories and files that are served by changing the > pxelinux.cfg/default file. For BIOS I put my debian-installer directory > (which contains the boot screen, menus, etc) under gtk. So I just have > lines like this in my pxelinux.cfg/default file: > > path gtk/debian-installer/amd64/boot-screens/ > default gtk/debian-installer/amd64/boot-screens/vesamenu.c32 > > However, I can't figure out how to tell UEFI to look in specific > directories. Instead I've been left with just having to create a symlink > from the default directory that bootnetx64.efi looks in to point to the > actual directory that my GRUB files exist. > > How do you configure UEFI PXE booting to use different directories then > the defaults? > > Let me try to explain what I'm seeing a little better: > > This is my TFTP server. The base directory is /srv/tftp: > > root@broodwar:/srv/tftp/pxeboot# ls -l > total 48208 > -rw-r--r-- 1 tftp tftp 435712 Mar 15 10:38 bootnetx64.efi > drwxr-xr-x 1 tftp tftp4 Sep 28 11:10 centos > drwxr-xr-x 1 tftp tftp4 Sep 28 11:10 debian > drwxr-xr-x 1 tftp tftp8 Sep 28 11:16 fedora > drwxr-xr-x 1 tftp tftp 120 Sep 17 10:04 gtk > -rw-r--r-- 1 tftp tftp 116624 Sep 28 09:30 ldlinux.c32 > -rw-r--r-- 1 tftp tftp25372 Sep 30 10:40 memdisk > -rw-r--r-- 1 tftp tftp 29360128 Sep 13 2016 mini.iso > -rw-r--r-- 1 tftp tftp 19370928 Sep 13 2016 netboot.tar.gz > drwxr-xr-x 1 tftp tftp 16 Sep 28 11:17 opensuse > -rw-r--r-- 1 tftp tftp42988 Sep 13 2016 pxelinux.0 > drwxr-xr-x 1 tftp tftp 248 Sep 30 10:31 pxelinux.cfg > drwxr-xr-x 1 tftp tftp 20 Sep 28 11:17 ubuntu > drwxr-xr-x 1 tftp tftp 32 Sep 30 09:40 windows > drwxr-xr-x 1 tftp tftp 52 Sep 17 10:04 xen > > You can see that under the base directory I have a pxeboot directory > which can serve both pxelinux.0 and bootnetx64.efi. I also have a gtk > folder which is where the debian-installer folder resides under (this > has items like my boot screens and menus as well as GRUB related files > for UEFI). So, when booting via BIOS I tell my pxelinux.cfg file to > look under the gtk folder as shown above. bootnetx64.efi however is > looking for the following files: > > >- debian-installer/amd64/grub/x86_64-efi/command.lst >- debian-installer/amd64/grub/x86_64-efi/fs.lst >- debian-installer/amd64/grub/x86_64-efi/crypto.lst >- debian-installer/amd64/grub/x86_64-efi/terminal.lst >- debian-installer/amd64/grub/grub.cfg > > I know this because this is what is reported in the tftp log files. I > have to have a symlink called debian-installer in my root directory > (/srv/tftp/debian-installer) pointing to my gtk folder > (srv/tftp/pxeboot/gtk/debian-installer). > > root@broodwar:/srv/tftp/pxeboot# ls -l .. > total 4 > drwxr-xrwx 1 tftp tftp 128 Jan 23 15:24 cisco_config > lrwxrwxrwx 1 root root 29 Mar 15 12:34 debian-installer -> > pxeboot/gtk/debian-installer/ > drwxr-xr-x 1 tftp tftp 242 Mar 15 12:33 pxeboot > > How do I tell bootnetx64.efi to just look directly in that folder > instead of looking at the default location? > > Thanks, > Joshua As someone who is curious about PXE, did you ever figure this out? Thanks, David
If Linux Is About Choice, Why Then ...
On Mon, 13 Mar 2017 12:30:11 -0700 Patrick Bartek wrote: > The Linux mantra has always been "choice," plethoras of choices. So why > at install time, is there no choice for the init system? You get what > the developers decide. Yes, you can install a new one -- I've done it > and it works -- but only after the install. It'd be a lot easier, if > there were a choice to begin with just like whether you want a GUI and > which one. > > Now, I know with LFS, you get to choose everything, etc. But is a > choice of init at install time so outrageous that no one ever > considered it or is it technically unfeasible or something else. > > Just curious. > Because this reply is so late I'm CC'ing you off list. I sympathize, I run Gentoo Linux and us OpenRC. I plan on running Devuan, a Debain derivative that supports lots of different init systems. Why no one looks at their project and sees the people involved when making a statistic up for the amount of dissatisfied systemd users I don't know. Sincerely, David
Re: system drive encryption question
Le 06/04/2017 à 13:10, Nathanael Schweers a écrit : Rick Thomas writes: You need an un-encrypted /boot partition to hold the kernel and initrd, of course… This is not true, although I also thought it to be the case. Grub2 can handle LUKS, so it is possible to encrypt the whole disk. Actually not the whole disk (except if you are going to install GRUB's boot/core images on another device, but the full /boot, including /boot/grub, can be encrypted. However my opinion is that encrypting /boot provides little benefit in general. Here is why. Encryption provides two main benefits : confidentiality and tamper-proof. There is nothing confidential in /boot, but if tamper-proof matters to you then all the boot components, including GRUB's boot/core images, which cannot be encrypted, must be tamper-proof too. This can be achieved by installing them on a write-only device, or on a removable device used only for booting, or using some "trusted computing" framework (UEFI secure boot, TPM module...). I recently stumbled across a post where the procedure is explained using archlinux as an example. I’m not sure whether debian includes a version of Grub which can also do so, but in principle an unencrypted /boot partition is not needed. The version of GRUB included in Jessie at least can handle an encrypted /boot. However the Debian installer does not handle this case correctly. You must add the following line in /etc/default/grub in order for grub-install to install the core image with crypto modules and for update-grub to generate a proper grub.cfg : GRUB_ENABLE_CRYPTODISK=y (not =1 or =true as seen on some documentation) The procedure in the post you point to is flawed in Debian Jessie : if you run update-grub or grub-mkconfig before adding the line in /etc/default/grub, it won't add the required "cryptomount" commands to open encrypted devices. Actually it is grub-mkconfig which is broken : if the line is present, it adds an cryptomount command in every menu entry, even when not needed (and generates boot-time errors). If the line is missing, it adds insmod commands to load crypto modules when needed but not the cryptomount commands.
Avaya IP Office/Aura Users
Hi, are you interested in acquiring *Avaya Users* list for your marketing campaigns? We also have other technology users like: Mitel Polycom Vonage ShoreTel Nextiva 8x8, Inc Five9 VirtualPBX Riverbed Brocade F5 Networks Cisco Systems Citrix Systems AT&T Lync Server Juniper Networks Verint Systems Aruba Networks *Features*: • 85% on email, 90% on other Data. 100% opt-in to receive third party information. • Name, Title, Email, Phone Number, Company name, Web Address, Physical Address, SIC Code, Industry, Company Size (Employee and revenue). • Excel or CSV. Format for unlimited usage Please drop us a quick email with your thoughts when you get the chance and I can send you samples on the same for you to test our quality. Regards, Beverly White Technology list consultant Demand generation team "We respect your privacy, if you do not wish to receive any further emails from our end please reply with a subject "*Leave Out*" Other Services: MPO | Marketing Automation | Market research | Email appending | Email campaigning | SEO | 360 Degree profiling | Data Cleansing and De-duplication | etc
Blue Coat Customers Contacts
Hi, Would you be interested in Targeted *Blue Coat* leads? We are happy to provide the database across globe, specifically *North America, EMEA, APAC* and *Latin America*. We also have other users like *Imperva Incapsula, Symantec, MacAfee, Force Point, Cisco systems, Cloud flare *and many more Data Guarantees: 90-95% Deliver ability on emails and 98% accuracy on other contact information. Please review and let me know your thoughts, I will get back to you counts, pricing and more information in my next email. Looking forward to hear from you! Regards, *Margie Edwards │ *Marketing Manager
Blue Coat Customers Contacts
Hi, Would you be interested in Targeted *Blue Coat* leads? We are happy to provide the database across globe, specifically *North America, EMEA, APAC* and *Latin America*. We also have other users like *Imperva Incapsula, Symantec, MacAfee, Force Point, Cisco systems, Cloud flare *and many more Data Guarantees: 90-95% Deliver ability on emails and 98% accuracy on other contact information. Please review and let me know your thoughts, I will get back to you counts, pricing and more information in my next email. Looking forward to hear from you! Regards, *Margie Edwards │ *Marketing Manager
Re: system drive encryption question
Hi F-, have a look at /etc/default/cryptdisks > # Mountpoints to mount, before cryptsetup is invoked at initscripts. Takes > # mountpoins which are configured in /etc/fstab as arguments. Separate > # mountpoints by space. > # This is useful for keyfiles on removable media. Default is unset. ^^ I just tried it on a Fujitsu Lifebook E781, but i have LVM running and get missing volume (containing the mountpath) :-( No time for further testing now, so... gould luck and kind regards readU Frank FHDATA: > > > hello, > > I am not currently using debian as linux OS but > considering it ... > > > If I clean install debian (latest of course) and during > the install process have its / (system drive) > encrypted with pass-phrase > > then later on, can I add a key, residing on > a usb flash drive, to that encryption? > > if yes, is there a step-by-step method one can follow to do that? > > > > thank you, > F- > >