Re: Planning a new Debian box!
On Mar 27, 2015, at 10:57 PM, Bob Bernstein wrote: > On Fri, Mar 27, 2015 at 02:30:47PM -0600, Paul E Condon wrote: > > Yup. They are like that. Dell *servers* can be bought with empty disks (no OS). No MS tax, and there's no chance of computer fan(s) emitting MS bits and polluting the room. Without the MS tax, the bottom of the line towers are reasonably priced. >> It took dd about 30 hours to wipe the disk in my old Dell. Try a dban CD. It takes a while to wipe a disk, but way less than 30 hours, using DoD algorithms. And it wipes in parallel -- it wipes all the disks it can find on the computer, at the same time, even if they're different sizes; even if some are SCSI and some are SATA. -- Glenn English -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6a560ff2-c916-46b5-80a4-479fdcad0...@slsware.net
Re: Planning a new Debian box!
Bob Bernstein wrote: > Shortly I will become the owner of a refurbished Dell with Win7 already on > its 160g sata hard drive. > > I have no need or use for a multi-OS multi-boot machine. I only want wheezy > on this for now. > > Question: can I entrust to the Debian installer the task of repartitioning > and formatting the HD with all that Windoze cruft already on it? If you delete all the windows partitions, create new partition(s), install Debian and install a new boot loader, you should get no problems from windows. Last time I bought a notebook, I decided to keep Windows 7 around for diagnostic purposes. I found that Partition Wizard[1] Live CD by Minitool, can handle all of the issues in shrinking a windows partition to create space for another OS. This was much easier than the windows partition resizing tool, which is trickly, limited and awkward as hell. Cheers > Or, are there steps I ought to take prior to launching the installer, > perhaps involving other disk tools? I don't trust what M$ puts on hard > drives! 1. http://www.partitionwizard.com/free-partition-manager.html > TIA Debian peeps! -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150328084137.GA24759@sprite
Re: What is the correct way to set encrypted swap with systemd?
~Stack~ wrote: > Remember back a few months ago when systemd wouldn't stop fsck'ing my > swap partition? Why would systemd fsck the swap? swap does not need fscking. > I know it has to do with encrypted swap partitions. I proved that last > time and I can prove it this time too. The method I have been using for > a _very_ long time and has _always_ worked pre-systemd is this: > $ grep swap /etc/crypttab > sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom > cipher=aes-xts-plain64,size=256,swap > $ grep swap /etc/fstab > /dev/mapper/sda3_crypt noneswap sw 0 0 I have the same setup on Debian Sid with systemd, just like you: ,[ /etc/crypttab | # | cswap /dev/disk/by-id/md-uuid-a805edd5:bcfd4c98:ce747c2c:77d42131 /dev/urandomswap,cipher=aes-cbc-essiv:sha256,size=256 ` ,[ /etc/fstab | /dev/mapper/cswap noneswapsw,pri=10 0 ` And this just works. My setup is even more complex, because the to-be-swap partition is on a md-RAID device. The journal contains: , | ~# journalctl --since="2015-03-28 13:19:40" | grep -i swap | Mar 28 13:19:40 skuld systemd[1]: Expecting device dev-mapper-cswap.device... | Mar 28 13:19:44 skuld systemd[1]: Starting Cryptography Setup for cswap... | Mar 28 13:19:45 skuld mkswap[998]: Setting up swapspace version 1, size = 3901692 KiB | Mar 28 13:19:45 skuld mkswap[998]: no label, UUID=93b9f463-bb59-4eb9-bc62-0fe2c3448f4e | Mar 28 13:19:45 skuld systemd[1]: Started Cryptography Setup for cswap. | Mar 28 13:19:45 skuld systemd[1]: Found device /dev/mapper/cswap. | Mar 28 13:19:45 skuld systemd[1]: Activating swap /dev/mapper/cswap... | Mar 28 13:19:45 skuld kernel: Adding 3901692k swap on /dev/mapper/cswap. Priority:1 extents:1 across:3901692k FS | Mar 28 13:19:45 skuld systemd[1]: Activated swap /dev/mapper/cswap. | Mar 28 13:19:45 skuld systemd[1]: Starting Swap. | Mar 28 13:19:45 skuld systemd[1]: Reached target Swap. ` And presto: encrypted swap. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/0bg8v4gjj...@mids.svenhartge.de
temporarily disable shutdown
Hi, how can I temporarily disable shutdown or reboot? My use case is the following: I create a file /tmp/NO_SHUTDOWN. If that file exists, a shutdown or reboot should not be possible. I have molly-guard installed and a script in /etc/molly-guard/run.d/ tests the existence of that file and prevents shutdown/reboot on the commandline. But a user in KDE can still do reboot/shutdown from either KDE or even KDM. How can I prevent that with a file /tmp/NO_SHUTDOWN. Thank you for your help Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/mf6odd$lje$1...@ger.gmane.org
Re: temporarily disable shutdown
It's as simple as correcting user/group permissions. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5516e78a.1020...@mrqueue.com
Re: temporarily disable shutdown
Am 28.03.2015 um 18:29 schrieb Matthias Bodenbinder: > Hi, > > how can I temporarily disable shutdown or reboot? > > My use case is the following: I create a file /tmp/NO_SHUTDOWN. If that file > exists, a shutdown or reboot should not be possible. > I have molly-guard installed and a script in /etc/molly-guard/run.d/ tests > the existence of that file and prevents shutdown/reboot on the commandline. > > But a user in KDE can still do reboot/shutdown from either KDE or even KDM. > How can I prevent that with a file /tmp/NO_SHUTDOWN. If you are using jessie and systemd, you can use systemd-inhibit [1]. You can run something like systemd-inhibit --what=shutdown --mode=block /bin/sleep 3600 to block shutdown for 1h. Cheers, Michael [1] http://www.freedesktop.org/software/systemd/man/systemd-inhibit.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: [solved] What is the correct way to set encrypted swap with systemd?
On 03/28/2015 08:32 AM, Sven Hartge wrote: > ~Stack~ wrote: > >> Remember back a few months ago when systemd wouldn't stop fsck'ing my >> swap partition? > > Why would systemd fsck the swap? swap does not need fscking. I have no idea. But, if I disable the swap partition the system boots just fine. If I enable it, fsck tries to run and the partition is complains about is the swap partition. I have no idea why systemd.fsck does this. :-/ [snip] > I have the same setup on Debian Sid with systemd, just like you: > > ,[ /etc/crypttab > | # > | cswap /dev/disk/by-id/md-uuid-a805edd5:bcfd4c98:ce747c2c:77d42131 > /dev/urandomswap,cipher=aes-cbc-essiv:sha256,size=256 > ` Thank you!! I think I just found out what my note "systemd.fsck doesn't like UUID's" meant! I was assuming it was in the /etc/fstab or somewhere, but when I noticed you have the /dev location of your disk and I have a UUID in the /etc/crypttab I decided to give it a try. $ grep swap /etc/crypttab # causes systemd to fsck swap #sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom cipher=aes-xts-plain64,size=256,swap # systemd doesn't fsck swap sda3_crypt /dev/sda3 /dev/urandom cipher=aes-xts-plain64,size=256,swap I reverted all of my changes that I took notes on and bada-bing-bada-boom! It works now! Out of curiosity (and because I have a sacrificial VM with various snapshots I can easily reset to), I setup a encrypted swap on a Ubuntu 15.04 alpha (pre-systemd) with my previous method. Swap worked perfectly. I 'apt-get update'd 15.04 and installed the systemd package (and a lot of "dependencies" o_O). On the first boot systemd.fsck had issues with swap and didn't mount it. I changed it to the disk instead of UUID and rebooted. Works!! So it isn't just systemd in Debian either. At least I now know in the future not to use UUID for swap in /etc/crypttab! Sometimes it seems that the most painful and frustrating problems have the most trivial solutions. :-D Thanks! ~Stack~ signature.asc Description: OpenPGP digital signature
who to report a kernel bug to in Jessie
My computer crashes and the text on the screen says it's a kernel bug. The first pid is comm, upowerd. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5516f5e6.4080...@lockie.ca
Re: [solved, unsafely?] What is the correct way to set encrypted swap with systemd?
Quoting ~Stack~ (i.am.st...@gmail.com): > On 03/28/2015 08:32 AM, Sven Hartge wrote: > > ~Stack~ wrote: > > > >> Remember back a few months ago when systemd wouldn't stop fsck'ing my > >> swap partition? > > > > Why would systemd fsck the swap? swap does not need fscking. > > I have no idea. But, if I disable the swap partition the system boots > just fine. If I enable it, fsck tries to run and the partition is > complains about is the swap partition. I have no idea why systemd.fsck > does this. :-/ > > [snip] > > I have the same setup on Debian Sid with systemd, just like you: > > > > ,[ /etc/crypttab > > | # > > | cswap /dev/disk/by-id/md-uuid-a805edd5:bcfd4c98:ce747c2c:77d42131 > > /dev/urandomswap,cipher=aes-cbc-essiv:sha256,size=256 > > ` > > Thank you!! I think I just found out what my note "systemd.fsck doesn't > like UUID's" meant! I was assuming it was in the /etc/fstab or > somewhere, but when I noticed you have the /dev location of your disk > and I have a UUID in the /etc/crypttab I decided to give it a try. > > $ grep swap /etc/crypttab > # causes systemd to fsck swap > #sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom > cipher=aes-xts-plain64,size=256,swap > # systemd doesn't fsck swap > sda3_crypt /dev/sda3 /dev/urandom cipher=aes-xts-plain64,size=256,swap > > I reverted all of my changes that I took notes on and > bada-bing-bada-boom! It works now! That cure looks retrograde to me because it throws away the uniqueness of UUIDs. What if /dev/sda3 changes, for whatever reason. A systemd 216 man page for crypttab says: "WARNING: Using the swap option will destroy the contents of the named partition during every boot, so make sure the underlying block device is specified correctly." Could you not try using a /dev/disk/by-foo/... entry instead and see if that works? (I don't recognise the particular one Sven uses.) Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150328191553.ga13...@alum.home
Re: who to report a kernel bug to in Jessie
On Sat 28 Mar 2015 at 14:41:42 -0400, James wrote: > My computer crashes and the text on the screen says it's a kernel bug. > The first pid is comm, upowerd. If we knew *exactly* what the screen told you and in what circumstances the crash occurs and how repeatable it is we might be able to help you. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/28032015193400.efd4d04a9...@desktop.copernicus.demon.co.uk
Re: Need help with CUPS printing
On 20150327_0237-0400, ken wrote: > On 03/26/2015 07:38 PM, Paul E Condon wrote: > >I'm running Jessie, as close to plain vanilla as my hardware allows. > >I have a HP Laserjet 5MP. This is an ancient device. It has built-in > >firmware for Level 2 Postscript printing and a special socket for > >Apple Localtalk connection, but no USB. It is a sturdy old beast and > >was running nicely until quite recently. But in a special configuration > >that needs to be understood in order to give help: > > > >My main desktop computer on which I receive email, and create my own > >documents has *only* USB. I bought a special cable that has a USB to > >Centronics conversion dongle at one end. But I can't use it because the > >socket for Centronics on the printer is in recessed place in the > >printer where the dongle won't fit and I can't enlarge the place > >without sawing away parts of the printer framework that are necessary > >for the paper feed system to work. So, instead, I put into service an > >old micro-mini Dell (now running Jessie) and put CUPS on it, and > >configured it to be a print server. But all this was well before I had > >any idea that there would ever be anything like Jessie in my > >future. At first, after some fiddling, the print server worked under > >Jessie, but now it has stopped working. The printer continues to > >produce test pages when requesting them from the old Dell keyboard and > >in self-test mode by pushing buttons on the printer itself, not by > >typing at the computer keyboard. > > > >After installing the most recent upgrades to Jessie on both computers > >this morning, I tried to print a few pages from iceweasel and printing > >worked. But I also want to be able to print from Emacs, which I use to > >compose my emails, such as this one. Emacs told be that there was no > >default printer even though I had just selected the printer on the old > >Dell from a pick-list presented to be by the print user interface > >presented to me by the Emacs user interface. I think I should configure > >the Cups server on my desktop computer to indicate that that printer > >over on the old Dell is the one for Emacs. But how do I do that? > > > >I can't trust my own investigations to determine if there have been any > >recent changes in the Jessie CUPS packages in the recent past. I know > >there was a new version of CUPS at the time that Jessie entered pre-release > >freeze, and I pretty sure my system was working then and not something > >that I lost in my transition from Wheezy. And, of course, I'd like a > >more foreword looking suggestion than to re-install Wheezy. I'd like this > >fixed before Jessie release because I have a bad feeling that the longer > >I wait the further from the main-stream I will be. I need, with my old > >hardware, to be as close to the middle of the herd of users as I can be. > > > >The print driver for the HPLj-5MP that I have been using in recent years > >is the one with (recommended) in its listing in the pick-list of all HP > >print drivers in the localhost:631 web site on both computers. Beyond that > >I can't think of anything people might need to know about my set-up. I'd > >be glad to answer any questions about things that I haven't realized might > >be important. > > > >Please help > > > > The first thing to do is to set up printing from the machine you set up as a > print server. Can you do that? That is, can you bring up cups from its > keyboard and print a test page? This is more a proof a connectivity than a > test of the print server's cups setup, as the "print server" can serve > simply as a network node through which you connect from other machines on > your network to the printer. > > Once you can do that, you should be able to print from whatever other > printer(s) permitted on your network by configuring it/them for that print > server's IP address. You first need to ensure you can ping the print server > from your other machine(s). Once you can do that, then set up cups on the > print client(s). I just had the experience of having composed a long email and loosing it. Thanks for the response. There is more to say if my computer is stable enough to get it sent. Thanks very much. -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150328195747.ga10...@big.lan.gnu
Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?
On 03/28/2015 02:15 PM, David Wright wrote: > Quoting ~Stack~ (i.am.st...@gmail.com): [snip] >> $ grep swap /etc/crypttab >> # causes systemd to fsck swap >> #sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom >> cipher=aes-xts-plain64,size=256,swap >> # systemd doesn't fsck swap >> sda3_crypt /dev/sda3 /dev/urandom cipher=aes-xts-plain64,size=256,swap > > That cure looks retrograde to me because it throws away the uniqueness > of UUIDs. What if /dev/sda3 changes, for whatever reason. > > A systemd 216 man page for crypttab says: >"WARNING: Using the swap option will destroy the contents of the >named partition during every boot, so make sure the underlying >block device is specified correctly." > > Could you not try using a /dev/disk/by-foo/... entry instead and see > if that works? (I don't recognise the particular one Sven uses.) OGood catch! That completely blitzed my mind. I knew there was a reason for the UUID's! :-) In my /dev/disk/by-id/ directory I have both "dm-name-sda3_crypt" and "dm-uuid-CRYPT-PLAIN-sda3_crypt" which point to "../../dm-1". I can not use either of those in my /etc/crypttab because then I get the systemd.fsck problem again. Maybe that was the problem with the UUID?? However, I also have "ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3" and "wwn-0x10001354922489237504x-part3" that point to "../../sda3". Both of those will boot correctly and mount swap. Here is my update that works: sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3 /dev/urandom cipher=aes-xts-plain64,size=256,swap So my guess, if I understand this correctly, is that if I use the encrypted container, systemd.fsck freaks out, tries to and fails to mount, then just ignores swap altogether. However, if I tell LUKS to encrypt the actual partition, that somehow means systemd.fsck is happy with it. So bizarre. Thanks for pointing that out David! ~Stack~ signature.asc Description: OpenPGP digital signature
Re: [solved, unsafely?] What is the correct way to set encrypted swap with systemd?
David Wright wrote: > That cure looks retrograde to me because it throws away the uniqueness > of UUIDs. What if /dev/sda3 changes, for whatever reason. This is why you use /dev/disk/by-* and not the raw device name, just like I did. > Could you not try using a /dev/disk/by-foo/... entry instead and see > if that works? (I don't recognise the particular one Sven uses.) Because my swap resides on a md-RAID I use the UUID of the RAID. S° -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1bg9ngsjj...@mids.svenhartge.de
Re: who to report a kernel bug to in Jessie
On 03/28/2015 03:36 PM, Brian wrote: On Sat 28 Mar 2015 at 14:41:42 -0400, James wrote: My computer crashes and the text on the screen says it's a kernel bug. The first pid is comm, upowerd. If we knew *exactly* what the screen told you and in what circumstances the crash occurs and how repeatable it is we might be able to help you. I took a picture of the screen. http://lockie.ca/~rjl/20150328_142159_small.jpg I think the other times it crashed had the same info on the screen. I am using lxde now and it hasn't crashed yet. Before I had icewm. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55171273.80...@lockie.ca
Re: [solved] What is the correct way to set encrypted swap with systemd?
~Stack~ wrote: > # causes systemd to fsck swap > #sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom > cipher=aes-xts-plain64,size=256,swap > # systemd doesn't fsck swap > sda3_crypt /dev/sda3 /dev/urandom cipher=aes-xts-plain64,size=256,swap Where did you get that UUID from in the first place? I have a certain suspicion I'd like to confirm before commenting on that. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2bg9nlsjj...@mids.svenhartge.de
Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?
~Stack~ wrote: > On 03/28/2015 02:15 PM, David Wright wrote: Quoting ~Stack~ > (i.am.st...@gmail.com): >>> $ grep swap /etc/crypttab >>> # causes systemd to fsck swap >>> #sda3_crypt UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e /dev/urandom >>> cipher=aes-xts-plain64,size=256,swap >>> # systemd doesn't fsck swap >>> sda3_crypt /dev/sda3 /dev/urandom cipher=aes-xts-plain64,size=256,swap >> >> That cure looks retrograde to me because it throws away the uniqueness >> of UUIDs. What if /dev/sda3 changes, for whatever reason. >> >> A systemd 216 man page for crypttab says: >>"WARNING: Using the swap option will destroy the contents of the >>named partition during every boot, so make sure the underlying >>block device is specified correctly." >> >> Could you not try using a /dev/disk/by-foo/... entry instead and see >> if that works? (I don't recognise the particular one Sven uses.) > OGood catch! That completely blitzed my mind. I knew there was a > reason for the UUID's! :-) > In my /dev/disk/by-id/ directory I have both "dm-name-sda3_crypt" and > "dm-uuid-CRYPT-PLAIN-sda3_crypt" which point to "../../dm-1". I can > not use either of those in my /etc/crypttab because then I get the > systemd.fsck problem again. Those device nodes only appear _after_ /etc/crypttab has been parsed. By using them inside the crypttab, you create a chicken-and-egg problem. > Maybe that was the problem with the UUID?? I guess, you used the UUID of the swap inside the crypted device. But this UUID changes on every boot, so it is of no use. > However, I also have "ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3" and > "wwn-0x10001354922489237504x-part3" that point to "../../sda3". Both of > those will boot correctly and mount swap. Here is my update that works: > > sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3 > /dev/urandom cipher=aes-xts-plain64,size=256,swap > Of course. /etc/crypttab needs the device on which to create the crypted device mapping. > So my guess, if I understand this correctly, is that if I use the > encrypted container, systemd.fsck freaks out, tries to and fails to > mount, then just ignores swap altogether. However, if I tell LUKS to > encrypt the actual partition, that somehow means systemd.fsck is happy > with it. So bizarre. No, not bizzare at all, quite logic if one thinks about what layer is put on top of what other layer. You have /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3 at the bottom. On top of that, you get /dev/mapper/sda3_crypt. And on top of that you get your swap-space. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3bg9o3djj...@mids.svenhartge.de
javascript in iceweasel
Running Wheezy 7.8 w/ iceweasel 31.5.3. Some sites won't work, telling me I need to install/activate javascript. Not sure how to do this. I assume java is loaded because I see some icedtea 6 packages installed. No idea how to activate javascript, assuming it's lurking on the HD. Searches turned up virtually nothing useful. The few relevant hits talked about going to Tools -> Options which doesn't exist on my copy. Any pointers appreciated.. -- Bob Holtzman A fair fight is the result of poor planning. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150328210710.ga9...@cox.net
Re: javascript in iceweasel
On Sat, 28 Mar 2015 14:07:10 -0700 Bob Holtzman wrote: Hello Bob, >talked about going to Tools -> Options which doesn't exist on my copy Found there in Windows, IIRC. In Linux it's Edit menu -> Preferences. If it's not there (in later versions, it appears not to be) use about:config and look for javascript.enabled and set it to your choice. It's a boolean, so clicking will toggle between true and false. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" People stare like they've seen a ghost Titanic (My Over) Reaction - 999 pgpw9MiVRniZs.pgp Description: OpenPGP digital signature
Re: javascript in iceweasel
On 2015-03-28, Bob Holtzman wrote: > Running Wheezy 7.8 w/ iceweasel 31.5.3. Some sites won't work, telling > me I need to install/activate javascript. Not sure how to do this. I > assume java is loaded because I see some icedtea 6 packages installed. > No idea how to activate javascript, assuming it's lurking on the HD. > Searches turned up virtually nothing useful. The few relevant hits > talked about going to Tools -> Options which doesn't exist on my copy. > > Any pointers appreciated.. > Brad's post answers your question. Just FYI, JavaScript is not related to Java and Icedtea. Those latter are used for running Java applets and applications from a web browser. It's a common misunderstanding arising from the similarity in nomenclature. -- Liam -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmhe7vs.3l5.liam.p.otoole@dipsy.tubbynet
GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode..
debian: I did a fresh install of Debian using debian-7.6.0-i386-netinst.iso today. When I rebooted, I saw: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode.. grub rescue> I figured that there was something incompatible between the older ISO and current files. So, I downloaded debian-7.8.0-i386-xfce-CD-1.iso and installed that. When I rebooted, I saw: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode.. grub rescue> Any suggestions? TIA, David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5517234a@holgerdanske.com
GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode..
debian: I did a fresh install of Debian using debian-7.6.0-i386-netinst.iso today. When I rebooted, I saw: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode.. grub rescue> I figured that there was something incompatible between the older ISO and current files. So, I downloaded debian-7.8.0-i386-xfce-CD-1.iso and installed that. When I rebooted, I saw: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode.. grub rescue> Any suggestions? TIA, David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/551720a3.5070...@gmail.com
Re: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode..
On Saturday 28 March 2015 21:55:22 David Christensen wrote: > debian: > > I did a fresh install of Debian using debian-7.6.0-i386-netinst.iso > today. When I rebooted, I saw: > > GRUB loading.. > Welcome to GRUB! > > error: incompatible license > Entering rescue mode.. > grub rescue> > > I figured that there was something incompatible between the older ISO > and current files. > > > So, I downloaded debian-7.8.0-i386-xfce-CD-1.iso and installed that. > When I rebooted, I saw: > > GRUB loading.. > Welcome to GRUB! > > error: incompatible license > Entering rescue mode.. > grub rescue> > > > Any suggestions? Try googling the error. https://www.google.co.uk/search?q=error%3A+incompatible+license+Entering+rescue+mode..&oq=error%3A+incompatible+license+Entering+rescue+mode..&aqs=chrome..69i57j69i58.1188j0j7&sourceid=chrome&es_sm=93&ie=UTF-8 http://www.bleepingcomputer.com/forums/t/428530/error-incompatible-license-entering-rescue-mode-grub-rescue/ HTH Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201503282224.48387.lisi.re...@gmail.com
Re: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode..
On Saturday 28 March 2015 21:55:22 David Christensen wrote: > debian: > > I did a fresh install of Debian using debian-7.6.0-i386-netinst.iso > today. When I rebooted, I saw: > > GRUB loading.. > Welcome to GRUB! > > error: incompatible license > Entering rescue mode.. > grub rescue> > > I figured that there was something incompatible between the older ISO > and current files. > > > So, I downloaded debian-7.8.0-i386-xfce-CD-1.iso and installed that. > When I rebooted, I saw: > > GRUB loading.. > Welcome to GRUB! > > error: incompatible license > Entering rescue mode.. > grub rescue> > > > Any suggestions? > > > TIA, > > David Or: https://lists.debian.org/debian-user/2011/11/msg00611.html Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201503282225.30540.lisi.re...@gmail.com
Re: xfce with gtk3 applications?
Argh, now it works. Turns out that the themes from gtk3-engines-xfce seem to have a problem. E.g. Xfce-winter from gtk3-engines-xfce doesn't work, Adwaita from gnome-themes-standard-data does. Am 03/27/15 um 13:04 schrieb mad: > Hmmm, doesn't seem to help. > > Am 27.03.2015 um 11:17 schrieb Alexis: >> >> mad writes: >> >>> More ideas? >> >> It might be that gnome-settings-daemon needs to be running, although >> doing so might well mess with XFCE's settings setup >> >> >> Alexis. > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55172c4f@sharktooth.de
Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?
On 03/28/2015 03:37 PM, Sven Hartge wrote: > ~Stack~ wrote: [snip] >> In my /dev/disk/by-id/ directory I have both "dm-name-sda3_crypt" and >> "dm-uuid-CRYPT-PLAIN-sda3_crypt" which point to "../../dm-1". I can >> not use either of those in my /etc/crypttab because then I get the >> systemd.fsck problem again. > > Those device nodes only appear _after_ /etc/crypttab has been parsed. By > using them inside the crypttab, you create a chicken-and-egg problem. Oh. Then yeah, that does explain some things...quite a bit actually. >> Maybe that was the problem with the UUID?? > > I guess, you used the UUID of the swap inside the crypted device. But this > UUID changes on every boot, so it is of no use. Huh. More thoughts on that below. >> However, I also have "ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3" and >> "wwn-0x10001354922489237504x-part3" that point to "../../sda3". Both of >> those will boot correctly and mount swap. Here is my update that works: >> >> sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3 >> /dev/urandom cipher=aes-xts-plain64,size=256,swap >> > > Of course. /etc/crypttab needs the device on which to create the crypted > device mapping. > >> So my guess, if I understand this correctly, is that if I use the >> encrypted container, systemd.fsck freaks out, tries to and fails to >> mount, then just ignores swap altogether. However, if I tell LUKS to >> encrypt the actual partition, that somehow means systemd.fsck is happy >> with it. So bizarre. > > No, not bizzare at all, quite logic if one thinks about what layer is > put on top of what other layer. > > You have /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3 at the > bottom. On top of that, you get /dev/mapper/sda3_crypt. And on top of > that you get your swap-space. OK. So that actually does explain a lot. In another post on this thread you asked where I got that UUID from. That question fits in well here so I am just going to dump it all here. :-) I just checked a number of my systems with blkid and the UUID's I am using are indeed the physical /dev/sdx# UUID's.. All of the bizarre behavior totally make sense in those layers you described if the LUKS swap UUID is auto generated and different every boot. On the older Wheezy systems I also show a UUID for the LUKS swap device but I am not using that one. I rebooted a host and it did change. I have finally joined two previously disconnected thoughts in my brain and learned something today! :-) But at the same time, I am still not sure as to why systemd.fsck has issues with the UUID of the partition but is OK with the /dev/disk/by-id/pointer. Is this the correct way of doing it? (EG: have I been doing it wrong this whole time by using the physical partitions UUID? Should I update my other not-yet-updated-to-Jessie hosts to use /dev/disk/by-id?) Thanks for clarifying this! I do appreciate it. ~Stack~ signature.asc Description: OpenPGP digital signature
Re: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode..
On Sat 28 Mar 2015 at 14:55:22 -0700, David Christensen wrote: > I did a fresh install of Debian using debian-7.6.0-i386-netinst.iso > today. When I rebooted, I saw: > > GRUB loading.. > Welcome to GRUB! > > error: incompatible license > Entering rescue mode.. > grub rescue> > > I figured that there was something incompatible between the older > ISO and current files. > > > So, I downloaded debian-7.8.0-i386-xfce-CD-1.iso and installed that. > When I rebooted, I saw: > > GRUB loading.. > Welcome to GRUB! > > error: incompatible license > Entering rescue mode.. > grub rescue> > > > Any suggestions? My concept of installing Debian includes putting GRUB in the MBR. You appear to have an inconsistency between the modules in /boot/grub and the version of GRUB in the MBR. The rescue mode of the netinst ISO can be used to reinstall GRUB. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150328233901.gb22...@copernicus.demon.co.uk
Re: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode..
On 03/28/2015 03:24 PM, Lisi Reisz wrote: Try googling the error. Been there, done that. I was hoping this was a known issue. This is the best clue I've found so far: http://marc.info/?l=debian-user&m=133683363210396&w=1 See console session below. Any suggestions? David # grub-install --recheck hd0 /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/sda3_crypt. Check your device.map. Auto-detection of a filesystem of /dev/mapper/sda3_crypt failed. Try with --recheck. If the problem persists please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to # cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/disk/by-id/usb-SanDisk_Ultra_Fit_4C530123140926106290-0:0 # /usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub /usr/sbin/grub-probe: info: `/dev/fd0' looks like a floppy drive, skipping. /usr/sbin/grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd0. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd1. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: scanning hd0 for LVM. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: no LVM signature found. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: scanning hd1 for LVM. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: no LVM signature found. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos3. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos2. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos1. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1,msdos1. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos3. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos2. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos1. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1,msdos1. /usr/sbin/grub-probe: info: the size of hd1 is 253952. /usr/sbin/grub-probe: info: scanning hd0 for LVM. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: no LVM signature found. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: scanning hd0,msdos3 for LVM. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: no LVM signature found. /usr/sbin/grub-probe: info: scanning hd0,msdos2 for LVM. /usr/sbin/grub-probe: info: the size of hd0 is 31266816. /usr/sbin/grub-probe: info: no LVM signature found. /usr/sbin/grub-probe: info: scanning hd0,msdos1
Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?
~Stack~ wrote: > In another post on this thread you asked where I got that UUID from. > That question fits in well here so I am just going to dump it all > here. :-) > I just checked a number of my systems with blkid and the UUID's I am > using are indeed the physical /dev/sdx# UUID's.. All of the bizarre > behavior totally make sense in those layers you described if the LUKS > swap UUID is auto generated and different every boot. If you use a static key and not /dev/urandom you can reuse the swap-space that is already present. But that defeats the purpose of encrypting the swap-space; you _want_ to forget the key and recreate the encryption layer on every boot so that there is no chance of any information leak from previous runs. > But at the same time, I am still not sure as to why systemd.fsck has > issues with the UUID of the partition but is OK with the > /dev/disk/by-id/pointer. UUID=... uses the UUID of the filesystem or swap-space on a partition, _not_ the ID of the partition itself. That is totally different ID. Note that you have /dev/disk/by-id (which is the physical ID of the device, partition, device map or md-RAID-set) while /dev/disk/by-uuid is the UUID of whatever filesystem is on any device. You can only use the physical ones in /etc/crypttab. I guess by using the wrong (UU)ID the automatic dependency solvers of systemd create a deadlock while trying to activate the correct units in the correct order to do what you told it. This then turns into a fine demonstration of computer sciences GIGO principle: Garbage In - Garbage Out. Of course, systemd could be a bit nicer and tell you if there is something totally wrong, but maybe none of the authors has yet stumbled upon this problem because they _know_ it does not work and hence never tried it and never built any safe-guards into systemd to fail in a nicer way. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4bga2r0jj...@mids.svenhartge.de
La verità é cattiva
http://www.anti- aristokratie.blogspot.ch/2015/03/la- verita-e-cattiva.html http://1drv.ms/1BFVzuy
La verità é cattiva
http://www.anti- aristokratie.blogspot.ch/2015/03/la- verita-e-cattiva.html http://1drv.ms/1BFVzuy
Wheezy wifi problems
After figuring out how to get iwlwifi installed and now being able to turn on the transciever, the problem becomes being asked for authentication as in a password or encryption key to connect to the network. I don't remmember setting up a password or key for this.My previous install of wheezy didn't do this. Anyone have an idea how I can get connected? Any pointers appreciated. -- Bob Holtzman A fair fight is the result of poor planning. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150329032743.ga6...@cox.net
Re: Planning a new Debian box!
On Fri, Mar 27, 2015 at 10:41:37PM -1000, Joel Roth wrote: > I found that Partition Wizard[1] Live CD by Minitool, can > handle all of the issues in shrinking a windows partition to > create space for another OS. Thanks for the h/t. Reminds me of Partition Magic from years ago. Boy did I get a lot of miles out of _that_ utility! -- Bob Bernstein -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150329040126.ga16...@sixtiessurvivor.org
Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?
On 03/28/2015 06:45 PM, Sven Hartge wrote: > ~Stack~ wrote: > >> In another post on this thread you asked where I got that UUID from. >> That question fits in well here so I am just going to dump it all >> here. :-) > >> I just checked a number of my systems with blkid and the UUID's I am >> using are indeed the physical /dev/sdx# UUID's.. All of the bizarre >> behavior totally make sense in those layers you described if the LUKS >> swap UUID is auto generated and different every boot. > > If you use a static key and not /dev/urandom you can reuse the > swap-space that is already present. But that defeats the purpose of > encrypting the swap-space; you _want_ to forget the key and recreate the > encryption layer on every boot so that there is no chance of any > information leak from previous runs. > >> But at the same time, I am still not sure as to why systemd.fsck has >> issues with the UUID of the partition but is OK with the >> /dev/disk/by-id/pointer. > > UUID=... uses the UUID of the filesystem or swap-space on a partition, > _not_ the ID of the partition itself. That is totally different ID. > > Note that you have /dev/disk/by-id (which is the physical ID of the > device, partition, device map or md-RAID-set) while /dev/disk/by-uuid is > the UUID of whatever filesystem is on any device. > > You can only use the physical ones in /etc/crypttab. > > I guess by using the wrong (UU)ID the automatic dependency solvers of > systemd create a deadlock while trying to activate the correct units in > the correct order to do what you told it. This then turns into a fine > demonstration of computer sciences GIGO principle: Garbage In - Garbage Out. > > Of course, systemd could be a bit nicer and tell you if there is > something totally wrong, but maybe none of the authors has yet stumbled > upon this problem because they _know_ it does not work and hence never > tried it and never built any safe-guards into systemd to fail in a nicer > way. Thanks for the explanation. I now understand the results of a lot of my experiments today. It makes a lot more sense and I understand they garbage aspect of pointing to the swap file system (which changes) instead of the physical partition for swap. One more question if you don't mind: I understand why the encrypted partition UUID is going to change every time, but the physical partition UUID for my /dev/sda3 shouldn't change though. If they are the same systemd.fsck shouldn't have a problem with the physical partition UUID of /dev/sda3, but yet it does (at least for me). So what is the difference between the UUID pointing to /dev/sda3 and the /dev/disk/by-id pointing to /dev/sda3? Thanks Sven! You have been a great help in me understanding this better! signature.asc Description: OpenPGP digital signature
Re: javascript in iceweasel
On Sat, Mar 28, 2015 at 09:15:03PM +, Brad Rogers wrote: > On Sat, 28 Mar 2015 14:07:10 -0700 > Bob Holtzman wrote: > > Hello Bob, > > >talked about going to Tools -> Options which doesn't exist on my copy > > Found there in Windows, IIRC. In Linux it's Edit menu -> Preferences. > If it's not there (in later versions, it appears not to be) use > about:config and look for javascript.enabled and set it to your choice. > It's a boolean, so clicking will toggle between true and false. Javascript enabled shown as true, however, there are a whole pile of javascript options listed with only a few turned off. Still in the dark. Thanks for the reply. -- Bob Holtzman A fair fight is the result of poor planning. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150329045141.ga7...@cox.net
Re: javascript in iceweasel
On Sat, Mar 28, 2015 at 09:41:16PM +, Liam O'Toole wrote: > On 2015-03-28, Bob Holtzman wrote: > > Running Wheezy 7.8 w/ iceweasel 31.5.3. Some sites won't work, telling > > me I need to install/activate javascript. Not sure how to do this. I > > assume java is loaded because I see some icedtea 6 packages installed. > > No idea how to activate javascript, assuming it's lurking on the HD. > > Searches turned up virtually nothing useful. The few relevant hits > > talked about going to Tools -> Options which doesn't exist on my copy. > > > > Any pointers appreciated.. > > > > Brad's post answers your question. Yes. It just didn't seem to work. > Just FYI, JavaScript is not related > to Java and Icedtea. Those latter are used for running Java applets and > applications from a web browser. It's a common misunderstanding arising > from the similarity in nomenclature. Thanks. I was aware of thatThanks. I was aware of that. -- Bob Holtzman A fair fight is the result of poor planning. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150329045554.gb7...@cox.net
Re: javascript in iceweasel
On 03/29/2015 12:55 AM, Bob Holtzman wrote: On Sat, Mar 28, 2015 at 09:41:16PM +, Liam O'Toole wrote: On 2015-03-28, Bob Holtzman wrote: Running Wheezy 7.8 w/ iceweasel 31.5.3. Some sites won't work, telling me I need to install/activate javascript. Not sure how to do this. I assume java is loaded because I see some icedtea 6 packages installed. No idea how to activate javascript, assuming it's lurking on the HD. Searches turned up virtually nothing useful. The few relevant hits talked about going to Tools -> Options which doesn't exist on my copy. Any pointers appreciated.. Brad's post answers your question. Yes. It just didn't seem to work. Just FYI, JavaScript is not related to Java and Icedtea. Those latter are used for running Java applets and applications from a web browser. It's a common misunderstanding arising from the similarity in nomenclature. Thanks. I was aware of thatThanks. I was aware of that. Which java are you using?? Oracle or IcedTea/Openjdk? There used to be a mozilla java plugin in the repos which should enable everything for you. I'm not finding it. :) Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55178dac.5060...@gmail.com
Re: GRUB loading.. Welcome to GRUB! error: incompatible license Entering rescue mode..
debian-user: I think the problem is that the motherboard/ BIOS (Intel D865GBF, circa 2005) is just too old to use a USB flash drive (SanDisk Ultra Fit 16 GB USB 3.0) as the system drive. When I connect the same drive to a newer motherboard (Intel D945GNT, circa 2009), GRUB is happy. David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55178472.4050...@holgerdanske.com
Re: javascript in iceweasel
On Sat, 28 Mar 2015 21:51:41 -0700 Bob Holtzman wrote: Hello Bob, >Javascript enabled shown as true, however, there are a whole pile of >javascript options listed with only a few turned off. I've not played with those; Not sure what effects it'd have. >Still in the dark. Thanks for the reply. YW. One thought - are you using any sort of ad blocker or other plugin that might be having an effect? Running in safe mode would help eliminate/confirm possibilities. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" You destroyed my confidence, you broke my nerve Nervous Wreck - Radio Stars pgpSqqf7V6TfF.pgp Description: OpenPGP digital signature
NetworkManager & tun/br enigma
Hello, I'm trying to get a NetworkManager-independent bridg up and running to be able to have my firewall manage traffic to/from lxc containers. My '/etc/network/interfaces' looks like this: > auto lo > iface lo inet loopback > > # tun/tap/bridge combo for lxc container networking > auto tun0 > iface tun0 inet manual > tunctl_user root > upip link set tun0 up > down ip link set tun0 down > auto br0 > iface br0 inet static > bridge_ports tun0 > bridge_maxwait0 > bridge_stpoff > address 172.16.0.1 > netmask 255.255.255.0 > dns-searchvirt.local No matter what I do to the > [ifupdown] > managed=true/false parameter in '/etc/NetworkManager/NetworkManager.conf', 'ifconfig' doesn't show me the tun0/br0 interfaces. When I manually call 'service networking re/start', the process gets stuck unresponsively. 'CTRL-C'ing out 'ifconfig' now shows the tun/br interfaces. 'tail /var/log/messages' reports: > IPv6: ADDRCONF(NETDEV_UP): tun0: link is not ready Any hints on what may be wrong and how to proceed? Sincerely, Joh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/mf844o$ra5$1...@ger.gmane.org
