I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
I have two partitions in LVM. They are added in /etc/fstab to mount automatically. But, they are not working. The process to mount partitions seems to be happening before the service /etc/init.d/lvm2 is started. I can get it mounted using "mount -a" command, but not during the boot time. What should I do get it automatically mounted on every boot?
I'm running Debian Etch AMD64, and currently trying to clean up my system in preparation for an upgrade to Lenny. One problem I have is that resolvconf (which is installed) does not start at boot time, but if I start it manually then bring the NIC down and back up, it works OK, with no error/warning messages.
A windows server named SRV is sharing folders for each users in /share/From a Debian computer on network logged with the user session "foo" I can mount the remote directory /share/foo with:smbmount //SRV/share/$LOGNAME /remote_directorythen the prompt ask me for password and when I have gave it the remote directory is mounted correctly.Now I would like to make this at boot time.If I put the same command in the .bashrc, when I boot, the remote directory is not mounted when the session is opened but then if I open a console, it ask me for password and the directory is mounted.This way is not convenient and it would be better if the directory is mounted when the user open his session and using the same password.The point is that every user should have a his own remote directory mounted when the session is opened.
On Debian Etch I used to understand how to change boot kernel parameters with Grub. You could just edit menu.lst.
With the newer Grub in Squeeze I am without a clue! I want to set up a ramdisk, say 128 Megs in size, and add that to my boot parameters so that it is created every time the machine starts. Do I set something in /etc/default/grub ?
I'm trying to stop all boot time messages from appearing -- basically I'd like to have a simple blank screen from grub to xdm.
I tried everything -- used the "quiet" option in grub's config, added dmesg -n 1 to rc.local, changed console=ttySx, set kernel.printk in sysctl.conf to 4 1 1 7, and even eradicated rsyslogd altogether... to no avail. I still see all sorts of messages on my screen.
so as my title implies I like to login to my headless debian box after it reboots yet havent found any info on that. Can someone please tell me of script which I suppose would be used to make vino start as a process right after boot
Running Debian stable. I added the following command to rc.local and made it executable:mount -t cifs -o username=ted,password=computer,uid=mooreted,gid=users "//192.168.1.121/Storage Volume" /mnt/vortexAfter rebooting dmesg throws the following error:
I am running Debian-Squeeze with apache2. However, apache2 doesn't start at boot time, even though there is of course the required script in init.d. I can start it later on using "/etc/init.d/apache2 start". I have checked the configuration with "apachectl configtest" - giving the answer "Syntax ok". How do I get it to start automatically at boot time?
I like to login to my headless debian box after it reboots yet havent found any info on that. Can someone please tell me of script which I suppose would be used to make vino start as a process right after boot.
I'm using Fedora 12 since 2 years lately, I really enjoy this S.O., it's quite robust and wonderful, but a couple of months ago it is really slow to boot up when startup the computer, I've checked everything, but seems to be ok, I had a partition lost arround that date, but recover successfully, it happens when I run gparted that It cannot see partition on my 500 GB disk, but still boots up. When running Mandriva live cd, it can see (?) all partitions on that disk, even with Fedora Dolphin I can access this partitions. What could it be?
you can refer to this ubuntu thread for context, but i'll sum up what i'm trying to do here to spare the reading. basically i want to be able to schedule a filesystem check with automatic repairs at the next boot time. but i'm not sure if this will try to automatically fix errors which is what i want to do. the reason i want to do this is because i experienced a power outage (the machine was not plugged into an UPS) and i want to make sure everything is ok.
my cmos battery is dead , not worrying that much about it but the problem is ubuntu , it has trouble booting thanks to fsck , there is a bug herebut i cant boot , i get the following error # Superblock last mount time is in the futureand i cant boot , i can get it working sometimes , with allot of work , but normaly it just fails !i came to the conclusion that the CMOS time and date keeps reseting and so ubuntu thinks that the last time i booted was in the future (if this makes any sense) and fsck freaks
My usb stick with Debian only loads from the usb hub it's crazy. I just tried putting the usb stick onto a usb3 port in my desktop and also on a usb2 port even the one where the usb hub is connected to and it wont' load!. Same initramfs prompt happens as when connected on the laptop usb ports.
the usb hub has usb2 speeds so is not that the stick is under usb1.1 emulation.
I noticed that when my server boots up, it's network interface on eth0 is always down and I always must run the 'ifup eth0' command in order to get it to work for some reason. I checked my configuration and it looks legit to me...
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
Anyone know why my system is booting with out bringing up my eth0 interface? It's very annoying.
I have configured a RaLink wireless card to connecto to an 802.1x network. I connect by selecting the network, and the i give the credentials(username/password). How do i configure Debian to automatically connect to this network when a session begins?
I've just installed debian sid and see that I've the kernel 2.6.32. I was a bit surprise as on ubuntu I had the 2.6.35 and debian sid is supposed to be more up to date that ubuntu (maybe I'm wrong).So I checked what were the packages available :
mart@mart-laptop:~$ uname -a Linux mart-laptop 2.6.32-5-686-bigmem #1 SMP Sat Oct 30 23:25:58 UTC 2010 i686 GNU/Linux mart@mart-laptop:~$ sudo aptitude search ^linux-image
First of all, my computer is running Debian Jessie. uname -a gives me this output: Code: Select allLinux felix-PC 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
So today I updated my system with aptitude update and aptitude upgrade, and there was few paquages that were updated. Among them was one "linux-image" or "linux-headers". I believe that it is linked to this security update: [URL].... .
During the time aptitude upgrade was running, I was simply surfing on Iceweasel. However, it seems that my system suddenly restarted, without asking me the permission or without notifying me. It really looked like I pressed the restart key, but I actually didn't. My computer battery was full charged and plugged in. So, I do believe that it is my system that rebooted himself after the aptitude upgrade was completed (or even during the upgrade, I don't know).
So my computer restarts, and brings me to GRUB menu: I boot Debian and then I get the usual [ OK ] ***** lines telling that the system boots normally. But this time, I get some errors:
Code: Select all[FAILED] Failed to set up automount Arbitrary Executable file format file system Automount point ... [FAILED] Failed to start load kernel module ... [FAILED] Failed to mount /boot/efi [DEPEND] Dependency failed for Local File Systems
I arrive then in Emergency mode with this message: Code: Select all Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or type Control-D to continue):
I tried systemctl default but it doesn't boot my system normally. I also tried Control-D but it just reprints the same message. And finally I typed journalctl -xb, which gives me a long log file (855 lines) that I do not understand.
I would give this log file, but it seems that my internet connexion is broken (because of the kernel, I mean), even with an Ethernet cable. So I can't connect with ssh to the computer I use at the moment, and I can't either send it to myself by mail. I tried to mount an usb key, but it seems that any key won't be mounted because of a kernel problem.
An obvious solution to my problem may be to come back to an older kernel version. However, only the lasted kernel version (x86_64 Linux 3.16.0-4-amd64) is installed. dpkg --list | grep linux-image gives me indeed:
Code: Select alliF linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u3 amd64 Linux 3.16 for 64-bit PCs ii linux-image-amd64 3.16+63 amd64 Linux for 64-bit PCs (meta-package)
I do not know how to come back to an older kernel, as far as I haven't any internet connection and as far as I seem to not be able to load an usb key.
I have a Insprion 14R (N4010) and when I hibernate it will usually restore without a problem, but maybe 15% of the time it will reboot while loading. I would like to figure why, since I'd rather not lose anything... My swap space is 5.9GB, I have 4GB RAM (video uses 1gb, so I have 3gb usable)