Bug#640677: installation-reports: Default user "not in the sudoerfs file" after standard install
I'd be happy to help. I could volunteer to make suggestions about reorganizing the website to make it easier for new people to find what they need. And I'd be more than happy to go through the installer and make recommendations as to which steps could be explained a little better, which gave me trouble, etc. Also, this bug should be fixed in the stable repo asap if it hasn't already: http://crunchbanglinux.org/forums/topic/14634 (see last post). It's an easy fix, just one line of code. That gave me much trouble after installing + full update / upgrade of the stable, when trying attempting to switch to testing repo for Xfce 4.8. On Tue, Sep 6, 2011 at 12:04 PM, Christian PERRIER wrote: > Quoting Lennart Sorensen (lsore...@csclub.uwaterloo.ca): > >> As for WEP versus WPA, no idea. I have only ever done installs using >> wired ethernet. Wifi is too flacky for me to trust for an installation >> where a network outage could make you have to start over. > > > WPA is activated (but not yet widely tested) in the installer for the > next Debian version, not in the stable installer. > > Not commenting about people giving us lessons about "hey this is > 2011", except the usual comment: patches welcome. We are well aware > that the stable D-I has no WPA support...just because nobody pushed > this to its end during the development of D-I for squeeze. We're not > magicians: features are not implemented just because someone wishes > them. > > > Another comment about the "user rights" part of this installation > report: "man su". Using "sudo" is not the default behaviour for > administrative access on *nix machines. It is indeed possible if the root > account is indeed deactivated, just like Lennart mentioned. It is also > possible to choose this behaviour in expert installs. > > > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKbjL4Vv8iksNYv1vc9cveyfgzztwqgcslgwui+66a+h...@mail.gmail.com
Upcoming Point Releases
Hi, we finally got target dates for the next point releases of both Lenny and Squeeze. Lenny should get 5.0.9 on October 1st; Squeeze will follow on October 8th with 6.0.3. NEW for Lenny will be closed on the weekend of September 24th; NEW for Squeeze on the weekend of October 1st. The upload of debian-installer for Lenny should happen on the closing weekend at the latest; the middle of week 38 would be appreciated, so that we have everything together on the 24th. For Squeeze it would be cool to have the kernel in for testing end of next week (16/17th). The d-i upload should be there the middle of week 39, October 1st at the latest. base-files can be uploaded now, as it will be held in NEW until closing time anyway. Kind regards and thanks for your efforts Philipp Kern signature.asc Description: Digital signature
Bug#640677: installation-reports: Default user "not in the sudoerfs file" after standard install
dryphi writes: > Yes that package is installed. Is that good or bad? If it is installed it will try to use kexec to reboot the system. This does not work on all computers. Remove the package and try again? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84zkigkxsj@sauna.l.org
Bug#549373: Netinstall from USB-stick fails due to kernel mismatch
I faced the same bug today when using a netinstall of squeeze on amd64. I think the severity of this bug should be increased. Johan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cajop35kohxm0bmsgf6r4klunhjy55hvywkbzs8nkzjkbv7b...@mail.gmail.com
Bug#529343: debian-installer: physical volume for encryption: doesnt care if already encrypted and kills data
On Tue, May 19, 2009 at 07:02:42AM +0200, Christian Perrier wrote:
> Quoting Tobias Winter (tob...@linuxdingsda.de):
> > When having to reinstall a system with an encrypted root-partition, the
> > installer gives no means to
> > reuse a physical colume for encryption which has already been set up in a
> > previous install.
>
> Already reported as #451535. given the current lack of manpower
> working on partman-crypto, I doubt this is fixed unless someone comes
> up with a patch.
Here's a first pass at this. What do people think?
The one thing I don't think I've got right yet is writing out
/etc/crypttab at the end of installation. This needs a bit more work to
write out the correct files in the partman device directory without
causing partman to reinitialise the encrypted volume.
* Add an "Activate existing encrypted volumes" option to the
partman-crypto main menu. If selected, this searches for existing
volumes, and for each one prompts for its passphrase and attempts to
open it; it then returns directly to the partitioning menu
(closes: #529343, LP: #420080).
=== modified file 'choose_partition/crypto/do_option'
--- choose_partition/crypto/do_option 2009-11-10 14:20:25 +
+++ choose_partition/crypto/do_option 2011-09-07 14:18:17 +
@@ -12,6 +12,113 @@
. /lib/partman/lib/crypto-base.sh
+find_encrypted_partitions () {
+ local ret dev num id size type fs path name
+
+ ret=1
+ for dev in $DEVICES/*; do
+ [ -d "$dev" ] || continue
+ cd "$dev"
+
+ open_dialog PARTITIONS
+ while { read_line num id size type fs path name; [ "$id" ]; };
do
+ [ "$ret" = 1 ] || continue
+ [ "$fs" != free ] || continue
+ if cryptsetup isLuks "$path" 2>/dev/null; then
+ ret=0
+ fi
+ done
+ close_dialog
+
+ if [ "$ret" = 0 ]; then
+ return 0
+ fi
+ done
+
+ return 1
+}
+
+get_passphrase () {
+ db_set partman-crypto/passphrase-existing ""
+ db_fset partman-crypto/passphrase-existing seen false
+ db_subst partman-crypto/passphrase-existing DEVICE "$1"
+ db_input critical partman-crypto/passphrase-existing
+
+ db_go || return 1
+
+ db_get partman-crypto/passphrase-existing || RET=''
+ echo -n "$RET"
+}
+
+do_cryptsetup () {
+ local id path cryptdev pass
+
+ id="$1"
+ path="$2"
+ cipher="$(cryptsetup luksDump "$path" |
+ sed -n '/^Cipher name:/s/.*[[:space:]]//p')"
+ if [ "$cipher" ]; then
+ crypto_load_modules dm-crypt "$cipher"
+ fi
+
+ cryptdev="${path##*/}_crypt"
+ if ! cryptsetup status "$cryptdev" >/dev/null 2>&1; then
+ while :; do
+ pass="$(get_passphrase "$path")" || return 1
+ if [ -z "$pass" ]; then
+ return 1
+ fi
+ echo -n "$pass" | log-output -t partman-crypto \
+ cryptsetup -d - luksOpen "$path" "$cryptdev" \
+ && break
+ done
+
+ echo "$cryptdev" >"$id/crypt_active"
+ db_subst partman-crypto/text/in_use DEV "${cryptdev##*/}"
+ db_metaget partman-crypto/text/in_use description
+ partman_lock_unit "$(mapdevfs "$path")" "$RET"
+ fi
+}
+
+do_activate () {
+ local dev partitions num id size type fs path name part
+
+ for dev in $DEVICES/*; do
+ [ -d "$dev" ] || continue
+ cd "$dev"
+
+ partitions=
+ open_dialog PARTITIONS
+ while { read_line num id size type fs path name; [ "$id" ]; };
do
+ [ "$fs" != free ] || continue
+ partitions="$partitions $id,$path"
+ done
+ close_dialog
+
+ for part in $partitions; do
+ id="${part%%,*}"
+ path="${part#*,}"
+
+ if cryptsetup isLuks "$path" 2>/dev/null; then
+ do_cryptsetup "$id" "$path" || continue
+ fi
+ done
+ done
+
+ # Encrypted devices as configured by d-i usually contain LVM PVs
+ export LVM_SUPPRESS_FD_WARNINGS=1
+ log-output -t partman-crypto pvscan
+ log-output -t partman-crypto vgscan
+ log-output -t partman-crypto vgchange -a y
+
+ # Tell partman to detect filesystems again.
+ rm -f /var/lib/partman/filesystems_detected
+
+ stop_parted_server
+ restart_partman
+ exit 0
+}
+
do_create () {
local parts line pv output vg pathmap
parts=""
@@ -89,10 +196,25 @@ confirm_changes partman-crypto || exit 0
com
Bug#640677: (forw) Re: Bug#640677: installation-reports: Default user "not in the sudoerfs file" after standard install
On Wed, Sep 07, 2011 at 05:53:30AM +0200, Christian PERRIER wrote: > Got it, thanks. > I was unaware of the dichotomy between distributions in regards to the > use of sudo / su. This was my first experience with Debian. > I got the machine running and am currently attempting to upgrade to > Xfce 4.8. I installed Synaptic and let it run; looking forward to > seeing where it is when I return home later today. I am not personally a fan of synaptic. I prefer apt-get from the command line, but aptitude is certainly more powerful. I also don't do upgrades from inside X since libc likes restarting kdm which kills the session (gdm at least is smarter and just signals to restart on the next logout which is a much saner design). > Sorry if my report seemed accusatory. I spent several days trying to > complete the install and was becoming increasingly frustrated. > Documentation is lacking; that is to say, it does exist, but it's > difficult to identify the document(s) that pertain to you, and each > document is so detailed that it takes far too much time to sort > through to find what you need. It's both quicker and easier to learn > by trial-and-error or simply ask someone "hey, what's the command for > this?". I do Google for answers every chance I get and read or skim > through documentation, but often my questions are not answered. Linux in a nutshell is pretty universal. Lots of good commands in there. > For example: I know it may seem asinine, but is there a document > somewhere on the debian.net site that says "use 'su' and not 'sudo" > following the install"?? This simple bit of information would have > helped considerably, especially for a user coming from Ubuntu. How did you even know sudo existed? Besides nothing prevents you from loging in as root directly on the console. That is the traditional method to be root. su is handy, sudo just another way to manage it. Options: login as root ssh root@localhost (if ssh server is installed) su - (better than just su since the - makes the PATH and other environment correct for root) sudo (if you feel like configuring it) I think gnome and kde both have 'launch a root shell' commands too. > Aside from the difficulty with networking, the rest of the install was > relatively straight-forward. The descriptions at each step of the > Debian installer were sufficient, although some were a bit brief. It > was much easier to install via LAN cable, and I'd say that part of the > installer needs a little work (I could not get WEP to work either), > but otherwise I didn't have any trouble with the installer. I think part of the problem is that very few people in the past ever wanted to install over wifi, so that part of the installer didn't get much work. Go back a number of years and PPPoE users had the same complaints. I think that works now, not sure. > In summary, a _brief_, plainly labeled how-to somewhere that contained > the following would have made everything run much more smoothly for > me: > 1. Pointed to the "unofficial" / non-free ISO / IMG / installer / > whatever (I have clicked around on the site and I still cannot find > it, someone emailed me a link). That one is rather hard to find. Of course since it is not official, the official docs don't seem to want to talk about it. > 2. Said to use a wired connection due to the lackluster portion of the > installer. > 3. Explained that Debian prefers not to use 'sudo' and to use 'su' instead. Not sure why such a detail is relevant. I have no idea why a new user would even know what sudo is. If you know what sudo is it is rather hard to believe you didn't know about su first, but perhaps I have used *nix for too long to understand that. > 4. Listed the code for the testing source "deb" links, and the best > way to add them. > Honestly that could all be put into 1/4 of a word-document, haha. To some extent, you probably should be using testing if you don't already know how to configure apt and find packages. It does occationally break and you get to pick up the pices yourself so you better have an idea how to do so. > I hear you about offering to help rather than complaining. Again, I > wasn't trying to complain, but rather point out areas of difficulty > for me that might be used to improve the process for other users. I'd > love to help if I could but I'm currently in med school and do not > have much free time. Is there anything I could offer to do? I'm > somewhat new to *nix but I am a quick learner. Documentation can always be improved, although there is a fine line between so much information that is mostly useless to all but a few people and impossible to find what you need versus not enough details for anyone. This doesn't mean there couldn't be a collection of howto's on how debian stuff is done. I wonder if the debian wiki has any of that. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact
Imprimerie SENPQ - Vous avez des projets d'impression de documents
Cette newsletter vous a été envoyée au format graphique HTML. Si vous lisez cette version, alors votre logiciel de messagerie préfère les e-mails au format texte. Vous pouvez lire la version originale en ligne: http://ymlp129.com/zAPBFZ Bonjour, Si vous avez des projets d'impression de documents prochainement, n'hésitez pas à me contacter pour une éventuelle consultation de prix par e-mail. Nos coordonnées : Imprimerie SENPQ 35, rue Victor Hugo 93500 Pantin Richard Pasquet Téléphone : 01 48 10 86 75 Fax : 01 48 10 86 79 e-mail : richard.pasq...@senpq.fr Bien à vous. _ Désinscription / Changer d'adresse e-mail: http://ymlp129.com/u.php?id=geqqsqmgsgjbhbeguqs Powered par YourMailingListProvider
Bug#640789: Crash on folder name with spaces
Package: iso-scan Version: 1.36 Severity: normal This bug was originally reported in https://bugs.launchpad.net/ubuntu/+source/iso-scan/+bug/838720 by Sylvain Dansereau. It seems that an unescaped $dir in debian/iso-scan.postinst makes iso-scan exit while searching for iso images, if a folder name contains spaces. line 165: isolist=$(find $dir $opt -name "*.iso" -o -name "*.ISO" 2>/dev/null) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGoORu5i=tbpbNbqJF=ywxyvmfhegd8mrtqrg80ivhg7ob7...@mail.gmail.com
