Re: Running an application on a new VT
Hello, On 2019-09-16 13:53, Christoph Pleger wrote: I am using the program openvt to run another program. openvt is used to open a new virtual terminal and then run the given program on the new VT. In my case, I want to start a KDE Plasma session on the new VT. Unfortunately, this did not work as expected: After entering the command 'openvt -s -w -- dbus-run-session startplasmacompositor', the KDE session did not start on the new VT, but on tty1, from where I had entered the openvt command. Then, I tried with 'openvt -s -w -- /bin/bash', but though this ran bash on a new virtual terminal, entering 'dbus-run-session startplasmacompositor' on the new VT caused a switch back to tty1 and again, the desktop session started there. Does anybody know why not the new VT is used for the desktop session and how that behaviour can be changed? This is totally crazy: Even when I omit the -w option to openvt, so that I can log out from tty1, then switch to the new VT and enter 'dbus-run-session startplasmacompositor' there, the KDE session starts on tty1, though of course logging out from /dev/tty1 changed its owner to root. So, how can a process with real UID, effective UID and saved UID (I checked that) change the ownership of a device that was owned by root? Still nobody who has an idea what is going on here with the virtual terminals? Regards Christoph
Permission problems - though all three UIDs are 0
Hello, I want to ask for the possible reasons why a program, called from another program with setuid-root file permissions and an additional setreuid(0,0) to also set the real uid to 0, still gets an "Operation not permitted" error. In my case, I execve lvcreate from the setuid-root binary. This works well when I use my program as a non-root user from the command line, but I want to call it is a non-root user from pam_exec PAM module and with that lvcreate fails. Regards Christoph PS: Please, no discussion about possible security holes in setuid-programs here
Re: PATA-disk named sda
Hello, > > In the newest Ubuntu Release, my PATA-disk is called sda instead of > > hda. Is that a general feature in newer kernel versions or is it a > > special feature in Ubuntu? > > General. SATA and now PATA drives map onto the /dev/sd range as do > SCSI, USB etc It seems to be not that simple, at least not if both the old IDE interface and the new libata interface are enabled as modules: In my Ubuntu system, I created two kernel packages (from the same kernel source and with the same configuration) and installed them. Afterwards, I re-created the initial ramdisks, one with the Ubuntu feisty utilities and one with Debian etch utilities. So, I had the same kernel with different ramdisks. With the Ubuntu ramdisk, my harddrive was named sda, but with the Debian ramdisk, it was named hda. So, the name of the drive can depend on something which happens in the ramdisk environment. Does anybody know what that is? And is there a kernel command line parameter which restores the old behaviour? And what about hdparm (setting 32bit I/O and multi-sector mode)? Suren wrote that 32bit I/O makes no sense when using DMA. Maybe that's right, but it does not correspond with my experiences. At least, I have the "feeling" that my IDE disks work much faster since I enabled 32bit support (DMA already was on before). Regards Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PATA-disk named sda
Hello, > In recent kernels both PATA and SATA (SCSI too) drives are handled by > libata library. It calls all the drives sd* . If so, what about the use of hdparm then? I could not change parameters like DMA, MultSectIO and 32-Bit support with hdparm. sdparm also did not do that work. Regards Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PATA-disk named sda
Hello, In the newest Ubuntu Release, my PATA-disk is called sda instead of hda. Is that a general feature in newer kernel versions or is it a special feature in Ubuntu? Regards Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Size of kernel modules
Hello, I have a machine here which I installed with Ubuntu 7.04. Immediately after the installation had been finished, I installed the Ubuntu package which contains the Ubuntu-modified sources of the linux kernel. I extracted the resulting tar.bz2-file, copied the configuration of the currently running kernel to .config and created a file localversion-irb which contains the line "-irb" and then called "make menuconfig". In the menu, I changed the CPU type from 586 to Pentium Pro and entered "-686" as the localversion. Finally, I used the Ubuntu tool make-kpkg with option "--initrd" to create a new kernel. The option "--initrd" causes the installation scripts of the kernel package to automatically create an initial ramdisk for the kernel. After the new kernel package had been created, I installed it. After that, I looked into the directory /boot and was very surprised: The initial ramdisk of the new kernel was much larger than the initrd of the old kernel. To find out the cause for this, I investigated how directories /lib/modules/$old and /lib/modules/$new differ. I found out that the filenames are the same, but the size of the files differs very much. I found a module file in the new directory that was almost five times as large as the file with the same name in the old directory. So, my question is the follwing: Is it an expected feature that the file sizes of modules grow so much only because of a different cpu type and a different localversion, or is there probably a bug in my build tools? Regards Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
NFSROOT with NFS Version 3
Hello, I tried to switch an NFSROOT-Environment from NFS version 2 to NFS version 3, but unfortunately my test client machine now hangs every time after booting as soon as some bigger file system activity should occur. I tried Kernel 2.6.14.7 and Kernel 2.6.16.32. The problem did not occur with NFS version 2. Does anybody know the problem and/or a solution? Regards Christoph Pleger - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Swap areas lose their signatures after reboot
Hello,
> swsusp plays with them... Are you using swsusp?
I am not using swsusp.
I found out that as I had alredy guessed the swap signature
("SWAPSPACE2" at address 0xFF6 of the swap partition) has been deleted
after a reboot.
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 10 GB in Opteron machine
Hello, I now could compile the amd64-kernel successfully. I installed it on my machine, rebooted and in the beginning everything seemed fine. But after mounting the root (ext 3) filesystem (or before mounting, I do not know exactly) the machine hangs. The last message I see is: Mounting root filesystem, starting kjournald. What can I do now? Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 10 GB in Opteron machine
Hello, On Fri, 22 Jul 2005 12:39:55 +0200 Jakob Oestergaard <[EMAIL PROTECTED]> wrote: > > 1. Is it possible to compile a 64-bit kernel on a 32-bit machine (or > > at least on a 64-bit machine with 32-bit software) and if yes, how > > can I do that? > > Yes. On Debian Sarge, I have a few wrapper scripts to accomplish it - > all attached to this mail - just untar them in /usr/local/bin on a > standard x86 32-bit Sarge distro. Use 'kmake' instead of 'make' when > you are working with your kernel source (eg. 'kmake menuconfig', > 'kmake all') > > Sarge comes with all the necessary toolchain support to build a 64-bit > kernel. > > It should be equally possible on most other distros of course, I just > haven't felt the urge to go waste my time with them :) I am also using Debian sarge. I extracted the tarfile to /usr/local/bin end executed "kmake menuconfig". Everything seemed fine so far. But a few seconds after starting the compilation (kmake bzImage) I got this error message: In file included from ... include/asm/mpspec.h:6:25: mach_mpspec.h: No such file or directory Hm. I understand why that file cannot be found: It only exists in the asm-i386 directory. But why does the compilation process look for a file that belongs to i386, but not to x86_64? Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 10 GB in Opteron machine
Hello, On Fri, 22 Jul 2005 05:05:40 -0400 Jeff Garzik <[EMAIL PROTECTED]> wrote: > Christoph Pleger wrote: > > At last I found out that setting HIGHMEM support to 64 GB is the > > problem. But is it really not possible to use more than 4GB on an > > Opteron machine? > > Build and boot a 64-bit kernel, not a 32-bit kernel. > > There is no highmem option for the 64-bit kernel, because it doesn't > need one. I have two questions: 1. Is it possible to compile a 64-bit kernel on a 32-bit machine (or at least on a 64-bit machine with 32-bit software) and if yes, how can I do that? 2. All other software on the machine is 32-bit software. Will that software work with a 64-bit kernel? Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
10 GB in Opteron machine
Hello, I had a working kernel configuration for an Opteron machine. Since that configuration was supposed to support many kinds of hardware, it contained many settings that were not optimal for an Opteron machine. So I created a new configuration especially for that machine. But the resulting kernel could not be booted. To find the problem I took the working configuration and changed and it in many small steps and after every change compiled the kernel, installed it and rebooted to see if the kernel still boots. At last I found out that setting HIGHMEM support to 64 GB is the problem. But is it really not possible to use more than 4GB on an Opteron machine? I have set the processor type to Opteron and disabled SMP support. I am using Kernel 2.6.11.12. Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Signing modules in Kernel 2.4
Hello, I found a patch for Kernels 2.6 that ensures kernel integrity by digitally signing kernel modules. Is something similar available for 2.4-Kernels? Kind regards Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
IDE PCI DMA
Hello, I compiled a 2.4.28 kernel with modular IDE support. Running that kernel on a machine and looking into /proc/ide/hda/settings shows that DMA is not used for that disk, although I had chosen "use PCI DMA by default when available". When a kernel with built-in IDE support is run, DMA for hda is activated. Why is it not activated in case of a module? Kind regards Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
FIFO-Scheduling in Kernel 2.2
Hello, I experienced problems in programs which used priorities under FIFO-Scheduling with Kernel 2.2 although these programs worked well with Kernel 2.0. I read in this list that other people had the same problems. Is any solution (a newer kernel version or a special patch) available for that problem? Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
