Affichage des articles dont le libellé est ubuntu. Afficher tous les articles
Affichage des articles dont le libellé est ubuntu. Afficher tous les articles

mardi 9 novembre 2021

Linux cleaning tips (systemd, apt/ubuntu, docker)

 (evolutive article where I store what's been useful to me to clean space on linux servers I'm using)

Note : my current servers are running Ubuntu.



OS / SystemD : purge logs bigger than ...

Only keep 10M of each log files handle through syslog

sudo journalctl --vacuum-size 10M


OS / apt : remove remnants

Remove automatically all unused packages Remove automatically installed packages not needed anymore (i.e. packages that were installed as dependencies of packages that have now been removed or aren't requiring this dependency anymore)

apt options :

  •   autoremove - Remove automatically all unused packages
  •   clean - Erase downloaded archive files
  •   autoclean - Erase old downloaded archive files

sudo apt-get clean autoremove autoclean



Docker : remove logs older than ...

Only keep the last 1000h of docker containers logs

sudo docker image prune --all --filter "until=1000h" -f


Docker : remove remnants

Be careful ! If your docker environments are not running they might be deleted by some of the following commands !

Remove unused volumes, containers, images, networks, etc.

sudo docker system prune -f 

sudo docker system prune -a --volumes


vendredi 11 mai 2012

Ubuntu modifications

Nouvelle ressource de modifications à apporter à Ubuntu pour une plus grande facilité d'installation. http://modifyubuntu.com/12.04

samedi 16 avril 2011

Eeepc RT2860 Driver Wifi problem

Solution qui fonction pour moi sous Ubuntu pour installer le driver Ralink sur Ubuntu en remplacement du driver par défaut fourni avec le kernel. Le module incriminé est "rt2860sta.ko", utilisé pour le wifi sur un Asus Eee 1000H.



Ceci est un mini tuto rédigé pour cette machine:

> Linux kilt 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:21 UTC 2011 i686
> GNU/Linux
>
> Ubuntu en distrib 10.04
>
> module wifi rt2860sta


Il faut avoir téléchargé sur les sites appropriés ce paquet :

2010_01_29_RT2860_Linux_STA_v2.3.0.0.tar.bz2
2010_07_16_RT2860_Linux_STA_v2.4.0.0.tar.bz2


Voici les commandes à taper :

lsmod |grep rt

<désactiver le wifi>
sudo rmmod rt2860sta

<décompresser l'archive>
cd <Répertoire créé>
make
cd os/linux/
ls
sudo insmod rt2860sta.ko

<SI insertion réussie : Réactiver le wifi>
<SINON refaire la même avec l'autre tar.bz2>

<tester si ça marche>
<Si ok, pour que ce soit le driver par défaut, copier dans les modules du kernel>
sudo cp rt2860sta.ko /lib/modules/2.6.XXX-generic/kernel/drivers/staging/rt2860/rt2860sta.ko

vendredi 15 avril 2011

Lastest stable version of firefox

Directly from mozilla, have the repository point directly to firefox (found looking for the ubuntu release of firefox 4).

sudo add-apt-repository ppa:mozillateam/firefox-stable
sudo apt-get update && sudo apt-get upgrade

dimanche 10 octobre 2010

(links) For my camera


AVCHD Videos

I've got a Panasonic DMC-ZX3 since a few month and I found a few informations on how to view, convert, etc. the videos it takes. They are in HD and outputed in a strange .MTS files (and some others, I'll write more on that some time later). Regular players can't read those files, and I eventually found some converting tools under linux (I'm using ubuntu)


AVCHD = sudo apt-get install libavcodec-extra-52 winff openshot
http://blog.yann.info/2010/05/16/avchd-pour-les-nuls-et-les-pauvres/





Tethering (using computer as a screen for the camera while shooting)

Meanwhile, I found this website explaining how to use your computer screen for your camera. I didn't test already, but I like the idea.


http://grahambinns.com/blog/2010/04/18/gphoto2-f-spot-win/

dimanche 5 septembre 2010

Nautilus Main Toolbar made compact

Since I've got my Asus eeepc 1000h, I've been looking from time to time for a way to reduce spare space on the different apps. I hence went for ubuntu-notebook-remix and it's customizations, but not everything was included. Noticeably, Nautilus, the default file browser for gnome has a "main toolbar" very space-greedy, and without simple customization ways proposed.


