I followed The Perfect Server - Debian Lenny on howtoforge website. (Just changed some instructions to fit Sqeeze) * I did not install Control Panel, just software like LAMPP & Mail Servers - SMTP(SSL+AUTH) + POP(SSL) + IMAP(SSL).When I installed PHP it installed it with Suhosin Patch, but that patch was giving me a headache with some web scripts that I write for myself. So I decided to compile it for myself. Here is how I done it:
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
When I build the kernel 2.6.30 source, the rpm package is very big and needed or root filesystem 800-900 Mb. I use "make rpm" as described in Configure, Build and Install a Custom Linux Kernel - openSUSE.
I am trying to build a custom kernel but I couldn't. Here are the steps to reproduce it: 1. Set Up an RPM Build Environment as its is explained in [URL] 2. Then follow the instructions in [URL] 3. When I try to install the kernel source rpm I get the following error:
[matias@Centos ~]$ rpm -i [URL warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root . . . warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: unpacking of archive failed on file /home/matias/rpmbuild/SOURCES/linux-2.6.18.tar.bz2;4ba24901: cpio: read
scanning them with Avast! and Malwarebytes Anti-Malware or by running registry cleaners like Ccleaner.However, I think it would be cool to have a Live system that I could boot from my flashdrive that I could have programs installed to do all this with.It would be cool if I could use Puppy Linux, since it loads and runs from RAM, which gives a huge speed boost when compared to running a live version of a distro like Ubuntu, but I don't really know my way around Puppy, or how to make my own "pupplet". Also, from what I could tell, Puppy Linux didn't have a package manager like Pacman or Aptitude.Here's a list of programs I would like to have a Linux alternative to use:-Avast! Anti-virus-Ccleaner (registry cleaner)-Malwarebytes Anti-Malware/Superantispyware (malware/spyware cleaner)-Perhaps also a Defrag program like Defraggle
We have an appliance with image being installed from CD/DVD installation This appliance image is based on CentOS 4.7 kernel/installer/etc. Everything works fine, we ship this product for about 2 years. Recently I had to move it (port everything) to CentOS 5.5 Everything went fine and it works fine except one minor thing )) We can't install it from CD/DVD image yet. Actually it start fine, finds kickstart file, creates partitions correctly, copies install image to harddrive, but fails the next step when it tries to install RPM's
The message we get:
Quote: the file termcap-5.5-1.20060701.1.noarch.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media. Please verify your installation source. If you exit your system will be left in an inconsistent state that will likely require re-installation"
I'm new to linux and recently installed openSUSE 11.1 on my Lenovo Thinkpad SL500. So far it's great... only problem is the hotkeys and brightness control don't work. Digging around online I found this "experimental" driver that purportedly works fine, but I have no idea how to compile, install, or otherwise use it. Here... tetromino's lenovo-sl-laptop at master - GitHub I'm not sure what to do with the makefile and C file provided. For example, what do I do with this instruction...
"To enable the brightness control, load the module with the "control_backlight=1" module parameter (i.e. insmod lenovo-sl-laptop.ko control_backlight=1 )" I know someone on here will be able to explain how to do this in a "computer engineering for chemists" language! I'm comfortable enough working in the terminal with commands, but have found no real straightforward explanation of how to do so (only "programming" experience is MATLAB m file writing).
After troubleshooting the lockup problem on my installation of Lucid, I want to wipe the thing and reinstall. I have an integrated Broadcom wireless chipset that I want to integrate the firmware into the new Lucid install disc, along with Nvidia's 180.06 drivers for my GeForce4 440 Go (yes, it's an old machine). I need to build this from XP though, since my current Lucid install is to the point of unusable.
Is there any good way to do that? With XP builds you can use nLite to slipstream just about anything into a clean XP install, including all available hotfixes, extra drivers and a few applications. Is there a similar program for building Ubuntu installs that can do that as well? Also, if I download a new ISO of Lucid to build from, will it have all the current updates integrated, or it be up to me to do it? Edit: just realized I posted this under the wrong topic.
I just rebuild the kernel for slackware 13, everything works, but root file system which is ext3 is mounted as ext2. Normally I've build ext3, ext4 and so on as modules, not in the kernel... but if I do this, then the kernel mounts the file system as ext2, which is build in the kernel. I also modified rc.modules so I can make sure that ext3,ext4,jbd are loaded, but it doesnt work.
If you can access Suse Studio here is thlink to the buildLFS Host - SUSE GalleryGoogle hasn't been friendly and neither has a search on these forums, I don't know which man to read so a finger in the right dirrection (preferably not the middle) would be nice as far as that goesRight now the yast live installer trips up at %84 while saving the boot loader configuration and displays a popup that says �An error occurred during initrd creation. /sbin/mkinitrd: illegal optionI then press enter to acknowledge the message and the installation continues without a hitch.
When I go to boot up (no other os installed) grub says it cant find the file initrd-2.6.34.7-0.5-defaultIf you boot the live cd again you can mount the boot partition and you�ll find a broken symlink called initrd that islooking for the missing file above.Like I said above, if it an obvious fix, all I need is some direction, I don't mind reading. (been doing that all day)If you need more specifics Id be happy to supply, I'm just not sure whats relevant and don't want to bloat the post.
I recently tossed Ubuntu for Debian Unstable for my personal machines and I'm having trouble building Emerald into a package. I've already configured and installed the package (using the usual ./configure, make, make install) but I wanted to make a deb for future use (for myself and for others). However every time I try to run dpkg-build I get the following error message.
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?
I'm in love with my Opensuse 11.2. Love my KDE 4.4. The only thing I miss from my Ubuntu installation, is the ability to use Boxee. I would be more than willing to compile Boxee from source. I only have 2 problems with that:
1) I don't know where I can find all the build-deps or what they are for that matter to build Boxee.
2) I'm running on a Netbook. Yes, my measly Intel Atom is no fun for compiling and building.
What are my options/what can I do to get Boxee up and running on 11.2? I've tried searching on build service for an RPM, but I think due to legal restrictions, Boxee can't be on there.
looking for LIBEVENT... configure: error: Package requirements (libevent >= 2.0.10) were not met: In order to build transmission 2.21.I need libeventnew version of transmission,I need to build libevent-dev >= 2.0.10 and installed first.But I can't get any information about building development files for libevent.
as I'm advancing in building some nice rpm I finally wanted to install on of my gems also the build was successful the actual install fails with missing dependencies.
Code:
$ rpm --root /home/sascha/rpmbuild/ -i ./RPMS/x86_64/memcached-1.4.1-2.x86_64.rpm error: Failed dependencies: libc.so.6()(64bit) is needed by memcached-1.4.1-2.x86_64 libc.so.6(GLIBC_2.2.5)(64bit) is needed by memcached-1.4.1-2.x86_64
I'm working on a custom Debian "spin" (one customized for personal/work use). I did this once before with an Ubuntu build, but attempting it with Debian has loaded me with a steady flow of walls (everyone loves debugging!). Despite a variety of approaches, none of my images seem to boot. I've tried the following with both SysV and systemd. the search results I find are vague, at best. I'll attempt to categorize and explain this as intelligently as possible.
A variety of ISOs were tried in Virtualbox, so these are the errors they're yielding; I'm currently down on removable media since I loaned my flash disks to a couple students for their finals, so I can't boot that way until Tuesday. I really hope that the error is something that can be identified regardless of whether or not I'm using a virtual environment.
Method 1: This Guide This appealed to me the most at first because I run a stripped-the-hell-down version of Ubuntu on my work laptop. (Wheezy/Haswell yielded unfavorable results, and at the time Jessie's SysV compatibility was undesirable, but I'll probably switch back by the end of the week if possible.) I have a feeling that this guide may simply be obsolete, or maybe I'm just neglecting a crucial step. Here's the output: a lovely kernel panic.
Method 2: refractasnapshot With it properly configured (and with syslinux-utils installed -- head-on-a-stick and fsmithred), I tried two different approaches: the first, I ran it within the chroot environment mentioned above; the second, I created a Virtualbox build and ran it within that. Both yielded the same errors:
For each, I received two complains: about piix_smbus and no valid rapl domains, and the system hangs indefinitely (ie, all night). Following some search results, I blacklisted i2c_piix4 and paevm, then rebuilt the image, and mounted it in VirtualBox. At boot:
Code: Select allEDD: Error 0c00 reading sector 276375 No DEFAULT or UI configuration directive found! boot: _
I been trying all day to compile a kernel i downloaded from http://www.kernel.org/ (2.6.32.8 )Following this help thread viewtopic.php?t=4468.When i invoke make xconfig i'm just kinda lost at that point. Not really sure what to do, so i just save it as is and then compile/install.when i try to boot the kernel, a kernel panic happens saying it can't not mount the root partition.So i am sure i am missing a step with the xconfig part but not sure what.
I'm trying to build my own livecd using the debian live project: [URL]. At the end (/usr/lib/finish-install.d) I want the installler to change some configuration files. The custom user selected during the installation I want to put into a variable:
Code: #!/bin/sh User=$(getent passwd 1000 | sed -e 's/:.*//') if [ "$User" != "user" ] ; then in-target sed -i "s/home/user/home/$User/g" /etc/smb.conf in-target sed -i "s/USER=user/USER=$User/g" /etc/default/sabnzbdplus fi
The script seems to work fine because when I have a look at the configuration files the lines have been modified. However the $User was empty. Anyone of you have some knowledge about debian-live and know how to retrieve the custom user that was entered during the installation?
I have an init script running as a special build user which performs an automated build that fails with (Too many open files).I updated /etc/security/limits to allow the special user more open files, but that didn't work - the init script still isn't allowed more open files.Here's a demonstration of the problem;
Trying to install SW 13.1 (on DVD) on the following system: M/B Intel: DX38BT Processor Intel Core 2 Quad Q6700 - 2.66GHz, 8MB Cache, 1066MHz FSB, Socket 775 Memory Corsair Dual Channel 8192MB PC10600 DDR3 1333MHz Memory (4x2048MB) Graphics Diamond Radeon HD 3850 Video Card - Viper, 512MB GDDR3, PCI Express 2.0 P/S Ultra 1000W
My goal is to install the i386 build on one partition and the 64-bit build on another. I have been away from Linux for a while and am sick to death of Win7, want to come home. :-}
Booted on i386 side of DVD, system freezes after a couple of lines that start with ATA2. Does not respond to 3 finger salute, ctrl-c, nothing. Have to press reset. I have tried both huge.s and hugesmp.s kernels
Booted on 64-bit side, comes up fine. I performed the install, selected for automatic lilo install. Lilo install hung but I was able to reboot. I booted off the 64-bit side again, entered the following: huge.s root=/dev/sde3 rdinit= ro It booted fully to the login prompt but the keyboard does not work, no input.
for a project I am working on, I need the same install configuration on every machine, and I'd like to have all the packages I need on one disc, with none of the ones I don't. I also need to use a non-standard file systems(jffs2,nilfs) as the hardware end of my project works on flash memory, and would like these two FSs to replace the typical magnetic disk based choices.
I've written my custom keyboard layout, where I'm trying to remap the Menu key as Super. The key gets remapped, however Super is not recognized as a modifier key, unlike with a standard layout I've used as a comparison. What puzzles me is that the left Windows key, which I never refer to in my custom layout stops working as well.
Here is the relevant section of my custom layout:
Output of xev command shows the key has been remapped correctly:
After my NVIDIA card died I decided it was time to buy an AMD card again (R9 270X), but I didn't think AMD drivers were such a pain in Linux as people said. Of course, in some distros anyway. On Arch, for example, there's no official release because Arch's developers would have to hold Xorg in order to make a closed-source driver available, because AMD's pace isn't in pair with Linux. So in order to install AMD's drivers on Arch I must rely on some guy's unnoficial repositories, but that isn't the whole problem. Even though I'm cool with adding repos and downgrading Xorg, I'm not cool with it not working for a lot of apps, so that's where I decided to try a few distros. Manjaro is a no-go because it installs Flash as default. openSUSE although is a very good distro, is a complete mess when it comes to repositories, specially multimedia ones. Ubuntu/Mint are also a no-go, Ubuntu because after 12.04 they have a spyware by default, and Mint because it contains non-free stuff by default.
So here I come! I ran Debian in the past for a long time (aside from a breaf period last year) and it was lovely, I could easily set up a custom encrypted install, but now I don't remember how to, and it's killing me. I don't like how the installer doesn't show the partitions size as they actually are, and I don't like how the automated encrypted LVM setup doesn't let me chose the encryption algorithm or the timeframe between each passphrase attempt. That's why I must create my install, and here's what I used to do on Arch (the part that really matters), converted to what I use on Debian:
Code: Select all# modprobe dm-mod
(create one 1GB partition for /boot, unencrypted ; create another big 930 GB formatted as "8e" - LVM - on dev/sda2) Code: Select all# fdisk /dev/sda (chose my ciphers and iter time) Code: Select all# cryptsetup -c twofish-xts-plain64 -y-s 512 --iter-time 5000 luksFormat /dev/sda2 (open the luks container on "sda2_crypt")
[Code].....
After this is done, I go to the "partition disks" page where I select each partition/volume to it's correct destination. I then proceed to installing the base system, configuring apt, and all that. Now, before I install Grub I used to execute the following commands on shell:
Code: Select all # nano /etc/crypttab
I used to put something there, but I don't remember what exactly. It's been a long time since I used Debian for long! But here's what I put there:
On macbook air 6.2, i've installed a Debian jessie mate DE, dual boot using refind. I'm currently fine-tuning it. I've made a script following powertop advice:
I'd like to create my own custom Debian live CD — the idea being to have my own rescue CD with my favorite Debian tools installed. I read about bootcd and was going to give that a try, after creating the ideal system in a qemu virtual machine.
How much exactly can you install on a system so that bootcd can still fit it on a CD? I'm presuming there is some kind of compression involved. When I tried to create my VM, I coudln't get Jessie + LXDE to install onto a 2GB virtual drive (net install) so naturally I'm wondering what I'm going to be able to put on a 700MB CD.
I just installed Debian 8 (loving it so far) and everything its working right except for one thing: The monitor resolution!
I've got a LG 22 inch monitor and it supports up to 1360x768 but the display settings only shows 1024x768 as max resolution. Doing a little research i was able to get the desire resolution (1360x768) through the use of the tool "xrandr". The problem is that the resolution its not permanent and i need to invoke the xrandr script (i wrote a very basic "script" to set the resolution) on every restart or session logout and of course this is annoying. I've tried to use "crontab" to invoke the script on every restart but for some reason did not worked.
So, making more research i saw that apparently the correct way to set the resolution is by making use of "xorg.conf" but didn't quite get how to do....
I'd like to create a custom squeeze kernel. Is it a really bad idea to edit to edit the kernel config file directly instead of using "make config", "make menuconfig" or "make gconfig"? My problem is I missing a search function, for example in "make menuconfig" and cannot find some entries.
I run Debian Squeeze on the powerpc architecture and I'd like to install the newest Iceweasel on it. The Debain Mozilla repo only has binary packages for i386 and amd64 but provides sources.
So I did: apt-get source iceweasel
which resulted in the creation of these files/directories:
the correct way to remove custom kernels? I was trying to install a driver and only got it half way right and I want to wipe the slate clean and try again.Here's the original:Debian GNU/Linux, kernel 2.6.26-2-amd64root(hd0,4)kernel/boot/vmlinuz-2.6.26-2-amd64 root=UUID=64dcc531-f5b0-47e8-99c4-abeecfab9353 ro quietinitrd/boot/initrd.img-2.6.26-2-amd64
