Upgrading guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel
HI Our system runs with Debian 6 squeeze (2.6.32) Kernel with N2600 hardware. I know the version is old. Due to business implication we are not able to update it. Recently, we tried connecting multiple monitors (CRT and HDMI) and we had no luck in making this display controllable. On goggling, it was found some graphic driver(cedarview drivers) issues with kernel. I am pretty new Linux kernel stuffs and applying upgrades.Request some guidance on the same. -- Regards Venkat.S -- 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/551a4b8a.4010...@vortexindia.co.in
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
"Instead we will soon have GNU/systemd, [a] much simpler, unified platform. GNU/systemd will be a better target for third-party developers and easier to support." What? Foolish guys... Reading behind the words - no cooperation, discussion and respect, we will take over! Completely wrong... Would like to read official answer and plans from Debian project. With some clarification of possible impact on security and Debian itself (who will audit "their" kernel?). On Mon, Mar 30, 2015 at 6:00 PM, Patrick Bartek wrote: > On Mon, 30 Mar 2015, Renaud (Ron) OLGIATI wrote: > > > http://distrowatch.com/weekly.php?issue=20150330#community > > > > Or is it serious ? > > I'm not laughing. > > B > > > -- > 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/20150330090013.3f77f...@debian7.boseck208.net > >
jessie: newly add user cannot log into LXDE
I downloaded and installed debian testing （jessie rc2 netinstall） today. Then I tried to add user manually (useradd/passwd) or through the Preferences/Users and Groups GUI. In both cases the newly created user cannot log into the LXDE session. Investigation showed that user home directory was not automatically created with either methods or efforts trying to change user to "Desktop" user in the Preferences/Users and Groups GUI. As a result lightdm failed to save ~/.dmrc file and ended session. It logged the error but didn't display. Manually creating user home ended the problem. I'd like to file a bug against lightdm, the Preferences/Users and Groups GUI and probably the useradd for this usability issue. I don't recall encountering this with many years experiences with different distros and desktops. It is probably my first time trying with LXDE though unless I used before without recognizing. How do you suggest if to file this bug? I'm fine if someone in devel team can help filing it. Thanks. Regards, Liyu
Re: Upgrading guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel
On Tue, 31 Mar 2015 12:53:54 +0530 venkat wrote: > HI > > Our system runs with Debian 6 squeeze (2.6.32) Kernel with N2600 > hardware. I know the version is old. Due to business implication we > are not able to update it. > Recently, we tried connecting multiple monitors (CRT and HDMI) and we > had no luck in making this display controllable. > On goggling, it was found some graphic driver(cedarview drivers) > issues with kernel. > I am pretty new Linux kernel stuffs and applying upgrades.Request > some guidance on the same. You could start here: https://wiki.debian.org/DebianUpgrade And then if you have specific questions that you can't find answers to online, ask here. If you need to upgrade, but can't for business reasons, then you have a bigger problem. You could see if there are any packages available in backports that could help you, but that's about the only suggestion I have if you need a newer graphics driver. Other than that, you would probably have to upgrade (or build what you need from source, which I wouldn't recommend). Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpZEdpgydcz5.pgp Description: OpenPGP digital signature
Re: jessie: newly add user cannot log into LXDE
On Tue, 31 Mar 2015 00:16:11 -0700 Liyu L wrote: > I downloaded and installed debian testing （jessie rc2 netinstall） > today. Then I tried to add user manually (useradd/passwd) or through > the Preferences/Users and Groups GUI. In both cases the newly created > user cannot log into the LXDE session. > > Investigation showed that user home directory was not automatically > created with either methods or efforts trying to change user to I can¨t help you with the graphical method, as I've never used it, but useradd doesn't create the home directory unless you specifically tell it to. From the man page: useradd is a low level utility for adding users. On Debian, administrators should usually use adduser(8) instead. -m, --create-home Create the user's home directory if it does not exist. The files and directories contained in the skeleton directory (which can be defined with the -k option) will be copied to the home directory. By default, if this option is not specified and CREATE_HOME is not enabled, no home directories are created. So no bug report should be necessary for useradd, unless you did specify "-m" and it didn't create the home directory - this is expected behaviour. adduser, on the other hand, *does* create it by default, and that may be confusing since the names are so similar. Regards, Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpOgrTRcHvss.pgp Description: OpenPGP digital signature
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
On Tuesday 31 March 2015 08:21:12 Peter Viskup wrote: > "Instead we will soon have GNU/systemd, [a] much simpler, unified platform. > GNU/systemd will be a better target for third-party developers and easier > to support." > What? Foolish guys... Reading behind the words - no cooperation, discussion > and respect, we will take over! Completely wrong... > > Would like to read official answer and plans from Debian project. With some > clarification of possible impact on security and Debian itself (who will > audit "their" kernel?). You're not going to get it. The whole thing was an April Fool joke released early. It will live in memory like the spaghetti trees. http://en.wikipedia.org/wiki/Spaghetti-tree_hoax 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/201503310925.06451.lisi.re...@gmail.com
Re: Upgrading guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel
Hi Peter Thanks for the response, I really understand the need for the upgrade. We are definitely working on it.It would definitely take some time. To handle current situation, I wanted to somehow use 2.6.32 kernel with newest version of cedarview driver. If you show me a trigger point where to start this process it would be great. Regards Venkat.S On 31-03-2015 13:13, Petter Adsen wrote: On Tue, 31 Mar 2015 12:53:54 +0530 venkat wrote: HI Our system runs with Debian 6 squeeze (2.6.32) Kernel with N2600 hardware. I know the version is old. Due to business implication we are not able to update it. Recently, we tried connecting multiple monitors (CRT and HDMI) and we had no luck in making this display controllable. On goggling, it was found some graphic driver(cedarview drivers) issues with kernel. I am pretty new Linux kernel stuffs and applying upgrades.Request some guidance on the same. You could start here: https://wiki.debian.org/DebianUpgrade And then if you have specific questions that you can't find answers to online, ask here. If you need to upgrade, but can't for business reasons, then you have a bigger problem. You could see if there are any packages available in backports that could help you, but that's about the only suggestion I have if you need a newer graphics driver. Other than that, you would probably have to upgrade (or build what you need from source, which I wouldn't recommend). Petter -- Regards Venkat.S -- 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/551a7f7d.8030...@vortexindia.co.in
Re: Upgrading guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel
On Tue, 31 Mar 2015 16:35:33 +0530 venkat wrote: > Hi Peter > > Thanks for the response, I really understand the need for the > upgrade. We are definitely working on it.It would definitely take > some time. To handle current situation, I wanted to somehow use > 2.6.32 kernel with newest version of cedarview driver. > If you show me a trigger point where to start this process it would > be great. I did a little searching, and from what I find, I don't think you can without upgrading. The problem is not only the old kernel, but old versions of X and the necessary libraries. The *only* other option you would have, would be to build everything you need from source, and I would *not* recommend you try that, as it could get you into a world of trouble. If this is a machine you rely on for business, then you want a stable base. Upgrading core libraries and other components would be such an intrusive procedure that you are very likely to bring the whole system down. I'm sorry, but I think you are out of luck until you are able to upgrade the entire distribution. Take note that I haven't done any extensive research into this, I just did a couple of quick searches, but what I read makes me pretty sure that an upgrade is the best way forward for you. Petter PS: Please don't top post. -- "I'm ionized" "Are you sure?" "I'm positive." pgphOh0KrZ4wv.pgp Description: OpenPGP digital signature
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
On Tue, 31 Mar 2015 09:21:12 +0200 Peter Viskup wrote: > "Instead we will soon have GNU/systemd, [a] much simpler, unified platform. > GNU/systemd will be a better target for third-party developers and easier > to support." > What? Foolish guys... Reading behind the words - no cooperation, discussion > and respect, we will take over! Completely wrong... Not to mention so much easier for malware devs... Cheers, Ron. -- Toute loi qui viole les droits imprescriptibles de l'homme, est essentiellement injuste et tyrannique; elle n'est point une loi. -- Maximilien Robespierre -- http://www.olgiati-in-paraguay.org -- -- 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/20150331080217.44275...@ron.cerrocora.org
Webcam device `not found'
Hi all. On my Acer Aspire One netbook, when I launch cheese, it complain that the device is `not found'. Googling around I've found many similar issues but no solution. Please help whoever can. I have Sid. Thanks, Rodolfo -- 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/87619hjqa8@gmail.com
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
On Tuesday 31 March 2015 13:02:17 Renaud OLGIATI wrote: > On Tue, 31 Mar 2015 09:21:12 +0200 > > Peter Viskup wrote: > > "Instead we will soon have GNU/systemd, [a] much simpler, unified > > platform. GNU/systemd will be a better target for third-party developers > > and easier to support." > > What? Foolish guys... Reading behind the words - no cooperation, > > discussion and respect, we will take over! Completely wrong... > > Not to mention so much easier for malware devs... It's not real. Sheesh. http://en.wikipedia.org/wiki/Spaghetti-tree_hoax Spaghetti doesn't grow on trees. systemd is not, so far at any rate, taking over any part of teh kernel. When spaghetti starts to grow on trees, and with genetic modification, who knows, then perhaps systend will fork teh kernel. People believed the spaghetti tree hoax, you know. (I remember it!!) 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/201503311329.29128.lisi.re...@gmail.com
Re: Upgrading guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel
On 31-03-2015 17:01, Petter Adsen wrote:
On Tue, 31 Mar 2015 16:35:33 +0530
venkat wrote:
Hi Peter
Thanks for the response, I really understand the need for the
upgrade. We are definitely working on it.It would definitely take
some time. To handle current situation, I wanted to somehow use
2.6.32 kernel with newest version of cedarview driver.
If you show me a trigger point where to start this process it would
be great.
I did a little searching, and from what I find, I don't think you can
without upgrading. The problem is not only the old kernel, but old
versions of X and the necessary libraries. The *only* other option you
would have, would be to build everything you need from source, and I
would *not* recommend you try that, as it could get you into a world of
trouble.
If this is a machine you rely on for business, then you want a stable
base. Upgrading core libraries and other components would be such an
intrusive procedure that you are very likely to bring the whole system
down.
I'm sorry, but I think you are out of luck until you are able to
upgrade the entire distribution. Take note that I haven't done any
extensive research into this, I just did a couple of quick searches,
but what I read makes me pretty sure that an upgrade is the best way
forward for you.
Petter
PS: Please don't top post.
Thanks for pointing. This I am very new to this sort of posting
environment. Will improve.
Thanks petter,
The explanation is pretty clear now. I am able to visualize the effect
now and we will immediately start working on this process
However, I just want to explain the the requirement which i am working
on. It would be great if you help me with some pointers.
Primary intent : To control connected HDMI and CRT monitors individually.
We use VESA as display driver for connected display(Single display).
Now, we are trying to extend and use dual display as said (HDMI and CRT).
We configured it using BIOS and see the display output in connected
screen (HDMI and CRT).
Interestingly, we notice that XRANDR does not reflect any info on
connected devices. Is updating kernel the only way to solve this?? or is
there some configuration error on my side.
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
800x600 75.0*
"grub.cfg" -- http://pastebin.com/Lqidputz
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 9b5e2b33-b876-4f5c-9a61-0c685c403a6d
echo'Loading Linux 2.6.32-5-686 ...'
linux/boot/vmlinuz-2.6.32-5-686 root=/dev/sda1 nomodeset
echo'Loading initial ramdisk ...'
initrd/boot/initrd.img-2.6.32-5-686
}
### END /etc/grub.d/10_linux ###
"xorg.conf" -- http://pastebin.com/g1MFsdWE
Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # []
#Option "DefaultRefresh" # []
#Option "ModeSetClearScreen" # []
Identifier "Card0"
Driver "vesa"
VendorName "Intel Corporation"
BoardName "Cedarview Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
--
Regards
Venkat.S
--
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/551a9e80.5080...@vortexindia.co.in
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
Reading Wikipedia- it says systemd was chosen as default on Jessie after discussion over these mailing lists... Is this wrong? > On Mar 31, 2015, at 04:25, Lisi Reisz wrote: > >> On Tuesday 31 March 2015 08:21:12 Peter Viskup wrote: >> "Instead we will soon have GNU/systemd, [a] much simpler, unified platform. >> GNU/systemd will be a better target for third-party developers and easier >> to support." >> What? Foolish guys... Reading behind the words - no cooperation, discussion >> and respect, we will take over! Completely wrong... >> >> Would like to read official answer and plans from Debian project. With some >> clarification of possible impact on security and Debian itself (who will >> audit "their" kernel?). > > You're not going to get it. The whole thing was an April Fool joke released > early. It will live in memory like the spaghetti trees. > > http://en.wikipedia.org/wiki/Spaghetti-tree_hoax > > 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/201503310925.06451.lisi.re...@gmail.com > -- 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/0a44ad7d-4ce5-4c5e-ba4d-ef96941c3...@gmail.com
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
argh :-) this will definitely be one of the best for long time :-D On Tue, Mar 31, 2015 at 10:25 AM, Lisi Reisz wrote: > On Tuesday 31 March 2015 08:21:12 Peter Viskup wrote: > > "Instead we will soon have GNU/systemd, [a] much simpler, unified > platform. > > GNU/systemd will be a better target for third-party developers and easier > > to support." > > What? Foolish guys... Reading behind the words - no cooperation, > discussion > > and respect, we will take over! Completely wrong... > > > > Would like to read official answer and plans from Debian project. With > some > > clarification of possible impact on security and Debian itself (who will > > audit "their" kernel?). > > You're not going to get it. The whole thing was an April Fool joke > released > early. It will live in memory like the spaghetti trees. > > http://en.wikipedia.org/wiki/Spaghetti-tree_hoax > > 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/201503310925.06451.lisi.re...@gmail.com > >
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
On Tue, Mar 31, 2015 at 11:07:57AM -0400, bjf...@gmail.com wrote: > Reading Wikipedia- it says systemd was chosen as default on Jessie after > discussion over these mailing lists... > > Is this wrong? No. You can see some of the discussion here: https://bugs.debian.org/727708. You can probably find more deliberation on the Debian Committee mailing list at https://lists.debian.org/debian-ctte/ > > > > On Mar 31, 2015, at 04:25, Lisi Reisz wrote: > > > >> On Tuesday 31 March 2015 08:21:12 Peter Viskup wrote: > >> "Instead we will soon have GNU/systemd, [a] much simpler, unified platform. > >> GNU/systemd will be a better target for third-party developers and easier > >> to support." > >> What? Foolish guys... Reading behind the words - no cooperation, discussion > >> and respect, we will take over! Completely wrong... > >> > >> Would like to read official answer and plans from Debian project. With some > >> clarification of possible impact on security and Debian itself (who will > >> audit "their" kernel?). > > > > You're not going to get it. The whole thing was an April Fool joke > > released > > early. It will live in memory like the spaghetti trees. > > > > http://en.wikipedia.org/wiki/Spaghetti-tree_hoax > > > > 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/201503310925.06451.lisi.re...@gmail.com > > > > > -- > 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/0a44ad7d-4ce5-4c5e-ba4d-ef96941c3...@gmail.com > signature.asc Description: Digital signature
e2fsck.conf and ssh_known_hosts: where?
e2fsck.conf: While attempting to debug a flaky HDD under Jessie, I had occasion to inspect the conf file /etc/e2fsck.conf, and found that it doesn't exist on any of my computers. But the man e2fsck mentions file e2fsck.conf and man e2fsck.conf states that the default location is /etc/e2fsck.conf . Has support for site specific configuration been abandoned? Or where is it kept? (open)ssh-known-hosts: While searching in /var to see if I could find e2fsck.conf without asking I found an empty directory, /var/cache/openssh-known-hosts . The Debian wiki has an article about how to use ssh-keyscan to build a small database of known hosts for use on a LAN. The article says the file (not directory) of known hosts should placed in /etc/ssh. Is Debian's plan to move to using /var for a known-hosts DB? or is the empty directory just some cruft? I think a directory is a better way than a file, because it is easier to make atomic changes in directory structure than adding/removing individual lines in a file. Both /var and /etc are OK as a location, for me. Does the software that implements known-host checking at ssh-login-time look in both places? Does it look for both names (hyphens vs. underscores)? Kind regards, -- 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/20150331160944.gb20...@big.lan.gnu
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
On Tuesday 31 March 2015 16:07:57 bjf...@gmail.com wrote: > Reading Wikipedia- it says systemd was chosen as default on Jessie after > discussion over these mailing lists... > > Is this wrong? No, it's right. It's all this nonsense about systemd forking the kernel that is rubbish. It was an April Fool "joke". 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/201503311701.23692.lisi.re...@gmail.com
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
On 31/03/15 14:29, Lisi Reisz wrote: > > People believed the spaghetti tree hoax, you know. (I remember it!!) > Do you remember the (much later) san-seriffe hoax? http://en.wikipedia.org/wiki/San_Serriffe -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France | -- 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/551ac7f7.5090...@vanderhoff.org
installing debian
i downloaded debian 7.8.0 binary 3 iso image, which was 4.7GB, i wrote it on a dvd so taht i can install on my machine, but it cannot be detected as bootable, help, how can i install on where have i gone wrong. thanks
Re: installing debian
On Tue 31 Mar 2015 at 20:06:27 +0300, Vincent Omondi wrote: > i downloaded debian 7.8.0 binary 3 iso image, which was 4.7GB, i wrote it > on a dvd so taht i can install on my machine, but it cannot be detected as > bootable, help, how can i install on where have i gone wrong. thanks The installation system is only on the first DVD and CD images. -- 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/31032015182743.1428399c3...@desktop.copernicus.demon.co.uk
Re: installing debian
On Tue, 31 Mar 2015 20:06:27 +0300 Vincent Omondi wrote: > i downloaded debian 7.8.0 binary 3 iso image, which was 4.7GB, i > wrote it on a dvd so taht i can install on my machine, but it cannot > be detected as bootable, help, how can i install on where have i gone > wrong. thanks You need to burn it explicitly as an ISO image, not save it as a file, which is normally what drag-and-drop will do. Pretty much all CD/DVD burning software will do this, but it is not a common task for most computer users so it may not be easy to find it among the options. Depending on the configuration of your present OS, double-clicking on the saved .iso file may open the burning software in the correct mode. Keep the disc you made already as a backup of the .iso file, in case you need to do this again. -- Joe -- 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/20150331183753.5daaf...@jresid.jretrading.com
Re: e2fsck.conf and ssh_known_hosts: where?
On 2015-03-31 18:09 +0200, Paul E Condon wrote: > e2fsck.conf: > > While attempting to debug a flaky HDD under Jessie, I had occasion to > inspect the conf file /etc/e2fsck.conf, and found that it doesn't > exist on any of my computers. That file is not shipped in any current version of the e2fsprogs package, although it has been at some point in the distant past. On my system it is listed as an obsolete conffile, and its timestamp indicates it was last modified in 2007. > But the man e2fsck mentions file > e2fsck.conf and man e2fsck.conf states that the default location is > /etc/e2fsck.conf . Has support for site specific configuration been > abandoned? Or where is it kept? If you create /etc/e2fsck.conf, e2fsck will read it. Cheers, Sven -- 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/87iodhawur@turtle.gmx.de
Re: installing debian
My download was 3 seperate ISOs? That I burned to DVDs, It worked perfict Tim Bester From: Joe To: debian-user@lists.debian.org Sent: Tuesday, March 31, 2015 1:37 PM Subject: Re: installing debian On Tue, 31 Mar 2015 20:06:27 +0300 Vincent Omondi wrote: > i downloaded debian 7.8.0 binary 3 iso image, which was 4.7GB, i > wrote it on a dvd so taht i can install on my machine, but it cannot > be detected as bootable, help, how can i install on where have i gone > wrong. thanks You need to burn it explicitly as an ISO image, not save it as a file, which is normally what drag-and-drop will do. Pretty much all CD/DVD burning software will do this, but it is not a common task for most computer users so it may not be easy to find it among the options. Depending on the configuration of your present OS, double-clicking on the saved .iso file may open the burning software in the correct mode. Keep the disc you made already as a backup of the .iso file, in case you need to do this again. -- Joe -- 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/20150331183753.5daaf...@jresid.jretrading.com
Re: e2fsck.conf and ssh_known_hosts: where?
i am using ubuntu 14.04.1, i downloaded the image on 29th march 2015, from the torrent links provided by debian.org website... On Tue, Mar 31, 2015 at 8:41 PM, Sven Joachim wrote: > On 2015-03-31 18:09 +0200, Paul E Condon wrote: > > > e2fsck.conf: > > > > While attempting to debug a flaky HDD under Jessie, I had occasion to > > inspect the conf file /etc/e2fsck.conf, and found that it doesn't > > exist on any of my computers. > > That file is not shipped in any current version of the e2fsprogs package, > although it has been at some point in the distant past. On my system it > is listed as an obsolete conffile, and its timestamp indicates it was > last modified in 2007. > > > But the man e2fsck mentions file > > e2fsck.conf and man e2fsck.conf states that the default location is > > /etc/e2fsck.conf . Has support for site specific configuration been > > abandoned? Or where is it kept? > > If you create /etc/e2fsck.conf, e2fsck will read it. > > Cheers, >Sven > > > -- > 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/87iodhawur@turtle.gmx.de > >
Re: temporarily disable shutdown
Am 29.03.2015 um 17:35 schrieb Michael Biebl: > Am 29.03.2015 um 11:42 schrieb Matthias Bodenbinder: >> Am 28.03.2015 um 18:51 schrieb Michael Biebl: >>> You can run something like >>> >>> systemd-inhibit --what=shutdown --mode=block /bin/sleep 3600 >>> >>> to block shutdown for 1h. >> >> This does NOT work. I tested it with debian testing. > > Are you sure you are using systemd as PID 1? PID 1 is /sbin/init with lrwxrwxrwx 1 root root 20 Feb 13 12:22 /sbin/init -> /lib/systemd/systemd All my tests where with local root: KDE+konsole, as regular user. Either executing "poweroff" via "su -" in the konsole or clicking shutdown button in KDE. Example: In konsole #1: su - systemd-inhibit --what="idle:sleep:shutdown" --mode=block sleep 3600 In konsole #2: su - poweroff The computer is just powered off. 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/mfenu3$qqf$1...@ger.gmane.org
Jessie: NIS breaks network ??
Dear Srs, I'm preparing a new jessie box (test system, preparing for deploying as soon as it gets into stable). Installed the base system, with kde and gnome, and included a small script in /etc/NetworkManager/dispatcher.d to set hostname and hosts files with info from DHCP. Worked nicely. Installed ntp, ntpdate, tcsh and autofs. There were a few missing NFS mounts, since mount info should come from NIS, but everything still worked nicely. So, I installed NIS, and except for a small delay everything was still ok. ypwhich returned one of NIS servers (it took about two seconds, but succeeded). Restarted autofs, and all filesystems came up nicely. System was fast and responsive. Then, I rebooted the box, and now It won't bring eth0 up anymore. Tried removing NIS, and networking got back to normal. Could not understand the situation, so far. Any hints? Best regards, João
Specijalna ponuda za otkup automobila
Poštovani, Želeli bi smo da Vas obavestimo da vršimo otkup automobila, kamiona, plovila ... u Srbiji po najboljim cenama, a što je najvažnije isplaćujemo odmah! Pogledajte ovaj email kako biste saznali o specijalnim pogodnostima koje pružamo firmama i pojedincima. Vršimo otkup polovih, havarisanih i slupanih automobila. Više informacija možete dobiti na sajtu http://otkupautomobila.rs http://otkupautomobila.rs i na http://otkupautomobila.rs/beograd http://otkupautomobila.rs/beograd/ Srdačan pozdrav, Otkup Automobila Ako niste želeli da primite ovaj mejl molimo kliknite ovde. http://www.email.beohosting.com/index.php/lists/ja3700f47n29b/unsubscribe/ef352tlex8626/kl052xfsm8d4e
Re: temporarily disable shutdown
Quoting Matthias Bodenbinder (matth...@bodenbinder.de): > Am 29.03.2015 um 17:35 schrieb Michael Biebl: > > Am 29.03.2015 um 11:42 schrieb Matthias Bodenbinder: > >> Am 28.03.2015 um 18:51 schrieb Michael Biebl: > >>> You can run something like > >>> > >>> systemd-inhibit --what=shutdown --mode=block /bin/sleep 3600 > >>> > >>> to block shutdown for 1h. > >> > >> This does NOT work. I tested it with debian testing. > > > > Are you sure you are using systemd as PID 1? > > PID 1 is /sbin/init > with > lrwxrwxrwx 1 root root 20 Feb 13 12:22 /sbin/init -> /lib/systemd/systemd > > All my tests where with local root: KDE+konsole, as regular user. Either > executing "poweroff" via "su -" in the konsole or clicking shutdown button in > KDE. > > Example: > > In konsole #1: > su - > systemd-inhibit --what="idle:sleep:shutdown" --mode=block sleep 3600 > > In konsole #2: > su - > poweroff > > The computer is just powered off. Not using KDE myself, I can only comment on the CLI (and thanks for the clear posting). I think you need to understand that root privilege overrides any inhibitions, as one might expect. This is what works for me: jessiebox ~$ /bin/su - Password: jessiebox ~# systemd-inhibit --what="idle:sleep:shutdown" --mode=block sleep 3600 and moving to a VC or another xterm: jessiebox ~$ /sbin/poweroff Operation inhibited by "sleep 3600" (PID 28227 "systemd-inhibit", user root), reason is "Unknown reason". Please retry operation after closing inhibitors and logging out other users. Alternatively, ignore inhibitors and users with 'systemctl poweroff -i'. jessiebox ~$ jessiebox ~$ systemctl poweroff -i AUTHENTICATING FOR org.freedesktop.login1.power-off-ignore-inhibit === Authentication is required for powering off the system while an application asked to inhibit it. Authenticating as: root Password: [password not typed] Failed to execute operation: Connection timed out Failed to start poweroff.target: Access denied polkit-agent-helper-1: pam_authenticate failed: Authentication failure jessiebox ~$ Now that would have worked if I had typed the password. jessiebox ~$ systemd-inhibit --list Who: /bin/sleep 3600 (UID 0/root, PID 4051/systemd-inhibit) What: shutdown Why: Unknown reason Mode: block 1 inhibitors listed. jessiebox ~$ AIUI it's up to root to check for inhibitions. I also get te impression that mollyguard is really just for trying to prevent you accidently closing down a machine you've ssh'd to because you think you're still local. (I prevent this by using differently coloured prompt strings.) I don't know how well it's integrated with systemd. 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/20150331194555.ga12...@alum.home
Re: Re: how to debug this fuse problem
Hi
I met the same error message today and got it fixed in following way:
root@myhost01 grub]# dmesg |grep fuse
[5174104.384024] fuse: disagrees about version of symbol iov_iter_get_pages
[5174104.384027] fuse: Unknown symbol iov_iter_get_pages (err -22)
[5174118.853162] fuse: disagrees about version of symbol iov_iter_get_pages
[5174118.853166] fuse: Unknown symbol iov_iter_get_pages (err -22)
...
[root@myhost01 grub]# modprobe fuse
ERROR: could not insert 'fuse': Invalid argument
[root@myhost01 grub]# uname -r
3.16.0-0.bpo.4-amd64
[root@myhost01 grub]# dpkg-query -W 'linux-image-3.16.0-0.bpo.4-amd64'
linux-image-3.16.0-0.bpo.4-amd643.16.7-ckt4-3~bpo70+1
The following command shows that we should not concern about what is
ckt4, which can be considered a group of package
[root@myhost01 grub]# dpkg -l |grep 3.16.7-ckt4-3
ii linux-compiler-gcc-4.6-x86 3.16.7-ckt4-3~bpo70+1
amd64Compiler for Linux on x86 (meta-package)
ii linux-headers-3.16.0-0.bpo.4-amd64 3.16.7-ckt4-3~bpo70+1
amd64Header files for Linux 3.16.0-0.bpo.4-amd64
ii linux-headers-3.16.0-0.bpo.4-common 3.16.7-ckt4-3~bpo70+1
amd64Common header files for Linux 3.16.0-0.bpo.4
ii linux-image-3.16.0-0.bpo.4-amd64 3.16.7-ckt4-3~bpo70+1
amd64Linux 3.16 for 64-bit Pcs
[root@myhost01 grub]# strace modprobe fuse
execve("/sbin/modprobe", ["modprobe", "fuse"], [/* 18 vars */]) = 0
brk(0) = 0x7fb341646000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7fb340dcb000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=37031, ...}) = 0
mmap(NULL, 37031, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb340dc1000
close(3)= 0
...
open("/sys/module/fuse/initstate", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
stat("/sys/module/fuse", 0x7fffd899d190) = -1 ENOENT (No such file or
directory)
open("/sys/module/fuse/initstate", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
stat("/sys/module/fuse", 0x7fffd899d190) = -1 ENOENT (No such file or
directory)
open("/lib/modules/3.16.0-0.bpo.4-amd64/kernel/fs/fuse/fuse.ko",
O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=164264, ...}) = 0
mmap(NULL, 164264, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fb3405e4000
init_module(0x7fb3405e4000, 164264, "") = -1 EINVAL (Invalid argument)
munmap(0x7fb3405e4000, 164264) = 0
close(3)= 0
write(2, "ERROR: could not insert 'fuse': "..., 49ERROR: could not
insert 'fuse': Invalid argument
) = 49
munmap(0x7fb340d42000, 505175) = 0
munmap(0x7fb340c6f000, 863489) = 0
munmap(0x7fb340bee000, 524731) = 0
munmap(0x7fb340dc9000, 4256)= 0
exit_group(1) = ?
[root@myhost01 ~]# dpkg -l |grep fuse
ii libfuse2:amd64 2.9.0-2+deb7u1amd64Filesystem
in Userspace (library)
Above two commands show the package fuse is not installed, only libfuse2
package is installed. This is the problem!
[root@myhost01 module]# aptitude install fuse
[root@myhost01 module]# dpkg -l |grep fuse
ii fuse 2.9.0-2+deb7u1amd64Filesystem in Userspace
ii libfuse2:amd64 2.9.0-2+deb7u1amd64Filesystem
in Userspace (library)
You must reboot the server to make it work
[root@myhost01 module]# shutdown -r now
[root@myhost01 ~]# modprobe fuse
[root@myhost01 ~]# echo $?
0
[root@myhost01 ~]# lsmod |grep fuse
fuse 87557 1
--
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/551af99a.60...@gameloft.com
Re: installing debian
i have successfully downloaded debian-7.8.0-amd64-netinst.iso but this time it shows 'invalid or corrupt kernel image' how to i go about this? On Tue, Mar 31, 2015 at 10:15 PM, Vincent Omondi wrote: > thanks, i'll try and get back to u guys if i go through any other problem. > > On Tue, Mar 31, 2015 at 9:24 PM, Joe wrote: > >> On Tue, 31 Mar 2015 21:04:06 +0300 >> Vincent Omondi wrote: >> >> > i am using ubuntu 14.04.1, i burned the iso image on to a dvd using >> > K3B, i have used k3b to burn other iso images and successfully >> > booted them, but for debian it cannot boot, i feel like i have left >> > sth or i dont have the correct image for booting,... if i open dvd to >> > which i bured the image, i get the following files, as displayed by >> > the attached image, ... is something missing??? cause in the other >> > dvd i have of bootable iso, they have a boot file or sth of that kind >> >> Sorry, that's the most common reason for ISO problems. I did it myself >> years ago, and I've seen countless posts from others who have. >> >> I can't really help about full OS images, I always use the netinstall CD >> image https://www.debian.org/CD/netinst/ and build a system from there. >> The smallest netinstall is only a few hundred MB, it's worth trying one >> of those to see if the boot problem still exists. To actually build a >> complete system from that does need a reasonable Internet connection, >> but just trying to boot it may offer some hint on why a full DVD is >> having trouble. >> >> As Brian said, not all the DVDs of a set will boot, you would normally >> boot number 1 and install a basic system from that, then install any >> further software you want from the other DVDs. >> >> Best of luck. >> >> -- >> Joe >> > >
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
On Tue, 31 Mar 2015 10:50:03 +0200 Lisi Reisz wrote: > You're not going to get it. The whole thing was an April Fool joke released > early. It will live in memory like the spaghetti trees. Those were the days. They were singing while they harvested the spaghetti too. This report came at the end of a serious current events program called "Panorama" (This was mercifully before the BBC had to say 'on-the-ground' before every report) In the 1970's I was reading The Times while flying to Houston from Heathrow. I had forgotten it was April 1st: there was an article about an amazing discovery whilst experimenting on animals. One of the procedures had inadvertently miniaturized some of the test subjects. This began a line of inquiry that led to experiments on human volunteers. These tests concluded startling additional revelations about how anything within the process chamber was scaled down while retaining its original proportions. During the government's subsequent debate over state secrets there was a leak to the press that was to have a profound impact on the transportation industry, among others. The prospect of thousands of passengers and their luggage shrunk to the size of gelatin capsules and transported in aeroplanes across the globe at a fraction of the current cost, was very exciting to some. It was said that once a passenger arrived at their destination the 'process' would be reversed within a similar chamber with they and their possessions returned to their original size. The Times quoted a statement by Sir Freddie Laker that preparations were well advanced toward Laker Airways offering special flights to accommodate this novel method of travel. There were reports, as yet unsubstantiated, that some volunteers were not able to be returned to their original sizes but these setbacks were not considered to be a major concern to the current plans moving forward. -- CK pgp9BIAmytOqO.pgp Description: OpenPGP digital signature
Re: installing debian
On Tuesday 31 March 2015 22:31:32 Vincent Omondi wrote: > i have successfully downloaded debian-7.8.0-amd64-netinst.iso but this time > it shows 'invalid or corrupt kernel image' how to i go about this? Download it again. It should be alright. Did you md5sum or shasum check your download? Lisi > On Tue, Mar 31, 2015 at 10:15 PM, Vincent Omondi wrote: > > thanks, i'll try and get back to u guys if i go through any other > > problem. > > > > On Tue, Mar 31, 2015 at 9:24 PM, Joe wrote: > >> On Tue, 31 Mar 2015 21:04:06 +0300 > >> > >> Vincent Omondi wrote: > >> > i am using ubuntu 14.04.1, i burned the iso image on to a dvd using > >> > K3B, i have used k3b to burn other iso images and successfully > >> > booted them, but for debian it cannot boot, i feel like i have left > >> > sth or i dont have the correct image for booting,... if i open dvd to > >> > which i bured the image, i get the following files, as displayed by > >> > the attached image, ... is something missing??? cause in the other > >> > dvd i have of bootable iso, they have a boot file or sth of that kind > >> > >> Sorry, that's the most common reason for ISO problems. I did it myself > >> years ago, and I've seen countless posts from others who have. > >> > >> I can't really help about full OS images, I always use the netinstall CD > >> image https://www.debian.org/CD/netinst/ and build a system from there. > >> The smallest netinstall is only a few hundred MB, it's worth trying one > >> of those to see if the boot problem still exists. To actually build a > >> complete system from that does need a reasonable Internet connection, > >> but just trying to boot it may offer some hint on why a full DVD is > >> having trouble. > >> > >> As Brian said, not all the DVDs of a set will boot, you would normally > >> boot number 1 and install a basic system from that, then install any > >> further software you want from the other DVDs. > >> > >> Best of luck. > >> > >> -- > >> Joe -- 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/201503312253.19174.lisi.re...@gmail.com
Re: Upgrading guidance for Cedarview driver in Debian 6 - 2.6.32 Kernel
Quoting venkat (venka...@vortexindia.co.in): > Primary intent : To control connected HDMI and CRT monitors individually. > > We use VESA as display driver for connected display(Single display). > Now, we are trying to extend and use dual display as said (HDMI and > CRT). > We configured it using BIOS and see the display output in connected > screen (HDMI and CRT). > > Interestingly, we notice that XRANDR does not reflect any info on > connected devices. Is updating kernel the only way to solve this?? > or is there some configuration error on my side. Have you tried running Xorg -configure as root, which will write xorg.conf.new into the current directory. That should at least tell you what's being seen by the X server. If what you posted is exactly that, then it doesn't look very hopeful. 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/20150331224134.gb15...@alum.home
Making initramfs agree with rootfs about time zone
I have a dual-boot Win7/Debian jessie system. Because Windows doesn't deal gracefully with handling the hardware time-of-day clock the proper way (hwclock set to GMT, all TZ handling in software), this means that the hwclock changes for daylight savings time. The Debian installation itself copes fine with this, but the initramfs configuration appears to not account for it, resulting in a complaint about timestamps from systemd-fsck every time I boot Debian (which I may well do 2-3 times a day because of things like "leaving the house" and "switching to Windows to play Wine-unfriendly video games"). Is there a convenient way in Debian jessie to make the initramfs be configured with the same idea of the hwclock's behaviour as the configuration on my hard drive, so that I stop getting these annoying-but-not-obviously-harmful messages? -- 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/551b2626.5030...@zen.co.uk
Debian Jessie crashes
http://lockie.ca/crashes/20150328_142159_small.jpg During browsing the web. http://lockie.ca/crashes/20150331_191601_small.jpg -- 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/551b2fea.80...@lockie.ca
Re: Making initramfs agree with rootfs about time zone
It's an open bug in Debian Jessie: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767040 Until the bug is fixed you can create the file /etc/e2fsck.conf containing > [options] > broken_system_clock=1 Janis Am 01.04.2015 um 00:56 schrieb Martin Read: > I have a dual-boot Win7/Debian jessie system. Because Windows doesn't > deal gracefully with handling the hardware time-of-day clock the proper > way (hwclock set to GMT, all TZ handling in software), this means that > the hwclock changes for daylight savings time. > > The Debian installation itself copes fine with this, but the initramfs > configuration appears to not account for it, resulting in a complaint > about timestamps from systemd-fsck every time I boot Debian (which I may > well do 2-3 times a day because of things like "leaving the house" and > "switching to Windows to play Wine-unfriendly video games"). > > Is there a convenient way in Debian jessie to make the initramfs be > configured with the same idea of the hwclock's behaviour as the > configuration on my hard drive, so that I stop getting these > annoying-but-not-obviously-harmful messages? > > -- 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/551b307a.5050...@hamme.info
Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?
On 03/29/2015 07:06 AM, Sven Hartge wrote: > ~Stack~ wrote: > >> 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? > > Please provide an example of such an UUID and the way you obtained it. Greetings Sven, So something odd has happened... # blkid |grep sda3 /dev/sda3: PARTUUID="0003efe2-03" /dev/mapper/sda3_crypt: UUID="f4aad427-3462-4dcf-a40d-617e90a7b1cb" TYPE="swap" # grep sda3 /etc/crypttab sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3 /dev/urandom cipher=aes-xts-plain64,size=256,swap That "PARTUUID" is odd because it used to be a UUID...huh...really not sure what happened...but I have a guess (below)... But on my not-yet-updated-to-an-OS-with-systemd boxes they are either configured for keys or use the UUID from blkid and that UUID is what is in /etc/crypttab. In my first email this "UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e" was taken from blkid. Clearly that is no longer the case and would explain why UUID doesn't work. :-) So off I went to read about UUID vs PARTUUID. Short notes: UUID == filesystem PARTUUID == partition Thus, I would want to point to the partition PARTUUID because (as you pointed out to me earlier) the swap filesystem is going to change every time due to urandom and thus the UUID should be changing on every boot...blkid is probably seeing that this is a ever changing swap partition and just returning the PARTUUID for me. But putting that PARTUUID in my /etc/crypttab didn't work and I ended up with the systemd.fsck timing out and not mounting swap. Hrm. Well, I guess the disk-by-id works so I will just use that for now. Thanks again! I have learned a ton about cryptab, swap, UUID/PARTUUID, and the boot process. :-) ~Stack~ signature.asc Description: OpenPGP digital signature
Re: Is this an April Fool joke running early ? (Systemd to fork the kernel)
Apparently I saw the news about the news before the actual new. ;-) http://ostatic.com/blog/systemd-developers-fork-kernel-docker-package-management Later, Seeker -- 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/551b5a36.2060...@comcast.net
Re: e2fsck.conf and ssh_known_hosts: where?
Hi. On Tue, 31 Mar 2015 10:09:44 -0600 Paul E Condon wrote: > While searching in /var to see if I could find e2fsck.conf without > asking I found an empty directory, /var/cache/openssh-known-hosts . > > The Debian wiki has an article about how to use ssh-keyscan to build a > small database of known hosts for use on a LAN. The article says the > file (not directory) of known hosts should placed in /etc/ssh. Is > Debian's plan to move to using /var for a known-hosts DB? or is the > empty directory just some cruft? I think a directory is a better way > than a file, because it is easier to make atomic changes in directory > structure than adding/removing individual lines in a file. Both /var > and /etc are OK as a location, for me. Does the software that > implements known-host checking at ssh-login-time look in both places? > Does it look for both names (hyphens vs. underscores)? /var/cache/openssh-known-hosts is used by [1] as a temporary storage. A conventional known-hosts DB is still residing where it belongs, i.e. $HOME/.ssh/known-hosts and /etc/ssh_known_hosts (and these two are still single files). [1] https://packages.debian.org/jessie/openssh-known-hosts REco -- 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/20150401073305.91eeab79df4e9e5295715...@gmail.com
Re: Debian Jessie crashes
Hi. On Tue, 31 Mar 2015 19:38:18 -0400 James wrote: > http://lockie.ca/crashes/20150328_142159_small.jpg > > During browsing the web. > http://lockie.ca/crashes/20150331_191601_small.jpg Consider using Jessie's kernel, not Wheezy's. If it fails too - fill a bug. Reco -- 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/20150401082112.907bc5fc0f335df52c965...@gmail.com
Re: [solved securely now??] What is the correct way to set encrypted swap with systemd?
On 20150331_1923-0500, ~Stack~ wrote: > On 03/29/2015 07:06 AM, Sven Hartge wrote: > > ~Stack~ wrote: > > > >> 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? > > > > Please provide an example of such an UUID and the way you obtained it. > > Greetings Sven, > > So something odd has happened... > > # blkid |grep sda3 > /dev/sda3: PARTUUID="0003efe2-03" > /dev/mapper/sda3_crypt: UUID="f4aad427-3462-4dcf-a40d-617e90a7b1cb" > TYPE="swap" > > # grep sda3 /etc/crypttab > sda3_crypt /dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_42K5CE0TT-part3 > /dev/urandom cipher=aes-xts-plain64,size=256,swap > > That "PARTUUID" is odd because it used to be a UUID...huh...really not > sure what happened...but I have a guess (below)... > > But on my not-yet-updated-to-an-OS-with-systemd boxes they are either > configured for keys or use the UUID from blkid and that UUID is what is > in /etc/crypttab. In my first email this > "UUID=ef2496cd-ca4d-43aa-8c90-dba084029f6e" was taken from blkid. > Clearly that is no longer the case and would explain why UUID doesn't > work. :-) > > So off I went to read about UUID vs PARTUUID. Short notes: > UUID == filesystem > PARTUUID == partition > > Thus, I would want to point to the partition PARTUUID because (as you > pointed out to me earlier) the swap filesystem is going to change every > time due to urandom and thus the UUID should be changing on every > boot...blkid is probably seeing that this is a ever changing swap > partition and just returning the PARTUUID for me. > > But putting that PARTUUID in my /etc/crypttab didn't work and I ended up > with the systemd.fsck timing out and not mounting swap. Hrm. > > Well, I guess the disk-by-id works so I will just use that for now. ~Stack~, You can also use disk LABEL=. As implemented, the LABEL is actually applied to individual partition. As long as every partition has a different LABEL values there is no ambiguity. You only need to have unique values for partitions that you feel you will be mounting and umounting. Partitions with no LABEL value set never get compared by LABEL value. The system has always insisted on setting a unique UUID value on every partition. Its done that way because of a design decision of Debian developers. But it has a tiny flaw that you can avoid by using LABEL values, which YOU can be sure are unique because you didn't do repeats, whereas UUIDs are randomly generated and there is a tiny, but non-zero chance of repeats for UUIDs. > > Thanks again! I have learned a ton about cryptab, swap, UUID/PARTUUID, > and the boot process. :-) > > ~Stack~ ~Stack~, If I read your message above, you are having trouble understanding how to use the UUID/PARTUUID system for identifying partitions on disks. I suggest that you don't need to use it, and if you don't use it you don't need to understand it. It can be there because it has been put there during the initalization of Debian, and it won't hurt anything until you try to use it and make a mistake in trying to use it. I was once troubled by a similar situation when Debian first started to use UUID, until I realized that for some disks, I had no intention of ever changing the partion structure that was put there initially. For disks that I did have some special use and some ideas about how that special use might change in the future, I put LABEL=... on their partitions and used LABEL= paradigm to identify the partitions. This is what I do with all my external drives. And I put sticker on the outside of the drive enclosure with the LABEL= value written with a ball point pen on it. It is my personal responsibility to myself that I never put the same LABEL= value on two different disks. You can even put a LABEL= value on the root system disk that is always /dev/sda1 during installation. I suggest that you use LABEL=sda1. LABEL= settings can be any string of alphnumeric characters <= sixteen long. As I see it, the only benefit that you the user get from using the UUID/PARTUUID system is that if some Linux user is browsing through the internals of what is written on your disk, he may wonder where you got the software to do that and treat you with a little more respect. Let me assure you, you are not Rodney Dangerfield -- 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/20150401051932.ga31...@big.lan.gnu