I found this page pointing to some package to customize the toolbar. Look at the screenshots on this page to see the effect. If the link is down, look for the package to install (code is bellow).

"nautilus elementary"

Those commands were copy-pasted from the above link for re-usability :

To install "nautilus-elementary" from it's PPA :

sudo add-apt-repository ppa:am-monkeyd/nautilus-elementary-ppa
sudo apt-get update && sudo apt-get upgrade
nautilus -q #restarts nautilus



To compile nautilus

sudo apt-get install bzr
sudo apt-get build-dep nautilus
bzr branch lp:nautilus-elementary
cd nautilus-elementary/
./configure --prefix=/usr && make
sudo make install

And restart nautilus :

nautilus -q




That's it. Then customize everything to suit your needs via the Tweaks tab you can find via Edit > Preferences menu in Nautilus. To customize the toolbar, simply right click on it.

mercredi 13 janvier 2010

A way to make a usbkey bootable (saved)




SAVED FROM :




How-to: Installing Ubuntu Linux on a usb pendrive


This tutorial will show how-to install Ubuntu on a usb stick. Even though this tutorial uses Ubuntu as its base distribution, you could virtually use any type of Linux liveCD distribution.


Being able to run Linux out of a usb bar is a great way to enjoy the live CD experience (being able to use Linux on any computer you might get by) and the big advantage of being easier to carry around than a CD.


1. Requirements




In order to reproduce this tutorial, you will need a few items such as:



  • a ubuntu liveCD

  • a usb bar of at least 1G

  • a running Linux operating system


Now that you have all this, it is time to prepare you USB bar do host the Ubuntu liveCD files.


2. Setting up the USB disk


2.1. Finding the device




In the first place, you need to plug your usb drive and check under which device it is associated. To find out the device, run:


$ sudo fdisk -l


On my system, the device appears as being /dev/sdb, I will therefore use /dev/sdb as a reference for this tutorial, please replace it accordingly to your system (might be sda, sdc ...).

Once you found your device, you are going to create the partitions.


Using the wrong device name might destroy your system partition, please double check


2.2. Making the partitions


Make sure every of your already mounted partition are unmounted:


$sudo umount /dev/sdb1


and then launch fdisk, a tool to edit partition under linux:


sudo fdisk /dev/sdb


We are going delete all the partition and then create 2 new partition: one fat partition of 750M which will host the files from the live CD iso, and the rest on another partition.


At fdisk prompt type d x where x is the partition number (you can simply type d if you only have one partition), then:




  • n to create a new partition

  • p to make it primary

  • 1 so it is the first primary partition

  • Accept the default or type 1 to start from the first cylinder


  • +750M to make it 750 Meg big

  • a to toggle the partition active for boot

  • 1 to choose the 1 partition

  • t to change the partition type

  • 6 to set it to FAT16



Now we have out first partition set up, let's create the second one:



  • n to create yet again a new partition

  • p to make it primary

  • 2 to be the second partition

  • Accept the default by typing Enter


  • Accept the default to make your partition as big as possible

  • Finally, type w to write the change to your usb pendrive


Partitions are now created, let's format them.


2.3. Formatting the partitions


The first partition is going to be formated as a FAT filesystem of size 16 and we are going to attribute it the label "liveusb".


$ sudo mkfs.vfat -F 16 -n liveusb /dev/sdb1


The second partition is going to be of type ext2 with a blocksize of 4096 bytes and the label casper-rw. Mind that it has to be labeled as casper-rw otherwise the tutorial won't work!.



$ sudo mkfs.ext2 -b 4096 -L casper-rw /dev/sdb2


At this stage, our usb pendrive is ready to host the liveCD image. Now, let's copy the files to the usb bar.





How-to: Installing Ubuntu Linux on a usb pendrive -- page 2


3. Installing Ubuntu on the USB stick


3.1. Mounting Ubuntu liveCd image


In the first place we need to mount our ubuntu iso. Depending if you have the .iso file or the CD, there is 2 different ways of mounting it.


3.1.1. Mounting from the CD


People using Ubuntu or any other user-friendly distro, might just have to insert the cd and it will be mounted automatically. If this is not the case:



$ sudo mount /media/cdrom


should mount it.


3.1.2. Mounting from an .iso image file


We will need to create a temporary directory, let say /tmp/ubuntu-livecd and then mount our iso (I will be using a feisty fawn iso).


