Why isn't `dirmngr` installed by default in Stretch?
Hi! Why isn't the package `dirmngr` installed by default in Stretch? The package is required if you want to add external repositories' GPG keys. Regards, Albin
Re: Libvirt in Stretch?
On 01/04/2017 09:05 PM, Nicholas Geovanis wrote: > See this post from November: > https://lists.debian.org/debian-user/2016/11/msg00518.html > > On Wed, Jan 4, 2017 at 1:58 PM, Ansgar Burchardt <"Ansgar > Burchardt"@43-1.org> wrote: > >> Albin Otterhäll writes: >>> It seems that the package `libvirt-bin` has been deprecated in Stretch >>> (it isn't available via the repositories). I can't find any >>> documentation regarding virtualization using KVM in Stretch. >>> >>> What's the replacement for `libvirt-bin`? >> >> The libvirt-bin package in Debian 8 has: >> >> +--- >> | Package: libvirt-bin >> | Version: 1.2.9-9+deb8u3 >> | [...] >> | Depends: libvirt-daemon-system (>= 1.2.9-9+deb8u3), libvirt-clients (>= >> 1.2.9-9+deb8u3) >> | [...] >> | Description: programs for the libvirt library >> | [...] >> | This is a transitional package. You can safely remove it. >> +--- >> >> So you are probably looking for libvirt-daemon-system and/or >> libvirt-clients. >> >> Ansgar >> >> > Thank you! Didn't see that post. Regards, Albin
Libvirt in Stretch?
Hi! It seems that the package `libvirt-bin` has been deprecated in Stretch (it isn't available via the repositories). I can't find any documentation regarding virtualization using KVM in Stretch. What's the replacement for `libvirt-bin`? Thanks in advance! Regards, Albin Otterhäll
Re: Guidelines for allocating system resources for VMs?
Martin Read: > On 14/05/16 10:05, Albin Otterhäll wrote: >> I want to use virtual machines for my everyday work on my laptop (with a >> Intel Core i5-3320M @ 2.60 GHz * 4 and 16GB RAM), using KVM on Debian as >> my hypervisor. >> >> But I can't find any general guidelines for how much system resources to >> "give" to a VM. How many logical cores? How much RAM? Note that the >> primary OS only should act as a hypervisor. > > How much RAM and how many cores do you think the work in question needs? > > Answer that, and you have the basis for your answer. > > The thing is that I don't know (don't know how to access the necessary information either), and assigning as much as possible would probably be the best solution. I plan in the future buy a GPU and use PCI passthrough to use a VM for gaming, and then I would need to assign as much resources as possible. -- Regards, Albin
Guidelines for allocating system resources for VMs?
I want to use virtual machines for my everyday work on my laptop (with a Intel Core i5-3320M @ 2.60 GHz * 4 and 16GB RAM), using KVM on Debian as my hypervisor. But I can't find any general guidelines for how much system resources to "give" to a VM. How many logical cores? How much RAM? Note that the primary OS only should act as a hypervisor. I will primarily use a Debian VM (i.e. Debian VM on Debian), but I also want to be able to run a Windows 10 VM (Windows VM on Debian). It's not necessary for both VMs to run simultaneously. -- Regards, Albin
Re: Installer crash at the end of installation
On 05/11/2016 07:41 PM, Dan Ritter wrote: On Wed, May 11, 2016 at 07:20:16PM +, Albin Otterhäll wrote: I'm trying to install Debian on a Lenovo Thinkpad T430. This is not the first time I install Debian on this machine, no problems earlier. The problem is that the installer crash at the end of the "[s]elect and install packages" step. All the packages have been downloaded and most of them are installed; the installer crash about 85 percent into the installation. I've tried to redo the step and the whole installation, nothing helps. I've verified the ISO with GPG and SHA512sums and done an integrity check of the USB disk. This is the last part of the error log (/var/log/syslog): Your problem is the disk, the cable, or the USB port. kernel: [...] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK kernel: [...] sd 0:0:0:0: [sda] CDB: kernel: [...] Write(10): 2a 00 00 17 c0 00 00 00 08 00 kernel: [...] EXT4-fs error (device dm-1): ext4_journal_check_start:56: Detected aborted journal This. Which led to the kernel remounting it read-only: '/usr/bin/scrollkeeper-rebuilddb.distrib': Read-only file system and this will bite you later: lilo-installer: LILO not usable on EFI PCs without BIOS compatibility; use grub-efi The answers I got on IRC suggests that it was something wrong with my SSD. So I tested it with all the tools I know. First I run an extended self-test with S.M.A.R.T. tools. Everything comes up OK. No fails. I when run badblocks: # badblocks -vsw /dev/sda Checking for bad blocks in read-write mode From block 0 to 234431063 [---] Pass completed, 0 bad blocks found. (0/0/0 errors) It's suggested to me to test by write random data to a file in a similar environment to "emulate" the debian-installer. This is what I did: 1. Create new GPT partition table 2. Create new partition labeled for LVM with recommended start and end (+1MiB to last block) 3. Encrypt the partition with LUKS. 4. Create physical volume, volume group and a logical volume spanning the whole partition. 4. Create EXT4 file system on logical volume. 6. Create file 'foo' and write to it with: # dd bs=4M if=/dev/urandom of=foo status=progress 236059623424 bytes (236 GB, 220 GiB) copied, 13192.2 s, 17.9 MB/s dd: error writing 'foo': No space left on device 56284+0 records in 56283+0 records out 236072116224 bytes (236 GB, 220 GiB) copied, 13192.8 s, 17.9 MB/s Have you any suggestions on what I can do? Return the disk, get a new one. This one is defective. -dsr- Yeah, it certenly seems so. Thanks for your time! Regards, Albin
Installer crash at the end of installation
beled for LVM with recommended start and end (+1MiB to last block) 3. Encrypt the partition with LUKS. 4. Create physical volume, volume group and a logical volume spanning the whole partition. 4. Create EXT4 file system on logical volume. 6. Create file 'foo' and write to it with: # dd bs=4M if=/dev/urandom of=foo status=progress > 236059623424 bytes (236 GB, 220 GiB) copied, 13192.2 s, 17.9 MB/s > dd: error writing 'foo': No space left on device > 56284+0 records in > 56283+0 records out > 236072116224 bytes (236 GB, 220 GiB) copied, 13192.8 s, 17.9 MB/s Have you any suggestions on what I can do? Thanks in advance! Regards, Albin Otterhäll
Installer crash at the end of installation
onment to "emulate" the debian-installer. This is what I did: 1. Create new GPT partition table 2. Create new partition labeled for LVM with recommended start and end (+1MiB to last block) 3. Encrypt the partition with LUKS. 4. Create physical volume, volume group and a logical volume spanning the whole partition. 4. Create EXT4 file system on logical volume. 6. Create file 'foo' and write to it with: # dd bs=4M if=/dev/urandom of=foo status=progress > 236059623424 bytes (236 GB, 220 GiB) copied, 13192.2 s, 17.9 MB/s > dd: error writing 'foo': No space left on device > 56284+0 records in > 56283+0 records out > 236072116224 bytes (236 GB, 220 GiB) copied, 13192.8 s, 17.9 MB/s Have you any suggestions on what I can do? Thanks in advance! Regards, Albin Otterhäll
Re: How to clear notifications?
On 03/03/2016 02:43 PM, Albin Otterhäll wrote: > How can I clear the notifications in Gnome? I still want them, but be > able to clear them. I've tried to restart gnome shell (Alt+F2, input > "r", and press enter), but they are still there. The notifications comes > from the clock app. Seems that I only had to move the mouse to the bottom of the screen. It seemed that it didn't work at first, but it does.
How to clear notifications?
How can I clear the notifications in Gnome? I still want them, but be able to clear them. I've tried to restart gnome shell (Alt+F2, input "r", and press enter), but they are still there. The notifications comes from the clock app.
Re: Why so big EFI partition?
On 03/03/2016 12:55 AM, Steve McIntyre wrote: > Basically, there are lots of > reported (real and potential) issues with smaller sizes, so we've > picked a larger size by default for the guided partitioning. I wasn't aware of the potential problems. Funny that Ubuntu's documentation still recommends 200MiB if at least 512MiB is recommended. Btw, can the Debian installer handle *iB units? When I installed it only mentioned "MB" and "GB".
Re: Why so big EFI partition?
On 03/02/2016 11:57 PM, SamuelOPH wrote: > They are on a "default" use case, but if you're using systemd-boot you are > responsible for configuring a nice way to keep only the last kernel images > on the ESP (it's not hard to do) and automagically update it. > > If you're using the Debian's default Grub2, you should be using less than > 1MiB. Thanks for your answers! But I don't yet understand why someone would use systemd-boot instead of the default boot manager instead of the default one? I'm reading the Arch Wiki article[1], but it doesn't discuss _why_ you would like to use it. [1] https://wiki.archlinux.org/index.php/Systemd-boot
Re: Why so big EFI partition?
On 03/02/2016 11:37 PM, SamuelOPH wrote: > I believe you mean ESP (EFI System Partition) Haha, you are correct. :) > [...] this limit will grow with time with initramfs and vmlinuz getting bigger [---] Doesn't old kernel images get removed after some time?
Re: Why so big EFI partition?
On 03/02/2016 11:24 PM, SamuelOPH wrote: > 20MB for storing both files for one kernel version So a EPA partition with 128MiB is more than enough?
Re: Why so big EFI partition?
On 03/02/2016 11:05 PM, SamuelOPH wrote: > [---] if you wanna use systemd-boot your kernel and initramfs [---] What does systemd-boot and initramfs do? And how much space does they take?
Re: Why so big EFI partition?
On 03/02/2016 07:42 PM, Pascal Hambourg wrote: > There is no ratio. 500 MB is the generally recommended size for the EFI > system partition even though the Debian GRUB EFI bootloader needs much > less, and 250 MB for /boot is one of the questionable arbitrary choices > that the guided mode does for you. If you're not happy with these > choices feel free to use the manual mode instead. Why is it generally recommended? Does other distributions store other things in the EFI partition that Debian doesn't?
Re: Current stability of Debian testing?
On 03/02/2016 02:45 PM, Sven Hartge wrote: > People just doing a blind "apt dist-upgrade" every day without knowing > what happens, why it happens and how to fix the emerging problems will > have a very bad time using Testing, because there will be a day where an > innocent "apt dist-upgrade" removes half their packages. Doesn't it exist any "extensions" to apt that checks for reported bugs? I'm aware that I've to check for eventual bugs if I'm going with testing and not doing any blind aptitude dist-upgrade. Btw, where is the best place to check for problems? I subscribe to the testing mailing list, but it doesn't have much activity. Is the problems so few, or is the problems discussed elsewhere?
Why so big EFI partition?
When doing a guided partition when installing debian, the debian-installer creates a EFI (/boot/efi) partition with approximately 500MB, and a /boot partition with around 250MB. Why this weird ratio between them? To my knowledge only the bootloader(s) in located on the /boot/efi partition, and the kernel images on /boot. Canonical says that 100MiB is minimum for Ubuntu's EFI partition, and 200MiB is recommended. And on a related note: Does debian-installer support *iB units? Thanks in advance! Regards, Albin
Re: Current stability of Debian testing?
On 03/02/2016 01:45 PM, Michael wrote: > Ive been using it for the last few months, and have had no major issues > that where not of my own causing.. :) Good! According to the Debian wiki it's recommended to do a "minimal" installation. I assume it's just debian with all the "extra" (Gnome and print-server) in the debian-installer unchecked? If so, how would I go about to install whose later after the "upgrade" from stable to testing after editing /etc/apt/sources.list?
Current stability of Debian testing?
What is the current stability of Debian testing (Stretch)? I know it had quite a lot of stability issues some months ago, and wondering if they are resolved yet.
Re: XFS on root
On 02/27/2016 06:16 PM, Adam Wilson wrote: > [---] use ext2 for /boot [---] Why use Ext2 and not Ext 3 or 4 for /boot?
Re: Where can I find the bugs for a package in stable?
On 03/01/2016 08:57 AM, to...@tuxteam.de wrote: > Have a look at: > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=iceweasel;dist=stable > > Now: how did I find out? Well, I first went to > > https://bugs.debian.org/ > > entered iceweasel and noticed the ";dist=unstable" at the end. Yeah, > looking at the URL is considered arcane these days [1]. Then I > searched for Iceweasel and noticed this ";dist=unstable" at the end > of the resulting URL. "Oh, lookee" I thought, and tried and changed > it to ";dist=stable" [---] Yeah, I found the page with the same method. Thought of modifying the URL after I saw it in the replies. Thanks for your time! :)
Re: Where can I find the bugs for a package in stable?
On 03/01/2016 08:52 AM, Shin Ice wrote: > Related to Iceweasel: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=Iceweasel I did find that page before I asked my question, but it's the buglist for unstable. But when I checked the URL i saw that you could change "unstable" to "stable" and access the right page. Thanks for your time!
Where can I find the bugs for a package in stable?
Iceweasel has crashed two times in a day, and I would like to report it (or read the bug report if it's already reported). But I can only find the bug-list for Sid. Where to find the currently active bugs for stable?
