Re: blu ray burning with samsung se506cb in debian jessie
On Tuesday 15 March 2016 08:39:21 Thomas Schmitt wrote: > > This option is the only way for me to burn reliably with my old BR drive > > What are the negative symptoms if you do not use this option ? I did a test on a bluray this evening without -speed option and the disk was burnt without issue (and without weird message at the end). I guess that growisofs got better. All the best -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Re: User's bin path not recognised in login script
On 24/03/16 00:30, David Wright wrote: ... I don't know what you mean by "login" script because you haven't yet told us (I believe) what your machine is configured to do when you boot it up. If you've installed some sort of Desktop Environment, then the DE has the responsibility of selecting the shell that runs your "login" script and, indeed, what the filename of that script is. You're right - I didn't explicitly tell you that my desktop environment is Mate which I chose when I installed Debian recently. There's a "Control Centre" which has a GUI application "Startup Applications" which is pre-populated by items such as "GPG Password Agent", "Mate Settings Daemon", "Pulse Audio", etc. You can add your own item by specifying name and command. This is where I added a bash script I wrote which I called "Login" which is located in ~/bin. All my other scripts in there are run in a Mate terminal or via a launcher icon on the desktop, and in both cases they use the path set up in ~/.bashrc. Anyway, thanks for the information (including the existence of dash). Unfortunately I don't have time to delve deeper into this now as I have another project that has reared its head, so I'd ask you not to spend any more of your time responding, as I will not revisit this thread. And thanks to all other responders for their efforts.
Re: Installing newer kernels
On 2016-03-24, David Christensen wrote: > On 03/23/2016 07:46 PM, John Hasler wrote: >> David Christensen writes: >>> If I am running version N, have changed the configuration file to M', >>> and then upgrade to version N+1, you're saying dist-upgrade throws >>> away +X and -Y. I may want or need those. >> >> The package management system will notice that you have changed the >> file. You will be asked if you want to keep the old version, install >> the new one, look at a diff, or shell out and do something else. > > Okay -- not as grim as I thought. Yeah, it's like there are people behind the scenes thinking these things out ahead of time or something! > > David > > -- Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and so entirely in harmony with the demagogic appeals to cultural democracy that accompany (and distract one’s attention from) the ever-tightening grip of plutocratic capitalism. - Susan Sontag
Re: blu ray burning with samsung se506cb in debian jessie
Hi,
Dominique Dumont wrote:
> I guess that growisofs got better.
It depends on the starting point of the comparison. {:)
https://tracker.debian.org/media/packages/d/dvd%2Brw-tools/changelog-7.1-11
shows two program changes in the last 5 years. None would be
related to speed or physical quality of drive and media.
The youngest patch of 2015 is by me.
The other one from 2011 does not change growisofs behavior with
empty BD-R, but only with those which already contain some data.
If speed reduction reproducibly helps, then there is a bad relation
between drive and medium, not a wrongdoing in the burn software.
As for growisofs getting better, one should strive for applying
at least the first patch in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794868
which is tested by Fedora since 4 years.
Have a nice day :)
Thomas
test
-- Sincerely, Gavrilov Aleksey System Administrator Ltd. "Hearst Shkulev Digital Rugion" tel .: 8 (351) 729-94-90, ext. 345 mob. +7 999 581 7934 gavri...@info74.ru Chelyabinsk, st. Melkombinat February 1st Precinct, 18, office 208 for TRC `Rodnik`
Re: Installing newer kernels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 23, 2016 at 08:07:45PM -0700, David Christensen wrote: > On 03/23/2016 07:46 PM, John Hasler wrote: > >David Christensen writes: > >>If I am running version N, have changed the configuration file to M', > >>and then upgrade to version N+1, you're saying dist-upgrade throws > >>away +X and -Y. I may want or need those. > > > >The package management system will notice that you have changed the > >file. You will be asked if you want to keep the old version, install > >the new one, look at a diff, or shell out and do something else. > > Okay -- not as grim as I thought. It's actually one of the things which has kept me as a happy Debian user all the time, In a way, I feel respected as an admin of my system: /etc is *my* green (as are /usr/local et al), the usual /bin, /var, /usr/bin and so on are the distro's. It's a clear contract. That doesn't mean "they" are out to "get me": if I changed something on /etc and the original version evolved behind my back (e.g. more config options), Debian goes out of its way to notice the situation and help me fixing it. Compare this to some uber-tentacl-y admin tools with no clear limits about which parts of the system they are supposed to touch or to leave alone (they've gotten better over the years, admittedly). Debian treats me as a grown-up, and I appreciate that deeply. - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlbzotkACgkQBcgs9XrR2kYmAwCfa5AP8FUlcOQplBk5ogOnVsd2 ZC8AnRBYqBITCT2Ed0QgTD85E+5i8Gx3 =gMGq -END PGP SIGNATURE-
Re: Error with Apache MPM itk
Le 23/03/2016 21:05, to...@tuxteam.de a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 23, 2016 at 04:40:57PM +0100, Olivier Desport wrote: It's true that Apache is running under www-data group on Jessie : [...] But on Wheezy, Apache is running under root, so I don't have to give execute access to the folder : [...] But that's what I am saying: just chgrp the folder to www-data; I asume that the perms are 0750 -- voilà. The group *has* the necessary w+x access. You don't have to give that to *all*. OK. I've changed the folders groups owner to www-data with r-x permissions. Only the owner have rwx permissions and it works well when I upload a file from a web site. By the way -- running Apache under root seems a bad idea. The least security issue gives a potential attacker root! I can't imagine that this was the default in Wheezy (actually I'm pretty sure it wasn't). You're right. regards - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlby9xwACgkQBcgs9XrR2kbZNACdGol+oXiyWReIeHlafhG8tA4+ pIkAnAxZHR5zU8lM0ZcAR6NGdh5QgGcc =OVq7 -END PGP SIGNATURE-
Re: Error with Apache MPM itk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Mar 24, 2016 at 10:05:29AM +0100, Olivier Desport wrote: [...] > OK. I've changed the folders groups owner to www-data with r-x > permissions. Only the owner have rwx permissions and it works well > when I upload a file from a web site. Glad you could solve your problem :-) regards - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlbzqqAACgkQBcgs9XrR2kYW1ACZAaXru8Md7mZQvWkrA8aDR0jz +EcAnjxXXaL0ZVfJr45P/CVtYA+rnwtd =scsb -END PGP SIGNATURE-
Re: Error with Apache MPM itk
Thanks for your help. Le 24/03/2016 09:51, to...@tuxteam.de a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Mar 24, 2016 at 10:05:29AM +0100, Olivier Desport wrote: [...] OK. I've changed the folders groups owner to www-data with r-x permissions. Only the owner have rwx permissions and it works well when I upload a file from a web site. Glad you could solve your problem :-) regards - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlbzqqAACgkQBcgs9XrR2kYW1ACZAaXru8Md7mZQvWkrA8aDR0jz +EcAnjxXXaL0ZVfJr45P/CVtYA+rnwtd =scsb -END PGP SIGNATURE-
Setting up Fakeraid with mdadm
Hello, I am trying to use an "LSI Megaraid Software RAID" with mdadm, but I have not been successful so far. When I configure a RAID 1 in the BIOS Setup-Utility and boot from network with an NFSROOT, a ddf container device is detected as /dev/md127 and a raid device as /dev/md126, but when I reboot, the previously created RAID configuration has been destroyed, that is, when I start the BIOS-RAID-Utility again, it does not 'remember' the configuration it created earlier. As a solution of the above problem, I already tried to create an mdadm RAID 1 without BIOS support, that is, I deactivated the RAID feature in BIOS-Setup and after booting with NFSROOT, used 'mdadm --create ...', but I did not manage to make that RAID bootable. So, how can I setup a RAID 1 over two whole disks with mdadm? Regards Christoph
[HITB-Announce] HITB2016AMS CommSec Call for Papers
Alongside the CommSec Exhibition Village held at HITB Security Conference in Amsterdam, a FREE TO ATTEND track of talks will also be held on the 26th and 27th of May and we are calling on the community of hackers, makers, builders and breakers to send us their 30 / 60 minute talk abstracts for consideration to be included. Thanks to our sponsor NIXU, access to these track of talks is completely FREE TO ATTEND and we are encouraging everyone to come! If you're in Amsterdam during these dates, this is the place you want to be! In total we have spots for 12 x 30 minute presentations and we're looking for talks that cover a wide range of topics including: - Electronics & Micro Controllers - Arduino's, ARM, RaspberryPi, etc - Mobile Communications (GPRS/3G/HSDPA etc) - Hardware / Embedded Reverse Engineering - Home Automation - Network Security - Software Security - RFiD, Bluetooth and NFC - Next Generation Application Development - 3D Printing / Fabrication - Programming - Privacy - Data Security Submissions must be sent via email to hitb-comm...@hackinthebox.org with the following details included: - Your full name - Your designation / job title - The length of your talk (standard is 30 minutes including Q&A) - Title of your submission - Details of your talk (please be as verbose as possible) - Any special requirements (as standard we supply a VGA projector) What You Get: - 1 x VIP conference pass to #HITB2016AMS on the 26th and 27th - 1 x invite to official speakers reception on the 25th evening - 1 x invite to the post conference party on the 27th evening More details: http://conference.hitb.org/hitbsecconf2016ams/commsec-track-call-for-papers/ Regards, Hafez Kamal Hack in The Box (M) Sdn. Bhd 36th Floor, Menara Maxis Kuala Lumpur City Centre 50088 Kuala Lumpur, Malaysia Tel: +603-26157299 Fax: +603-26150088
systemd networkd and mount remote-fs
Hi An error occurs when the system boots. Conditions for the appearance. The main network interface configured to receive via dhcp. cat /etc/systemd/network/00_eth0.network [Match] Name=eth0 [Network] DHCP=yes# <- cat /etc/systemd/network/10_interface_mesh0_ipv4.network # Ansible managed: modified on 2016-01-29 17:12:05 [Match] Name=mesh0 [Network] Address=172.16.35.5/24 cat /etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback systemd-analyze plot > bootup.svg https://drive.google.com/file/d/0Bxc-zRqh3G-fdmdNT0FFTTdhdnc/view?pref=2&pli=1 systemctl status media-dst.mount ... ● media-dst.mount - /media/dst Loaded: loaded (/etc/fstab)Active: failed (Result: exit-code) since Чт 2016-03-24 15:41:56 YEKT; 36min ago Where: /media/dst What: //192.168.0.37/dst Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 701 ExecMount=/bin/mount -n //192.168.0.37/dst /media/dst -t cifs -o rw,credentials=/root/.smb,iocharset=utf8,_netdev,uid=1000,gid=1000 (code=exited, status=32) мар 24 15:41:56 itregion-gavrilov systemd[1]: media-dst.mount mount process exited, code=exited status=32 мар 24 15:41:56 itregion-gavrilov systemd[1]: Failed to mount /media/dst. мар 24 15:41:56 itregion-gavrilov systemd[1]: Unit media-dst.mount entered failed state. мар 24 15:41:56 itregion-gavrilov mount[701]: mount error(101): Network is unreachable мар 24 15:41:56 itregion-gavrilov mount[701]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) ... I also read this thread here ( https://lists.debian.org/debian-user/2015/06/msg01545.html ) I found that the error only occurs if the configured network interface systemd dhcp. Adding a script solves the problem, but it's clumsy solution. [Unit] Description=Waiting for CIFS server DefaultDependencies=no Conflicts=shutdown.target Wants=network-online.target Before=network-online.target shutdown.target After=network.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/sh -c "while ! ping -c 1 gw_ip >/dev/null; do sleep 1; done" # Modify this timeout to your heart's content. TimeoutStartSec=10 [Install] WantedBy=network.target I formed the opinion that systemd does not wait for dhcp-clients when he insists. Where can I write to create ticket for this error? -- Sincerely, Gavrilov Aleksey System Administrator Ltd. "Hearst Shkulev Digital Rugion" tel .: 8 (351) 729-94-90, ext. 345 mob. +7 999 581 7934 gavri...@info74.ru Chelyabinsk, st. Melkombinat February 1st Precinct, 18, office 208 for TRC `Rodnik`
Re: Setting up Fakeraid with mdadm
On Thu, Mar 24, 2016 at 11:52:05AM +0100, Christoph Pleger wrote: > Hello, > > I am trying to use an "LSI Megaraid Software RAID" with mdadm, but I have > not been successful so far. When I configure a RAID 1 in the BIOS > Setup-Utility and boot from network with an NFSROOT, a ddf container > device is detected as /dev/md127 and a raid device as /dev/md126, but when > I reboot, the previously created RAID configuration has been destroyed, > that is, when I start the BIOS-RAID-Utility again, it does not 'remember' > the configuration it created earlier. > > As a solution of the above problem, I already tried to create an mdadm > RAID 1 without BIOS support, that is, I deactivated the RAID feature in > BIOS-Setup and after booting with NFSROOT, used 'mdadm --create ...', but > I did not manage to make that RAID bootable. > > So, how can I setup a RAID 1 over two whole disks with mdadm? You can either use the LSI's built-in RAID system or mdadm but not both. Don't use the fakeraid. If you actually have a decent LSI card (2002 or 3003 chipset) you could use the real RAID that is provided there, instead. In that case, RAID will show up as /dev/sda. Configure the LSI to present individual disks and then use mdadm the normal way: partition the disks into two sets, a small /boot partition and a large /. (Or three partitions per disk: /boot, / and /home.) Create mdadm pairs for each of sda1,sdb1 sda2,sdb2 sda3,sdb3 ... and set /dev/md0, for /boot, as bootable. The Debian installer can handle all of this easily. -dsr-
Re: systemd networkd and mount remote-fs
root@itregion-gavrilov:/tmp# systemctl status media-dst.mount ● media-dst.mount - /media/dst Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Чт 2016-03-24 15:41:56 YEKT; 1h 21min ago Where: /media/dst What: //192.168.0.37/dst Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 701 ExecMount=/bin/mount -n //192.168.0.37/dst /media/dst -t cifs -o rw,credentials=/root/.smb,iocharset=utf8,_netdev,uid=1000,gid=1000 (code=exited, status=32) мар 24 15:41:56 itregion-gavrilov systemd[1]: media-dst.mount mount process exited, code=exited status=32 мар 24 15:41:56 itregion-gavrilov systemd[1]: Failed to mount /media/dst. мар 24 15:41:56 itregion-gavrilov systemd[1]: Unit media-dst.mount entered failed state. мар 24 15:41:56 itregion-gavrilov mount[701]: mount error(101): Network is unreachable мар 24 15:41:56 itregion-gavrilov mount[701]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) I also read this thread here ( https://lists.debian.org/debian-user/2015/06/msg01545.html ) I found that the error only occurs if the configured network interface systemd dhcp. Adding a script solves the problem, but it's clumsy solution. On 24.03.2016 16:35, Gavrilov Aleksey wrote: systemd-analyze plot > bootup.svg https://drive.google.com/file/d/0Bxc-zRqh3G-fdmdNT0FFTTdhdnc/view?pref=2&pli=1 systemctl status media-dst.mount ... ● media-dst.mount - /media/dst Loaded: loaded (/etc/fstab)Active: failed (Result: exit-code) since Чт 2016-03-24 15:41:56 YEKT; 36min ago Where: /media/dst What: //192.168.0.37/dst Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 701 ExecMount=/bin/mount -n //192.168.0.37/dst /media/dst -t cifs -o rw,credentials=/root/.smb,iocharset=utf8,_netdev,uid=1000,gid=1000 (code=exited, status=32) мар 24 15:41:56 itregion-gavrilov systemd[1]: media-dst.mount mount process exited, code=exited status=32 мар 24 15:41:56 itregion-gavrilov systemd[1]: Failed to mount /media/dst. мар 24 15:41:56 itregion-gavrilov systemd[1]: Unit media-dst.mount entered failed state. мар 24 15:41:56 itregion-gavrilov mount[701]: mount error(101): Network is unreachable мар 24 15:41:56 itregion-gavrilov mount[701]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) ... I also read this thread here ( https://lists.debian.org/debian-user/2015/06/msg01545.html ) I found that the error only occurs if the configured network interface systemd dhcp. Adding a script solves the problem, but it's clumsy solution. -- Sincerely, Gavrilov Aleksey System Administrator Ltd. "Hearst Shkulev Digital Rugion" tel .: 8 (351) 729-94-90, ext. 345 mob. +7 999 581 7934 gavri...@info74.ru Chelyabinsk, st. Melkombinat February 1st Precinct, 18, office 208 for TRC `Rodnik`
Re: Setting up Fakeraid with mdadm
Hello, > Configure the LSI to present individual disks and then use mdadm > the normal way: partition the disks into two sets, a small /boot > partition and a large /. (Or three partitions per disk: /boot, / > and /home.) > > Create mdadm pairs for each of sda1,sdb1 sda2,sdb2 sda3,sdb3 > ... and set /dev/md0, for /boot, as bootable. The Debian > installer can handle all of this easily. Isn't it possible to use mdadm for mirroring disks as a whole, instead of single partitions? I am not using the debian installer, but want to boot from network with an NFSROOT, create a basic system on the RAID and then reboot from RAID. Regards Christoph
Re: Sudo
> Or simply "sudo bash --login" > I haven't needed to use root login for years, In which sense is this not a "root login"? Or would "su -" not be considered a root login either? What about "ssh root@localhost"? Stefan
Re: Setting up Fakeraid with mdadm
Hello, > Isn't it possible to use mdadm for mirroring disks as a whole, instead of > single partitions? If mdadm cannot create such RAIDs, is it possible to disable mdadm and use dmraid instead? On the web, I have found information about a kernel command line option 'nomdmonddf', but almost all of the information had to do with Ubuntu, so I do not know if 'nomdmonddf' also works for Debian. Regards Christoph
Re: Sudo
On Thu 24 Mar 2016 at 09:42:51 (-0400), Stefan Monnier wrote: > > Or simply "sudo bash --login" > > I haven't needed to use root login for years, > > In which sense is this not a "root login"? You don't log in. You don't get the shell specified in /etc/passwd. You're just running bash as a login shell, ie it starts up differently. > Or would "su -" not be considered a root login either? No. > What about "ssh root@localhost"? Yes. Type w and you'll see the time at which you just logged in. Try all these methods as an ordinary user. Then touch /etc/nologin and try them again. Shells work, logins don't. Cheers, David.
Re: Setting up Fakeraid with mdadm
On Thu, Mar 24, 2016 at 01:52:30PM +0100, Christoph Pleger wrote: > Hello, > > > Configure the LSI to present individual disks and then use mdadm > > the normal way: partition the disks into two sets, a small /boot > > partition and a large /. (Or three partitions per disk: /boot, / > > and /home.) > > > > Create mdadm pairs for each of sda1,sdb1 sda2,sdb2 sda3,sdb3 > > ... and set /dev/md0, for /boot, as bootable. The Debian > > installer can handle all of this easily. > > Isn't it possible to use mdadm for mirroring disks as a whole, instead of > single partitions? Yes, but if it's going to be your main boot and root, don't do that. > I am not using the debian installer, but want to boot from network with an > NFSROOT, create a basic system on the RAID and then reboot from RAID. That's fine. All of this can be done by hand with fdisk or parted, mdadm, and mkfs. -dsr-
Re: Sudo
> Yes. Type w and you'll see the time at which you just logged in. That seems to me like a completely unimportant detail, with little to no consequence. When compared to the consequences of having a shell with uid==0 this seems like nitpicking. So, it confirms my suspicion that "root login" is used to refer to a distinction that is pretty much irrelevant (tho I guess there is the fact the root access occurs via some other local user, so you get a tiny little bit of a trace). Stefan "who usually uses `su -` but thinks of it as a `root login`"
Re: Does anyone know how to configure a Brother MFC-J5720DW with cups?
On Wed 23 Mar 2016 at 20:31:31 +, Brian wrote: > pdl=application/octet-stream,image/urf" > > PDFs will not print. I own up to spreading misinformation if I implied > they would. I stated that an iOS device sends PDFs and then went on to deduce that the printer performs some conversion to something the printer can print. As you said > So you appear to be saying that what passes through the AirPrint > wire or wifi link is a PDF. The printer then converts it to BUL, > then raster. You were right to prod me because the statement about PDFs definitely being passed from device to printer in all circumstances is incorrect. The deduction is also false. Suppose the printer advertises pdl=application/vnd.hp-PCL,application/pdf.image/jpeg,image/urf as mime types it accepts. In that case the printer is a PDF printer and it will print a PDF directly sent to it. image/urf is an obligatory mime type for AirPrint. So what does an iOS application send? My guess is that the application knows it can send application/pdf or image/urf and sends application/pdf because it is first in the list. The PDF is rasterised on the printer. If pdl=application/vnd.hp-PCL,image/jpeg,image/urf there is only the choice of image/urf. urf is a raster format which will be rasterised to the printer's language on the printer. Having stressed the importance of Bonjour broadcasts a few times I went on (in pursuit of solving a problem) to ignore the role they play on the client side.
Unable to connect WiFi when resuming from system sleep after stretch update on 2016-03-22
Hi, I have been experiencing an issue after I updated my stretch system (apt upgrade) few days ago. When I resume the system from sleep mode (power button -> suspend; power button -> resume), the WiFi does not connect. And does not even scan the available network. I found a workaround to avoid to fully restart the system by executing this script on system resume: > iwconfig wlan0 txpower auto > /etc/init.d/wicd stop > /etc/init.d/dbus reload > /etc/init.d/wicd start My next step will be to automate this script to be started at system resume. But, I wonder if this is because of a bug since it happens after a system update or a miss-configuration on my side. Thank you, Julien Langlois
Re: Setting up Fakeraid with mdadm
Hello, >> >> Isn't it possible to use mdadm for mirroring disks as a whole, instead >> of >> single partitions? > > Yes, but if it's going to be your main boot and root, don't do > that. How is that done if it is not the boot disc? And why can it not be the boot disc, though it could with dmraid? I am still wondering why mdadm discovered the RAID that I had created with the BIOS RAID utility, but destroyed it. I wanted to re-install the machine anyway, but what if had used netboot with nfsroot as a rescue system for the machine? Regards Christoph
Re: Re: Iceweasel update error on Wheezy
iceweasel 44.0.2 deb http://debian.salud.gob.sv/debian-mozilla/ wheezy-backports iceweasel-release http://wiki.salud.gob.sv/wiki/Actualizaciones_y_sources.list
Re: Setting up Fakeraid with mdadm
On Thu, Mar 24, 2016 at 05:08:06PM +0100, Christoph Pleger wrote: > Hello, > > >> > >> Isn't it possible to use mdadm for mirroring disks as a whole, instead > >> of > >> single partitions? > > > > Yes, but if it's going to be your main boot and root, don't do > > that. > > How is that done if it is not the boot disc? And why can it not be the > boot disc, though it could with dmraid? If it's not the boot disk, you do: # mdadm --create --level raid1 -n 2 /dev/sda /dev/sdb or other options that make you happy. If you do this, you can make a filesystem in your new md device, or you can try to partition it and then make filesystems. This approach, in my experience, leads to confused initramfs and grub configs that take hours to debug. So my advice is: don't do that. -dsr-
Changing Boot Order
Assembled Wisdom! I am running wheezy, and would like to upgrade to jessie. To that end I've bought a CD and a USB stick from LinuxCollections. My problem: when booting I can't get into my bios to change the boot order. No matter what key I press, the system continues on with a re-boot of my old wheezy. Details: my motherboard is a "Military Class Motherboard", which I believe is also called MSI. When the image flashed on the screen, only for a few seconds, I see at the bottom instructions to press either the F11 key, or the Delete key. But when I press either of these, nothing happens. So my question is: can I change the boot order from withing wheezy, after I have booted and wheezy is already in use? [ Yes, I should have saved the material that came with my machine. But I have recently moved, quite hurriedly, and I fear that the paper manuals were lost. ] Thanks in advance for all help and suggestions! Alan -- Alan McConnell : http://globaltap.com/~alan/ "War is God's way of teaching Americans geography."(Bierce) Know thyself. If you need help, call the C.I.A.
Re: Issues running VLC on Xserver
On Wed, 23 Mar 2016 06:00:02 +0100 Himanshu Shekhar wrote: > I have been using VLC for playing videos, as it scales up the video to fit > the screen even if the size of video doesn't match the screen size. This > was done using "Always fit windows" settings. However, after some recent > update (no idea which one), videos with smaller resolution doesn't scale > up. They run in the middle of the screen, and when "always fit windows" is > checked, it runs in the same size in the top left corner of the window. > Things work fine in GNOME Videos. > This is not the same everywhere, as when I login to "GNOME on Wayland", VLC > work fine. There is no issue. > > Also, when I change "Hardware accelerated decoding" to X11 codecs, few > videos work well (mp4/mkv/avi), while sometimes (now-a-days frequent), > entire RAM gets used up. On running VLC from Terminal, I saw some messages > about segmentation fault. I don't know, try: $ vlc --reset-config -- CK
Re: Changing Boot Order
Greetings, I don't have an answer to your question but maybe sharing a personal experience will help with the problem entering bios setup. I recently had the same issue using a wireless keyboard and discovered the system only responded to a hardwired keyboard at that point in the boot process. By using a USB keyboard instead of the wireless, I was able to enter setup and change the boot order. HTH Tom Ashley On 03/24/2016 04:44 PM, Alan McConnell wrote: Assembled Wisdom! I am running wheezy, and would like to upgrade to jessie. To that end I've bought a CD and a USB stick from LinuxCollections. My problem: when booting I can't get into my bios to change the boot order. No matter what key I press, the system continues on with a re-boot of my old wheezy. Details: my motherboard is a "Military Class Motherboard", which I believe is also called MSI. When the image flashed on the screen, only for a few seconds, I see at the bottom instructions to press either the F11 key, or the Delete key. But when I press either of these, nothing happens. So my question is: can I change the boot order from withing wheezy, after I have booted and wheezy is already in use? [ Yes, I should have saved the material that came with my machine. But I have recently moved, quite hurriedly, and I fear that the paper manuals were lost. ] Thanks in advance for all help and suggestions! Alan
Re: Linux CLI gnuplot-ish program to do maps?
I did it! :) Here is the command to get Fatu Hiva! gmt pscoast -R-138.75/-138.55/-10.6/-10.4 -JM6i -Pc \ -Ba0.33/a0.33/WeSn -S0/100/200 -Ggray -Dh \ -W0.1 > fatu-hiva.ps The result (the PNG after convert(1)): http://user.it.uu.se/~embe8573/pics/fatu-hiva.png http://user.it.uu.se/~embe8573/pics/fatu-hiva.ps Still, not much of a map tho... I'll have to figure out how to add the villages... and mountains... and moais... and aku-akus! But it is possible, just like I knew that it would be! :) -- underground experts united http://user.it.uu.se/~embe8573 Emacs Gnus Blogomatic . http://user.it.uu.se/~embe8573/blogomatic - so far: 19 Blogomatic articles -
Re: Changing Boot Order
On 24 March 2016 at 20:44, Alan McConnell wrote: > Assembled Wisdom! > > I am running wheezy, and would like to upgrade to jessie. To > that end I've bought a CD and a USB stick from LinuxCollections. > My problem: when booting I can't get into my bios to change the > boot order. No matter what key I press, the system continues > on with a re-boot of my old wheezy. > > Details: my motherboard is a "Military Class Motherboard", which > I believe is also called MSI. When the image flashed on the screen, > only for a few seconds, I see at the bottom instructions to press > either the F11 key, or the Delete key. But when I press either of > these, nothing happens. Try hitting the F11 key twice and then quickly move to the delete key and hit it twice as well. That works for mine. Regds MF > So my question is: can I change the boot > order from withing wheezy, after I have booted and wheezy is already > in use? > > [ Yes, I should have saved the material that came with my machine. > But I have recently moved, quite hurriedly, and I fear that the paper > manuals were lost. ] > > Thanks in advance for all help and suggestions! > > Alan > > -- > Alan McConnell : http://globaltap.com/~alan/ >"War is God's way of teaching Americans geography."(Bierce) >Know thyself. If you need help, call the C.I.A. > > -- Climostat Ltd Rm 5169 The Heath Business & Technical Park The Heath Runcorn Cheshire WA7 4QX Tel. 01 928 515 015
Re: Changing Boot Order
Alan McConnell wrote: > Assembled Wisdom! > > I am running wheezy, and would like to upgrade to jessie. To > that end I've bought a CD and a USB stick from LinuxCollections. > My problem: when booting I can't get into my bios to change the > boot order. No matter what key I press, the system continues > on with a re-boot of my old wheezy. > > Details: my motherboard is a "Military Class Motherboard", which > I believe is also called MSI. When the image flashed on the screen, > only for a few seconds, I see at the bottom instructions to press > either the F11 key, or the Delete key. But when I press either of > these, nothing happens. So my question is: can I change the boot > order from withing wheezy, after I have booted and wheezy is already > in use? > > [ Yes, I should have saved the material that came with my machine. > But I have recently moved, quite hurriedly, and I fear that the paper > manuals were lost. ] > > Thanks in advance for all help and suggestions! yes, it is in grub you can change which is booted first. the file: /etc/default/grub (make backup copy if you make changes you are unsure about) songbird
Re: Changing Boot Order
On Thursday 24 March 2016 20:44:54 Alan McConnell wrote: > Assembled Wisdom! > > I am running wheezy, and would like to upgrade to jessie. To > that end I've bought a CD and a USB stick from LinuxCollections. > My problem: when booting I can't get into my bios to change the > boot order. No matter what key I press, the system continues > on with a re-boot of my old wheezy. > > Details: my motherboard is a "Military Class Motherboard", which > I believe is also called MSI. When the image flashed on the screen, > only for a few seconds, I see at the bottom instructions to press > either the F11 key, or the Delete key. But when I press either of > these, nothing happens. So my question is: can I change the boot > order from withing wheezy, after I have booted and wheezy is already > in use? > > [ Yes, I should have saved the material that came with my machine. > But I have recently moved, quite hurriedly, and I fear that the paper > manuals were lost. ] To answer the question you didn't ask, when you press F11 or Del, do you press once and hope? If so, press the start button, and press Del continuously, immediately, until it has either ignored you and booted, or brought up the BIOS. If that doesn't work, try again with F11. Again, as you press the start button start continuously pressing F11 until it has either brought up the boot menu or ignored you. Ideally with a PS2 keyboard. I have had problems even with a USB keyboard, and a wireless one for that purpose is certainly a no-no. The answer to your actual question is that I don't know. :-( Lisi Lisi
Re: Changing Boot Order
Alan McConnell composed on 2016-03-24 16:44 (UTC-0400): I am running wheezy, and would like to upgrade to jessie. To that end I've bought a CD and a USB stick from LinuxCollections. My problem: when booting I can't get into my bios to change the boot order. No matter what key I press, the system continues on with a re-boot of my old wheezy. Details: my motherboard is a "Military Class Motherboard", which I believe is also called MSI MSI is a motherboard brand. Military Class is a feature class MSI marketing uses. I have one such: https://us.msi.com/product/motherboard/B85-G41-PC-Mate.html ... [ Yes, I should have saved the material that came with my machine. But I have recently moved, quite hurriedly, and I fear that the paper manuals were lost. ] If indeed yours is a MSI motherboard, which is probably fairly obvious early in POST, then pop the cover, find the model number stenciled largely on it, and find a PDF manual on MSI's web site. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: Changing Boot Order
On Thu 24 Mar 2016 at 16:44:54 (-0400), Alan McConnell wrote: > Assembled Wisdom! > > I am running wheezy, and would like to upgrade to jessie. To > that end I've bought a CD and a USB stick from LinuxCollections. > My problem: when booting I can't get into my bios to change the > boot order. No matter what key I press, the system continues > on with a re-boot of my old wheezy. > > Details: my motherboard is a "Military Class Motherboard", which > I believe is also called MSI. When the image flashed on the screen, > only for a few seconds, I see at the bottom instructions to press > either the F11 key, or the Delete key. But when I press either of > these, nothing happens. So my question is: can I change the boot > order from withing wheezy, after I have booted and wheezy is already > in use? On a Dell, by the time you see the message, it's a bit late for pressing F12 (as it happens) to get a one-time boot menu. You really need to start tapping the key repeatedly as soon as the screen displays anything. Ditto for F2 (your DEL) to get to the BIOS. Cheers, David.
clamav.securite.com no longer exists
Having just got used to a daily message from apt-cacher-ng (presumably because of changes in sid's archive), I'm now getting a 4-hourly slew of messages from clamav saying curl: (6) Couldn't resolve host 'clamav.securiteinfo.com' I stumbled upon http://www.gossamer-threads.com/lists/clamav/users/63524 and wondered if the ball is in my court or the Debian maintainer's. Cheers, David.
Re: Sudo
On Thu 24 Mar 2016 at 11:15:35 (-0400), Stefan Monnier wrote: > > Yes. Type w and you'll see the time at which you just logged in. > > That seems to me like a completely unimportant detail, with little to > no consequence. When compared to the consequences of having a shell > with uid==0 this seems like nitpicking. > > So, it confirms my suspicion that "root login" is used to refer to > a distinction that is pretty much irrelevant (tho I guess there is the > fact the root access occurs via some other local user, so you get > a tiny little bit of a trace). > > Stefan "who usually uses `su -` but thinks of it as a `root login`" Whether the distinction is important to you or not doesn't change the meaning of the words themselves. Besides, I didn't think there were any unimportant details when dealing with security. "Sloppy usage usually implies, and certainly encourages, sloppy thinking." (CJ Date) Cheers, David.
Re: systemd networkd and mount remote-fs
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790448 -- Sincerely, Gavrilov Aleksey System Administrator Ltd. "Hearst Shkulev Digital Rugion" tel .: 8 (351) 729-94-90, ext. 345 mob. +7 999 581 7934 gavri...@info74.ru Chelyabinsk, st. Melkombinat February 1st Precinct, 18, office 208 for TRC `Rodnik`