$ mkdir /tmp/ubuntu-livecd

$ sudo mount -o loop /path/to/feisty-desktop-i386.iso /tmp/ubuntu-livecd


Once the cd image is ready, it is time to mount the newly created usb bar partitions:



3.2. Mounting the usb bar partitions


Same here, you might be able to get both your partition by simply replugging the usb pendrive, partition might appears as: /media/liveusb and /media/casper-rw. If this is not the case, then you will need to mount them manually:


$ mkdir /tmp/liveusb

$ sudo mount /dev/sdb1 /tmp/liveusb


All the partitions we need are now mounted, let's copy the files.


3.3. Copying the files to the usb bar



Let positionned yourself on the CD image directory (in my case: /tmp/ubuntu-livecd , but it might be /media/cdrom , and copy at the root of your usb first partition:



  • the directories: 'casper', 'disctree', 'dists', 'install', 'pics', 'pool', 'preseed', '.disk'

  • The content of directory 'isolinux'

  • and files 'md5sum.txt', 'README.diskdefines', 'ubuntu.ico'

  • as well as files: 'casper/vmlinuz', 'casper/initrd.gz' and 'install/mt86plus'


$ cd /tmp/ubuntu-livecd

$ sudo cp -rf casper disctree dists install pics pool preseed .disk isolinux/* md5sum.txt README.diskdefines ubuntu.ico casper/vmlinuz casper/initrd.gz install/mt86plus /tmp/liveusb/


It might complain about symbolic links not being able to create, you can ignore this.



Now let's go to the first partition of your usb disk and rename isolinux.cfg to syslinux.cfg:


$ cd /tmp/liveusb

$ sudo mv isolinux.cfg syslinux.cfg


change /tmp/liveusb according to your settings


Edit syslinux.cfg so it looks like:



DEFAULT persistent
GFXBOOT bootlogo
GFXBOOT-BACKGROUND 0xB6875A
APPEND file=preseed/ubuntu.seed boot=casper initrd=initrd.gz ramdisk_size=1048576 root=/dev/ram rw quiet splash --
LABEL persistent
menu label ^Start Ubuntu in persistent mode
kernel vmlinuz
append file=preseed/ubuntu.seed boot=casper persistent initrd=initrd.gz ramdisk_size=1048576 root=/dev/ram rw quiet splash --
LABEL live
menu label ^Start or install Ubuntu
kernel vmlinuz
append file=preseed/ubuntu.seed boot=casper initrd=initrd.gz ramdisk_size=1048576 root=/dev/ram rw quiet splash --
LABEL xforcevesa
menu label Start Ubuntu in safe ^graphics mode
kernel vmlinuz
append file=preseed/ubuntu.seed boot=casper xforcevesa initrd=initrd.gz ramdisk_size=1048576 root=/dev/ram rw quiet splash --
LABEL check
menu label ^Check CD for defects
kernel vmlinuz
append boot=casper integrity-check initrd=initrd.gz ramdisk_size=1048576 root=/dev/ram rw quiet splash --
LABEL memtest
menu label ^Memory test
kernel mt86plus
append -
LABEL hd
menu label ^Boot from first hard disk
localboot 0x80
append -
DISPLAY isolinux.txt
TIMEOUT 300
PROMPT 1
F1 f1.txt
F2 f2.txt
F3 f3.txt
F4 f4.txt
F5 f5.txt
F6 f6.txt
F7 f7.txt
F8 f8.txt
F9 f9.txt
F0 f10.txt

Woof, finally we have our usb disk almost usuable. We have a last thing to do: make the usb bootable.


3.4. Making the usb bar bootable.


in order to make our usb disk bootable, we need to install syslinux and mtools:


$ sudo apt-get install syslinux mtools


And finally unmount /dev/sdb1 and make it bootable:


$ cd


$ sudo umount /tmp/liveusb

$ sudo syslinux -f /dev/sdb1


Here we are :D , reboot, set your BIOS to boot from the usb bar and enjoy Ubuntu linux from a pendrive


4. Troubleshooting


If you are having trouble booting on the usb bar, this might be due to your MBR being corrupted. In order to fix it up, you can use lilo (I installed lilo on my box only for thid purpose).


$ lilo -M /dev/sdb


will fix the MBR on device /dev/sdb





lundi 20 avril 2009

Aptitude, apt & cie. (Mainly for Debian, but Ubuntu works on the same way)

Ce post tourne autour des commandes apt, aptitude et dpkg

Installer une selection de paquets :


D'un côté :
$ dpkg --get-selections > liste-pkg

De l'autre côté :
# dpkg --set-selections < liste-pkg
# apt-get dselect-upgrade


Ressources non officielles de paquets pour Debian





Paquets installés automatiquement (jeux de dépendance)


$ aptitude why python-notify


Update automatique sans interaction humaine



export DEBIAN_FRONTEND=noninteractive
yes '' | apt-get -y -o Dpkg::Options::="--force-confdef" -o
X Dpkg::Options::="--force-confold" dist-upgrade


(originaire de : http://www.ouaza.com/livre/admin-debian/
site web du livre "Cahier de l'admin, sur GNU/Linux «Lenny» " )

Utile également :
https://help.ubuntu.com/community/Repositories/CommandLine

mardi 2 décembre 2008

eee bug: Randomly changing mac-address [SOLVED ?]

Bon, en fait je me retrouve avec un p*** de problème pas bien documenté :
à chaque suspend, ma carte réseau se retrouve avec une nouvelle mac-address.

En soit c'est bien pour quand je suis dans un point d'accès anodin, mais au labo où l'IP est alloué en fonction de la mac-addr enregistrée, cela me pose justement pb.

Bon, reprenons.

Diagnostique :
dans le fichier /etc/udev/rules.fr/70-persistent-net.rules à chaque suspend ou hibernate je me retrouve avec une nouvelle entrée de la forme


# Converted from /etc/iftab on upgrade
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="xx:xx:xx:xx:xx:xx", ATTRS{type}=="1", KERNEL=="eth*", NAME="eth1"


mais ce fichier semble généré par "75-persistent-net-generator.rules".

Il y a des chances que ce soit le driver qui se plante et n'aille pas chercher au bon endroit en mémoire l'adresse MAC, donnant ainsi l'impression de la générer à chaque fois.


TO DO


SOLUTION ??? :: http://ge.ubuntuforums.com/showthread.php?s=4d9cb6139d81046390c9da0ac5f7e48f&t=770173&page=6

Autre solution ?????
http://forum.ubuntu-fr.org/viewtopic.php?id=168719
sudo modprobe -r forcedeth
sudo modprobe forcedeth
sudo /etc/init.d/networking restart
et donner les dernières lignes d'un dmesg après cette manip?






solution



Solution trouvée : remplacer le module atl1e par la version trouvée ici :

ATL1E Linux Driver for Ethernet controller: Attansic Technology Corp. Unknown device 1026 (rev b0)
CAUTION: Do NOT confuse this with the ATL1 Driver (without the "E" at the end)









Copy from : http://jan.ucc.nau.edu/wal2/atheros_attansic.html
in order not to loose it.
########################################################################################

ATL1E Linux Driver for Ethernet controller: Attansic Technology Corp. Unknown device 1026 (rev b0)

CAUTION: Do NOT confuse this with the ATL1 Driver (without the "E" at the end)


Symptoms: On an Asus Eee PC 1000H running Ubuntu 8.04 (Hardy Heron) with the 2.6.24-19-generic kernel


lspci yields:

03:00.0 Ethernet controller: Attansic Technology Corp. Unknown device 1026 (rev b0)

and the wired ethernet is nonfunctional.


In addition to what I've written below, you should also read:


http://ubuntuforums.org/showthread.php?t=770173&page=2



http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492029
 
(In Debian, the module will be included in the 2.6.26 kernel.)


In my case, since I had rebooted the machine many times before building the module (see below for building),
udev had added a bunch of lines for "newly discovered"
ethernet cards with all different MAC addresses,
so I had to edit /etc/udev/rules.d/70-persistent-net.rules and delete ALL lines for ethernet devices
named eth0, eth1, eth2, etc.

(See

http://ubuntuforums.org/showthread.php?p=3869356

but do NOT change
75-persistent-net-generator.rules as that post says).


The following worked for me to build the module on an Asus Eee PC 1000H running Ubuntu 8.04 (Hardy Heron).


Jie Yang at Atheros mailed me the Version 1.0.1.0 driver source,
and I saved it as filename
l1e-linux-v1.0.1.0.tar.gz .

md5sum for the tarball above: d83196e507f9b2bea47514ba97fffd6f
sha1sum for the tarball above: 1f6a1ee6280add6e4c8d2f110ecd176c6f0e9134

Do all of the following as root:

Install the build-essential package: apt-get install build-essential

Make a new directory somewhere named l1e-linux-v1.0.1.0

cd into that new empty directory and tar -zxvf /some/dir/l1e-linux-v1.0.1.0.tar.gz

cd to the "src" directory in the module source tree

KBUILD_NOPEDANTIC=1 make
The above should succeed with no errors or warnings.

KBUILD_NOPEDANTIC=1 make install
Expect a warning like "cannot write to /var/cache/man/cat7/atl1e.7.gz in catman mode".

Edit /etc/modules and add on a line by itself,
atl1e
as the first non-comment line, then reboot.

After rebooting, verify the driver loaded as follows:

$ dmesg|grep Atheros

Atheros(R) AR8121/AR8113/AR8114 PCI-E Ethernet Network Driver - version 1.0.1.0
Copyright (c) 2007 Atheros Corporation.

$ sudo modprobe -l atl1e
/lib/modules/your-kernel-version/kernel/drivers/net/atl1e/atl1e.ko

This driver, atl1e, should NOT
be confused with the atl1 driver (which has a lot of info at http://atl1.sourceforge.net/
but which is not pertinent here).

Until the atl1e kernel driver module is included in the Linux kernel, the above build process
will have to be repeated every time you start running a new kernel.











Some links



Reduire l'utilisation du ventillo :
http://hartvig.de/2008/howto-reduce-fan-noise-level-on-the-eee-pc-900-1000-1000h-part-ii/

Laisser le dd se reposer :
http://doc.ubuntu-fr.org/laptop_mode

Contrôler quelles itf réseau sont ouvertes, lesquelles ne le sont pas :
http://greg.geekmind.org/eee-control/

Plus général :
http://doc.ubuntu-fr.org/asus_eee_pc_1000h

encore plus général :

http://www.netvibes.com/ramvi#Ubuntu_Eee

vendredi 28 novembre 2008

Installation de Ubuntu-eee sur Asus Eee Pc 1000H

Quelques petites remarques


  • partitionnement : j'ai fait le partitionnement à la main, en mode manuel, leur GUI ne faisait pas ce que je voulait ou ne marchait pas bien.

  • compiz : compiz n'a pas l'air de tourner, en tout les 3 modes d'affichage disponible dans Preferences > Appearance > Visual Effects sont :
    1. None

    2. Normal

    3. Extra

    et parmis ceux-là, seul le premier fonctionne (les deux autres ont soit des pb de transparence, soit de résolution, etc. mais ne sont en tout cas pas fonctionnels.



  • BIOS : pour aller dans le bios au démarrage s'il est nécessaire d'activer le boot sur USB, ce sont les touches ESC ou F2 (1 ou 2 fois)





Quelques questions non encore résolues :


  • Comment ajouter un plus grand nombre de bureaux virtuels ?


  • Comment ajouter dans les "places" du menu de gauche des liens ouvrant directement un shell dans les repertoires en question (nautilus c'est pas que je m'en fout mais ... en fait si ) ?


  • Comment modifier les icônes affichées au milieu pour qu'elle soient sous la forme de liste ou au moins d'icônes plus petites ?


  • Comment ajouter d'autres applets dans le 'gnome-panel' présent en haut ?


  • Comment accéder au bureau "en tant que tel", c.a.d. sans l'affichage prenant tout l'écran ? (qui est cela dit bien pratique)



jeudi 27 novembre 2008

Unbuntu-eee sur Asus Eee Pc 1000H

ubuntu-eee. Version d'ubuntu customisée pour les eee. Installée sans soucis (pour l'instant), voir les liens suivant pour plus d'info. Le principal intérêt en première prise en main est le thème qui réduit beaucoup l'utilisation de l'écran, et un fond de desktop incluant reprenant ce qui est généralement dans les trois menus "Applications" "Places" "System" sous gnome.
Pour l'instant (Nov 2008) c'est la version 8.04.1 qui sert toujours de base à ce remix ubuntu.

On notera dans la même veine le projet "Ubuntu Netbook Remix"
(description du projet ici)
un autre fork de ubuntu : eeeXUbuntu (à base de XUbuntu).


Ubuntu-eee : usb key bootable, à la main. Leur soft faisant cela en mode feignant ne marchait pas, alors je suis passé par là. Fonctionnement nickel de la clef.



Ubuntu sur un asus Eee PC 1000H : installation de Ubuntu Hardy (non modifiée) et résolution de qq pbs.



Forum Ubuntu, page sur ubuntu eee et sur le eee 1000h




Au final la machine marche bien après installation.



Son ok,
wifi ok,
ethernet ok,
Xwindows ok,
"accélérateurs" clavier ok,
suspend (ok ; il râle mais pas encore identifié le pb. pas apparent en tout cas),
bluetooth : non testé
...


Remarque :
Installé en double boot en redimensionnant la partition windows xp, mais pas encore testé si elle tourne toujours.



lundi 27 octobre 2008

non-root mount for external usb ext3 hard drive

J'ai récemment acquis un disque dur externe USB 2.5", que j'ai formaté en ext3.

Mauvaise surprise à l'auto-détection, il est par défaut (contrairement aux clefs usb en FAT32) mis en lecture seule pour les utilisateurs lambdas, et uniquement en lecture-écriture pour root.

Lors du formatage utilisation de :


sudo fdisk /dev/sdb1
sudo mkfs.ext3 /dev/sdb1
sudo e2label /dev/sdb1 {{snip label}}




Pour modifier le mode de montage et mettre ça dans fstab, j'ai eu recours à la commande vol_id pour trouver les paramètres.


# vol_id /dev/sdb1
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID={{snip}}
ID_FS_UUID_ENC={{snip}}
ID_FS_LABEL={{snip label}}
ID_FS_LABEL_ENC={{snip}}
ID_FS_LABEL_SAFE={{snip}}



J'ajoute alors dans /etc/fstab la ligne suivante :

LABEL={{snip label}} /media/{{snip mount point}} ext3 user,auto 0 0



Ca à l'air de marcher comme il faut !!





VOL_ID(8) vol_id VOL_ID(8)

NAME
vol_id - probe filesystem type and read label and uuid

SYNOPSIS
vol_id [--export] [--type] [--label] [--label-raw] [--uuid]
[--skip-raid] [--probe-all] [--help] [device]

DESCRIPTION
vol_id is usually called from a udev rule, to provide udev with the
filesystem type, the label and the uuid of a volume. It supports most
of the common filesystem formats and detects various raid setups to
prevent the recognition of raid members as a volume with a filesystem.

vendredi 10 octobre 2008

Medibuntu packages

From : Medibuntu
Medibuntu (Multimedia, Entertainment & Distractions In Ubuntu) is a repository of packages that cannot be included into the Ubuntu distribution for legal reasons (copyright, license, patent, etc).

Medibuntu is a packaging project dedicated to distributing software that cannot be included in Ubuntu for various reasons, related to geographical variations in legislation regarding intellectual property, security and other issues [...]




From : Ubuntu Forums : Comprehensive Multimedia & Video Howto

sudo wget http://www.medibuntu.org/sources.list.d/hardy.list -O /etc/apt/sources.list.d/medibuntu.list

wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key add - && sudo apt-get update

vendredi 29 août 2008

mount iso Ubuntu and NetBSD

Ubuntu way


$ sudo mkdir /media/iso
$ sudo mount -t iso9660 netbsd/i386cd-4.0.iso /media/iso -o loop
$ ls -la /media/iso/


NetBSD way


$ su
# vnconfig -c vnd0 /home/mark/i386cd-3.0.1.iso
# mount_cd9660 /dev/vnd0d /image/

(from : http://wiki.netbsd.se/How_to_install_NetBSD_from_an_USB_Memory_Stick )

Ubuntu /proc et usb

Par défaut sous ubuntu il semble que les périph usb ne soient pas montés dans /proc.


# mount -t usbfs /dev/bus/usb /proc/bus/usb/



sources :
http://ubuntuforums.org/showthread.php?t=622964
http://blog.linuxoss.com/2006/05/running-vmware-workstation-55-on-suse-101/

mercredi 5 décembre 2007

Fonte moche Firefox sous ubuntu gutsy

Quand c'est moche comme ça :



Une seule solution :

sudo apt-get remove msttcorefonts


:-)

Tags : Fonte bizarre, Fonte moche, ms true type, ubuntu gutsy firefox

vendredi 18 mai 2007

man 2

Sous feisty fawn (ubuntu) les man pages de la section 2 ("system calls") sont dans le paquet
manpages-dev
ca peux servir... ;-)